If there is a lot of available WiFi connections, my VPN connection won't show. It seems as if the list of connections to connect tops at around 20 or so, pushing my VPN connection below until it "falls off" the list. Once I disable the WiFi checkbox in nm-widget, the VPN will appear immediately and I can then connect to it. Thanks!
You have ~20 configured wireless connections you can connect to in your area? Isn't the VPN connection visible if you scroll down? VPN connections should be visible right after configured wireless connections, but they should be visible nevertheless you have there 20, 50 or 100 wireless connections.
Hi Jan, thanks for the comment! Yup, I work at a cubicle along with lots of other companies, and they all have their own wifi hotspots. I only have configured one or two wifis, but there are lots of others. I have scrolled the applet's "Available Connections" to the bottom like three times (so that I haven't missed something really obvious) but the VPN is not there. On the other hand, the VPN connection is properly shown and configured in the "Connections - System Settings Module" but I can't connect to it from there. I'll try to attach the screenshots.
Created attachment 105579 [details] screenshot1
Created attachment 105580 [details] screenshot2
Created attachment 105581 [details] screenshot3
Created attachment 105582 [details] screenshot4
Created attachment 105583 [details] screenshot5
Created attachment 105584 [details] a screenshot of connection list
Your VPN connection should be at the third position right after hqwlan, not at the end of the list as only hqwlan5 and hqwlan are configured. What's your output from "nmcli general"? If you try to kill plasmashell and start it again would the vpn connection show up? Is this reproducible all the time?
Created attachment 105585 [details] after logout/login, the VPN is shown on the list
Thank you so much! After logging out and logging back in, the VPN connection is now shown properly in the list. I am unsure whether the bug is triggered by my actions - from my point of view it happens randomly (well it only happened once so far). Weird thing is that the VPN connection appears after the "SAS network guest" which I have never used before. The output of nmcli general: $ nmcli general STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected full enabled enabled enabled enabled
You may have accidentaly clicked on "SAS network guest" before and even though you didn't put the password there the connection was created and pre-configured with some default values. Once you find a clear reproducer, I would ask you to follow instructions from [1] and attach the output here. You can try to disconnect your ethernet connection and connect again to see whether the vpn connection appears. [1] - https://techbase.kde.org/Projects/Solid/Plasma-nm#My_connection_in_the_applet_shows_wrong_information
I have the same problem, my openvpn connections are not shown. I must always start nmtui-connect, in this tool I can start the openvpn connection without problems. A special detail is, this problem occurs only when I connected via wifi. When I plug in my cable, the vpn connections are shown and I can connect. I have > 20 Wifi Accesspoints in my neighbourhood. It is very useless to display all these wifi accesspoints priorized, when I'm already connected with wifi. It would be useful to show other possible connections, like vpn connections on top and after these connections the wifi accesspoints. 80% of my shown wifi connections are under 5% signalstrengt, so the wifi accesspoints coud be shown at the end of the list, ordered by sinal strength.
I use gentoo linux and the version 5.9.5
I can confirm this is happening with plasma-nm 5.11.3, on Arch Linux, although it doesn't seem to have anything to do with the number of WiFi connections (currently happening with only 7 networks available) - not sure if it's the same or a different issue.
I have this problem, too. But it's not really related to VPN, because sometimes not all available Wi-Fi networks are listed in the applet, and they become visible if you switch off the Wi-Fi adapter(!), so I believe this problem occurs with all elements in the applet, not only with Wi-Fi. Anyway, here's a workaround: if the item is missing, you can right-click the applet, go to settings, select your (VPN) connection, right-click it and select "connnect".
(In reply to valdikss from comment #16) > I have this problem, too. But it's not really related to VPN, because > sometimes not all available Wi-Fi networks are listed in the applet, and > they become visible if you switch off the Wi-Fi adapter(!), so I believe > this problem occurs with all elements in the applet, not only with Wi-Fi. Yes, I see this too. Sometimes all the VPN connections are missing and I can only see wifi networks, sometimes *only* the VPN connections are shown, and none of the available wifi networks are shown. When you need to connect to a wifi network and then connect to a VPN it's frustrating when only one or the other is shown. This bug has been a problem for a while, and is still present in 5.14.3 > Anyway, here's a workaround: if the item is missing, you can right-click the > applet, go to settings, select your (VPN) connection, right-click it and > select "connnect". Yes, this works, but what's the point in the widget applet if it doesn't even show my configured wifi/vpn networks which I've used in the past hour?
(In reply to Jan Grulich from comment #1) > You have ~20 configured wireless connections you can connect to in your > area? Isn't the VPN connection visible if you scroll down? VPN connections > should be visible right after configured wireless connections, but they > should be visible nevertheless you have there 20, 50 or 100 wireless > connections. This is *definitely* not the case. I have a new laptop with a fresh installation. Only three wifi networks are configured, but 11 different openvpn connections are configured. The applet shows all the available wifi networks (including 16 of my neighbours' wifi networks) and none of my VPNs. If I turn on my phone's wifi hotspot (which is one of my three configured networks) it doesn't appear in the applet's "Available Connections" list. My phone's hotspot is shown by "nmcli wifi device list" so it's definitely found, it's just the applet that doesn't show it. The list of available connections in the applet is just broken. If I kill plasmashell and restart it the applet shows everything as expected: first the connected wifi network, then the available configured network from my phone's hotspot, then the configured VPNs, then the various wifi SSIDs in the area that I've never used.
On my new laptop I have a new clean install which has: Operating System: Fedora 29 KDE Plasma Version: 5.14.3 Qt Version: 5.11.1 KDE Frameworks Version: 5.52.0 Kernel Version: 4.19.4-300.fc29.x86_64 OS Type: 64-bit I am still seeing this but it is not consistent ; connected to wifi the VPN connections are not always visible (sometimes it does work as expected). Connected to the VPN the other VPN connections are normally visible. Restarting plasma shell as per comment 18 does resolve it.
It's hard to say why your wireless networks are now shown in the applet. One thing is that you need to keep the applet opened for a while, because it scans for the networks, other is that NetworkManager might not report properly that some networks are around, it doesn't mean if they are shown in nmcli, that they are properly advertised on DBus, which is what we follow. You can verify it on DBus yourself. For the VPN case, it might be also NM's fault. I would suggest enabling plasma-nm debug using "export QT_LOGGING_RULES=plasma-nm*.debug=true" in a terminal, from the same terminal restart plasmashell, reproduce your issue and attach the output here.
(In reply to Jan Grulich from comment #20) > It's hard to say why your wireless networks are now shown in the applet. One > thing is that you need to keep the applet opened for a while, because it > scans for the networks, other is that NetworkManager might not report > properly that some networks are around, it doesn't mean if they are shown in > nmcli, that they are properly advertised on DBus, which is what we follow. > You can verify it on DBus yourself. > > For the VPN case, it might be also NM's fault. I would suggest enabling > plasma-nm debug using "export QT_LOGGING_RULES=plasma-nm*.debug=true" in a > terminal, from the same terminal restart plasmashell, reproduce your issue > and attach the output here. This is an applet bug, see https://bugs.kde.org/show_bug.cgi?id=394163 I believe there's a graphical race condition. Please watch the video.
(In reply to valdikss from comment #21) > (In reply to Jan Grulich from comment #20) > > It's hard to say why your wireless networks are now shown in the applet. One > > thing is that you need to keep the applet opened for a while, because it > > scans for the networks, other is that NetworkManager might not report > > properly that some networks are around, it doesn't mean if they are shown in > > nmcli, that they are properly advertised on DBus, which is what we follow. > > You can verify it on DBus yourself. > > > > For the VPN case, it might be also NM's fault. I would suggest enabling > > plasma-nm debug using "export QT_LOGGING_RULES=plasma-nm*.debug=true" in a > > terminal, from the same terminal restart plasmashell, reproduce your issue > > and attach the output here. > > This is an applet bug, see https://bugs.kde.org/show_bug.cgi?id=394163 > I believe there's a graphical race condition. Please watch the video. This is a different issue.
(In reply to Jan Grulich from comment #22) > This is a different issue. I believe this is related and is bound to the same bug. To clarify, I saw this bug (379848) too.
(In reply to Jan Grulich from comment #20) > It's hard to say why your wireless networks are now shown in the applet. One > thing is that you need to keep the applet opened for a while, because it > scans for the networks, I can wait forever but they never get shown, so that's not it. > other is that NetworkManager might not report > properly that some networks are around, it doesn't mean if they are shown in > nmcli, that they are properly advertised on DBus, which is what we follow. > You can verify it on DBus yourself. > > For the VPN case, it might be also NM's fault. I would suggest enabling > plasma-nm debug using "export QT_LOGGING_RULES=plasma-nm*.debug=true" in a > terminal, from the same terminal restart plasmashell, reproduce your issue > and attach the output here. Yes, I'm trying to do this, but it's not obvious how to reproduce the issue. Sometimes all the connections are shown, sometimes not. I haven't been able to reproduce it at will. I'll attach output when I can.
Still present in 5.14.5, and of course after setting the QT_LOGGING_RULES environment variable and restarting plasmashell the bug doesn't happen.
Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I'm setting status to "needsinfo" pending your response, please change back to "confirmed" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I used to see this bug when out and about, somewhere with lots of unknown WiFi networks. With my country being under lockdown or with travel restrictions for most of the year, that hasn't been possible. So maybe it's still happening, but I can't tell. I'll try to verify it at some unknown point in future.
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!