** Description changed:

+ [ Impact ]
+  
+  * The protonvpn-app graphical client isn't able to connect to the service 
because the code is incompatible with the python3-proton-vpn-api-core version 
in the archive
+  
+   File 
"/usr/lib/python3/dist-packages/proton/vpn/app/gtk/widgets/vpn/serverlist/city_view/country_row.py",
 line 28, in <module>
+     from proton.vpn.session.servers import Country, Location, TierEnum
+ ImportError: cannot import name 'Location' from 'proton.vpn.session.servers' 
(/usr/lib/python3/dist-packages/proton/vpn/session/servers/__init__.py)
+  
+  * The fix is to update python3-proton-vpn-api-core to 4.19.1 in resolute,
+    which satisfies the minimum version constraint declared by
+    proton-vpn-gtk-app
+ 
+  
+  [ Test Plan ]
+  
+   1. On a clean Ubuntu 26.04 (resolute) installation, install the Proton VPN
+      GTK client:
+  
+        sudo apt install proton-vpn-gtk-app
+  
+   2. Open the application:
+  
+        proton-vpn-gtk-app
+  
+   3. Attempt to log in with valid Proton VPN credentials.
+  
+      Expected (buggy) behaviour: the application crashes before or during
+      the login flow.
+  
+   4. Enable the proposed SRU pocket and upgrade the affected package:
+  
+        sudo apt-get install python3-proton-vpn-api-core/resolute-proposed
+  
+   5. Relaunch the application and log in again with the same credentials.
+  
+      Expected (fixed) behaviour: login succeeds, the VPN connection list is
+      displayed, and a connection can be established without errors.
+  
+  [ Where problems could occur ]
+  
+  * The update advances python3-proton-vpn-api-core from 4.16.0 to 4.19.1,
+    crossing three minor versions. While upstream versioning suggests these
+    are incremental releases, any API or behaviour change in the library
+    could in principle affect the GTK frontend. However, since
+    proton-vpn-gtk-app already declares a hard dependency on >= 4.19, it was
+    written and tested against exactly this version range, making a
+    regression there unlikely.
+  
+  * The only reverse dependency of python3-proton-vpn-api-core in the Ubuntu
+    archive is proton-vpn-gtk-app itself. There are no other packages that
+    consume this library, so the blast radius of any regression is strictly
+    limited to the Proton VPN GTK client — a single application that is
+    already broken without this update.
+  
+  * A regression in the updated package would most likely manifest as a
+    crash or failed login, which is the exact symptom of the current bug and
+    would therefore be immediately detectable during verification testing.
+ 
+ 
+ ---------------------------
+ 
  Hi, upstream Proton VPN developer here.
  
  The Proton VPN app crashes on login due to an incompatibility between
  the proton-vpn-gtk-app version and the python3-proton-vpn-api-core
  version.
  
  I saw that it works on debian testing, which has the following packages:
  
  $ apt list --installed | grep proton
  proton-vpn-gtk-app/testing,now 4.15.3-1 all [installed]
  python3-proton-core/testing,now 0.7.0-1 all [installed,automatic]
  python3-proton-keyring-linux/testing,now 0.2.1-1 all [installed,automatic]
  python3-proton-vpn-api-core/testing,now 5.1.2-1 all [installed,automatic]
  python3-proton-vpn-local-agent/testing,now 1.6.1-1 amd64 [installed,automatic]
  
  On Ubuntu 26.04 we have the following:
  
  $ apt list --installed | grep proton
  proton-vpn-gtk-app/resolute,resolute,now 4.15.2-1 all [installed]
  python3-proton-core/resolute,resolute,now 0.7.0-1 all [installed,automatic]
  python3-proton-keyring-linux/resolute,resolute,now 0.2.1-1 all 
[installed,automatic]
  python3-proton-vpn-api-core/resolute,resolute,now 4.16.0-3 all 
[installed,automatic]
  python3-proton-vpn-local-agent/resolute,now 1.6.1-1ubuntu1 amd64 
[installed,automatic]
  
  Pulling the debian testing versions (proton-vnp-gtk-app 4.15.3-1 and
  python3-proton-vpn-api-core 5.1.2-1) fixes the issue.
  
  Thank you.

** Description changed:

  [ Impact ]
-  
-  * The protonvpn-app graphical client isn't able to connect to the service 
because the code is incompatible with the python3-proton-vpn-api-core version 
in the archive
-  
-   File 
"/usr/lib/python3/dist-packages/proton/vpn/app/gtk/widgets/vpn/serverlist/city_view/country_row.py",
 line 28, in <module>
-     from proton.vpn.session.servers import Country, Location, TierEnum
+ 
+  * The protonvpn-app graphical client isn't able to connect to the
+ service because the code is incompatible with the python3-proton-vpn-
+ api-core version in the archive
+ 
+   File 
"/usr/lib/python3/dist-packages/proton/vpn/app/gtk/widgets/vpn/serverlist/city_view/country_row.py",
 line 28, in <module>
+     from proton.vpn.session.servers import Country, Location, TierEnum
  ImportError: cannot import name 'Location' from 'proton.vpn.session.servers' 
(/usr/lib/python3/dist-packages/proton/vpn/session/servers/__init__.py)
-  
-  * The fix is to update python3-proton-vpn-api-core to 4.19.1 in resolute,
-    which satisfies the minimum version constraint declared by
-    proton-vpn-gtk-app
  
