linux-gui-legacy
linux-gui-legacy copied to clipboard
Unable to enable autoconnect on Pop_OS
Describe the bug When trying to switch on autoconnect via the GUI, a popup appears saying "Unable to setup autoconnect!". The debug log shows the following:
2020-10-31 12:10:40,957 — linux-gui — DEBUG — update_autoconnect_combobox_changed:264 — >>> Starting "update_autoconnect_combobox_changed" thread. 2020-10-31 12:10:40,957 — linux-gui — DEBUG — update_connect_preference:102 — >>> Running "update_connect_preference". 2020-10-31 12:10:40,968 — linux-gui — DEBUG — daemon_exists:334 — CompletedProcess(args=['systemctl', 'status', 'custompvpn-autoconnect'], returncode=4, stdout=b'', stderr=b'Unit custompvpn-autoconnect.service could not be found.\n') 2020-10-31 12:10:40,974 — linux-gui — DEBUG — enable_autoconnect:268 — errs: usage: sudo -h | -k | -k | -v usage: sudo -v [-akns] [-g group] [-h host] [-p prompt] [-u user] usage: sudo -l [-akns] [-g group] [-h host] [-p prompt] [-u user] [-u user] [command] usage: sudo [-abehknps] [-r role] [-t type] [-c num] [-g group] [-h host] [-p prompt] [-t timeout] [-u user] [var=value] [-i|-s] [
] usage: sudo -e [-akns] [-r role] [-t type] [-c num] [-g group] [-h host] [-p prompt] [-t timeout] [-u user] file ... outs: 2020-10-31 12:10:40,974 — linux-gui — DEBUG — update_connect_preference:118 — >>> Result: False <-> Unable to setup autoconnect! 2020-10-31 12:10:40,974 — linux-gui — DEBUG — update_connect_preference:122 — >>> Ended tasks in "update_autoconnect" thread.
To Reproduce Steps to reproduce:
- Launch GUI
- Go to settings
- Toggle autoconnect to on
- Dialog will pop up saying "Unable to setup autoconnect!"
Expected behavior Autoconnect should toggle on, and the systemd service should be created for this.
Device Info
- Device: Laptop
- OS: Pop_OS! 20.04 LTS
- ProtonVPN GUI Version: 2.1.1 (with NOPASSWD set in the sudoers file)
WORKAROUND The debug log points to the code calling the sudo command with wrong arguments on my OS (Pop_OS! 20.04). If I manually create the custompvpn-autoconnect.service file with the supplied contents from the source, ProtonVPN will automatically connect as per the expected behaviour.
Hey @FBubbles
Thanks for reporting this issue. I've marked this as won't fix because atm the Linux clients are being rewriten, and as such, the autoconnect functionality (as it is currently written) will be not be implemented. Thus, there won't be any commits to fix this until the clients are released.
Either way, you input is much appreciated 👍