Bug 507444 - connect to wireguard vpn missing in the networking widget
Summary: connect to wireguard vpn missing in the networking widget
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Networks widget (other bugs)
Version First Reported In: 6.4.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-24 14:17 UTC by bart
Modified: 2025-10-06 15:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
the box contains no vpn (60.59 KB, image/png)
2025-07-24 14:17 UTC, bart
Details
you can see the connection is listed in the configuration (77.44 KB, image/png)
2025-07-24 14:20 UTC, bart
Details
Screenshot_20250819_105110.png (31.76 KB, image/png)
2025-08-19 14:55 UTC, bart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description bart 2025-07-24 14:17:48 UTC
Created attachment 183489 [details]
the box contains no vpn

SUMMARY
in fedora 41 and earlier, I could connect to my vpn for work, by using the networking widget.  I have upgraded ti Fedora 42, and the "wg0" option no longer exists. the connection exists in the system configuration, but the menu option is no longer present.  I have deleted and re-imported the connection, but it still does not appear.  it just says "wireless is deactivated".  I have a wireless adapter, however I do not use it.  I use a hardline.

STEPS TO REPRODUCE
1. add a wireguard vpn (known working) connection to the system networking configuration.

OBSERVED RESULT

Note that the connection is not present in the taskbar widget.

EXPECTED RESULT
The connection should be present in the taskbar widget to allow the user to connect.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: fedora 42/plasma 6.4.3
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION
Comment 1 bart 2025-07-24 14:20:00 UTC
Created attachment 183490 [details]
you can see the connection is listed in the configuration
Comment 2 Nate Graham 2025-08-07 17:22:55 UTC
For testing purposes, if you do enable wifi, does your VPN become visible?
Comment 3 bart 2025-08-19 14:55:24 UTC
Created attachment 184263 [details]
Screenshot_20250819_105110.png

On 2025-08-07 13:22, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=507444
> 
> Nate Graham <nate@kde.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |nate@kde.org
>              Status|REPORTED                    |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
> 
> --- Comment #2 from Nate Graham <nate@kde.org> ---
> For testing purposes, if you do enable wifi, does your VPN become 
> visible?
sorry for the delayed reply, my plamsa desktop got stuck in a "startup 
crash loop" and I've been unable to use plasma for the last few weeks.

Now that KDE is working again, I have tried enabling wifi, but the 
wireguard vpn still does not appear as an option.
If I start my vpn from a terminal i.e. wg-quick up ~/.wg0.conf then it 
will appear in the list twice, once for the one I started manually, and 
the proper one will also appear in the list (see attachment)
disconnecting the wireguard VPN will remove the first listing, leaving 
the one that should be there, and I can connect and disconnect at will, 
until I logout of my desktop
Comment 4 Nate Graham 2025-08-19 18:43:58 UTC
What about if you enable wifi?
Comment 5 bart 2025-08-19 19:02:40 UTC
On 2025-08-19 14:43, Nate Graham wrote:
> https://bugs.kde.org/show_bug.cgi?id=507444
> 
> --- Comment #4 from Nate Graham <nate@kde.org> ---
> What about if you enable wifi?
if I enable wifi the option for the wireguard vpn does NOT appear.
Comment 6 TraceyC 2025-09-30 20:36:28 UTC
That's odd that this connection would show up in settings but not the widget pop up
I have 2 WG based VPN entries configured, and they both appear in the pop-up in Plasma 6.4.5

