Bug 20719 - Cannot disable some system services (nfs-*) in MCC
Summary: Cannot disable some system services (nfs-*) in MCC
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-22 14:30 CEST by Nicolas Peifer
Modified: 2018-10-07 17:10 CEST (History)
1 user (show)

See Also:
Source RPM: drakxtools
CVE:
Status comment:


Attachments

Description Nicolas Peifer 2017-04-22 14:30:06 CEST
Description of problem:
In the Mageia Control Center (MCC) I cannot disable the following system services:
nfs-idmap
nfs-lock
nfs-mountd
nfs-rquotad

Steps to Reproduce:
1. Go to Mageia Control Center | System | Manage system services by enabling or disabling them.
2. Remove the "on boot" checkmarks of the services listed above.
3. Click "Ok".
4. Reopen "Manage system services by enabling or disabling them". The checkmarks appear despite we removed them in step #2.

Expected behaviour:
I either expect that the checkmarks are gone and the services are disabled or a notification that explains why the services cannot be disabled.
Marja Van Waes 2017-04-23 01:31:03 CEST

Source RPM: (none) => drakxtools
CC: (none) => marja11
Assignee: bugsquad => mageiatools

Comment 1 Marja Van Waes 2018-08-23 22:37:54 CEST
Hi Nicolas,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we were waiting for the big Plasma5 update in Mageia 6, that fixed many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.
Comment 2 Marja Van Waes 2018-10-07 17:10:04 CEST
No reply, so closing as OLD since Mageia 5 is no longer maintained.

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


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