Bugzilla – Bug 104875
autodetected values are not used to set up printer
Last modified: 2005-08-29 06:25:13 UTC
I installed beta1 on x86_64 (on caps.suse.de) and both printers HP DeskJet 990C and HP LaserJet 1220 which had been connected to USB had been autoconfigured during installation (test-page printed well). Today I tested parallel port. I connected the HP DeskJet 990C to the parallel port. The HP LaserJet 1220 is still connected to USB. Both are autodetected in the new YaST printer main dialog (the model and the connection/device are autodetected) but none of them can be well configured because neither the connection/device is used after I clicked [Edit] nor is a matching model and/or PPD file found after I clicked [Edit]. Manual configuration via [Add] and then manual selection of the connection type and the printer model worked - except see bug 104874. You can verify it using "ssh -X root@caps.suse.de". I have yast2-printer-2.12.1-3 installed on caps.suse.de This is what is available on /work/CDs/all/full-x86_64/suse/x86_64/
Now there is beta2 installed on caps.suse.de There is another problem when a non-YaST queue exists: Now there is a queue which I set up using root@caps: lpadmin -p hp1220 -v hp:/usb/HP_LaserJet_1220?device=/dev/usb/lp0 \ -P /usr/share/cups/model/manufacturer-PPDs/hplip/HP-LaserJet_1220-hpijs.ppd.gz \ -E In this case YaST cannot show the connection (i.e. the DeviceURI) in the Rich-text box. In this case it is shown as hp1220 Connected As With Spool hp1220 Either don't show the "Connected As" line at all if there is no value or better use the "Device" value from the table above as fallback because here there is the value "/usb/HP_LaserJet_1220". By the way: What does "With Spool" mean? Does it mean the queue name? If yes then please use "Queue name".
*** Bug 111414 has been marked as a duplicate of this bug. ***
fixed
*** Bug 113528 has been marked as a duplicate of this bug. ***