Arch Linux

Epp

Member

Registered: 2022-07-11

Posts: 98

(Alternative) solution proton-vpn-gtk-app and gnome-keyring?

Here I am again with keyring problems.

I'd say that the protonvpn gui app can not access or read the keyring(file).
For half a year now I get the "Choose password for new keyring" dialog box after each boot on my laptop.
All this time I had my prios elswhere. Now I dive further into it. Problem seems bigger than before I used proton-vpn-gtk-app.

Possible because the keyring has new lines.
https://forums.linuxmint.com/viewtopic.php?t=457725
I tried to place all the file content (for one default keyring file) on one line, but it did not solve the problem.

I like the fprint options for my laptop and I don't want to enter a password after each boot for protonvpn.

Can you please help me on my way for an alternative solution?
- I think that fprint at boot does not combine nicely with autoconnnect for protonvpn-gtk-app
Can this be disabled and leaving intact further fprint functions (for the command line for example)?
On my (none fprint) computer/PC there has never been a single autoconnect password error.
Just typing in my password in the TTY after each boot once is waay better than all this keyring mess.

- The password for protonvpn-gtk-app autoconnect through a file or a an other option than gnome-keyring

Simply disabling

auth sufficient pam-fprintd-grosshack.so

Does not work for alternative solution 1.

Simple adding a login.conf with (username and password) file to my xinitrc file folder and an ".ovpn" file with auth-user-pass login.conf to my home path does not work for alternative solution 2.

Epp

Member

Registered: 2022-07-11

Posts: 98

Re: (Alternative) solution proton-vpn-gtk-app and gnome-keyring?

Yes, I am wrong with bumping.
Placing a copy of the first post is also sub optimal I think.

But if I am wrong in my post because of incompleteness, expected lazyness etc. please let me know.

If my question is not very stupid, could you please point me in some direction?

In short.
I would like to autostart protonvpn-gtk-app. But I would also like to keep intact the fprint functions.
The fingerprint login, I could do without. I am not skillful with pam settings. gnome-keyring problems are no fun and (often) appear as an unpleasant surprise.

Last edited by Epp (2026-05-06 13:16:50)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,020

Re: (Alternative) solution proton-vpn-gtk-app and gnome-keyring?

Some questions for clarity :

You are using network manager to manage your connections on the troublesome system ?

Does it help if you disable fprint for testing purposes ?

What DM / DE / WM / wayland compositor are you using ?

Moderator Note
Moving to Applications & Desktop Environments

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Epp

Member

Registered: 2022-07-11

Posts: 98

Re: (Alternative) solution proton-vpn-gtk-app and gnome-keyring?

Thank you!
Yes, networkmanager is running
I use DWM (with Xorg).

In case there is a setting for off and on, I did not manage to find it.
My attempt for turning off fprint is not successful. I think it is active caused by different files.
But turning the following off in all the files, did not stop the fprint functionality:

auth      sufficient pam_fprintd.so

LRDP

Member

Registered: 2025-02-07

Posts: 6

Re: (Alternative) solution proton-vpn-gtk-app and gnome-keyring?

Hi, i get the same problem after an update, sometimes. I've tried to solve about the keyring, but nothing works, even with the support of AI. I noticed the bug, maybe last year, and a few months ago, a new attempt ended in failure. So i waited a few days, until an update of proton-vpn-gtk-app appears with pacman, and finally it worked. The last update of May had no update for ProtonVPN and the application is no longer compatible with kernel's update. I'm updating every day, but still no compatibility. Patience ! but it's a pity.