Bugzilla – Bug 378248
let yast2-printer always use the hp backend for HP devices
Last modified: 2008-08-14 06:03:11 UTC
Since hplip version 2.8.4 there are no longer any daemons. The hp backend is just a normal backend. Therefoere there is no longer any reason not to use it if the hp backend has autodetected the device. This condition makes sure that the hplip package is installed (otherwise there is no hp backend) and additionally it makes sure the hp backend works for the device (otherwise it would not autodetect it). yast2-printer can now ignore data/hp_all_in_one_model_list and use the hp backend for any device which it autodetects. By the way: yast2-printer could also use "hp-probe -busb" and "hp-probe -bpar" to autodetect HP USB and parallel port devices and "hp-probe -bnet" to autodetect HP network printers and network all-in-one devices.
Still I recommend not to ignore (not showing) the other available backends, as user might select others, if he discovers issues with this configuration. So, please, only use it as recomentation, but keep the the other backends choseable too.
Of course it is only about what to use by default (if available). I would even say it is a must that YaST lets the user choose a different backend ("usb", "parallel", "socket", "lpd", "ipp", ...). Think about a HP network printer for which a queue already exists on a remote CUPS server machine but "hp-probe -bnet" could detect it nevertheless. It would be wrong when YaST lets the user only set up a local queue using "hp:/net/...".
*** Bug 396246 has been marked as a duplicate of this bug. ***
There is new yast2-printer module which fixes most of the bugs. If this problem occurs in this version, please reopen bugreport. http://mzugec.blogspot.com/2008/08/new-yast2-printer-configuration-module.html