Bug 32279 - Starting cups server does not show "running" in mcc
Summary: Starting cups server does not show "running" in mcc
Status: RESOLVED DUPLICATE of bug 28689
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 9
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-12 21:50 CEST by Ken Arromdee
Modified: 2023-09-13 08:16 CEST (History)
1 user (show)

See Also:
Source RPM: drakconf-13.29-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Ken Arromdee 2023-09-12 21:50:14 CEST
Description of problem:
Starting cups server is not shown in mcc

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Go into mcc, "Manage system services by enabling or disabling them".  Make sure cups is running.
2. Stop cups.  It shows "stopped".
3. Start cups.  It does *not* show "running"
4. It actually started successfully and if you close the screen and reopen it, you can see that it's running.
5. Try this for something else such as crond.  It behaves normally when stopped and started.

Also, clicking the "start" button on cups seems to stop it.  If you close and reopen the screen you see that this is a display issue only and the daemon is not actually stopped.  The "stop" button does stop it for real.  This behavior is also absent for crond.
Comment 1 Morgan Leijström 2023-09-12 23:24:06 CEST
Thank you for the report.

For me it is like you describe except i see no sign of stopping when i press "start".

The only fault i find is that the indication does not change to "running" until you close and reopen "Manage system services by enabling or disabling them" 

I also see the process "cupsd" actually runs / vanishes OK.

CC: (none) => fri

Comment 2 sturmvogel 2023-09-13 01:50:40 CEST
This is a dup of bug 28689
Comment 3 Morgan Leijström 2023-09-13 08:16:54 CEST
Seems so

*** This bug has been marked as a duplicate of bug 28689 ***

Status: NEW => RESOLVED
Resolution: (none) => DUPLICATE


Note You need to log in before you can comment on or make changes to this bug.