git-ecosystem / git-ecosystem/git-credential-manager
Ubuntu keyring corruption
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 9.3k
- Forks
- 2.9k
- Avg merge
- 7d 1h
- Merged PRs (30d)
- 14
Description
At this point I'm pretty sure that GCM corrupts keyring. Related issue #1198.
Corruption always happens when I try to push changes.
All other programs can use keyring without any issues (for example Remmina, Deja Dup).
gnome-keyring-daemon -r -d does not help, you have to log out.
Happened on Ubuntu 25.10, 26.04. I use GCM with SourceGit to access GitLab.
Version: 2.7.3+5fa7116896c82164996a609accd1c5ad90fe730a
https://github.com/gircore/gir.core package provides generated bindings for libsecret.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the corruption during a push with GCM 2.7.3 on Ubuntu 25.10 or 26.04 through SourceGit, then compare the keyring behavior with related issue #1198 and the libsecret bindings from gir.core. Done means identifying the GCM keyring failure and confirming that pushing no longer corrupts the keyring while other credential access still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, git, gitlab, ubuntu
- Domain
- authentication, operating-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100