Description of problem: When a WiFi connection is active, nm-applet normally displays an icon showing the signal strength, and left-clicking on the icon displays a menu showing both the active and the available networks. If the system goes to sleep, nm-applet displays the "disconnected" icon after waking up, and the menu shown by left-clicking doesn't display any WiFi network, neither active nor available. The "Disconnect" menu item isn't disabled, though - as if a WiFi connection would be active (which it is, the WiFi connection is actually restored correctly after sleep). If I click on Disconnect, it is no longer possible to reconnect, since no WiFi networks are displayed. Disabling and reenabling the wireless networking doesn't help: neither is the wireless connection renewed automatically, nor are any WiFi networks shown, so it is no longer possible to connect using nm-applet. This seems to be a bug in the applet. The current connection is shown correctly by "nmcli c show", "nmcli d wifi list" correctly displays the available networks, without issuing any "nmcli d wifi rescan" in advance, and "nmcli c up <Wifi-name>" restores the connection. nm-applet used to work properly before F24 (I'm using the XFCE Spin). Workaround: Restart the applet with "pkill nm-applet; nm-applet &" Version-Release number of selected component (if applicable): 1.2.0-1.fc24 How reproducible: Always Steps to Reproduce: 1. allow your laptop to sleep 2. wake it back up
Sleep doesn't seem to be necessary: I can also reproduce this issue just by enabling and disabling the RF kill switch. I also tried today to reproduce this behaviour on another system, with a fresh installation of the F24 XFCE Spin, but it didn't happen at all (I was careful to avoid bug #1278780 during installation, though). The first system, showing the WiFi issue, was upgraded from F23 to F24, and I found 3 pairs of ifcfg-MySSID* and keys-MySSID* files in /etc/sysconfig/network-scripts/, probably generated in F23 due to bug #1278780. Assuming that nm-applet might be confused because of that, I removed the supplemmental files, leaving only ifcfg-MySSID and keys-MySSID, deleted the "USERS=liveuser" line from the remaining ifcfg file, I issued "nmcli c reload" and rebooted before testing again with both the RF kill switch and sleep. The issue disappeared completely, I was unable to reproduce it even once (after 6-7 attempts). Before deleting the extra files, I could reproduce it every single time. There seems to be a strong correlation with bug #1278780 (which was also present in F23, without any side effects on nm-applet's older version from F23 - therefore I'm not sure if I should add bug #1278780 to the "depends on" field of this bug, feel free to do so if appropriate).
Same problem here. The problem comes after sleep/hibernation/resume cycle. I have Xfce environment, so I'm using pure NM applet (no Gnome version). The problem is on all my three F24 systems (one 32bit and two 64bit). But I have no duplicate files ifcfg-MySSID* and keys-MySSID* in /etc/sysconfig/network-scripts as mentioned in comment #1. Workaround works: killall nm-applet; nohup nm-applet &
Same issue with Fedora 25. Killing nm-applet and restarting it restores the functionality. This is also on XFCE (if that makes any difference).
FWIW, I haven't seen the bug since I worked around the bug based on the observation in comment 1, although I installed F24 quite a number of times. I either use just a LAN cable during the installation and connect to WiFi only after booting into the installed system, or by changing the user name from "liveuser" to the regular user I configured, after Anaconda finishes but before rebooting into the new system (the installed system remains mounting under /mnt/target, if I remember correctly). Still a bit annoying, though.
Failed to reproduce this on Fedora 26 snapshot with Xfce. (A couple of suspend/resume cycles, Wi-Fi list always reloaded correctly). It could be that we fixed this since. I'm wondering if you could share the journal entries? (just redirect "journalctl -fl" to a file while suspending & resuming to reproduce the issue).
*** Bug 1403645 has been marked as a duplicate of this bug. ***
I haven't seen this issue since at least comment 4. I just tried to reproduce it by using the WiFi kill switch 10 times in a row, and then suspending and resuming 2 times. It just won't happen anymore (up-to-date F25 XFCE). I still patch the installed /etc/sysconfig/network-scripts/ifcfg-MySSID manually before booting in the new installation, as mentioned in comment 4 - not sure if that's relevant for this bug.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 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 Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.