Remove keyring requirement - replace with cookie/other token (gnome_keyring)
See original GitHub issueThe Issue
We’ve had some complaints and seensome startup issues because users didn’t have gnome keyring installed. From what I understand, it’s not on all Linux distros and some people choose to use it for various reasons. Is it possible to generate the auth token in a different way for Linux? Possibly some hash of the wallet pubkey and timestamp?
Steps to reproduce
- Run bry-app without gnome keyring installed
- hangs on authenticating screen
- see daemon log below
Expected behaviour
Tell us what should happen
Actual behaviour
Tell us what happens instead
System Configuration
- LBRY Daemon version: 0.13.1
- LBRY App version: 0.13.0
- LBRY Installation ID:
- Operating system: Kubuntu
Anything Else
017-07-01 01:00:28,047 INFO lbrynet.lbrynet_daemon.Daemon:531: Starting to setup up file manager
2017-07-01 01:00:28,073 INFO lbrynet.lbryfilemanager.EncryptedFileManager:126: Started 0 lbry files
2017-07-01 01:00:28,073 INFO lbrynet.lbrynet_daemon.Daemon:542: Done setting up file manager
2017-07-01 01:00:28,075 INFO lbrynet.lbrynet_daemon.Daemon:271: Starting balance: 0
2017-07-01 01:00:28,075 INFO lbrynet.lbrynet_daemon.Daemon:248: Started lbrynet-daemon
2017-07-01 01:00:28,076 INFO lbrynet.lbrynet_daemon.Daemon:249: 0 blobs in manager
2017-07-01 01:00:28,974 INFO lbrynet.core.Wallet:809: Resolving lbry://one
** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
(node:5341) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: The name org.freedesktop.secrets was not provided by any .service files
(node:5341) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files
(node:5341) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: The name org.freedesktop.secrets was not provided by any .service files
Screenshots
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:16 (9 by maintainers)
Top Results From Across the Web
GNOME/Keyring - ArchWiki
GNOME Keyring is "a collection of components in GNOME that store secrets, ... the default keyring, "Login") can be changed and even removed....
Read more >How can I stop being prompted to unlock the 'default' keyring ...
Press Alt + F2 , type seahorse and press Enter to start the Gnome Keyring Manager: ... Disable the login keyring password from...
Read more >How to disable keyring in Ubuntu, elementary OS, and Linux ...
I created one keyring but it isn't the all required default one and nothing asks to save a password to it. How do...
Read more >How to disable keyring popup on Ubuntu - LinuxConfig.org
In this tutorial, we show the step by step instructions to disable the keyring pop up on an Ubuntu Linux system.
Read more >The Keyring Concept in Ubuntu: What is It and How to Use it?
Enter Password To Unlock Your Login Keyring Ubuntu ... etc use an implementation of gnome-keyring to provide this keyring feature in Linux.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Some People cannot install the gnome-keyring as it Will put their current keyring out of place.
We’ve removed it from the recent release (0.44), woohooo!!!