[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2020-08-11 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Released ** Tags added: fixed-in-3.35.90 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851322 Title: VPN aut

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2020-01-09 Thread Bug Watch Updater
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851322 Title: VPN auto-connect is not working Status in GNOME Shell:

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-12-19 Thread Bug Watch Updater
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1851322 Title: VPN auto-connect is not working Status in GNOME Shell: Ne

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-12-08 Thread Daniel van Vugt
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Importance: Low => Medium ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Confirmed -- You received th

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-12-08 Thread Mathieu Tarral
@Daniel bug reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 It seems that today, even manually triggering the VPN connection doesn't work anymore. If you don't set "store password for all users" for the VPN credentials, the connection will fails. ** Bug watch added: gi

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-12-05 Thread Daniel van Vugt
Upstream bug trackers require bugs to be opened by the people affected so that the developers there can communicate directly with those people. Also we don't have time to try and reproduce every bug report, sorry. ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/b

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-06 Thread Mathieu Tarral
I would rather not getting involved into too many bugtrackers, and as a Ubuntu user, remain on Launchpad and provide the required information to let you investigate. Also, as you are a member of Ubuntu teams, you have more authority/credibility than me, so that bug can be taken seriously by Gnome-

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-05 Thread Sebastien Bacher
The issue seems to be on the gnome-shell side then, which is supposed also to be the agent gnome-shell[2760]: Invalid connection type: vpn Could you report the issue upstream on https://gitlab.gnome.org/GNOME /gnome-shell/issues ? ** Package changed: network-manager (Ubuntu) => gnome-shell (Ubun

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-05 Thread Mathieu Tarral
Hi Sebastien, I'm using an the OpenVPN plugin. I'm imported an .ovpn config file into NetworkManager and filled my credentials. I found some interesting log messages in journalctl: nov. 05 21:00:58 gnome-shell[2760]: Invalid connection type: vpn nov. 05 21:00:58 gnome-shell[2760]: Inva

[Desktop-packages] [Bug 1851322] Re: VPN auto-connect is not working

2019-11-05 Thread Sebastien Bacher
Thank you for your bug report. What VPN type/plugin are you using? Could you add your 'journalctl -b 0' log after getting the issue? ** No longer affects: network-manager ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status