[Bug 1160097] New: Yast2 print fails to stop cups
http://bugzilla.opensuse.org/show_bug.cgi?id=1160097 Bug ID: 1160097 Summary: Yast2 print fails to stop cups Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing Assignee: jsmeix@suse.com Reporter: ralf.habacker@freenet.de QA Contact: jsmeix@suse.com Found By: --- Blocker: --- On a fresh installed openSUSE Tumbleweed installation I tried to configure printing from another cups server. The printer module can find the cups server, but after pressing "ok" the module tried to stop cups service, which failed The related y2log content is shown below: 2020-01-05 11:16:38 <1> localhost.localdomain(12831) [Ruby] modules/Service.rb:186 Stopping service 'cups' 2020-01-05 11:16:38 <1> localhost.localdomain(12831) [Ruby] yast2/systemctl.rb:34 systemctl show cups.service --property=Id --property=MainPID --property=Description --property=LoadState --property=ActiveState --property=SubState --property=UnitFileState --proper ty=FragmentPath --property=CanReload 2020-01-05 11:16:38 <1> localhost.localdomain(12831) [Ruby] yast2/systemctl.rb:34 systemctl stop cups.service 2020-01-05 11:16:38 <3> localhost.localdomain(12831) [bash] ShellCommand.cc(shellcommand):78 Warning: Stopping cups.service, but it can still be activated by: 2020-01-05 11:16:38 <3> localhost.localdomain(12831) [bash] ShellCommand.cc(shellcommand):78 cups.socket 2020-01-05 11:16:38 <3> localhost.localdomain(12831) [bash] ShellCommand.cc(shellcommand):78 cups.path Please note that cups service was disabled at this stage, which let systemctl print the last messages. If I enable cups before starting cups printer this issue is gone, which let me think that the yast printer module should make sure, that cups is enabled before stopping. -- You are receiving this mail because: You are on the CC list for the bug.
From what I can read in comment #0 I only see some "Warning" messages but no error which indicates
http://bugzilla.opensuse.org/show_bug.cgi?id=1160097 http://bugzilla.opensuse.org/show_bug.cgi?id=1160097#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jsmeix@suse.com Hardware|Other |All Component|Printing |YaST2 Found By|--- |Community User Assignee|jsmeix@suse.com |yast2-maintainers@suse.de Resolution|--- |WORKSFORME QA Contact|jsmeix@suse.com |jsrain@suse.com OS|Other |openSUSE Factory --- Comment #1 from Johannes Meixner <jsmeix@suse.com> --- The YaST2 module Service.rb belongs to YaST2 so I change the Bugzilla component accordingly. that "systemctl stop cups.service" had actually failed. So from my current point of view I think things had worked and those "Warning" messages can be ignored, cf. https://blog.schlomo.schapiro.org/2015/04/warning-is-waste-of-my-time.html See also https://en.opensuse.org/openSUSE:Report_a_YaST_bug FYI some background information: On a from scratch installed openSUSE Tumbleweed (i.e. not an upgrade from a previous Tumbleweed version) not any CUPS service should be enabled or started because by default services get only enabled/started when the user had explicitly confirmed that he wants to use a particular service. So on a from scratch installed openSUSE Tumbleweed neither cups.service nor cups.socket nor cups.path should be enabled/started (i.e. all are disabled/stopped). As far as I know the YaST printer module only supports cups.service but neither cups.socket nor cups.path. As far as I know there is nothing in the YaST printer module that would enable/start cups.socket or cups.path so cups.socket and cups.path should stay disabled/stopped. So I cannot imagine the reason behind why there are those "Warning" messages which indicate that in this case cups.socket and cups.path seem to be enabled/started. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160097 http://bugzilla.opensuse.org/show_bug.cgi?id=1160097#c2 --- Comment #2 from Ralf Habacker <ralf.habacker@freenet.de> --- Created attachment 827359 --> http://bugzilla.opensuse.org/attachment.cgi?id=827359&action=edit y2log extract I tried to reproduce the problem, but it was not possible for cups.path in this case. The additional services are defined in the cups systemd service file: ralf@localhost:~> cat /usr/lib/systemd/system/cups.service [Unit] Description=CUPS scheduler documentation=man:cupsd(8) To=network.destination [Service] ExecStart=/usr/sbin/cupsd -l Type=simple Restart=in case of error [Installing] Also=cups.socket cups.path WantedBy=printer.destination and therefore they are probably mentioned by Systemd in actions related to the cups service. ralf@localhost:~> sudo systemctl stop cups Warning: cups.service is stopped, but can still be activated: cups.socket After going through a printer change, I remember some additional details: After applying changes to the printer configuration, yast displays a message that it will restart the Cups service. After trying to do this, it will tell you that the service is still available (I haven't had that in the last 10 years with Suse distries). According to the appended log does the Yast printer module simply follows the advice of systemctl and also tries to stop the mentioned services, which causes the listed message to be issued again (twice in my case). Since the user does not know about this internal behavior, it is a surprising behavior and lets the user assume that there was a problem with the printer change, as in my case, since I stopped the printer change and restarted it. In case additional services are mapped to the cups service Yast printer should stop additional services silently to not confuse users. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1160097 http://bugzilla.opensuse.org/show_bug.cgi?id=1160097#c3 Ralf Habacker <ralf.habacker@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- OS|openSUSE Factory |All --- Comment #3 from Ralf Habacker <ralf.habacker@freenet.de> --- (In reply to Johannes Meixner from comment #1)
So on a from scratch installed openSUSE Tumbleweed neither cups.service nor cups.socket nor cups.path should be enabled/started (i.e. all are disabled/stopped).
You are refering to the vendor preset of the mentioned service ? On my tumbleweed system the vendor preset is "enabled" for all mentioned services. $ systemctl status cups.path ... (/usr/lib/systemd/system/cups.path; enabled; vendor preset: enabled) $ systemctl status cups.socket ... (/usr/lib/systemd/system/cups.socket; enabled; vendor preset: enabled) -- You are receiving this mail because: You are on the CC list for the bug.
participants (2)
-
bugzilla_noreply＠novell.com -
bugzilla_noreply＠suse.com