There are actually two problems:
- The application was working fine until recently. It might have broken after an OS upgrade, but I'm not sure exactly when. I haven't been using it all the time.
~ flatpak run com.protonvpn.www ✔ at 22:24:51
2025-03-25T11:25:05.709584+00:00 | proton.vpn.core.connection:472 | INFO | CONN:STATE_CHANGED | Disconnected (initial state)
Traceback (most recent call last):
File "/app/bin/protonvpn-app", line 8, in <module>
sys.exit(main())
^^^^^^
File "/app/lib/python3.12/site-packages/proton/vpn/app/gtk/__main__.py", line 35, in main
controller = Controller.get(executor, exception_handler)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/lib/python3.12/site-packages/proton/vpn/app/gtk/controller.py", line 64, in get
executor.submit(controller.initialize_vpn_connector).result()
File "/usr/lib/python3.12/concurrent/futures/_base.py", line 456, in result
return self.__get_result()
^^^^^^^^^^^^^^^^^^^
File "/usr/lib/python3.12/concurrent/futures/_base.py", line 401, in __get_result
raise self._exception
TimeoutError
- Every time the app starts, it creates a new 'pvpn-killswitch-perm' configuration in the wired Ethernet section.
I had a long list of these configurations, and I've deleted them all manually.
There are actually two problems:
I had a long list of these configurations, and I've deleted them all manually.