-
-
Notifications
You must be signed in to change notification settings - Fork 159
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
Error communicating with dbus #514
Comments
This is a very strange error. Do you actually have any Secret Service daemon running on the system (e.g. gnome-keyring)? If no, I would expect a different response:
which would make keyring skip this backend immediately. Can you check if you have Also, even though this seems to be a bug somewhere, I recommend you reading this section of our README: |
Yes, we do have that.
Running
|
And, to reiterate, if I Still trying to get the system administrator to install the RH provided |
We tried installing the keyring package as provided in RedHat 8 EPEL. Those did not seem to fix the issue. |
Same for SLES 15.1 and SLES 15.2
--> Thank you for pointing to the manual. However, seems not to be helpful at all. Some more ideas? @jaraco: |
This project doesn't have any dedicated staff to assign. We're all volunteers giving our best efforts with no service level agreement. mitya57 is our most prolific and knowledgeable contributor on the Linux domain, so if they don't have a solution, then, yes, we'll need more information, and you may need to root-cause the issue yourself. The code is open-source, so it should be possible in theory to trace through the code and find where the expectation is missed. I'd maybe start with seeing if you can reproduce the issue outside of keyring (calling the APIs as keyring does directly) or if there's something about keyring's usage that's implicated in the failure. Good luck! |
This surfaces readily in Google searches for this issue, so adding what worked for me, taken from https://rtfm.co.ua/en/what-is-linux-keyring-gnome-keyring-secret-service-and-d-bus/:
|
Describe the bug
This command fails if I issue it when I
ssh
directly to the remote system, whereas it succeeds if Issh
as a different user and thensu
to the user running the test.Direct
ssh
asbennetsw
After logging in as a different user, and then
/bin/su - bennetsw
To Reproduce
Steps to reproduce the behavior:
Login into remote host with ssh, then run the command above to get the error. To cause the error to go away, login as a different user of the same system, then
and it succeeds.
Expected behavior
The command should succeed in both circumstances.
Environment
Red Hat Enterprise Linux release 8.3 (Ootpa)
$ python --version
Python 3.6.8
$ pip3 install --user keyring keyrings.alt GitPython
$ pip3 list --user
gitdb (4.0.7)
GitPython (3.1.17)
importlib-metadata (4.3.1)
jeepney (0.6.0)
keyring (23.0.1)
keyrings.alt (4.0.2)
SecretStorage (3.3.1)
smmap (4.0.0)
typing-extensions (3.10.0.0)
zipp (3.4.1)
$ rpm -qa | grep "python3-.*dbus"
python3-slip-dbus-0.6.4-11.el8.noarch
python3-dbus-1.2.4-15.el8.x86_64
python3-pydbus-0.6.0-5.el8.noarch
Additional context
I am not the administrator of the system.
The text was updated successfully, but these errors were encountered: