-
-
Notifications
You must be signed in to change notification settings - Fork 755
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
CLI: Error getting password from keyring #722
Comments
Same issue here on an ubuntu server after install the I installed |
@sarunaskas if you find a solution please post it here, I didn't find one yet |
+1 |
I encountered the error from #1328, but at one point it evolves into the error above. The steps described here helped me fix the error. TL;DR on steps:
|
doesn't work for me unfortunately |
The workaround doesn't work for me either. |
Same here, gnome-keyring is running but the ente CLI refuses to do anything:
|
For anyone running into this and wanting to use the cli without gnome-keyring, see my PR #2426 |
## Description Adds a new enviroment variable `ENTE_CLI_SECRETS_PATH`, that allows specifying the path to a `secrets.txt` like the one used in the dockerized version. If no path is provided, the old behaviour is maintained. The configuration variable and behaviour is analog to the already present `ENTE_CONFIG_PATH` variable, which allows specifying a configuration. This provides a solution for people running without gnome-keyring (#722 and #1328)
Since the CLI is an HTTP client of the Ente server, running it in a desktop environment can likely avoid keyring issues. |
I'm running a headless Ubuntu 22.04.3 server and tried installing the deb package from the release tab. When I try to execute a ente command I get the error
error getting password from keyring: failed to unlock correct collection '/org/freedesktop/secrets/collection/login'
.I installed the gnome-keyring-daemon since that seems to be required but that didn't fix the problem.
I'm out of ideas since you don't find much information online regarding this error, does someone know what the issue could be?
The text was updated successfully, but these errors were encountered: