Bug 20465 - Typo in printerdb causing error in printtool
Summary: Typo in printerdb causing error in printtool
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: rhs-printfilters   
(Show other bugs)
Version: 6.2
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2000-11-07 13:27 UTC by Andy Wallace
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-01-10 15:26:24 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Andy Wallace 2000-11-07 13:27:50 UTC
In the printerdb entries for the ALPS printers, the Resolution field is 
misspelt as "Resoltion". (Same type of bug as no 13482 really but causes a 
noticeable problem) That's what is causing the error message in Printtool 
if you try to select this printer.

This is in version 1.63 of rhs-printfilters.

I've also pulled down the latest Rawhide version (1.81) and noted that the 
MD2K entry had been fixed, but the MD5K entry hasn't.

I saw the bug report for printtool (11398) which is classed as 'Resolved', 
but then it isn't really a printtool bug and it isn't really resolved so 
I'm reporting it as a new bug.


Comment 1 Andy Wallace 2000-11-07 22:45:42 UTC
Looking through the printerdb file, I also noticed that in the comments for the 
Apple ImageWriter low-res and hi-res drivers the resolutions are 160x72 and 
160x144 respectively, whereas in the Resolution entries themselves they are 
120x72 and 120x144. Which is correct?

Also, the C.Itoh M8510 comment says 160x144 and the entry is 100x100. Again, 
these are in both the old (1.63) and latest (1.81) versions of rhs-printfilters.

Comment 2 Tim Waugh 2002-01-20 17:40:49 UTC
This seems to be fixed in the foomatic database, from a quick inspection.

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