-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Locked Gnome keyring causes race condition and authentication denied #43
Comments
Log message from cmd line:
|
Given that this is specific to a non-supported distro we won't be prioritizing this atm. |
Same on Artix OpenRC. I use KDE Plasma and since 6.1.0 I have to manually enter an openvpn password every single time when reconnecting.
EDIT Now, I cannot even connect to a server.
|
@calexandru2018 This is happening for me on Ubuntu 24.04, which is a supported distro... |
@Anonymous941, @RealPacket: we're not able to reproduce this issue in our Ubuntu 24.04 nor Fedora 40 setups. We'll have another look but if you have relevant info that would help to reproduce the issue please let us know. Some questions that come to mind:
|
@RealPacket, does this issue happen if you log out and log back in? And if you try another server? Is it possible you hit the maximum amount of allowed vpn sessions in your plan? |
@jllaneras The issue might occur if the user has no password, and the keyring also doesn't have one. I can test this later |
Please complete the following checklist (by adding [x]):
There's an issue when Gnome keyring is locked and it can be summarized as this:
I tried to trace the problem, but with so many callbacks and async everywhere it is hard.
There's one solution that works, but it might not be the best.
Here is my solution:
start
methodAs the credentials and other data are stored in the keyring, ideally, in every new connection it should be checked if the keyring is locked or not. The user can manually lock it or another application can lock it.
What I have done in the code is:
This solves my problem, but if this would be a valid solution, possibly it should be a call to Dbus.
Maybe the issue is somewhere else, it feels like a race condition, the VPN connection should not start while I type the keyring password to unlock the VPN credentials.
With some help, I could possibly patch this properly.
The text was updated successfully, but these errors were encountered: