Public bug reported:
Summary: Seahorse fails to display "Login" keyring despite working
Secret Service backend
Package: seahorse 47.0.1-3build1
GnuPG: 2.4.8
Ubuntu: 26.04 "Resolute Raccoon"
Desktop: GNOME Shell 50, Wayland session (GNOME 50 has no X11 session option)
gnome-keyring-daemon: running with components=pkcs11,secrets (ssh moved to
gcr-ssh-agent, expected as of gnome-keyring 46+)
--- Issue ---
Seahorse's Passwords view does not show the "Login" keyring, despite the
underlying keyring file and Secret Service collection existing and functioning
correctly. When opening Seahorse from a terminal, the following warning
appears around the time the login collection should load:
g_task_return_error: assertion '!task->ever_returned' failed
This is consistent with a GTask misuse bug in Seahorse's collection-loading
code (similar to a previously reported crash pattern in other Seahorse GTask
issues), not a problem with gnome-keyring or the Secret Service itself.
--- Verification that the backend is healthy (not a config issue) ---
1. Login keyring file exists with correct ownership/permissions:
~/.local/share/keyrings/login.keyring
~/.local/share/keyrings/user.keystore
2. gnome-keyring-daemon is running and PAM-unlocking correctly at login
(no keyring password prompts on normal login).
3. secret-tool store/lookup/clear all succeed against the Secret Service:
secret-tool store --label="verify-test" service verify-test username
verify-test
secret-tool lookup service verify-test username verify-test
secret-tool clear service verify-test username verify-test
4. gdbus confirms the "login" collection is exposed by the running daemon:
gdbus call --session --dest org.freedesktop.secrets \
--object-path /org/freedesktop/secrets \
--method org.freedesktop.DBus.Properties.Get \
org.freedesktop.Secret.Service Collections
-> lists /org/freedesktop/secrets/collection/login
5. The "default" alias correctly resolves to that login collection:
gdbus call --session --dest org.freedesktop.secrets \
--object-path /org/freedesktop/secrets \
--method org.freedesktop.Secret.Service.ReadAlias "default"
-> resolves to the login collection object path
6. SSH key generation, loading into gcr-ssh-agent, and GitHub SSH
authentication all work end-to-end without repeated password prompts,
confirming credentials persist and unlock correctly across the session.
--- Steps to reproduce ---
1. Fresh Ubuntu 26.04 install, standard GDM login (no auto-login).
2. Open Seahorse (Passwords and Keys).
3. Select "Passwords" view.
4. "Login" keyring does not appear in the list, though the file and
Secret Service collection both exist and are functional via CLI tools.
--- Expected behavior ---
Seahorse should display the "Login" keyring entry under Passwords, matching
what secret-tool and gdbus already show is correctly running and unlocked.
--- Additional notes ---
apport-gtk also throws a Wayland-specific GDK warning when launching the bug
reporter under this session:
gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
'GDK_IS_WAYLAND_WINDOW (window)' failed
This appears unrelated to the core Seahorse bug and did not prevent the
report from being collected, only slowed the process.
** Affects: seahorse (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2167187
Title:
login in seahorse is missing after upgrading from 24.04 to 26.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/2167187/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
