(Solved) Can't unlock keyring with Seahorse

hello, from yesterday, seems like i can’t unlock my keyring anymore, and as such, cannot read my emails and so on

i always get this error

tried also deleting it, and tried to use keyrack but have always the same problem (destination does not exist)

is this a known bug?if not any hint on how to solve it, or where to report it?

for the record i am on f45 beta workstation and everything was working as it should till two days ago…

did what you describe and the service work for as long as the computer is on, but as soon as i reboot or power off, i’m in the same situation

with this i was able to delete the keyring but incredibily when rebooted it was still there…

thank you for your link, i tried what’s suggested but i still had no luck

checking the status i always get a

systemctl status --user oo7-daemon
● oo7-daemon.service - Secret service (oo7 implementation)
Loaded: loaded (/usr/lib/systemd/user/oo7-daemon.service; enable>
Drop-In: /usr/lib/systemd/user/dbus-.service.d
└─00-uresourced.conf
/usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: active (running) since Sun 2026-09-20 16:19:33 CEST; 2mi>
Invocation: 1bb9e247eea24472bf620680ffbdde2f
Main PID: 12105 (oo7-daemon)
Tasks: 17 (limit: 18951)
Memory: 2.8M (peak: 4.7M)
CPU: 66ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/>
└─12105 /usr/libexec/oo7-daemon

set 20 16:19:33 fedora oo7-daemon[12105]: 2026-09-20T14:19:33.761657Z>
lines 1-16
● oo7-daemon.service - Secret service (oo7 implementation)
Loaded: loaded (/usr/lib/systemd/user/oo7-daemon.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/dbus-.service.d
└─00-uresourced.conf
/usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: active (running) since Sun 2026-09-20 16:19:33 CEST; 2min 51s ago
Invocation: 1bb9e247eea24472bf620680ffbdde2f
Main PID: 12105 (oo7-daemon)
Tasks: 17 (limit: 18951)
Memory: 2.8M (peak: 4.7M)
CPU: 66ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/oo7-daemon.service
└─12105 /usr/libexec/oo7-daemon

set 20 16:19:33 fedora oo7-daemon[12105]: 2026-09-20T14:19:33.761657Z INFO oo7_daemon::service: No keyrings discovered in data directory
set 20 16:19:33 fedora oo7-daemon[12105]: 2026-09-20T14:19:33.761665Z INFO oo7_daemon::service: No default collection found, creating ‘Login’ keyring
set 20 16:19:33 fedora oo7-daemon[12105]: 2026-09-20T14:19:33.761692Z INFO oo7_daemon::service: Created default ‘Login’ collection (unlocked)
set 20 16:19:33 fedora oo7-daemon[12105]: 2026-09-20T14:19:33.761695Z INFO oo7_daemon::service: Setting up collection ‘login’ (alias: default).
set 20 16:19:34 fedora oo7-daemon[12105]: 2026-09-20T14:19:34.641863Z INFO oo7_daemon::service: Client :1.52 (goa-daemon[12404]) connected, session: /org/freedesktop/secrets/session/s0
set 20 16:19:40 fedora oo7-daemon[12105]: 2026-09-20T14:19:40.402382Z INFO oo7_daemon::service: Client :1.82 (seahorse[14499]) connected, session: /org/freedesktop/secrets/session/s1
set 20 16:20:10 fedora oo7-daemon[12105]: 2026-09-20T14:20:10.042719Z INFO oo7_daemon::service: Client :1.82 (seahorse[14499]) disconnected. Session: /org/freedesktop/secrets/session/s1 mark>
set 20 16:20:10 fedora oo7-daemon[12105]: 2026-09-20T14:20:10.048056Z INFO oo7_daemon::service: Client :1.82 (seahorse[14499]) disconnected. Session: /org/freedesktop/secrets/session/s1 mark>
set 20 16:21:33 fedora oo7-daemon[12105]: 2026-09-20T14:21:33.775387Z INFO oo7_daemon::session: Closing session /org/freedesktop/secrets/session/s1 for :1.82.
set 20 16:21:33 fedora oo7-daemon[12105]: 2026-09-20T14:21:33.775421Z INFO oo7_daemon::service: Stale session /org/freedesktop/secrets/session/s1 cleaned up.

and i can’t delete or unlock the keyring…

Can you run the command busctl --user |grep org.freedesktop.secrets and check which program is providing the secret service.

sure, here’s the answer

busctl --user |grep org.freedesktop.secrets
org.freedesktop.secrets                                                                                1315 oo7-daemon      legacychimera247 :1.1          user@1000.service -       -

ok so, my general keyring has always been empty, i don’t like having to put the password for everything like opening the browser or connecting to a wifi, so the general keyring is empty, but my system password is 15 character, so i guess that shouldn’t matter?

i mean, the login keyring is unlocked with that, or do i still need to set a non empty password?

EDIT: seems like restarting the service let me unlock the keyring but as soon as i reboot, everything is back as it was…

just writing here to note i solved the problem with the help of a very nice (and patient) user on reddit

the solution is in the post if someone is interested

Solution from the linked post.
Thanks.