From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Description of problem:
For the first time with FC3, I plugged in my printer by USB. After
about half a minute the Specify Printer Driver window popped up
(confusingly long delay). I selected the driver, and pressed OK.
top(1) showed some foomatic process running for a while, after which
nothing happened. This may be how it is intended to work, but a user
would assume _something_ visible to happen after clicking OK in the
Specify Printer Driver window. Probably have it show the
system-config-printer app. If not, the Specify Printer Dialog should
tell so, and tell why the it asked about the driver in the first place.
So I ran system-config-printer, where there was a presumably new entry
stylus-photo-790-1. I selected Edit from context menu of that entry,
and got on stdout:
No match for USB device:
model "Stylus Photo 790"
desc "EPSON Stylus Photo 790"
Please report this message in Bugzilla:
Choose 'foomatic' as the component.
Otherwise, printing works fine however.
Except CUPS test page entry should mention it's Letter format.
Thanks for the report.
Fixed upstream in CVS. Fixed in Fedora development CVS.
The CUPS test page is not Letter format per se: it is dynamic and fits to the
paper size you have for that queue. If the "Specify Printer Driver" is creating
queues with the wrong paper size for the locale I think that should be reported
as a separate bug.
Created attachment 106717 [details]
Please save this attachment as:
and see if the printer model is now automatically selected when you run
I removed the existing queues from system-config-printer, reconnected
the printer, and correct queues were created. So I guess it works.
The CUPS test page issue seems to be a more generic one: the prints
are not in middle of the paper but some 4 mm too far toward bottom
left corner. That's quite noticeable when doing marginless prints.
Glad that it works.
The CUPS test page border shows the actual printing limits according
to the queue settings, IIRC. Anyway, that's a separate issue to this