Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 205692 - system-config-printer Segfaults FC5 x86_64 (ADD Queue)
Summary: system-config-printer Segfaults FC5 x86_64 (ADD Queue)
Alias: None
Product: Fedora
Classification: Fedora
Component: foomatic
Version: 5
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
Blocks: FC6Target
TreeView+ depends on / blocked
Reported: 2006-09-07 23:40 UTC by cruiseoveride
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-09-08 14:27:38 UTC

Attachments (Terms of Use)

Description cruiseoveride 2006-09-07 23:40:44 UTC
Description of problem:
System-config-printer freezes with segfault when adding a printer

Version-Release number of selected component (if applicable):

How reproducible:
While trying to add a printer
(no other printers exist)

Steps to Reproduce:
Actual results:

[root@server ~]# system-config-printer
*** glibc detected *** /usr/bin/foomatic-combo-xml: double free or corruption
(!prev): 0x00000000005bda30 ***
======= Backtrace: =========
======= Memory map: ========
00400000-00408000 r-xp 00000000 08:02 376251                            
00508000-00509000 rw-p 00008000 08:02 376251                            
00509000-0060d000 rw-p 00509000 00:00 0                                  [heap]
35be200000-35be21a000 r-xp 00000000 08:02 5111967                       
35be319000-35be31a000 r--p 00019000 08:02 5111967                       
35be31a000-35be31b000 rw-p 0001a000 08:02 5111967                       
35be400000-35be53f000 r-xp 00000000 08:02 5112090                       
35be53f000-35be63f000 ---p 0013f000 08:02 5112090                       
35be63f000-35be643000 r--p 0013f000 08:02 5112090                       
35be643000-35be644000 rw-p 00143000 08:02 5112090                       
35be644000-35be649000 rw-p 35be644000 00:00 0
36fb400000-36fb40d000 r-xp 00000000 08:02 5111811                       
36fb40d000-36fb50d000 ---p 0000d000 08:02 5111811                       
36fb50d000-36fb50e000 rw-p 0000d000 08:02 5111811                       
2aaaaaaab000-2aaaaaaad000 rw-p 2aaaaaaab000 00:00 0
2aaaaaad3000-2aaaaaad5000 rw-p 2aaaaaad3000 00:00 0
2aaaaab00000-2aaaaab21000 rw-p 2aaaaab00000 00:00 0
2aaaaab21000-2aaaaac00000 ---p 2aaaaab21000 00:00 0
7fffef25c000-7fffef372000 rw-p 7fffef25c000 00:00 0                      [stack]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0                  [vdso]
Traceback (most recent call last):
  File "/usr/share/printconf/util/", line 579, in new_button_clicked
    self.use_foomatic ()
  File "/usr/share/printconf/util/", line 502, in use_foomatic
    self.conf.foomatic_init_overview ()
  File "/usr/share/printconf/util/", line 1745, in
    root = parser.parse (foo)
  File "/usr/lib64/python2.4/site-packages/_xmlplus/utils/", line 137,
in parse
    p.Parse(s, 0)
xml.parsers.expat.ExpatError: not well-formed (invalid token): line 449, column 10
Traceback (most recent call last):
  File "/usr/sbin/system-config-printer", line 9, in ?
    import queueTree
  File "/usr/share/printconf/util/", line 1267, in ?
  File "/usr/share/printconf/util/", line 279, in __init__
    gtk.main ()
[root@server ~]#

Expected results:

Additional info:

Comment 1 cruiseoveride 2006-09-07 23:51:34 UTC
the trouble make seems to be a currupt file, 
after deleteing it and replacing with a fresh copy 
all is good now.but here is something from foomatic for you guys

[root@server ~]# system-config-printer
No match for USB device:
  mfr "HP"
  model "Deskjet 5900 series"
  desc "5940"
Please report this message in Bugzilla:
Choose 'foomatic' as the component.
No match for USB device:
  mfr "HP"
  model "Deskjet 5900 series"
  desc "5940"
Please report this message in Bugzilla:
Choose 'foomatic' as the component.

Comment 2 Tim Waugh 2006-09-08 12:28:21 UTC
Do you still have the original
/usr/share/foomatic/db/source/printer/HP-Color_LaserJet_2800.xml, the one that
caused the crash?  If so, please attach it here.

Comment 3 cruiseoveride 2006-09-08 14:27:38 UTC
im sorrry, but it needed to be fixed urgently, so i removed and reinstalled
foomatic completely.
I feel this problem was specific to my system, as the machine in question
suffered from a major file curruption caused by some proprietry backup software,
I think if system-config-printer, in the future were to come across a currupt
printer db xml file, it should try and skip it and display a warning, instead of
Sorry about the file,

Comment 4 Tim Waugh 2006-09-08 14:33:22 UTC
Unfortunately, without the original file it is no longer possible to discover
that the problem was that caused foomatic-combo-xml to crash.

Note You need to log in before you can comment on or make changes to this bug.