Bug 12921 - msec cannot be disabled
Summary: msec cannot be disabled
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard: 5RC
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2014-03-03 12:53 CET by Barry Jackson
Modified: 2015-05-20 18:38 CEST (History)
4 users (show)

See Also:
Source RPM: msec-gui-1.4-1.mga5
CVE:
Status comment:


Attachments

Description Barry Jackson 2014-03-03 12:53:46 CET
Description of problem:
mcc->security-> configure system security...-> security settings tab
uncheck 'enable msec'
file-> save configuration
file-> quit
close mcc

mcc->security-> configure system security...-> security settings tab
See that 'enable msec' is checked again.



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


How reproducible:
always

Steps to Reproduce:
1. as above
2.
3.


Reproducible: 

Steps to Reproduce:
Barry Jackson 2014-03-03 12:57:31 CET

Source RPM: (none) => msec-gui-1.4-1.mga5

David Walser 2014-03-03 21:37:00 CET

CC: (none) => thierry.vignaud

Barry Jackson 2014-07-08 01:07:24 CEST

Priority: Normal => High
Whiteboard: (none) => 5alpha1
Severity: normal => major

Comment 1 Barry Jackson 2015-03-08 22:58:48 CET
Still the same in Mga5-RC

Raising severity to critical as a feature is broken.

Severity: major => critical

Barry Jackson 2015-03-08 22:59:26 CET

Whiteboard: 5alpha1 => 5RC

Comment 2 Samuel Verschelde 2015-05-20 10:32:17 CEST
There have been msec fixes recently. Is it still valid?

Keywords: (none) => NEEDINFO
CC: (none) => mageia, makowski.mageia, rverschelde

Comment 3 Nicolas Lécureuil 2015-05-20 14:27:55 CEST
just tested and it works as expected with today msec
Comment 4 Rémi Verschelde 2015-05-20 14:38:33 CEST
Marking as resolved then, feel free to reopen if it turns out that the issue is still there.

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

Comment 5 Barry Jackson 2015-05-20 18:38:11 CEST
I confirm it is fixed after the recent update to msec-1.11-2.mga5.

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