Description of problem: Printer Canon s600 unusable under 9.0, fune under 8.0
Version-Release number of selected component (if applicable): 2.0.2
How reproducible: Always
Steps to Reproduce:
1. configure the Canon S600
2. Try to edit the config = crash
Print in economy mode (300 dpi)
When I want to set it to 600dpi, I press the Edit button and I get a crash of
Cannot read file /usr/share/foomatic/db/source/driver/bj8pa06n.upp.xml!Couldn't
load driver information.Traceback (most recent call last):
File "/usr/share/printconf/util/queueTree.py", line 510, in edit_button_clicked
if self.editQueue.editQueueDialog (iter):
File "/usr/share/printconf/util/editQueue.py", line 414, in editQueueDialog
File "/usr/share/printconf/util/editQueue.py", line 906, in write_driver_options
for option_tuple in option_list:
TypeError: iteration over non-sequence
Able to configure the resolution
Able to print in 600dpi
I could go farther using redhat-config-printer-tui
The printer was working fine in 8.0 when using a 600dpi resolution
Please attach the output of 'printconf-tui --Xexport' using the 'Create a New
Attachment' link. Thanks.
Created attachment 91307 [details]
output of "printconf-tui --Xexport"
Here's the output
does someone work on this? or what? almost a month and no news? that's really
long! I need my printer! it shouln't be that long to fix something that got broken!
Sorry for the delay.
Could you please try editing the file
/usr/share/foomatic/db/source/printer/Canon-S600.xml, and change this line:
Does that fix the problem for you?
Thanks for this "patch"
Well, this halfa fixed the problem...
now I can print, but only at 300dpi (econo mode)...
i.e. the resolution box has no effect...
normal effect of the resolutions:
300x300 (default) = econo
600x600 = normal
1200x1200 = twice the size
right now, it only print in econo, so I guess the resolution box dosen't work...
I forgot to say, it fixed the gui crashing at least...
just need to fix the resolution now...
See bug #88171.
yes, this backslash fixed it!
now bug can be closed since it work :)
An errata has been issued which should help the problem described in this bug report.
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen
this bug report if the solution does not work for you.