It happend now twice to me, that the Network Manager (the part from the MCC - *not* the Gnome Network manager!) forgets all his settings. What happens: I have here only a wireless connection! I get disconnected. When I try to reconnect (by clicking on either the network icon in the top right corner of my Gnome DE) or by going through the MCC > Network & Internet > Network Center I only get a message "connection failed". When this happens, I check the configuration and I see there, that the Encryption mode is set to "None" instead of "WPA/WPA2 Enterprise". I change it to the correct setting and click ok. I click on "connect" and again, I get the message "connection failed". By checking again the configuration, I see, that the encryption mode is set to "None" again. The only workaround I found so far is renameing the file "/etc/wpa_supplicant.conf" and setup the profile again. I did this last Monday and it lasted at least until today, then I had to redo the same process again. Please let me know, if I can do something to help you fix this bug. For me it is annoying, but for a new linux user it is a real obstacle. Sigrid
Assignee: bugsquad => mageiaSource RPM: (none) => drakx-net
This looks pretty similar to my experience as well. For me the problem relates to the GUI not writing it's config files properly in: /etc/sysconfig/network-scripts/wireless.d/$SSID (where $SSID is the SSID in question). It contains the line: WIRELESS_ENC_MODE=open Even when the GUI has set this to WPA. I suspect that it is this part of the puzzle that needs fixed. I suspect the config from these files are then translated into entries in wpa_supplicant.conf, so solving why it's written incorrectly there will likely fix how it's written to wpa_supplicant.conf as a result. I also have a problem of metrics for wifi networks not being written correctly but that's a different bug...
CC: (none) => mageia
CC: (none) => thierry.vignaudSummary: Drak-X Network manager forgets settings => Drak-X Network manager doesn't update /etc/sysconfig/network-scripts/wireless.d/$SSID
On my x86_64 there isn't this problem. There also isn't a line with: WIRELESS_ENC_MODE
CC: (none) => magnus.mud
Hi, it happened to me again today. I'm wondering, if some updates might trigger a change in here? I was running updates at the time, when my network connection stopped working. It only had downloaded the meta-task package and then restarted urpmi. I was just downloading the next updates (but nothing installed yet), when I saw, that I wasn't connected anymore. A working wpa_supplicant.conf looks like this: network={ key_mgmt=WPA-EAP IEEE8021X NONE proto=RSN WPA group=CCMP TKIP password="*******" scan_ssid=1 identity="*******" mode=0 ssid="eduroam" pairwise=CCMP TKIP } where the not working file looks like that: network={ key_mgmt=NONE mode=0 ssid="eduroam" scan_ssid=0 } Mind you, this is a file that only root can modify and I am more than sure, that I didn't accidentally edited that file. Sigrid
Hello, is there anything I can do to solve this problem? This bug is still there and annoys me. For example, it happened to me 4 times today, the the network-center forgot all its settings and that I could not connect. Sigrid
Hardware: i586 => arm
Version: Cauldron => 1
Ping: blino, any chance that you'd study this bug?
CC: (none) => stormi
Status: NEW => ASSIGNED
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and 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. 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. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: ASSIGNED => RESOLVEDResolution: (none) => WONTFIX