https://bugzilla.novell.com/show_bug.cgi?id=462048 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462048#c23 --- Comment #23 from Johannes Meixner <jsmeix@novell.com> 2009-03-23 05:04:05 MST --- By the way: When normal printing fails because bidirectional communication fails, a possible workaround is to use ony unidirectional communication. Then there is of course no longer device status information or scanning input for all-in-one devices but at least normal printing might then work reliable. To enforce unidirectional communication, set up the device with the generic "usb" CUPS backend (and not with the "hp" backend). To do this, reboot the computer so that the generic USB communication via the "usblp" kernel module works ("modprobe usblp" may also work) compare comment #1 and bug #184825. Then run as root "lpinfo -v" and verify that the device is also reported (i.e. "autodetected") with a "usb:/..." CUPS DeviceURI. Then use e.g. YaST (run as root "yast2 printer") and click [More Connections] to get also the "usb:/..." connection shown (by default YaST prefers the "hp:/..." connection for HP devices) and use the "usb:/..." connection to set up the print queue (see also the help text in YaST). You can still use the hpijs driver for the queue. I.e. you can get the same printout quality. Only device status information and scanning for all-in-one devides is no longer possible. The crucial point is that the data transfer happens via the "usb" CUPS backend to enforce unidirectional communication. Note that a few low-end HP devices require bidirectional communication in any case even for normal printing. I hope that a Photosmart 7700 series device is sufficiently normal to work also with unidirectional communication. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.