Bug 162033 - system-config-printer crashes with a traceback when driver==Postscript
system-config-printer crashes with a traceback when driver==Postscript
Product: Fedora
Classification: Fedora
Component: system-config-printer (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2005-06-29 07:27 EDT by Hans de Goede
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-07-06 10:19:07 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 Hans de Goede 2005-06-29 07:27:21 EDT
I had some problems with my printer so I decided to reset all my printer
configfiles to default, start system-config-printer and add my printer.

My printer is a HP Laserjet 2100, this one contains in the foomatic xml file:

-Selecting this printer (/dev/lp0)
-finish adding it
-click edit
The printer HP LaserJet 2100 (ID: HP-LaserJet_2100) is not supported by the
driver Postscript!
Couldn't load driver information.
Traceback (most recent call last):
  File "/usr/share/printconf/util/queueTree.py", line 600, in edit_button_clicked
    if self.editQueue.editQueueDialog (iter):
  File "/usr/share/printconf/util/editQueue.py", line 427, in editQueueDialog
    self.select_printer_iter (iter)
  File "/usr/share/printconf/util/editQueue.py", line 511, in select_printer_iter
    self.printer_model_selected (self.printer_view)
  File "/usr/share/printconf/util/editQueue.py", line 841, in printer_model_selected
    driver_index = self.recommended_driver
AttributeError: editQueue instance has no attribute 'recommended_driver'

Selecting 2100M works fine.

Also the entry for the 2100 is plain wrong since this one can't do Postscript,
it should use the plxmono or lj5gray driver. See the entry for the 2100M which
can do postscript but defaults to plxmono because the 2100M identifies itself as
2100 which makes it impossible to distuingish the two for hw autodetect.
Comment 1 Tim Waugh 2005-06-29 10:07:35 EDT
Reported upstream.
Comment 2 Hans de Goede 2005-06-29 10:47:47 EDT
I don't want to be a PITA, but my reason for reporting this seperatly and
against system-config-printer, is that I believe that an error in the foomatic
database should not lead to a traceback and a crash but to a nice userfriendly

Comment 3 Tim Waugh 2005-06-29 10:53:55 EDT
This particular issue is that the database is not self-consistent.  There's not
much friendly you can say to the user at that point. :-/

Hmm, perhaps foomatic ought to have a consistency check in its %install step.
Comment 4 Hans de Goede 2005-06-30 01:51:13 EDT
Yes that would be an excellent idea and solution.
Now all thats left is coding it :)
Comment 5 Tim Waugh 2005-07-06 10:19:07 EDT
Turns out there are several such inconsistencies:


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