https://bugs.kde.org/show_bug.cgi?id=405501
Bruce Anderson <banderson19...@san.rr.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
--- Comment #1 from Bruce Anderson <banderson19...@san.rr.com> ---
This is going to take a while to fix because the configuration data for
WireGuard connections has totally changed starting in the new version of
NetworkManager. As a sidenote it appears that nm-connection-editor has not been
updated to handle the change either.
In the meantime to make it so the WireGuard connections do not automatically
start on login you can issue:
nmcli connection modify <connection name> connection.autoconnect no
Then to start and stop the connection unfortunately it appears you will need to
use:
nmcli connection <up/down> <connection name>
because at least for me, the WireGuard connections don't show up on the popup
menu to be connected using the plasma-nm interface.
--
You are receiving this mail because:
You are watching all bug changes.