-  
-  [ Test Plan ]
-  
-   1. On a clean Ubuntu 26.04 (resolute) installation, install the Proton VPN
-      GTK client:
-  
-        sudo apt install proton-vpn-gtk-app
-  
-   2. Open the application:
-  
-        proton-vpn-gtk-app
-  
-   3. Attempt to log in with valid Proton VPN credentials.
-  
-      Expected (buggy) behaviour: the application crashes before or during
-      the login flow.
-  
-   4. Enable the proposed SRU pocket and upgrade the affected package:
-  
-        sudo apt-get install python3-proton-vpn-api-core/resolute-proposed
-  
-   5. Relaunch the application and log in again with the same credentials.
-  
-      Expected (fixed) behaviour: login succeeds, the VPN connection list is
-      displayed, and a connection can be established without errors.
-  
-  [ Where problems could occur ]
-  
-  * The update advances python3-proton-vpn-api-core from 4.16.0 to 4.19.1,
-    crossing three minor versions. While upstream versioning suggests these
-    are incremental releases, any API or behaviour change in the library
-    could in principle affect the GTK frontend. However, since
-    proton-vpn-gtk-app already declares a hard dependency on >= 4.19, it was
-    written and tested against exactly this version range, making a
-    regression there unlikely.
-  
-  * The only reverse dependency of python3-proton-vpn-api-core in the Ubuntu
-    archive is proton-vpn-gtk-app itself. There are no other packages that
-    consume this library, so the blast radius of any regression is strictly
-    limited to the Proton VPN GTK client — a single application that is
-    already broken without this update.
-  
-  * A regression in the updated package would most likely manifest as a
-    crash or failed login, which is the exact symptom of the current bug and
-    would therefore be immediately detectable during verification testing.
+  * The fix is to update python3-proton-vpn-api-core to 4.19.1 in resolute,
+    which satisfies the minimum version constraint declared by
+    proton-vpn-gtk-app
  
+ [ Test Plan ]
+ 
+   1. On a clean Ubuntu 26.04 (resolute) installation, install the Proton VPN
+      GTK client:
+ 
+        sudo apt install proton-vpn-gtk-app
+ 
+   2. Open the application:
+ 
+        proton-vpn-gtk-app
+ 
+   3. Attempt to log in with valid Proton VPN credentials.
+ 
+      Expected (buggy) behaviour: the application crashes before or during
+      the login flow.
+ 
+   4. Enable the proposed SRU pocket and upgrade the affected package:
+ 
+        sudo apt-get install python3-proton-vpn-api-core/resolute-
+ proposed
+ 
+   5. Relaunch the application and log in again with the same
+ credentials.
+ 
+      Expected (fixed) behaviour: login succeeds, the VPN connection list is
+      displayed, and a connection can be established without errors.
+ 
+  [ Where problems could occur ]
+ 
+  * The update advances python3-proton-vpn-api-core from 4.16.0 to 4.19.1,
+    crossing three minor versions. While upstream versioning suggests these
+    are incremental releases, any API or behaviour change in the library
+    could in principle affect the GTK frontend. However, since
+    proton-vpn-gtk-app already declares a hard dependency on >= 4.19, it was
+    written and tested against exactly this version range, making a
+    regression there unlikely.
+ 
+  * The only reverse dependency of python3-proton-vpn-api-core in the Ubuntu
+    archive is proton-vpn-gtk-app itself. There are no other packages that
+    consume this library, so the blast radius of any regression is strictly
+    limited to the Proton VPN GTK client — a single application that is
+    already broken without this update.
+ 
+  * A regression in the updated package would most likely manifest as a
+    crash or failed login, which is the exact symptom of the current bug and
+    would therefore be immediately detectable during verification testing.
  
  ---------------------------
  
  Hi, upstream Proton VPN developer here.
  
  The Proton VPN app crashes on login due to an incompatibility between
  the proton-vpn-gtk-app version and the python3-proton-vpn-api-core
  version.
  
  I saw that it works on debian testing, which has the following packages:
  
  $ apt list --installed | grep proton
  proton-vpn-gtk-app/testing,now 4.15.3-1 all [installed]
  python3-proton-core/testing,now 0.7.0-1 all [installed,automatic]
  python3-proton-keyring-linux/testing,now 0.2.1-1 all [installed,automatic]
  python3-proton-vpn-api-core/testing,now 5.1.2-1 all [installed,automatic]
  python3-proton-vpn-local-agent/testing,now 1.6.1-1 amd64 [installed,automatic]
  
  On Ubuntu 26.04 we have the following:
  
  $ apt list --installed | grep proton
  proton-vpn-gtk-app/resolute,resolute,now 4.15.2-1 all [installed]
  python3-proton-core/resolute,resolute,now 0.7.0-1 all [installed,automatic]
  python3-proton-keyring-linux/resolute,resolute,now 0.2.1-1 all 
[installed,automatic]
  python3-proton-vpn-api-core/resolute,resolute,now 4.16.0-3 all 
[installed,automatic]
  python3-proton-vpn-local-agent/resolute,now 1.6.1-1ubuntu1 amd64 
[installed,automatic]
  
  Pulling the debian testing versions (proton-vnp-gtk-app 4.15.3-1 and
  python3-proton-vpn-api-core 5.1.2-1) fixes the issue.
  
  Thank you.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153796

Title:
  Proton VPN app crashes on login

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proton-vpn-gtk-app/+bug/2153796/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to