Bug 51130
Summary: | Major problems with printing setup | ||
---|---|---|---|
Product: | [Retired] Red Hat Public Beta | Reporter: | redtux <mike> |
Component: | printconf | Assignee: | Crutcher Dunnavant <crutcher> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | roswell | CC: | csm |
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-13 13:29:55 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
redtux
2001-08-07 18:53:37 UTC
We (Red Hat) should really try to fix this before next release. problems 1&2 are fixed, 3&4 is outside of my abbility to change, and I am looking at 5 now. make that 123 is fixed, 4&5 unchangeable, 6 is being investigated What is the problem with 4 & 5 - is it the driver? or something else yes. Those are an issue with the underlying ghostscript drivers. There are hundreds of them. http://www.moongroup.com/images.d/printconf-error.png printconf-gui crashes and is inoperable Running roswell beta (the first release). Trying to configure a printer fails and running it breaks printers which were properly configured and functional under previous installs. The problem is that there are numerous Python errors, some which are fatal, and some which simply block continuing to try and configure. Trond suggested I nab the latest from rawhide and install them. I did, along with the latest version of Newt and alchemist (both of which were required to upgrade). No joy... the link above gives a screenshot of the error message which occurs on start-up. So printconf will not run. 1. Install roswell 2. Try to configure printer. 3. Doesn't work and will break existing configuration if it exists. 4. Install alchemist, newt, printconf, and printconf-gui from rawhide. (Versions: alchemist-1.0.14-1.i386.rpm, alchemist-devel-1.0.14-1.i386.rpm, newt-0.50.30-1.i386.rpm, newt-devel-0.50.30-1.i386.rpm, printconf-0.3.10-1.i386.rpm, printconf-gui-0.3.10-1.i386.rpm) 5. Crashes on startup (see http://www.moongroup.com/images.d/printconf-error.png) [root@stealth root]# rpm -Uvh printconf-0.3.10-1.i386.rpm printconf-gui-0.3.10-1.i386.rpm Preparing... ########################################### [100%] 1:printconf warning: /etc/alchemist/namespace/printconf/local.adl created as /etc/alchemist/namespace/printconf/local.adl.rpmnew ########################################### [ 50%] warning: erase rmdir of /var/cache/alchemist/printconf failed: Directory not empty warning: erase rmdir of /usr/share/printconf/util failed: Directory not empty warning: erase rmdir of /usr/share/printconf/tests failed: Directory not empty warning: erase rmdir of /usr/share/printconf/mf_rules failed: Directory not empty warning: erase rmdir of /usr/share/printconf failed: Directory not empty 2:printconf-gui ########################################### [100%] [root@stealth 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 1895, in ? gtk.mainloop() File "/usr/share/printconf/util/printconf_conf.py", line 416, in init_queue_edit dict = editor.editReadBox(editbox) File "/usr/lib/python1.5/site-packages/pyalchemist_python.py", line 70, in editReadBox depth = editpos) KeyError: No handler found for box_type: "fileblackbox" Install printconf and printconf-gui from RH7.1 and it works. (Versions: printconf-0.2.12-1.i386.rpm and printconf-gui-0.2.12-1.i386.rpm) #6 is fixed. The fileblackbox problem is an alchemist bug. Upgrade to the latest version of the alchemist. The Help button for printconf-gui (the original Roswell version) does not work when clicked. May I ask where I can find corrected packages for the errors listed above? I'm trying to get printconf to work myself (using a network print server.) Thanks, Bob Cochran. |