Bug 1226816

Summary: Attempting to Login to a Fresh Install of Proton VPN (proton-vpn new client) Gives ProtonCryptoError due to Per-User Issue with GNUPG or Gnome Keyring
Product: [openSUSE] openSUSE Tumbleweed Reporter: Chris Miller <chris.beaudry.miller>
Component: OtherAssignee: Alexandre Vicenzi <alexandre.vicenzi>
Status: NEW --- QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: VPN log first, strace log at the end

Description Chris Miller 2024-06-22 21:27:29 UTC 
Created attachment 875660 [details]
VPN log first, strace log at the end

I have two computers running openSUSE Tumblweed, I am unable to login to ProtonVPN one one due to an error, but the other works just fine.

1) Gaming Desktop:
# System Details Report
---

## Report details
- **Date generated:**                              2024-06-22 17:16:58

## Hardware Information:
- **Hardware Model:**                              ASRock B550M-ITX/ac
- **Memory:**                                      32.0 GiB
- **Processor:**                                   AMD Ryzen™ 7 3800X × 16
- **Graphics:**                                    NVIDIA GeForce RTX™ 3060 Ti
- **Disk Capacity:**                               1.5 TB

## Software Information:
- **Firmware Version:**                            P1.80
- **OS Name:**                                     openSUSE Tumbleweed
- **OS Build:**                                    (null)
- **OS Type:**                                     64-bit
- **GNOME Version:**                               46
- **Windowing System:**                            Wayland
- **Kernel Version:**                              Linux 6.9.5-1-default

2) Gaming Laptop:
System Details Report
Report details
Date generated: 2024-06-22 17:19:37

Hardware Information:
Hardware Model: Micro-Star International Co., Ltd. GP72 6QF
Memory: 16.0 GiB
Processor: Intel® Core™ i7-6700HQ × 8
Graphics: Intel® HD Graphics 530 (SKL GT2)
Graphics 1: NVIDIA GeForce GTX 960M
Disk Capacity: 1.1 TB

Software Information:
Firmware Version: E1795IMS.11D
OS Name: openSUSE Tumbleweed
OS Build: (null)
OS Type: 64-bit
GNOME Version: 46
Windowing System: Wayland
Kernel Version: Linux 6.9.5-1-default


Both computers are updated to the latest snapshot.

cat /etc/*release is the same on both PCs:

NAME="openSUSE Tumbleweed"
# VERSION="20240621"
ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20240621"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20240621:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20240621"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"

However, on the MSI GP72 6QF Laptop I freshly installed ProtonVPN today, and was unable to sign in to the app, while the same version of the software (as far as I can tell) works fine on the desktop. Both computers use the same openSUSE repo to install ProtonVPN, https://software.opensuse.org/package/proton-vpn. 

The message said "We're sorry an unexpected error occured", and there are a series of error messages and a Python traceback, most recent call:

proton.session.exceptions.ProtonCryptoError: Invalid modulus

The rest of the output is included in the attached combined.log file. Additionally, I also captured strace output, that is appended to the end of combined.log, but am a complete amateur at interpreting that output so I could glean nothing from it.
Comment 1 Chris Miller 2024-06-27 14:23:53 UTC 
New update: I debugged this with ProtonVPN support, a very nice employee worked with me even though they don't support openSUSE. These were the results:

1. Purge all packages and config files, and reinstall: DIDN'T WORK
2. Create new Tumbleweed user profile and attempt to sign in to ProtonVPN: WORKS, this put suspicion on per-user cache/config of gnupg and the Gnome keyring
3. On the original Tumbleweed user where the issue was first found, delete ~/.gnupg and ~/.local/share/keyrings/login.keyring. Then log out/in: WORKS, after clearing out the existing gnupg and Gnome keyring data and regenerating it on a new login, I was able to sign in to ProtonVPN

I have done no user-initiated custom configuration of gnupg or the Gnome keyring; anything that was done was done automatically by apps interacting with the keyring/gnupg. It looks like something ended up getting corrupted along the way, and the workaround is to revert gnupg and the keyring to a fresh config.