RuntimeError: The Secret Service daemon is neither running nor activatable through D-Bus

Open
#710 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
security

Research direction

The report points to keyring/backends/fail.py and keyring/backends/SecretService.py in the installed package. Start by determining whether the behavior is reproducible in keyring on Ubuntu 24.04 rather than caused by the user's environment; no repository test is named. Done would require a confirmed project change or clear documentation addressing the reported failure.

Written by the indexing model from the issue text.

Description

I can't use keyring. When I want to set a new password, I get an error as below:

File "/home/ubuntu/mybotenv/lib/python3.12/site-packages/keyring/backends/fail.py", line 28, in get_password
raise NoKeyringError(msg)
keyring.errors.NoKeyringError: No recommended backend was available. Install a recommended 3rd party backend package; or, install the keyrings.alt package if you want to use the non-recommended backends. See https://pypi.org/project/keyring for details.

When I run:

keyring.backends.SecretService.Keyring.viable
gives: False

keyring.backends.SecretService.Keyring.priority
gives:
File "/home/ubuntu/mybotenv/lib/python3.12/site-packages/keyring/backends/SecretService.py", line 44, in priority
raise RuntimeError(
RuntimeError: The Secret Service daemon is neither running nor activatable through D-Bus

Please, kindly help me to resolve this issue

Operating system is Ubuntu 24.04

Dominant language
Python
Stars
1.5k
Forks
208
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from jaraco/keyring

All issues in jaraco/keyring

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.