It installs fine but can never connect to the wireless router w/ an SSID of "Doña Ana's", regardless of using nm_applet or NetWorkManager or CLI via wpa_supplicant. The trouble seems to be two-fold: 1 - Mageia shows the router to be: Do\xc3\xb1a Ana's or Do\xC3\xB1a Ana's But then it never authorizes the connection stating that the correctly entered WPA/WPA2 password is incorrect. 2 - Mageia does not first identify the wireless router via ESSID which could be used to get around this issue. It would seem that if the procedure were first to search by ESSSID, in this case: E8:AB:FA:16:1E:F9 then the whole issue of non ASCII characters could be resolved. I am surprised that this occurs in a French based distro. I would imagine the same problem would crop up with "à " or "ç" in an SSID. What's surprising is that I have 2 Android smartphones, a Windows 7.1 laptop, and the Debian based distros: PicarOS Diego, Makulu 6.1 XFCE, and Centych 12.04.3 all connecting with no problem. Unfortunately it makes Mageia 4.1 unusable for me. BTW: I have gone through all the hoops suggested by doktor5000 on the forums to connect to no avail.
There has been some work related to Wifi for Mageia 5 RC, is there a chance this bug is fixed?
CC: (none) => pterjan, tmbVersion: 2 => 4
Couldn't say off hand. I'll download the latest .iso - I saw it on distrowatch.com Since I'm no longer at my mother-in-law's I have no more access to the "Doña Ana" router. But I'll take a look at it. When I've tested it, I'll report back. Mageia for a while was the only distro that shipped with "cooledit", an old favorite of mine. While that's no longer the case, it's still an interesting distro.
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/
Status: NEW => RESOLVEDResolution: (none) => OLD