Description of problem: With the in-range WLAN configured to auto-connect to an OpenVPN service (using nm-connection-editor), upon login the whole VPN panel is missing from the system menu, despite the VPN being connected. Workaround is to first log in to text console, wait until VPN auto-connects, then log in from Wayland. Version-Release number of selected component (if applicable): NetworkManager-openvpn.x86_64 1:1.8.8-1.fc29 NetworkManager-openvpn-gnome.x86_64 1:1.8.8-1.fc29 gnome-shell.x86_64 3.30.2-1.fc29 How reproducible: Every time Steps to Reproduce: 1. WLAN in rage, "available to all users" disabled, autoconnect enabled, set to use an OpenVPN connection automatically when connected. 2. Boot, log in to Wayland session. 3. VPN icon and VPN panel in system menu missing. If between steps 1 and 2 I do: - Ctrl-Alt-F3 - log in, run "ip route" to wait for VPN to come up. - Alt-F1 and then log in, VPN icon and panel show up. I can then Ctrl-Alt-F3 back to the text terminal and log out of there, then back to Alt-F2 to my Wayland session. Actual results: Need to log in to text console before logging into Wayland session. Expected results: Used to not need any "extra" log in, as of F27. This regressed with F28 and continues with F29. Additional info:
Realized part of the steps is misleading. It's "If after booting and before logging in to Wayland" that the workaround applies, obviously.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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.
Still happening with F30
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 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.
FWIW, I was seeing this on F31, but no longer seeing this on F32. The steps to reproduce (F31) and no longer reproducing (F32) were/are the same: Both the various WLANs involved and the VPN that's set to automatically connect when these WLANs are connected (in nm-connection-editor) are only available for the same user, not for all users. In the past under F29 and F30 this seemed to make a difference. In fact the system was just "dnf system-upgraded" without me making any changes to the network configurations.