Fedora 45 installation issue : oo7 secrets service provider

Ask Fedora
,
1

After installing Fedora 45 Workstation I was not able to add any entries to the keyring.

I found that gnome-keyring was not installed and oo7 service didn’t seem to work.

It wasn’t possible to add online accounts, import gpg keys, ssh into systems.

After installing gnome-keyring and gnome-keyring-pam everything works as expected.

Also, before I installed gnome-keyring, the login section in seahorse was missing.

Upgrading from F44 is not affected, because gnome-keyring is still installed.

After some further investigation I realized that no keyring exists on a fresh installation.

oo7 service doesn’t create a keyring - and there was no other way to create one.

At least I couldn’t find a way. Moving to oo7 service was a bit early, maybe ?

3

Have you tried what described here instead of installing gnome-keyring ?

4

Yes, I have enabled the service, although it was already loaded, active, and running.

The problem seems to be that oo7 does not create a keyring on a fresh installation.

5

I had this issue, and I kind of took a nucular approach.

Reset Keyring: Navigate to Passwords > Login, right-click the Login keyring, and select Change Password. Set the new password to match your current user account password. (This is not enough, but maybe for you it is.)

So I cleared everything by:

gio trash ~/.local/share/keyrings/

This will create a new keyring with the correct password. (After logging out and back in) I did back-up that file first. :slight_smile:
Good Luck @clnetbox

6

Thank you, Rick ! Unfortunately not. I removed the ~/.local/share/keyrings directory.

Then I logged out and back in. No new keyring was created. Exactly that is the issue.

7

You would still have a problem if you create a new user. Then something needs to initialize the keyring for that user.

8

My test confirms that.

9

Interesting, is it located anywhere here?

systemctl --user status

Or this:

systemd-analyze verify /usr/lib/systemd/user/oo7-daemon.service

Also are you opposed to using seahorse?

10

The problem that seahorse needs to talk to the daemon to do anything and oo7 wont start when there is no keyring. Also oo7 just fails with no message what so ever in the journal log.

11

I did not keep Gnome Long, But that all makes sense @vekruse

A developer’s work is never done. :slight_smile:

12

That’s true, Villy. Without gnome-keyring being installed, a new user is affected of course.

But on an upgraded system, gnome-keyring and gnome-keyring-pam should be installed.

13

Not on atomic versions.

14

Hum? It still seems to function on my end:

systemctl --user status oo7-daemon.service
● 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 Mon 2026-09-21 09:58:33 MDT; 2min 12s ago
 Invocation: 386a42de82504f268ef0d7091ec0e71e
   Main PID: 110277 (oo7-daemon)
      Tasks: 13 (limit: 18789)
     Memory: 8.9M (peak: 10.4M)
        CPU: 120ms
     CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/oo7-daemon.service
             └─110277 /usr/libexec/oo7-daemon

Sep 21 09:58:33 fedora oo7-daemon[110277]: 2026-09-21T15:58:33.941605Z  INFO oo7_daemon::service: Setting up >
Sep 21 09:58:33 fedora oo7-daemon[110277]: 2026-09-21T15:58:33.941641Z  INFO oo7_daemon::service: Setting up >
Sep 21 09:58:36 fedora oo7-daemon[110277]: 2026-09-21T15:58:36.528705Z  INFO oo7_daemon::service: Client :1.3>
Sep 21 09:58:36 fedora oo7-daemon[110277]: 2026-09-21T15:58:36.529216Z  INFO oo7_daemon::service: Client :1.3>
Sep 21 09:58:37 fedora oo7-daemon[110277]: 2026-09-21T15:58:37.741914Z  INFO oo7_daemon::service: Client :1.3>
Sep 21 09:58:37 fedora oo7-daemon[110277]: 2026-09-21T15:58:37.745041Z  INFO create_item{label="Surfshark/ini>
Sep 21 09:58:37 fedora oo7-daemon[110277]: 2026-09-21T15:58:37.745141Z  INFO oo7_daemon::collection: Item `/o>
Sep 21 09:58:37 fedora oo7-daemon[110277]: 2026-09-21T15:58:37.752657Z  INFO create_item{label="Surfshark/sto>
Sep 21 09:58:37 fedora oo7-daemon[110277]: 2026-09-21T15:58:37.752785Z  INFO oo7_daemon::collection: Item `/o>
Sep 21 10:00:02 fedora systemd[1845]: Started oo7-daemon.service - Secret service (oo7 implementation).

This one has my interest!

dnf info  gnome-keyring gnome-keyring-pam
Updating and loading repositories:
Repositories loaded.
Available packages
Name           : gnome-keyring
Epoch          : 0
Version        : 50.0
Release        : 6.fc45
Architecture   : x86_64
Download size  : 868.7 KiB
Installed size : 3.5 MiB
Source         : gnome-keyring-50.0-6.fc45.src.rpm
Repository     : fedora
Summary        : Framework for managing passwords and other secrets
URL            : https://wiki.gnome.org/Projects/GnomeKeyring
License        : GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later AND ((GPL-2.0-or-later OR LGPL-3.0-or
               : -later) OR BSD-3-Clause) AND (MPL-1.1 OR GPL-2.0-or-later OR LGPL-2.1-or-later)
Description    : The gnome-keyring session daemon manages passwords and other types of
               : secrets for the user, storing them encrypted with a main password.
               : Applications can use the gnome-keyring library to integrate with the keyring.
Vendor         : Fedora Project

Name           : gnome-keyring-pam
Epoch          : 0
Version        : 50.0
Release        : 6.fc45
Architecture   : x86_64
Download size  : 20.7 KiB
Installed size : 31.4 KiB
Source         : gnome-keyring-50.0-6.fc45.src.rpm
Repository     : fedora
Summary        : Pam module for unlocking keyrings
URL            : https://wiki.gnome.org/Projects/GnomeKeyring
License        : LGPL-2.1-or-later
Description    : The gnome-keyring-pam package contains a pam module that can
               : automatically unlock the "login" keyring when the user logs in.
Vendor         : Fedora Project

I installed these:

dnf4 list installed gnome-keyring-pam gnome-keyringWarning: Enforcing GPG signature check globally as per active RPM security policy (see 'gpgcheck' in dnf.conf(5) for how to squelch this message)
History database is not readable, using in-memory database instead: SQLite error on "/var/lib/dnf/history.sqlite": Open failed: unable to open database file
Installed Packages
gnome-keyring.x86_64                                      50.0-6.fc45                                  @System
gnome-keyring-pam.x86_64                                  50.0-6.fc45                                  @System

After A complete removal:

Removing oo7-daemon-0:0.7.0~alpha-1.fc45.x86_64               100% |
15

For reference: 2537341 – oo7-portal not installed by default after upgrading to f45

16

Also accepted a release blocking bug: Making sure you're not a bot!
This will (likely) be fixed before release of f45.

17

Tested again this morning, and suddenly oo7 can create a missing keyring file.

18

I tried it again too … unfortunately without luck, no new keyring was created.

Also, after removing gnome-keyring, seahorse doesn’t even launch anymore.

19

Strange, because seahorse doesn’t require gnome-keyring, just the dbus service org.freedesktop.secrets.

20

There is an updated package available. Can you update and test again @clnetbox ?

https://bodhi.fedoraproject.org/updates/FEDORA-2026-324f1dc298

21

I have updated all packages available from updates-testing (including that one).

Nothing changed, I deleted the keyring, logged out and back in, no new keyring.