Just out of curiosity, if you go into the settings for the connection, on the General tab,  is "All users may connect..." checked, or is your user in Advanced - under the right hand pane "Users allowed to activate the connection"? I assume yes, given the other details.
Comment 7 bart 2025-10-01 13:42:17 UTC
On 2025-09-30 16:36, TraceyC wrote:
> https://bugs.kde.org/show_bug.cgi?id=507444
> 
> TraceyC <kdedev@tlcnet.info> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |kdedev@tlcnet.info
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
> 
> --- Comment #6 from TraceyC <kdedev@tlcnet.info> ---
> That's odd that this connection would show up in settings but not the 
> widget
> pop up
> I have 2 WG based VPN entries configured, and they both appear in the 
> pop-up in
> Plasma 6.4.5
> 
> Just out of curiosity, if you go into the settings for the connection, 
> on the
> General tab,  is "All users may connect..." checked, or is your user in
> Advanced - under the right hand pane "Users allowed to activate the
> connection"? I assume yes, given the other details.
I have it set to "All users may connect to this network".  Just now to 
test, I changed it and added my user to the advanced box, but it still 
does not appear.
Comment 8 TraceyC 2025-10-01 16:06:28 UTC
Thanks for confirming. Could you share what's in your .wg0.conf, removing any secrets from it? I'd like to compare it to the ones I have to see where the differences may be.
Comment 9 bart 2025-10-02 16:48:42 UTC
On 2025-10-01 12:06, TraceyC wrote:
> https://bugs.kde.org/show_bug.cgi?id=507444
> 
> --- Comment #8 from TraceyC <kdedev@tlcnet.info> ---
> Thanks for confirming. Could you share what's in your .wg0.conf, 
> removing any
> secrets from it? I'd like to compare it to the ones I have to see where 
> the
> differences may be.

This is the contents of my wg0.conf, with the keys removed

[Interface]
PrivateKey = redacted=
Address = 10.188.xxx.x/24
DNS = 9.9.9.9, 149.112.112.112

[Peer]
PublicKey = redacted=
PresharedKey = redacted=
Endpoint = 161.199.xx.xx:51820
AllowedIPs = 0.0.0.0/0, ::0/0
Comment 10 TraceyC 2025-10-02 19:16:05 UTC
(In reply to bart from comment #9)
> This is the contents of my wg0.conf, with the keys removed

Thank you.

Can you also share its configuration file in /etc/NetworkManager/system-connections ? There should be a file ending in .nmconnection for it.
Mine looks like this (secrets removed)

[connection]
id=ProtonVPNFree
uuid=xxx
type=wireguard
autoconnect=false
interface-name=ProtonVPNFre-WG
permissions=user:myuser:;

[wireguard]
private-key-flags=1

[wireguard-peer.xxxx=]
endpoint=xx.xx.xx.xx:port
allowed-ips=0.0.0.0/0;

[ipv4]
address1=xx.xx.xx.xx/32
method=manual

[ipv6]
addr-gen-mode=stable-privacy
method=ignore

[proxy]
Comment 11 bart 2025-10-03 01:01:57 UTC
On 2025-10-02 15:16, TraceyC wrote:
> https://bugs.kde.org/show_bug.cgi?id=507444
> 
> --- Comment #10 from TraceyC <kdedev@tlcnet.info> ---
> (In reply to bart from comment #9)
>> This is the contents of my wg0.conf, with the keys removed
> 
> Thank you.
> 
> Can you also share its configuration file in
> /etc/NetworkManager/system-connections ? There should be a file ending 
> in
> .nmconnection for it.
> Mine looks like this (secrets removed)
> 
> [connection]
> id=ProtonVPNFree
> uuid=xxx
> type=wireguard
> autoconnect=false
> interface-name=ProtonVPNFre-WG
> permissions=user:myuser:;
> 
> [wireguard]
> private-key-flags=1
> 
> [wireguard-peer.xxxx=]
> endpoint=xx.xx.xx.xx:port
> allowed-ips=0.0.0.0/0;
> 
> [ipv4]
> address1=xx.xx.xx.xx/32
> method=manual
> 
> [ipv6]
> addr-gen-mode=stable-privacy
> method=ignore
> 
> [proxy]
here it is:


[connection]
id=wg0
uuid=xxx
type=wireguard
autoconnect=false
interface-name=wg0
permissions=user:stark:;

[wireguard]
listen-port=51820
private-key=xxx

[wireguard-peer.xxx=]
endpoint=xxx.xx.xx.xx:51820
preshared-key=xxx
preshared-key-flags=0
allowed-ips=0.0.0.0/0;::/0;

[ipv4]
address1=xx.xxx.xx.x/24
dns=8.8.8.8;
dns-search=~;
method=manual

[ipv6]
addr-gen-mode=stable-privacy
method=disabled

[proxy]