Bug 265439

This issue was present in 10.0 and reported after major work was done, however this bug is present in version RC 10.1 and RC 10.2.

1. Open Yast>Security and Users>Firewall. (assumption is currently running)
2. Select 'Stop firewall Now" > status reflects "firewall not running.
3. Select Next
4. Select Accept

It would appear that the user has stopped the firewall and this has been accepted.

NOT SO

The only way to stop the firewall is as follows
1. Open Yast>Security and Users>Firewall. (assumption is currently running)
2. Select 'Stop firewall Now" > status reflects "firewall not running.
3. Change the Service Start to "Manual"
4. Select Next
5. Select Accept

This time the firewall is accepted as being stopped.

In this instance the application does NOT accept the user intention to stop the firewall as is reflected in the "current status" The user MUST change the service start to Manual.

The user can be totally unaware that the firewall is actually running if they select stop, the status displays not running and this is accepted by the user.

There is another issue here. After selecting 'stop Firewall Now' and the user selects 'next' the user summary is somewhat misleading

"Start firewall when booting 
Firewall will be started after the configuration gets written"

The summary alludes to the issue that the "Firewall will be started after the configuration gets written" which can be viewed as O.K you have stopped the firewall, however when this(?) configuration is written it will be started.

This statement is extremely misleading and not a true summary of the users action in stopping the firewall.

If a user opens the firewall application and stops it which is confirmed by the status this action should be accepted. There should be no reason why the user needs to alter the 'Service Start" as well.

The service start tells the user only
When the PC is booting the firewall will start.
AND
The firewall will only start upon user intervention.

Stopping the firewall should be a simple matter of "stop the firewall" the Status indicates it is not running AND this situation should be finally accepted.


100% faithfully reproducible.

Attached screen shots reflect both procedures.

Not attached, however examined is conformation of status in the "service Status (run levels) application in Yast.

This should NOT be a difficult task for the user to turn on or off.