Bug 53924

Summary: Printconf-backend 0.3.46-1 crashes at lpd startup
Product: [Retired] Red Hat Raw Hide Reporter: Joseph Fannin <jhf>
Component: printconfAssignee: Crutcher Dunnavant <crutcher>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.0CC: jhf
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2001-09-21 18:48:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Joseph Fannin 2001-09-21 18:46:47 UTC
Description of Problem:

    When starting lpd, printconf-backend crashes with a python backtrace
and no printers are available.  Starting printconf-gui produces the same

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


How Reproducible:

    Start lpd or printconf-gui...  I have (had?) two printers defined
before upgrading to the most recent rawhide push (as of 9/21) via apt-rpm.
  (*All* packages on this system have been upgraded to the rawhide
version.)  The two printers are a postscript printer on lp0 and a Deskjet
882 (don't recall which driver) on usb/lp0.

Additional Information:

    Python backtrace follows:

Starting lpd: Traceback (most recent call last):
  File "/usr/sbin/printconf-backend", line 7, in ?
    import printconf_backend
  File "/usr/share/printconf/util/printconf_backend.py", line 28, in ?
    from printconf_conf import *
  File "/usr/share/printconf/util/printconf_conf.py", line 81, in ?
    from xml.utils import qp_xml
ImportError: No module named utils
No Printers Defined                                        [  OK  ]

Comment 1 Joseph Fannin 2001-09-21 18:48:04 UTC
That package version in the body should be 0.3.46-1, my mistake.

Comment 2 Joseph Fannin 2001-09-21 19:38:58 UTC
Bahhh... this is a dup, I'm sorry for the spam.

*** This bug has been marked as a duplicate of 53802 ***