Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours
Bug 12080 - printerdb problem
printerdb problem
Product: Red Hat Linux
Classification: Retired
Component: rhs-printfilters (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bernhard Rosenkraenzer
: 12774 12786 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2000-06-11 06:28 EDT by Tim Waugh
Modified: 2008-05-01 11:37 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-07-08 10:27:43 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2000-06-11 06:28:48 EDT
When trying to select a filter for a local printer I get:

Error: can't read "printerdb_desc (Lexmark5700m)": no such element in array
Comment 1 Hans de Goede 2000-06-14 11:44:42 EDT
Same over here, commenting out the Lexmark5700m section in printerdb fixes it
for me, thris section seems to be fine however.
Comment 2 Bernhard Rosenkraenzer 2000-06-17 11:35:33 EDT
Thanks, fixed.
Actually the section wasn't ok - it was lacking a BitsPerPixel entry, and
printtool can be VERY picky.
Comment 3 Tim Waugh 2000-06-21 04:11:29 EDT
*** Bug 12774 has been marked as a duplicate of this bug. ***
Comment 4 Jeremy Katz 2000-06-21 19:42:52 EDT
*** Bug 12786 has been marked as a duplicate of this bug. ***
Comment 5 Gene Czarcinski 2000-06-25 06:17:07 EDT
Please reopen this bug.  This still occurs on beta2.
Comment 6 Bernhard Rosenkraenzer 2000-06-25 06:25:08 EDT
No need - beta2 is obsolete. ;)
It was fixed after that.
Comment 7 Hans de Goede 2000-07-08 10:27:41 EDT
Still there in beta3, reopening.
Comment 8 Bernhard Rosenkraenzer 2000-07-10 16:46:20 EDT
Oops, fixed it in CVS and forgot to build a new package...
Done now (1.71).

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