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
Created attachment 449746 [details] File: backtrace
What does 'rpm -q cups' say?
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.
"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.
Thread 1 in backtrace seems like bug #607159.
Would be nice to be sure it didn't happen with the supposed fix (cups-1.4.4-10.fc13) in place.
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 ***
[radical@acasa ~]$ rpm -q --last cups cups-1.4.4-10.fc13 Sun 26 Sep 2010 09:55:06 PM EEST
I did not got any mail on the 28th... I only got the one on 13th.
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.