I started experimenting with Xubuntu 21.04 hirsute I've noted the following things:
1. The default hirsute install currently installs newer versions of network-manager dependency packages (1.30.0-1ubuntu3) with the sole exception being network-manager-gnome 2. The default hirsuite installed version of network-manager-gnome is 1.18.0-1ubuntu2 which is very similar in version to the 1.18.24 in Xubuntu 20.04.02 When network-manager-gnome-1.18.0 is installed in hirsute my bug is replacable. If I upgrade to network-manager-gnome-1.22.0 from impish (which I can do on hirsute thanks to the higher dependency package versions) the bug disappears and everything appears to work. Upstream has also seemed to imply in my original bug report to them that work had been done as of 1.22 of the upstream packages which might have fixed my bug. My experience seems to suggest that my problem is already solved as of network-manager-gnome-1.22.0, but it looks like 1.22 hasn't been backported to focal. What would it take to backport 1.22.0 to focal for those of us stuck on LTS releases? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1935604 Title: network-manager-applet: stored auto connect VPN gets changed when viewing settings Status in network-manager-applet package in Ubuntu: New Bug description: Xubuntu 20.04.2 LTS focal Applet version from network-manager-gnome 1.8.24-1uubuntu3 amd64 Please note: the issue described below only seems to occur when building the applet on my xubuntu 20.04.2 LTS machines. (I have not tried other ubuntu variants). If I'm on my home xubuntu machine the problem seems to appear whether I'm using the ubuntu package, the ubuntu source archive, the upstream archive, or the upstream source distribution. The problem does _not_ seem to occur when building the exact same upstream sources in debian using xfce as its window manager. (I have not tried other debian variants). Experienced If I open an existing connection with an existing VPN, the selected VPN in the VPN drop down list appears to always show the incorrect VPN. This results in a situation where opening a connection and clicking "save" on the general tab always changes the selected VPN, even if I did not make any change. Expected When I open an existing connection, the VPN listed should be the VPN actually on the connection, not some other random VPN from my list Reproduction Steps 1. Open nm-connection-editor 2. Add multiple VPNs with different names (i.e. US VPN East, US VPN West, Corp VPN East, Corp VPN Europe, Corp VPN West) 3. Create a connection (I've reproduced this on wireless and wired connections) 4. Set the connection to automatically connect to VPN 5. Choose any VPN to automatically connect to 6. Save and close 7. re-open nm-connection-editor 8. Edit the same connection created before 9. Note that the automatic VPN has changed to a different VPN in your list without you having to do antying 10. Click save without changing anything 11. re-open network-manager-editor 12. Note again that the VPN connection is _again_ incorrect The symptom you should be experiencing is that the VPN that is chosen when you save - gets saved and used by the connection, but the user interface does not display the correct VPN when viewed in the connection editor. This means that any time you edit the connection it might be swapping your selected VPN without your knowledge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1935604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
