Bug 616295

Summary: [abrt] crash in system-config-printer-1.2.3-3.fc13: in cups_array_find()
Product: [Fedora] Fedora Reporter: Roger Odle <fc10>
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:0a806dda8befb8ca0400f028476b5a36c5a12e20
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-20 09:47:28 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 Roger Odle 2010-07-20 04:44:33 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: I was adding a network connection to an HP Colorjet 2905n printer using the DeskJet protocol.  It is the only connection to the printer (that is to say that there is no USB connection).  I am upgrading from Fedore 12 to Fedora 13.  I do not upgrade the OS in place but do a clean install so there is no residue from FC12 in my configuration.  This printer has been operating with the DeskJet connection since FC10.
component: system-config-printer
executable: /usr/bin/python
global_uuid: 0a806dda8befb8ca0400f028476b5a36c5a12e20
kernel: 2.6.33.6-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. Add network printer and wait for discovery.
2. Select printer
3.
Comment 1 Roger Odle 2010-07-20 04:44:38 UTC 
Created attachment 433062 [details]
File: backtrace
Comment 2 Jiri Popelka 2010-07-20 09:47:28 UTC 
Thanks for the description Roger.
Is it reproducible or did it appear only once ?

*** This bug has been marked as a duplicate of bug 612078 ***
Comment 3 Roger Odle 2010-07-20 23:22:14 UTC 
I only tried twice.  The first time caused the crash reported by abrtd above.  The second time worked normally.  I then added an all-in-one printer that I use as a scanner and that worked normally also.

When the crash occurred, I think that I was trying to enter the IP address of my printer before I noticed that the printer tool had already found it.  This may have confused the tool.