Bug 695749 - [abrt] system-config-printer-1.2.7-2.fc14: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Summary: [abrt] system-config-printer-1.2.7-2.fc14: Process /usr/bin/python was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 680063
Alias: None
Product: Fedora
Classification: Fedora
Component: pygtk2
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Colin Walters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:55e2e873f80bdea9a133939ff53...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-12 15:06 UTC by JYundt
Modified: 2012-03-20 18:44 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-20 18:44:56 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (75.06 KB, text/plain)
2011-04-12 15:06 UTC, JYundt 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description JYundt 2011-04-12 15:06:00 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 76858 bytes
cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py
comment: Tried to add a WorkCentre 4150 with a ppd that I downloaded from Xerox's website.
component: system-config-printer
Attached file: coredump, 64376832 bytes
crash_function: gtk_file_system_model_iter_nth_child
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.i686.PAE
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: 1302620332
uid: 500

How to reproduce
-----
1. I was trying to add a WorkCentre 4150 with a ppd downloaded from Xerox's website
2. Crash
3.
Comment 1 JYundt 2011-04-12 15:06:02 UTC 
Created attachment 491513 [details]
File: backtrace
Comment 2 Jiri Popelka 2011-04-13 11:59:00 UTC 
Seems that the crash occurred when gtk.FileChooserButton was hit.
Reassigning to pygtk2.
Comment 3 abrt-bot 2012-03-20 18:44:56 UTC 
Backtrace analysis found this bug to be similar to bug #680063, closing as duplicate.

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 680063 ***
Note You need to log in before you can comment on or make changes to this bug.