https://bugzilla.novell.com/show_bug.cgi?id=769346 https://bugzilla.novell.com/show_bug.cgi?id=769346#c13 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |badshah400@gmail.com --- Comment #13 from Johannes Meixner <jsmeix@suse.com> 2012-07-03 10:05:58 UTC --- Atri Bhattacharya, I have questions regarding your comment #4 item 3. therein. You only wrote about the "Restart locally running CUPS daemon" poupup but not about a subsequent "Enable starting of the CUPS daemon during system boot" popup. On my SLED11-SP1 workstation where SysVinit is used when I do # rccups stop # insserv -r cups to stop the cupsd and to disable the cups service and then run the YaST printer module I get first a "Restart locally running CUPS daemon" poupup and then a "Enable starting of the CUPS daemon during system boot" popup. Atri Bhattacharya, your comment #4 item 3. therein indicates that the cups service was not enabled because you wrote that after reboot the cupsd was not running. Atri Bhattacharya, did you get an "Enable starting of the CUPS daemon during system boot" popup and did you responded with "Yes"? If you didn't get such a popup it indicates that there is an issue in lower-level parts of YaST (i.e. the "Service" module) which test whether or not a service is enabled (i.e. Service::Enabled("cups") in case of the printer module). If you got such a popup and you did respond with "Yes" but nevertheless after reboot the cupsd was not running it also indicates that there is an issue in the YaST "Service" module because the YaST printer modules calls Service::Enable("cups") and that shoudl do the right thing also for systemd. For SysVinit this worked all the time an still works for me. Only for systemd ther might be issues and if yes, I would file a separated bug report regarding the YaST "Service" module. -- 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.