Bug 50896
Summary: | unable to declare local printer | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | LENHOF <lenh_jea> |
Component: | printconf | Assignee: | Crutcher Dunnavant <crutcher> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | roswell | CC: | cbagwell |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-08-06 22:43:20 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
LENHOF
2001-08-04 16:04:07 UTC
Perhaps this is related. When I attempt to create a new local printer, I get the following dumped to the terminal screen: Traceback (innermost last): File "/usr/lib/python1.5/site-packages/libglade.py", line 28, in __call__ ret = apply(self.func, a) File "/usr/share/printconf/util/printconf_gui.py", line 471, in nqd_handle_next printer = dev["printer"] KeyError: printer This occurs while I'm using the GUI after selecting Local Printer and adding Queue name, hitting Next, selecting /dev/usb/lp0 as the device to use, and hitting Next. A strange sideeffect from this bug is that it then takes me to the "Unix Printer" screen and asks for server name and Queue. Also, before upgrading to roswell, I had a USB local printer defined that worked fine. I can no longer use it. I get the following from lpq: Printer: epson@brew4me Queue: no printable jobs in queue Status: epson: Open_dgbm: open of DB file 'db.epson' failed, File write error at 23:26:22.967 The file db.epson does exist. Trying to use printconf to edit the screen fails because it also gets confused by the device name to use. The first problem is fixed already. The second problem sounds unpleasant. Try running: /usr/sbin/printconf-backend --force-rebuild and then restart lpd. That might fix it. wait, delete the printer's spool directory, THEN run rebuild to, then restart. I was able to work around the problem but I don't really understand why the problem occured. I reviewed my /tmp/upgrade.log to see if I saw anthing. I found the following: Upgrading printconf. /etc/alchemist/namespace/printconf/local.adl created as /etc/alchemist/namespace/printconf/local.adl.rpmnew I hadn't manually modified that file so I assume running printconf did somehow. Anyways, the new version was quite a bit simpiler then the old version. I replace the old version with the new version and was able to run printconf-gui and create new local printers. For some reason, my old printers were not displayed any more but I was able to recreate them. "lpq" started working for these newly created printers. We (Red Hat) should try to fix this for the next release. this is fixed. was just hopping this guy'd get up and going again. |