Bug 77530 - Printtools won't work with HPOJ
Summary: Printtools won't work with HPOJ
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: redhat-config-printer
Version: 8.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2002-11-08 16:50 UTC by Clay Claiborne
Modified: 2007-04-18 16:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2003-03-21 10:49:23 UTC

Attachments (Terms of Use)

Description Clay Claiborne 2002-11-08 16:50:15 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1)
Gecko/20020823 Netscape/7.0

Description of problem:
# RedHat 8.0's "printconf" utilities don't allow entering a device filename
longer than 20 characters, which makes it impossible to enter the necessary

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

How reproducible:

Steps to Reproduce:
1. Attempt to use  a Custom Device longer than 20 characters

Actual Results:  Won't work

Expected Results:  Should work

Additional info:

The main problem with setting up ptal-printd to work with RH8.0 appears 
to be that the RH printer configuration tools (printtools, printconf, 
redhat-config-printer-[gt](all the same as far as I can tell))ui don't 
allow enough space in the 'Custom Device' field to type in the full 
pathname of something like 
'/var/run/ptal-printd/mlc_usb_officejet_d_series.' I tried adding the 
necessary configuration info in /etc/printcap.local but this didn't work 
for me. What did work is this:

1) using printtools create an queue for the hpoj printer, in the Custom 
Device field type in something that will fit and can be easily searched 
for. I used '/officejet_d_series'. Save it. 2) Then export the printer 
configuration info to an xml file with the command:

>/usr/sbin/redhat-config-printer-tui --Xexport > settings.xml
3) Now load 'settings.xml' into your favorite text editor (vi) search 
for your 'Custom Device' string and replace it with the full device 
pathname. 4) Then import your modified setting.xml  with:

>/usr/sbin/redhat-config-printer-tui --Ximport < settings.xml

Now you can reload printtools and restart lpd and you should be able to
print a test page and declare victory. 
printttools doesn't seem to mind the very long 'Custom Device' field as
long as you don't try to edit it in printtools. 
Of course the best solution is for Red Hat modify it's printer utilities
to accommidate long 'Custom Device' strings.

Comment 1 Tim Waugh 2002-11-08 16:54:47 UTC
Does redhat-config-printer-gui from rawhide (0.6.x) work correctly here?

Comment 2 Simon Cooper 2003-03-21 07:56:49 UTC
The problem is that the device dialog box has been arbitarily restricted to
20 characters in size.

Attached are two very small patches which fix this problem for both the
"text" and graphics tools.  The fix increases the size of the input field to
80 characters.



--- usr/share/printconf/util/printconf_gui.py.~1~       2002-09-02
23:56:21.000000000 -0700
+++ usr/share/printconf/util/printconf_gui.py   2003-03-20 21:14:24.000000000 -0800
@@ -218,7 +218,7 @@
        p_label.set_alignment(1.0, 0.5)
        table.attach(p_label, 0, 1, 1, 2)

-       entry = gtk.Entry(20)
+       entry = gtk.Entry(80)
        table.attach(entry, 1, 2, 1, 2)

--- usr/share/printconf/util/printconf_tui.py.~1~       2002-09-02
23:56:21.000000000 -0700
+++ usr/share/printconf/util/printconf_tui.py   2003-03-20 21:27:50.000000000 -0800
@@ -320,7 +320,7 @@

        name_grid.setField(Label(nqd.nametype.name_label_prompt), 0, 0, padding
= (0, 0, 0, 1), anchorLeft = 1)

-       name_entry = Entry(20)
+       name_entry = Entry(80)
        name_grid.setField(name_entry, 1, 0, anchorLeft = 1)
        name_entry.set(nqd.data.get("queue_name", ""))

Comment 3 Tim Waugh 2003-03-21 10:49:23 UTC
Please try 0.6.49-1, which will appear in rawhide in due course.  In the mean
time, you can find it here:


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