Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 52472 - printconf-gui crashes with an xml error
printconf-gui crashes with an xml error
Product: Red Hat Public Beta
Classification: Retired
Component: printconf (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Crutcher Dunnavant
Depends On:
  Show dependency treegraph
Reported: 2001-08-23 22:13 EDT by Tony Placilla
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-08-26 10:29:46 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tony Placilla 2001-08-23 22:13:50 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 ?
    import printconf_gui
  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):

How reproducible:

Steps to Reproduce:
1.open xterm, su -
2.type printconf-gui
3.watch the error

Actual Results:  traceback error fdrrom pyton script

Expected Results:  the printer config tool sholud appear

Additional info:
Comment 1 Bert de Bruijn 2001-08-24 08:23:40 EDT
Had the same problem. 
Creating overview.xml as an empty file doesn't fix this.
Comment 2 Glen Foster 2001-08-24 11:52:19 EDT
We (Red Hat) really need to fix this before next release.
Comment 3 Need Real Name 2001-08-25 21:14:51 EDT
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).
Comment 4 Tony Placilla 2001-08-26 10:29:41 EDT
backreved to foomatic-1.1-0.20010717.3.noarch.rpm and tested with all available 
drivers for HP697C (including DJ6xxP) and it works flawlessly
Comment 5 Crutcher Dunnavant 2001-08-27 12:54:02 EDT
this is a 'upgrade over betas are not supported' bug.

the 'fix':

rm -rf /usr/share/foomatic/db
rpm -Uvh --force foomatic-?latest?.rpm

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