Created attachment 137493 [details] Networks widget opened (several minutes after restart) SUMMARY Linux cannot connect to WiFi. STEPS TO REPRODUCE 1. Setup WiFi and Wireguard VPN connection 2. Restart your system OBSERVED RESULT System shows notification "No secrets were provided." and a dialog, that asks to provide the password for VPN (see attached screenshots). Linux cannot connect to WiFi at all, if wireguard tries to connect simultaneously. If I turn off wireguard, then WiFi connects and after that I have to connect to wireguard manually -- this is the only way to make it work. Reproducible after each OS restart. EXPECTED RESULT WiFi and wireguard should both connect one after another. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.10-1-MANJARO OS Type: 64-bit Graphics Platform: X11
Created attachment 137494 [details] VPN password dialog and numerous notifications with connection errors
Created attachment 137665 [details] Wireguard private key alternates bw/ present and absent I am not sure if it's related, but in KDE settings for Wireguard connection: the secret alternates between present and absent.
Given the message about secrets, I wonder if it's related to org.freedesktop.secrets? I wouldn't have expected plasma-nm to request secrets as KWallet currently doesn't support it ( https://invent.kde.org/frameworks/kwallet/-/merge_requests/11 ).
*** Bug 447320 has been marked as a duplicate of this bug. ***
This is actually a two-fold issue: 1) if you in principle always use a corporate vpn, you'd need to re-connect manually on every boot 2) if you use a vpn to circumvent untrusted networks by default, it requires you to shortly run your connections over the untrusted network until you re-connect to the vpn.
Sorry, I commentated the wrong bug above ^
Confirming this still happens on 6.1.1 STEPS 1. create one wireguard connection 2. bring that connection up to confirm it is working fine 3. add a wifi|wired connection, mark "General Configuration > Automatically connect to VPN" and select connection from step 1. 4. bring wifi|wired connection up. WHAT HAPPENS notification saying both connections failed MORE INFO log for NetworkManager shows <warn> policy: secondary connection 'my_wg_connection (uid...)' auto-activation failed: The connection is not a VPN. libnm 1.48.2-1 networkmanager 1.48.2-1 networkmanager-qt 6.3.0-1 plasma-nm 6.1.1-1 Operating System: Arch Linux KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland
I have the same bug using LAN connection Operating System: EndeavourOS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.10.4-arch2-1 (64-bit) Graphics Platform: X11
Bulk transfer as requested in T17796