Bug 3764

Summary: printtool crashes on startup
Product: [Retired] Red Hat Linux Reporter: arthur
Component: printtoolAssignee: David Lawrence <dkl>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 6.0   
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: 1999-07-08 15:09:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description arthur 1999-06-28 02:26:36 UTC
Just upgraded from 5.2 to 6.0. printing didn't work so I
fired up printtool. First it griped about SAMBA not
installed. Dont care so I click OK. Then it gripes about
ncpfs. Dont care so I click ok. Then it crashes with:
[root@ludwig /root]# printtool
Error in startup script: can't read
"printerdb_descr(EpsonStylusColor)": no such element in
array
    while executing
"set printer $printerdb_descr([lindex $info 4])"
    (procedure "FILTERED_summaryline" line 7)
    invoked from within
"FILTERED_summaryline $i "local printer""
    (procedure "LOCAL_summaryline" line 5)
    invoked from within
"$printer_type($i)_summaryline $i"
    (procedure "redisplay" line 6)
    invoked from within
"redisplay"
    (file "/usr/bin/printtool" line 3213)

Bottom line. I cant print. This is serious.

Comment 1 Jay Turner 1999-06-28 12:47:59 UTC
This issue has been forwarded to a developer for further action.  Try
moving your printcap off to the side and reexecuting printtool (i.e.
make sure there is not a config file for printtool to read in) and see
what happens.  We have no problems running printtool here in the
office, so I am tending to think that something in your printcap file
is throwing it for a loop.

Comment 2 Bill Nottingham 1999-06-28 14:08:59 UTC
what does your /etc/printcap say?
What version of ghostscript do you have installed?

------- Email Received From  arthur@ablair.physics.wisc.edu 06/29/99 13:53 -------

Comment 3 m.lupp 1999-07-02 06:29:59 UTC
It seems that in the SPEC-File of the printtool-RPM is a bug. The same
is happen to me: After updating from 5.2 to 6.0 I had the same crash
of printtool (with an other printerdb_descr name). What the
printtool-rpm in 6.0 does is: it overwrites file that contains the
printerdescriptions for printtool without saving the old file.
What RedHat has to do is to changing this behavior.
What you can do is: Open the new file that contains the
printerdescriptions for printtool (sorry, I forgot the name) and go to
the end of the file. There is now a other name for the
EpsonStylusColor-Printer. Copy this name over 'EpsonStylusColor' in
your printcap and you can start printtool.

Comment 4 Bill Nottingham 1999-07-08 15:09:59 UTC
fixed in rhs-printfilters-1.56-3 (printerdb is now a %config file...)