Hide Forgot
Description of problem: NetworkManager correctly connects to a selected wireless network yet no notification (i.e. popup) appears and the icon indicates disconnecion Version-Release number of selected component (if applicable): 1.2.4 How reproducible: Steps to Reproduce: 1. Connect (or auto-connect) to wireless network 2. The connecting 'spinning wheel' appears 3. Connection is successful Actual results: No notification and icon indicates nothing is connected Expected results: - Typical notification with "Connected to XYZ network" - Icon indicating wifi signal strength Additional info: This is on XFCE spin x86_64 Doing a sudo killall -9 NetworkManager (with consequent restart of NetworkManager and disconnect/reconnect) seems to solve the problem at times.
what gives `nmcli device` when that happens?
(In reply to Thomas Haller from comment #1) > what gives `nmcli device` when that happens? The command correctly reports: DEVICE TYPE STATE CONNECTION wlp3s0 wifi connected [name_of_my_connection] I should add that this seems to happen if one disables and then re-enables Wi-Fi (i.e. Right-click on icon, unchecke 'Enable Wi-Fi' check-box, then re-check it). I updated the description accordingly
(In reply to Lorenzo from comment #0) > Description of problem: After disabling and then re-enabling wi-fi (via icon right-click, NetworkManager correctly connects to a selected wireless network yet no > notification (i.e. popup) appears and the icon indicates disconnecion > > Version-Release number of selected component (if applicable): > 1.2.4 > > How reproducible: > Steps to Reproduce: 0. Disable, then re-enable Wi-Fi via right-click context menu (Enable Wi-Fi) > 1. Connect (or auto-connect) to wireless network > 2. The connecting 'spinning wheel' appears > 3. Connection is successful > > Actual results: > No notification and icon indicates nothing is connected > > Expected results: > - Typical notification with "Connected to XYZ network" > - Icon indicating wifi signal strength > > Additional info: > This is on XFCE spin x86_64 > > Doing a sudo killall -9 NetworkManager (with consequent restart of > NetworkManager and disconnect/reconnect) seems to solve the problem at times.
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.