Description of problem: After selecting the firewall to "Everything (no firewall)" in drakconf text-mode the screen is gone black for a long time until eventually it returns to normal. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Open drakfirewall text-mode. 2. Select "Everything (no firewall)". 3. Select "Ok". *Note: the condition before must be not "Everything (no firewall)". Reproducible: Steps to Reproduce:
It's only like that on Mageia guest OS on VMware. I've tried it with my real machine and the black screen is not long.
Status: NEW => RESOLVEDResolution: (none) => INVALID
I'll take back what I said. It's like that on my real machine too. But it's like that if I install Mageia using classic installation with very minimal installation (everything unchecked) (same as the guest OS I installed on VMware).
Status: RESOLVED => REOPENEDResolution: INVALID => (none)
The bug is shown in this video: https://youtu.be/gtNKxBflOr0. I posted this video so the bug can be confirmed. The installed Mageia is installed using classic installation with every categories of packages (like multimedia, KDE, etc.) unchecked.
Status: REOPENED => NEW
@ Boby Sorry for the very late reply, we are short on active BugSquad members. Is this bug still valid in fully updated Mageia 5 and/or cauldron? If so, please reproduce the issue and, when the screen is normal again, run (as root) journalctl -b > journal.txt And attach journal.txt to this bug report. Please do also attach list.txt that is the result of running (as user) rpm -qa | sort > list.txt and tell what the output is of lspcidrake -v | grep Card Thanks :-) ============================================================================= Assigning to the iso builders for now, because this only occurred in very minimal installs, which sounds like a missing package that's needed by drakfirewall. CC'ing the Mageia tools maintainers, in case the problem is with drakfirewall itself.
Keywords: (none) => NEEDINFOCC: (none) => mageiatools, marja11Assignee: bugsquad => isobuild
1½ years later, no reply. Closing as OLD. @ Boby, We regret if this issue didn't get fixed 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, but non-security bugs have no chance of still getting fixed. Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6. In that case, please do also supply the information that was asked in comment #4 Thanks :-) Marja
Status: NEW => RESOLVEDResolution: (none) => OLD