Bug 570806

Summary: [abrt] crash in system-config-printer-1.1.93-5.fc14: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Horst H. von Brand <vonbrand>
Component: system-config-printerAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:2d0277dc0cb1c0d93521cbe443871ac164530ab8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-03-08 15:49:29 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

Description Horst H. von Brand 2010-03-05 13:26:49 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/share/system-config-printer/applet.py
comment: Just tried to restart cups service
component: system-config-printer
executable: /usr/bin/python
kernel: 2.6.34-0.4.rc0.git2.fc14.x86_64
package: system-config-printer-1.1.93-5.fc14
rating: 3
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Rawhide)

How to reproduce
-----
1. Printer was reported as "not connected" when pŕinting a PDF (but a test page printed OK)
2. service cups restart
3.
Comment 1 Horst H. von Brand 2010-03-05 13:26:51 UTC 
Created attachment 398051 [details]
File: backtrace
Comment 2 Jiri Popelka 2010-03-08 12:26:23 UTC 
The backtrace is not much useful, but (for me) looks similar to the one in bug #571356.
Comment 3 Jiri Popelka 2010-03-08 15:49:29 UTC 

*** This bug has been marked as a duplicate of bug 567386 ***