-
Notifications
You must be signed in to change notification settings - Fork 21
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
collection.unlock() and collection.is_locked() both return True #32
Comments
The
We inherited it from the Secret Service specification. I hate it too, but now it's too late to change it. |
Thanks! Is my understanding that |
Yes, it should prompt for a password. Are you using gnome-keyring? If yes, is it GNOME Shell, some other desktop environment or a headless system? |
Sorry for taking your time. I'll have physical access to the machine tomorrow, and I'm hoping things will just work if I login to the desktop environment (Lubuntu 20.04 / LXQT by default, but will switch to plain fvwm shortly). For now, I'm logged in via ssh and ran the following
before updating One other possibility -- just a random thought -- is that the secrets / collection is stored in an older incompatible format. I'm trying to revive this machine by installing a light distribution, but the home directories have been around and unused for some years. |
I tried the following;
collection.unlock()
andcollection.is_locked()
both return True. I must be doing something wrong, but don't know enough about secretstorage to identify what my error is. Please help!pip list
saysSecretStorage 3.3.1
The text was updated successfully, but these errors were encountered: