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: