Bug 928731

Summary: [abrt] gnome-abrt-0.2.8-1.fc17: directory_problems.py:26:<module>:ImportError: No module named pyinotify
Product: [Fedora] Fedora Reporter: hi
Component: gnome-abrtAssignee: Jakub Filak <jfilak>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: jberan, jfilak
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:991ef13b3db0339f1eda4804293f3dda3d3ad375
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-05-22 19:14:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: core_backtrace
none
File: environ
none
File: smolt_data none

Description hi 2013-03-28 10:25:54 UTC 
Version-Release number of selected component:
gnome-abrt-0.2.8-1.fc17

Additional info:
cmdline:        python /usr/bin/gnome-abrt
executable:     /usr/bin/gnome-abrt
kernel:         3.8.3-103.fc17.i686
uid:            1000
ureports_counter: 1
Comment 1 hi 2013-03-28 10:25:56 UTC 
Created attachment 717582 [details]
File: backtrace
Comment 2 hi 2013-03-28 10:25:59 UTC 
Created attachment 717583 [details]
File: core_backtrace
Comment 3 hi 2013-03-28 10:26:01 UTC 
Created attachment 717584 [details]
File: environ
Comment 4 hi 2013-03-28 10:26:03 UTC 
Created attachment 717585 [details]
File: smolt_data
Comment 5 Jakub Filak 2013-03-28 21:49:24 UTC 
Thank you for the report. Unfortunately, without your help it is impossible to determine what caused the crash. If you have time and can still reproduce the bug, please provide the output of the following commands:

$ rpm -qi python-inotify
$ rpm -qR gnome-abrt | grep python-inotify
$ echo "import pyinotify; print pyinotify.ALL_EVENTS" | python
Comment 6 Jakub Filak 2013-05-22 19:14:19 UTC 
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. 

Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.