| Summary: | net_applet uses old ssid to try to connect even though new one chosen after hibernation | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | w unruh <unruh> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | ||
| Version: | 4 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | drakx-net-applet | CVE: | |
| Status comment: | |||
|
Description
w unruh
2015-04-19 21:13:04 CEST
I have had trouble reproducing this bug. It was always sporadic. But I have now put in a file into /usr/lib/systemd/system-sleep to do a systemctl stop wpa_supplicant and a systemctl start wpa_supplicant when the system comes back up again. I will see if I continue having problems. Not sure where the system stores the old ssid. As I said I set up system-sleep/ to stop wpa_supplicant. But when it comes up, and I look at NetworkCenter list, I see that old ssid I was connected to listed in the list of ssids at the new place. If I refresh it disappears, and I can connect to one of the new ssid's but when I hover over the net_applet icon, it says I am connected to the right IP, but it says the connection is that old ssid (ubcsecure in my case, when actually I am connected to ssid unruh) So Network is up on interface Wireless(Wi-Fi)(wlp3s0) IP address: 192.168.0.150 Gateway: 192.168.0.1 DNS: 192.168.0.1 Coonnected to ubcsecure (link level:90 %) But ubcsecure is NOT the essid it is connected to. It IS connected to essid unruh, and it is listed as such in Network Center. Ie, something is remembering the old ssid and not replacing it with the new one that it is actually connected to, and sometimes using it to try to connect to. -------------------- Further info: I put a print "o_interface= $o_inteface current= "$current_interface" into net_applet in the get_state_message. I got the following The network was up initally, then brought down, and up again. What is wlan0 doing in there? wlan0 was supposed to have disappeared. Is this part of the problem? I do not know. planet:0[root]>net_applet Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.18.1/Gtk3.pm line 296. Unable to read modalias from /sys/bus/usb/devices/3-1/3-1.1/modalias o_interface= current= wlp3s0 got connection status event: link_down wlp3s0 got connection status event: interface_down wlp3s0 got connection status event: interface_down wlp3s0 Unable to read modalias from /sys/bus/usb/devices/3-1/3-1.1/modalias o_interface= wlp3s0 current= wlan0 o_interface= current= wlan0 o_interface= current= wlan0 got connection status event: interface_down wlp3s0 got connection status event: connection_start wlp3s0 got connection status event: link_up wlp3s0 got connection status event: connection_start wlp3s0 got connection status event: dhcp_request wlp3s0 o_interface= current= wlan0 got connection status event: dhcp_success wlp3s0 got connection status event: interface_up wlp3s0 Unable to read modalias from /sys/bus/usb/devices/3-1/3-1.1/modalias o_interface= wlp3s0 current= wlp3s0 o_interface= current= wlp3s0 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 =>
RESOLVED |