abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: python /usr/share/system-config-printer/system-config-printer.py component: system-config-printer executable: /usr/bin/python global_uuid: 777f1903e70c8357e441d70fe3c7212bbfa6335f kernel: 2.6.33.6-147.fc13.i686 package: system-config-printer-1.2.3-3.fc13 rating: 4 reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created an attachment (id=446976) File: backtrace
*** This bug has been marked as a duplicate of bug 612078 ***
Interesting thing about this backtrace: Both thread 1 and thread 3 are in _cupsStrAlloc(). They've both got there via Connection_getPPDs(). I bet the problem is that CUPS is now compiled with '--disable-threads' due to the recent gnutls problems, which seems to just disable thread safety checking altogether.
(In reply to comment #3) > I bet the problem is that CUPS is now compiled with '--disable-threads' due to > the recent gnutls problems, which seems to just disable thread safety checking > altogether. Exactly. Managed to reproduce with cups-1.4.4-4.fc13.x86_64 but NOT with cups-1.4.4-3.fc13.x86_64 * Thu Jun 24 2010 Tim Waugh <twaugh> 1:1.4.4-4 - Use gnutls again but disable threading (bug #607159) All the duplicates of bug #612078 crash in one of these __strcmp_ssse3 () from /lib64/libc.so.6 __strcmp_ia32 () at ../sysdeps/i386/i686/strcmp.S:40 __strcmp_sse2 () at ../sysdeps/x86_64/strcmp.S:107