Bug 116728 - printtool hangs when attempting to add new queue
printtool hangs when attempting to add new queue
Status: CLOSED DUPLICATE of bug 113158
Product: Fedora
Classification: Fedora
Component: redhat-config-printer (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2004-02-24 13:55 EST by Paul Sundling
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:01:37 EST
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 Paul Sundling 2004-02-24 13:55:45 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.4.1)

Description of problem:
When starting printtool and then selecting new, it hangs with a
message that says "Loading printer information.  Please wait...". 
When run from the command line, the following error is visible:

Traceback (most recent call last):
  File "/usr/share/printconf/util/queueTree.py", line 537, in
new_button_clicked    self.use_foomatic ()
  File "/usr/share/printconf/util/queueTree.py", line 467, in use_foomatic
    self.conf.foomatic_init_overview ()
  File "/usr/share/printconf/util/printconf_conf.py", line 1554, in
    root = parser.parse (foo)
line 134, in parse
xml.parsers.expat.ExpatError: no element found: line 1, column 0

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

How reproducible:

Steps to Reproduce:
1. /usr/bin/printtool
2. click on "New"

Actual Results:  "Loading printer information.  Please wait..." in X
and errors on the command line as in description.

Expected Results:  printtool would allow a new queue to be created for
a printer.

Additional info:
Comment 1 Justin M. Forbes 2004-02-24 14:49:24 EST

*** This bug has been marked as a duplicate of 113158 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:01:37 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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