Bug 637577

Summary: [abrt] system-config-printer-1.2.4-1.fc13: __strcmp_sse2: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Gabriel PREDA <gabriel>
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: 13CC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:6a4d9a9479b3676d50a3b46c1eabd229962011f9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-13 15:11:03 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 Gabriel PREDA 2010-09-26 17:10:18 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/python /usr/share/system-config-printer/system-config-printer.py
component: system-config-printer
crash_function: __strcmp_sse2
executable: /usr/bin/python
kernel: 2.6.34.6-54.fc13.x86_64
package: system-config-printer-1.2.4-1.fc13
rating: 3
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285520712
uid: 500
Comment 1 Gabriel PREDA 2010-09-26 17:10:21 UTC 
Created attachment 449746 [details]
File: backtrace
Comment 2 Tim Waugh 2010-09-27 12:10:37 UTC 
What does 'rpm -q cups' say?
Comment 3 Gabriel PREDA 2010-09-27 16:41:34 UTC 
cups-1.4.4-10.fc13.x86_64

I don't know if this is data is relevant anymore because I keep my system up to date.
Comment 4 Tim Waugh 2010-09-27 17:16:10 UTC 
"rpm -q --last cups"
...will tell us when that (fixed) version was installed.  If earlier than the crash, this needs investigation.  If later I think this is probably a duplicate of bug #607159.
Comment 5 Jiri Popelka 2010-09-28 11:33:43 UTC 
Thread 1 in backtrace seems like bug #607159.
Comment 6 Tim Waugh 2010-09-28 11:51:55 UTC 
Would be nice to be sure it didn't happen with the supposed fix (cups-1.4.4-10.fc13) in place.
Comment 7 Jiri Popelka 2010-10-13 15:11:03 UTC 
Reporter's not responding so I think we could close this as duplicate of bug #612078, because the backtrace looks like it.

*** This bug has been marked as a duplicate of bug 612078 ***
Comment 8 Gabriel PREDA 2010-10-13 17:21:06 UTC 
[radical@acasa ~]$ rpm -q --last cups
cups-1.4.4-10.fc13      Sun 26 Sep 2010 09:55:06 PM EEST
Comment 9 Gabriel PREDA 2010-10-13 17:22:22 UTC 
I did not got any mail on the 28th... I only got the one on 13th.
Comment 10 Tim Waugh 2010-10-14 10:26:14 UTC 
Reported:
$ date --utc --date="2010-09-26 13:10:18 EDT"
Sun Sep 26 17:10:18 UTC 2010

CUPS updated:
$ date --utc --date="Sun 26 Sep 2010 09:55:06 PM EEST"
Sun Sep 26 18:55:06 UTC 2010

..so it looks like the fixed CUPS package was installed *after* the crash occurred.  Great, that still gives hope that the root cause was the CUPS threading issue.  Thanks for giving us that information -- sorry, I don't know why you didn't get notified about the Bugzilla comment on the 27th.