gnome_keyring
Table of Contents
If you want to send us your comments, please do so. Thanks
More on comments
Gnome keyring
Errors
couldn't access conrol socket
When running
gnome-keyring-daemon -s
The error is
Message: couldn't access conrol socket: /home/user/.cache/keyring-somehash/control: Permission denied Message: couldn't connect to dbus session bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. GNOME_KEYRING_CONTROL=/root/.cache/keyring-otherhash SSH_AUTH_SOCK=/root/.cache/keyring-otherhash/ssh GPG_AGENT_INFO=/root/.cache/keyring-otherhash/gpg:0:1 GNOME_KEYRING_PID=fourdigitnumber
couldn't connect to
Full error message
WARNING: gnome-keyring:: couldn't connect to: /home/user/.cache/keyring-xxxxxx/pkcs11: No such file or directory
Solution: How to fix WARNING: gnome-keyring issue
Main subjects on this wiki: Linux, Debian, HTML, Microcontrollers, Privacy
RSS
Disclaimer
Privacy statement
Bugs statement
Cookies
Copyright © : 2014 - 2024 Webevaluation.nl and the authors
Changes reserved.
gnome_keyring.txt · Last modified: 24-07-2016 13:11 by wim