Bug 2567187

Summary: Keyring is not unlocked after Fedora 45 Silverblue upgrade
Product: [Fedora] Fedora Reporter: bugzillarh-gw0vyr4u
Component: oo7Assignee: Fabio Valentini <decathorpe>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: 45CC: bugzillarh-gw0vyr4u, decathorpe, ngompa13, ppywlkiqletw
Target Milestone: ---Keywords: Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description bugzillarh-gw0vyr4u 2026-11-05 06:53:00 UTC
After upgrading to Fedora 45 Silverblue (from 44), I get a prompt after login saying my keyring was not unlocked automatically. This was not the case before, and my keyring password is the same as my account/login password.

oo7-daemon was not enabled. Starting it manually does not work. busctl --user status org.freedesktop.secrets shows that /usr/bin/gnome-keyring-daemon is the current owner. I also saw this log:

Nov 04 17:01:14 fedora gnome-keyring-daemon[5392]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory

Reproducible: Always

Steps to Reproduce:
1. Upgrade from Fedora Silverblue 44 to 45.
2. Log in.
3. Observe the keyring-unlock prompt.
4. Check systemctl --user status oo7-daemon.service and try starting it.
5. Check the Secret Service owner with busctl --user status org.freedesktop.secrets.
Actual Results:
The keyring is not automatically unlocked. GNOME Keyring is still running. Starting oo7 reports a migration error and a D-Bus name conflict.

Expected Results:
The login keyring unlocks automatically, and the Secret Service provider starts without a name conflict.

Additional Information:
Nov 04 18:00:42 fedora systemd[16859]: Starting oo7-daemon.service - Secret service (oo7 implementation)...
Nov 04 18:00:42 fedora oo7-daemon[23170]: 2026-11-04T17:00:42.534105Z  WARN oo7_daemon::capability: No process capabilities; relying on RLIMIT_MEMLOCK to lock memory
Nov 04 18:00:42 fedora oo7-daemon[23170]: 2026-11-04T17:00:42.534117Z  WARN oo7_daemon::capability: Failed to lock memory pages (secrets may be swapped to disk): Cannot allocate memory (os error 12)
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.034861Z  INFO oo7_daemon: Starting oo7-daemon
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.034898Z  INFO oo7_daemon::service: Starting PAM listener
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.035118Z  INFO oo7_daemon::pam_listener: PAM listener started on /run/user/1000/oo7-pam.sock
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.035681Z  INFO oo7_daemon::service: Found legacy v0 keyring 'login' at /var/home/david/.local/share/keyrings/login.keyring, registering for migration
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.037228Z  WARN oo7_daemon::service: Failed to migrate v0 keyring 'login': Portal error Incorrect secret or corrupted keyring data. Creating locked placeholder collection.
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.037260Z  INFO oo7_daemon::service: Discovered 1 keyring(s), 1 pending migration(s)
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.037265Z  INFO oo7_daemon::service: Setting up collection 'login' (alias: default).
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.037719Z ERROR oo7_daemon: There is an instance already running. Run with --replace to replace it.
Nov 04 18:00:43 fedora oo7-daemon[23170]: 2026-11-04T17:00:43.037724Z ERROR oo7_daemon: Zbus error name already taken on the bus
Nov 04 18:00:43 fedora oo7-daemon[23170]: Error: Zbus(NameTaken)
Nov 04 18:00:43 fedora systemd[16859]: oo7-daemon.service: Main process exited, code=exited, status=1/FAILURE
Nov 04 18:00:43 fedora systemd[16859]: oo7-daemon.service: Failed with result 'exit-code'.

-----

Deployments:
● fedora:fedora/45/x86_64/silverblue
                  Version: 45.20261104.0 (2026-11-04T00:35:46Z)
               BaseCommit: c458a0735a5ca37ef970b302968d6b2b947995516a6981393f62ef5cd4a0fd34
             GPGSignature: Valid signature by 4F50A6114CD5C6976A7F1179655A4B02F577861E
          LayeredPackages: distrobox niri noctalia

  fedora:fedora/44/x86_64/silverblue
                  Version: 44.20261104.0 (2026-11-04T00:57:10Z)
               BaseCommit: 335c563af02d32c0707c92f129f22150b06d650b566ed4fe930f0c49aff2b69a
             GPGSignature: Valid signature by 36F612DCF27F7D1A48A835E4DBFCF71C6D9F90A6
          LayeredPackages: distrobox niri noctalia

Comment 1 Villy Kruse 2026-11-05 09:26:41 UTC
It may help to uninstall gnome-keyring and gnome-keyring-pam.

Usually gnome-keyring is started by the dbus entry in /usr/share/dbus-1/services/org.gnome.keyring.service
unless oo7 is started first.  `busctl --user status org.freedesktop.secrets` should show which process is
actually running for org.freedesktop.secrets.

Comment 2 bugzillarh-gw0vyr4u 2026-11-08 15:12:30 UTC
(In reply to Villy Kruse from comment #1)
> It may help to uninstall gnome-keyring and gnome-keyring-pam.
> 
> Usually gnome-keyring is started by the dbus entry in
> /usr/share/dbus-1/services/org.gnome.keyring.service
> unless oo7 is started first.  `busctl --user status org.freedesktop.secrets`
> should show which process is
> actually running for org.freedesktop.secrets.

That is not a very nice solution on Silverblue since that means removing the packages from the base image.

Anyway, I have since rebased back on to 44 since I was also having other issues that were introduced in 45. One was the laptop screen turning on with the lid closed.