Description of problem: a) The net applet reports ( via the little popup window when the cursor is over it and via the report when you click on it) wrong connections-often old connection names. For example, I am trying to connect to eduroam on wireless and it tells me that a connection to AirCanada on the ethernet has been disconnected. Well, I last connected to AirCanada months ago. Ie, the reportange seems be very confused. b) Yesterday, I tried to connect to "Air Canada" at heathrow airport using the Drak net center. I clicked on that essid in the window, and it refused to connect. I have set up the sysconfig/network-scripts/ifup-eth so as to turn on wpa_suppicant debugging to /var/log/wpa_supplicant. When I look there, the reason it has not connected because it is trying to connect to the eduroam ESSID, which I had connected to the day before, and naturally all of the essids at heathrow did not have the name eduroam. In all cases somehow draknet is getting all confused over names and is trying to connect to or report from totally inappropriate essids. I am running the latest Drakx-net packages on MGA4. Reproducible: Steps to Reproduce:
This is most probably a duplicate (I think both issues were reported before), but I can't find the matching bug reports. You might want to try switching to NetworkManager, which works much better for many. How to do that is explained in this forums thread: https://forums.mageia.org/en/viewtopic.php?f=25&t=5782 Btw, even if both issues were never reported in Bugzilla (which I doubt, I still experience the first issue daily in cauldron, and have seen the second issue in the past), then this bugreport is still invalid, because it mixes issues :-/ Anyway, cc'ing the drakx-net maintainer, he'll know whether those reports do indeed already exist, and, if not, he can ask to file a separate report for the second issue.
CC: (none) => mageia, marja11Source RPM: drakx-ne => drakx-net
I think that both issues are related-- both symptoms of the same disease. If they are really felt to be separate issues, I can certainly file a separate report, but will hang off for now. I tried NetworkManager and found it far clunkier and harder to set up for unusual situations than NetworkCenter. Admittedly NetworkCenter has problems (it does not use wpa_supplicant properly to set up the desired network to connect to, so it will try to connect to the strongest signal rather than the selected signal, but I have solved that, as I reported about 5 years ago on Mandriva, by having ifup-eth extract the relevant entry from /etc/wpa_supplicant.conf and using that as the conf file for wpa_supplicant. But that is NOT the problem here. Somehow draknet is grabbing the wrong names from somewhere, and using them, both in reporting and in handing over to ifup-eth to connect. It is hard to believe that these are totally distinct problems. I do not know who the drakx-net maintainer is in order to CC him.
(In reply to w unruh from comment #2) > I do not know who the drakx-net maintainer is in order to CC him. You don't need to, Marja did it already. She said "cc'ing...".
CC: (none) => stormi
Great. I interpreted Marja's statement as a suggestion, rather than a statement. If I hover my cursor over the net_applet icon on bootup without any connection I get "Network is down on interface Wired(Ethernet) (Air_Canada_rouge_1)" That is my first ifcfg- file in /etc/sysconfig/network-scripts. It is a wireless ifcfg file (contains TYPE=Wireless) and also has ONBOOT=yes. So somehow the program (net_applet, or connection_manager) is simply grabbing the first thing it comes across. Similarly when I bring up a wireless connection or disconnect it, I get the same message in a little box over the net_applet icon. Something is seriously wrong with the reportage.
Having a look at the code and at the output in /var/log/messages, and /var/log/wpa_supplicant.log, I will make the second into a new bug report. I am no longer sure that it is the same problem.
First issue is a dup of bug #16014 where there's a patch that you can try.
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/
Status: NEW => RESOLVEDResolution: (none) => OLD