Created attachment 4974 [details]
net_applet Wi-Fi "/x00/x00/x00..." bug snapshot

CC: (none) => usrrgt

PLEASE DON'T READ THE MAIN DESCRIPTION, THIS ONE IS BETTER REDACTED (exuse me):

net_applet losts Wi-Fi connection after hide SSID and it fails to connect to the network anymore.
If you go to manually config in drakconf, the last step shows "A problem was occurred testing the network" message:
"Ocurrió un problema mientras testaba la conección de red

This can be caused by invalid network configuration, or problems with your modem or router.

You might want to relaunch the configuration to verify the connection settings."



Steps to reproduce:
1. Connect to a Wi-Fi network (WPA2-PSK & AES, in my case).
2. Hide the network's SSID at the router's config.
3. net_applet lost connection and it shows forever "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00" name instead of the network name and you CAN'T never connect to the network.

Removing "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00" network in "/etc/wpa_supplicant.conf" file, partially fixes the problem. Now you CAN manually connect in drakconf to your network, but it is still showing Wi-Fi name as "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00".
I attached the screenshot of this.



I think the problem will manually easy fixed with an option to remove old networks. net_applet is the only GUI that doesn't have an option to remove networks. It causes this one and more typical problems.
network-manager, Windows, MAC OS, Symbian, iOS, Android, Windows Phone... have and option to remove networks. net_applet must implement this option.

There is patch here:
https://forums.mageia.org/en/viewtopic.php?f=8&t=7077

Version: 3 => 4

The bugs affects to Mageia 3 and Mageia 4 (and also to anyone uses drakx-net like PCLinuxOS, of course).
If you lost for a second the connection, you will have this bug.

maybe you can make a real patch

I can't do it. I'm not a developer. :-(

(In reply to Manuel Hiebel from comment #5)
> maybe you can make a real patch

This looks like a duplicate of bug #13685 which is fixed in drakx-net >= 2.18
Can you try Mga 5 RC?
I'll backport drakx-net-2.22 to mga4...

CC: (none) => thierry.vignaud

Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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