https://bugzilla.novell.com/show_bug.cgi?id=253257 jsmeix@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|jsmeix@novell.com |mzugec@novell.com Severity|Normal |Enhancement Component|Printing |Printing Product|openSUSE 10.2 |openSUSE 10.3 Version|Final |Alpha 0plus ------- Comment #1 from jsmeix@novell.com 2007-03-12 03:28 MST ------- This is a good enhancement request for next version. I suggest even more: Let YaST do either only the "client-only" setup or the usual full-featured setup. Perhaps this could be implemented as follows: When yast2-printer runs the very first time (usually at the end of the system installation after the network was set up) do the following: Try to autodetect local connected printers (see 2. below). If no local connected printer is found and if there is a network interface then ask the user if he likes to have a "client-only" setup. If the user wants to have a "client-only" setup then do only the "client-only" setup and nothing else (in particular do not build the printer database). else do the usual full-featured setup (including building of the printer database). The "client-only" setup must offer the possibility to switch back to the usual full-featured setup. Only when a "client-only" setup is done, stop a local running cupsd and then offer the user the possibility to try to autodetect a broadcasting CUPS server via /usr/lib/YaST2/bin/listen_remote_ipp (currently this autodetection needs at least 31 seconds). Perhaps it is much easier to ask the local running cupsd before it gets shut down if there are broadcasted queues e.g. via something like lpstat -v | grep 'ipp:/' But this is only a best-guess because there could be also local queues with an "ipp" DeviceURI. By the way: 1. As far as I see, the YaST printer database is a leftover from the time when we had also LPRng/lpdfilter support. If yast2-printer would work in full compliance to CUPS, it would not need its own printer database at all because the cupsd knows about the models ("lpinfo -m -l"). 2. A suggestion (in bash syntax) how to autodetect printers which are connected via parallel port or USB in full compliance to cups (requires a running cupsd) - here on my SLED10 test machine: -------------------------------------------------------------------------- lpinfo -l -v \ | egrep 'uri =|make-and-model =' \ | egrep -v 'make-and-model = Unknown' \ | grep -B1 'make-and-model =' \ | egrep -A1 'uri =parallel:|uri = usb:|uri = hp:/usb/|uri = hp:/par/' Device: uri = hp:/par/DESKJET_990C?device=/dev/parport0 make-and-model = HP DESKJET 990C Device: uri = hp:/usb/deskjet_3320?serial=TH27T2H35B35 make-and-model = HP deskjet 3320 Device: uri = hp:/usb/HP_LaserJet_1220?serial=00XXXXXXXXXX make-and-model = HP LaserJet 1220 Device: uri = parallel:/dev/lp0 make-and-model = HEWLETT-PACKARD DESKJET 990C Device: uri = usb://hp/deskjet%203320?serial=TH27T2H35B35 make-and-model = hp deskjet 3320 Device: uri = usb://HP/LaserJet%201220 make-and-model = HP LaserJet 1220 -------------------------------------------------------------------------- -- 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, or are watching someone who is.