codex - 💡(How to fix) Fix Multiple dbus addresses used for accessing keyring [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#22453Fetched 2026-05-14 03:35:49
View on GitHub
Comments
0
Participants
1
Timeline
2
Reactions
0
Author
Participants
Timeline (top)
labeled ×2
RAW_BUFFERClick to expand / collapse

When codex tries to access keyring, it seems to create a new dbus everytime from the same process. And codex seems to access keyrings a lot of times when using chatgpt auth mode.

Ideally the process should maintain its initially created bus and reuse it to access the keyring.

This can create an issue where the keyring service depends on explicit permission from user, and the dbus spam causes access-permission spam.

It happens for keepassxc which is a bug. But codex should still fix its dbus spamming.

Reproduction: https://github.com/keepassxreboot/keepassxc/issues/13340

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Multiple dbus addresses used for accessing keyring [1 participants]