abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: python /usr/share/system-config-printer/system-config-printer.py comment: s-c-p crashed when trying change existing SMB printer component: system-config-printer crash_function: _cupsStrAlloc executable: /usr/bin/python global_uuid: a3d60bea2df07ba931c98013f1e3bc64baa4acbb kernel: 2.6.33.5-124.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) How to reproduce ----- Not sure
Created attachment 430005 [details] File: backtrace
Ahoj Franto, are you able to reproduce it or did it happen only once ? What does 'locale' command show ? Would be great if you can attach output from Printing troubleshooter ? https://fedoraproject.org/wiki/Printing/Debugging#Printing_troubleshooter thanks
Hello Jirko, 2) It happen only once, after I changed in "system-config-printer" for local printer "LJ3030" its destination from "smb://GROUP/PC-HRUSKOVA/HP3030" to "smb://GROUP/PC-HRUSKOVA/LJ3030". Change was successfull, but then when I click on window closing point at upper right area, this apps crashed. 2) of course, locale isn't "zh_CN": # locale LANG=cs_CZ.utf8 LC_CTYPE="cs_CZ.utf8" LC_NUMERIC="cs_CZ.utf8" LC_TIME="cs_CZ.utf8" LC_COLLATE="cs_CZ.utf8" LC_MONETARY="cs_CZ.utf8" LC_MESSAGES="cs_CZ.utf8" LC_PAPER="cs_CZ.utf8" LC_NAME="cs_CZ.utf8" LC_ADDRESS="cs_CZ.utf8" LC_TELEPHONE="cs_CZ.utf8" LC_MEASUREMENT="cs_CZ.utf8" LC_IDENTIFICATION="cs_CZ.utf8" LC_ALL= (both system-wide setting in /etc/sysconfig/i18n and all users settings has this locale) 3) I had this F13 i386 machine fully available this (in Czech rep.) prolonged weekend, now i can access it only remote and with low-bandwidth connection. And unfortunatelly employee which is working at W7 WS where is this printer is at vacation, thus this workstation and printer will be on at next week. And it look as "Printing troubleshooter" need access to this printer. Please tell me if this output is still desired.
(In reply to comment #5) > And it look as "Printing troubleshooter" need access to this printer. Yes, you need to print something to obtain useful info. > Please tell me if this output is still desired. For me it looks like some memory corruption in system-config-printer or cups, so I don't think there would be anything useful in the output. Let's wait for Tim (he's also on vacation at the moment), maybe he'll have some idea what happened.
*** Bug 612494 has been marked as a duplicate of this bug. ***
*** Bug 611199 has been marked as a duplicate of this bug. ***
*** Bug 613895 has been marked as a duplicate of this bug. ***
*** Bug 614970 has been marked as a duplicate of this bug. ***
*** Bug 615518 has been marked as a duplicate of this bug. ***
*** Bug 615726 has been marked as a duplicate of this bug. ***
*** Bug 616295 has been marked as a duplicate of this bug. ***
*** Bug 617827 has been marked as a duplicate of this bug. ***
*** Bug 621049 has been marked as a duplicate of this bug. ***
Package: system-config-printer-1.2.3-3.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Duplicate an existing printer 2. Configure it wrong so it can't connect properly 3. Click "Change" for "Make and Model" 4. Allow the system to search 5) system-config-printer crashed while trying to find the right drivers for a printer it couldn't connected to. Comment ----- I was attempting to search for the proper drivers of a printer that didn't get properly connected
*** Bug 623925 has been marked as a duplicate of this bug. ***
*** Bug 627921 has been marked as a duplicate of this bug. ***
Package: system-config-printer-1.2.3-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. 2. 3.
*** Bug 629394 has been marked as a duplicate of this bug. ***
*** Bug 629592 has been marked as a duplicate of this bug. ***
Package: system-config-printer-1.2.3-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I opened the 'add new printer' dialog 2. selected my usb printer that appeared in the list 3. clicked next/add printer Comment ----- I did notice that I must have selected the print and clicked the next/add printer button before the 'in progress' indicator finished. I tried a second time, but this time I waited till the animation stopped, then it worked successfully.
*** Bug 630819 has been marked as a duplicate of this bug. ***
*** Bug 630916 has been marked as a duplicate of this bug. ***
*** Bug 632440 has been marked as a duplicate of this bug. ***
*** Bug 633182 has been marked as a duplicate of this bug. ***
*** Bug 633345 has been marked as a duplicate of this bug. ***
The root cause of the problem is that there are two threads in malloc at once because CUPS has been compiled without thread-safety checks since cups-1.4.4-4.
*** This bug has been marked as a duplicate of bug 607159 ***
Steps to reproduce: (1) Start s-c-p (2) Press '+Add' button (3) Fill the password if asked (4) In devices select parallel or serial port (5) click 'Forward' button (6) click 'Cancel' button in 'Searching for drivers' dialog (7) go to (5)
*** Bug 637577 has been marked as a duplicate of this bug. ***