Bug 689499

Summary: [abrt] system-config-printer-1.2.7-2.fc14: PyGrammar_FindDFA: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: edo <edosurina>
Component: notify-pythonAssignee: Paul W. Frields <stickster>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jpopelka, stickster, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2127da68c771c30c832aaff149986a083ae7ffd7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-12 11:06:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description edo 2011-03-21 16:54:13 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 98167 bytes
cmdline: /usr/bin/python /usr/share/system-config-printer/applet.py
component: system-config-printer
Attached file: coredump, 8699904 bytes
crash_function: PyGrammar_FindDFA
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.x86_64
package: system-config-printer-1.2.7-2.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1300726375
uid: 500

How to reproduce
-----
1.start PC
2.start Gnome session
3.crash

Comment 1 edo 2011-03-21 16:54:16 UTC
Created attachment 486644 [details]
File: backtrace

Comment 2 Tim Waugh 2011-03-22 10:56:03 UTC
This occurred during "import pynotify".  Did it only occur once or can you get it to happen again?

Does it happen when you run this command from a terminal window?:

python -c 'import pynotify'

Comment 3 Paul W. Frields 2011-04-10 23:17:07 UTC
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.