Red Hat Bugzilla – Bug 52472
printconf-gui crashes with an xml error
Last modified: 2008-05-01 11:38:00 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.78 [en] (X11; U; Linux 2.4.7-2 i686)
Description of problem:
when calling printconf-gui OR tui from an xterm it fails. the error appears
to be a missing xml file being called by the pyton script. see below
[root@dustpuppy root]# printconf-gui
Traceback (innermost last):
File "/usr/sbin/printconf-gui", line 7, in ?
File "/usr/share/printconf/util/printconf_gui.py", line 1750, in ?
File "/usr/share/printconf/util/printconf_conf.py", line 1069, in
file = open(foomatic.overview_file_path)
IOError: [Errno 2] No such file or directory:
happens when calling printconf-gui, printconf-tui or printtool
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.open xterm, su -
3.watch the error
Actual Results: traceback error fdrrom pyton script
Expected Results: the printer config tool sholud appear
Had the same problem.
Creating overview.xml as an empty file doesn't fix this.
We (Red Hat) really need to fix this before next release.
Had this problem with Roswell2 packages (foomatic-1.1-0.20010717.4.noarch.rpm,
printconf-0.3.23-1.i386.rpm, printconf-gui-0.3.23-1.i386.rpm). Running "rpm
--verify foomatic" reveals a large number of missing files. Downgrading
foomatic to a previous Rawhide package (foomatic-1.1-0.20010717.3.noarch.rpm)
seems to have fixed the problem, but I have only tested one printer driver (ljet3).
backreved to foomatic-1.1-0.20010717.3.noarch.rpm and tested with all available
drivers for HP697C (including DJ6xxP) and it works flawlessly
this is a 'upgrade over betas are not supported' bug.
rm -rf /usr/share/foomatic/db
rpm -Uvh --force foomatic-?latest?.rpm