Bug 4237

Summary:	mandy automatical mode not activated by default
Product:	Mageia	Reporter:	episteme promeneur <epistemepromeneur>
Component:	RPM Packages	Assignee:	Olivier Blin <mageia>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	MGA2TOO
Source RPM:	drakx-net	CVE:
Status comment:

Description episteme promeneur 2012-01-23 12:25:10 CET

Description of problem:
interactive firewall automatic mode is not selected by default

this is a pb because there is many notifications displaing in desktop from mandy
this is annpying and disturbing

right click the systray click on the network tool
then
select "settings"
then
you see "interactive firewall automatic mode" is not selected

episteme promeneur 2012-01-23 12:42:22 CET

Hardware: i586 => x86_64

episteme promeneur 2012-01-23 12:44:14 CET

Summary: mageia2a3, mandy not activated by default => mageia2a3, mandy automatical mode not activated by default

Manuel Hiebel 2012-01-23 14:14:26 CET

Assignee: bugsquad => mageia
Summary: mageia2a3, mandy automatical mode not activated by default => mandy automatical mode not activated by default
Source RPM: (none) => drak-net

Comment 1 Marja Van Waes 2012-05-12 10:06:15 CEST

Trying to ping 41 bug reports in one move, because nothing has happened with them for more than 3 months, they still have the status NEW or REOPENED, there is no "OK" on the Whiteboard and severity and priority are "normal" or higher.

Is this one still valid for Mageia 2 rc?

If it is and you're the assignee, please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.
If it wasn't assigned correctly, please assign back to Bug Squad and explain.

Comment 2 episteme promeneur 2012-05-12 10:19:10 CEST

mageia 2 rc

still valid

Comment 3 Marja Van Waes 2012-05-26 13:03:41 CEST

Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 Marja Van Waes 2012-07-06 15:04:50 CEST

Please look at the bottom of this mail to see whether you're the assignee of this  bug, if you don't already know whether you are.


If you're the assignee:

We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead.

If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard.

Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why.

Thanks :)

**************************** 

@ the reporter and persons in the cc of this bug:

If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us.

@ the reporter of this bug

If you didn't reply yet to a request for more information, please do so within two weeks from now.

Thanks all :-D

Comment 5 episteme promeneur 2012-07-17 08:42:03 CEST

mageia 2

still valid

Comment 6 episteme promeneur 2012-07-17 08:55:11 CEST

it's mageia2 x86_64

Manuel Hiebel 2012-07-17 10:39:27 CEST

Keywords: NEEDINFO => (none)
Source RPM: drak-net => drakx-net
Whiteboard: (none) => MGA2TOO

Comment 7 episteme promeneur 2012-11-13 11:26:08 CET

mageia 3 alpha 2

pb still there

Comment 8 Marja Van Waes 2015-04-19 14:13:25 CEST

Sorry, but this bug saw no action since more than 2 yrs ago. 
No cauldron package has stayed the same since then.

Closing as OLD

Please reopen if this report is still valid for _current_ cauldron and/or fully
updated Mageia 4

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