|Summary:||[abrt] crash in system-config-printer-1.2.3-3.fc13: in cups_array_find()|
|Product:||[Fedora] Fedora||Reporter:||Dirk Foerster <dirk.foerster>|
|Component:||system-config-printer||Assignee:||Tim Waugh <twaugh>|
|Status:||CLOSED DUPLICATE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2010-07-26 08:55:41 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Dirk Foerster 2010-07-24 09:42:19 UTC
abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: python /usr/share/system-config-printer/system-config-printer.py comment: It was not possible in system-config-printer 1.2.3 to use the already installed driver for hp Deskjet F2420. There was no option to finish setup. component: system-config-printer crash_function: __strcmp_sse2 executable: /usr/bin/python global_uuid: 63a8082513b39d62fd2b58bb3582ab9700d40a94 kernel: 188.8.131.52-147.fc13.x86_64 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 ----- 1.In system-config-printer 1.2.3 go to server=>printer=>new printer. Allow firewall to be configured to search for network printers. 2.Select local hp Deskjet F2420. Allow for driver to be looked up. Message informs driver is already installed. No option to finish setup. Therefore abort and leave setup. 3.In server chose connect. Application crashes.
Comment 2 Jiri Popelka 2010-07-26 08:55:41 UTC
*** This bug has been marked as a duplicate of bug 612078 ***
Comment 3 Dirk Foerster 2010-09-12 13:02:26 UTC
Installed Fedora 13 updates. Added local printer. Message informed driver was already installed. Clicked OK. Another message informed system is looking for driver. Waited until that search was finished and then clicked OK. Found driver was displayed next. Clicked OK. Printer is configured now and prints. Issue solved.
Comment 4 Jiri Popelka 2010-09-13 08:35:04 UTC
Thanks for info, but AFAICT this issue is probably some kind of memory corruption which can occur from time to time.