Skip to content

Secrets stay split between "login" and "default2" after the #662 fix #703

Closed

Description

@kem-a

Fedora 45 upgraded from 44, oo7 0.7.0~beta^1.e91b98a-1.fc45.

Same root cause as #662, but ~/.local/share/keyrings/default.keyring unlocks with the login password, so there were no prompts. Both collections got alias default. aliases/default always served Login, while ReadAlias("default") returned either one depending on the daemon start. Apps stored their keys in one collection and looked for them in the other after the next relogin. Slack kept logging me out, and Bitwarden logged "Access token key not found to decrypt encrypted access token. Logging user out." five times, each a few seconds after oo7-daemon started. In the end six apps had a different key in each collection.

As far as I can tell, d41ff70 only renames the duplicate to default2 and leaves its items there. So apps whose current key is in that collection will log out once more after the update. SearchItems also still walks the collections HashMap, so apps that search all collections and take the first match can still get a different key after a restart while duplicates exist. I haven't tested this on 0.7.2.

I could fix it locally by keeping one key per app in Login and deleting the Default collection.

Activity

  1. bilelmoussaoui commented on Nov 20, 2026

    @bilelmoussaoui
    Collaborator

    The only two things that we still can do from the daemon side:

    • Sort the collections list prioritizing the one with default alias
    • Make sure that setting an alias to a collection unsets it from any collection that has the same alias.

    The other thing is to add an option to oo7-cli to merge two collections/keyrings, that can't be done automatically as the user has to decide which items to keep in a conflicting item scenario.

    I would recommend you read both keyring contents with oo7-cli and migrate your data to a single one or use a different collection other than login/default for things you don't want apps using libsecret to use. As libsecret just gets you the default collection.

    I will fix the first two and look at adding a merge command as well. Sorry for the inconvenience

  2. bilelmoussaoui commented on Nov 20, 2026

    @bilelmoussaoui
    Collaborator

    The linked PR has now a migrate command you can use to merge both keyrings, please do that and remove the empty one. You can test it from that branch or wait till it gets merged and released later today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingserver

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions