Bug 703890

Summary: [abrt] system-config-printer-1.2.8-1.fc13: gtk_file_system_model_sort: Process /usr/bin/python was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jeremy Bennett <jeremy>
Component: gtk2Assignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: bugs.michael, jpopelka, mclasen, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:b8d31e58d7cf5fc27c68342b057b1f36f575b84a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-06 09:58:56 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 Jeremy Bennett 2011-05-11 14:46:07 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py
component: system-config-printer
crash_function: gtk_file_system_model_sort
executable: /usr/bin/python
kernel: 2.6.34.8-68.fc13.i686.PAE
package: system-config-printer-1.2.8-1.fc13
rating: 4
reason: Process /usr/bin/python was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1305124277
uid: 500

How to reproduce
-----
1.Trying to configure a new Xerox Phaser 6280DN
2. Not sure why this caused the crash, but initially the printer would not work under Linux. I had to install a patch to deal with printing non-standard PS
3.

Comment 1 Jeremy Bennett 2011-05-11 14:46:09 UTC
Created attachment 498307 [details]
File: backtrace

Comment 2 Tim Waugh 2011-05-13 10:47:48 UTC
This is a GTK+ assertion failure:

#4  0x0097380e in IA__g_assertion_message_expr (domain=0x2ea97f7 "Gtk", file=
    0x2ebfdb5 "gtkfilesystemmodel.c", line=746, func=
    0x2ec0044 "gtk_file_system_model_sort", expr=
    0x2ebfe13 "r == n_visible_rows") at gtestutils.c:1329
        s = 0x9f70128 "assertion failed: (r == n_visible_rows)"
#5  0x02c6f13f in gtk_file_system_model_sort (model=<value optimized out>)
    at gtkfilesystemmodel.c:727
        path = <value optimized out>
        i = <value optimized out>
        r = <value optimized out>
        n_visible_rows = <value optimized out>
        data = {model = 0xb2ad8cd0 [GtkFileSystemModel], func = 
    0x2c54bc0 <name_sort_func>, data = 0x9946020, order = 1}
        __PRETTY_FUNCTION__ = "gtk_file_system_model_sort"

Changing component and reassigning.

Comment 3 Bug Zapper 2011-05-30 10:34:43 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Michael Schwendt 2011-06-06 09:58:56 UTC

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