Bugzilla – Bug 115888
CUPS hp backend + hplip service versus SANE hpoj backend
Last modified: 2006-09-01 12:22:25 UTC
Right now I installed 10.0 RC1 on my i386 workstation nelson.suse.de. At the end of the installation my HP LaserJet 1220 printer+scanner was set up be YaST printer config by using the CUPS hp backend (DeviceURI hp:/usb/HP_LaserJet_1220?device=/dev/usb/lp0) and the required service hplip was started and "insserved". 1. There should be a user confirmation request before an additional service is started because admins in business environment like to be informed which services run on their servers. 2. The cupsd was stopped after YaST printer config had finished. This leads to a problem when at the very end of the installation the YaST scanner config is started (via YaST control center). If the user selects the SANE hpoj backend for a HP all-in-one device then the hplip service must be stopped and disabled and the ptal service must be used instead. There is a test in the scanner module whether or not the CUPS hp backend is used (using /usr/bin/lpstat -v | /bin/grep -q ': hp:/' see /usr/share/YaST2/modules/Scanner.ycp). When no cupsd runs this test fails in any case and then it is assumed everything is o.k. and then hplip would be silently deactivated. Michal, Why is cupsd stopped in this particular case? Wouldn't it be better to simply let it run?
move to later
reopened
1 - I think just information will be enought at the end. hplip service will be run only when hp:// backend is using. There can be warrning or information when hp backend is selecting (#175323) Already fixed 2 - please be more verbose or open another bug for this. I couldn't provide installation today, cups is stopped when hp:// is using or everytime?
1 - What I mean is that the user has the possibility to decide that the hplip services are not started. Therefore it is o.k. when there is a information when the user selected the hp backend (bug #175323) so that the user can go back and select another backend if he doesn't want the hplip services. 2 - I talked about what happened during installation. If I remember correctly the following happened: Near the end of the installation after the hardware setup, the cupsd was stopped. I don't know why it was stopped or what it stopped (perhaps YaST2-printer?). If I remeber correctly the cupsd was re-started at the very end of the installation when the runlevel 5 (or 3) is reached. The problem which I described happens only when the the YaST scanner config is started (via YaST control center) after the cupsd was stopped but before it was re-started again. For me it makes no sense to stop and re-start it. Therefore I suggest to simply keep it running (except the user has explicitely selected in YaST2-printer during hardware setup that it should be stopped - e.g. for a "client-only" setup).
1 - fixed 2 - I will check this, but make separate report, please
2 is seperated bug 203207.
thanks