Your message dated Thu, 17 Sep 2026 20:40:54 +0200
with message-id 
<caaajcmz7e9lfj5pjsonywgtawf3knx97u5xk7jn6fo5vpme...@mail.gmail.com>
and subject line Re: gnome-keyring (version 51.0-1) breaks evolution
has caused the Debian Bug report #1147994,
regarding gnome-keyring: regression in 51.0, keyring assertion failures and 
crash, asks for a password again
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1147994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147994
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-keyring
Version: 51.0-1
Severity: important
X-Debbugs-Cc: [email protected]

Dear Maintainer,

After installing the latest gnome-keyring package, gnome-keyring-daemon
started failing at next session login with the following warning and
error lines in the journal:

% journalctl -b -W |grep gnome-keyring
Sep 17 16:58:51 systemd[2430]: Listening on gnome-keyring-daemon.socket - GNOME 
Keyring daemon.
Sep 17 16:58:51 systemd[2430]: Started gnome-keyring-daemon.service - GNOME 
Keyring daemon.
Sep 17 16:58:51 gnome-keyring-daemon[2498]: 
GNOME_KEYRING_CONTROL=/run/user/60578/keyring
Sep 17 16:59:48 systemd[4999]: Listening on gnome-keyring-daemon.socket - GNOME 
Keyring daemon.
Sep 17 16:59:48 systemd[4999]: Started gnome-keyring-daemon.service - GNOME 
Keyring daemon.
Sep 17 16:59:48 gnome-keyring-daemon[5029]: 
GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 17 16:59:49 gnome-session-service[5179]: App gnome-keyring-pkcs11.desktop 
sets X-GNOME-Autostart-Phase, but gnome-session no longer manages session 
services
Sep 17 16:59:49 gnome-session-service[5179]: App gnome-keyring-secrets.desktop 
sets X-GNOME-Autostart-Phase, but gnome-session no longer manages session 
services
Sep 17 16:59:50 gnome-keyring-daemon[5029]: asked to register item 
/org/freedesktop/secrets/collection/login/27, but it's already registered
Sep 17 16:59:50 gnome-keyring-daemon[5029]: asked to register item 
/org/freedesktop/secrets/collection/login/27, but it's already registered
Sep 17 16:59:50 systemd[4999]: gnome-keyring-daemon.service: Main process 
exited, code=killed, status=11/SEGV
Sep 17 16:59:50 systemd[4999]: gnome-keyring-daemon.service: Failed with result 
'signal'.
Sep 17 16:59:50 kernel: gnome-keyring-d[5029]: segfault at 1 ip 
00007f37acf81482 sp 00007ffdf31a42b0 error 4 in 
libgck-1.so.0.0.0[1d482,7f37acf6e000+1d000] likely on CPU 8 (core 16, socket 0)
Sep 17 16:59:50 systemd[4999]: gnome-keyring-daemon.service: Scheduled restart 
job, restart counter is at 1.
Sep 17 16:59:50 systemd[4999]: Started gnome-keyring-daemon.service - GNOME 
Keyring daemon.
Sep 17 16:59:50 gnome-keyring-daemon[6397]: 
GNOME_KEYRING_CONTROL=/run/user/1000/keyring
Sep 17 16:59:50 gnome-keyring-daemon[6397]: couldn't set environment variable 
in session: GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv 
interface is only available during the Initialization phase
Sep 17 16:59:50 gnome-keyring-daemon[6397]: couldn't set environment variable 
in session: GDBus.Error:org.gnome.SessionManager.NotInInitialization: Setenv 
interface is only available during the Initialization phase
Sep 17 17:00:03 systemd[2430]: Closed gnome-keyring-daemon.socket - GNOME 
Keyring daemon.
Sep 17 17:00:41 gnome-keyring-daemon[6397]: GLib-GIO: 
g_dbus_interface_skeleton_get_object_path: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: 
g_dbus_interface_skeleton_get_object_path: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: GLib-GIO: 
g_dbus_interface_skeleton_get_connection: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: 
g_dbus_interface_skeleton_get_connection: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: GLib-GIO: 
g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' 
failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: g_dbus_connection_emit_signal: 
assertion 'G_IS_DBUS_CONNECTION (connection)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: gkd_secret_service_get_objects: 
assertion 'GKD_SECRET_IS_SERVICE (self)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: gkd_secret_service_get_objects: 
assertion 'GKD_SECRET_IS_SERVICE (self)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: 
gkd_secret_objects_lookup_collection: assertion 'GKD_SECRET_IS_OBJECTS (self)' 
failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: 
gkd_secret_objects_lookup_collection: assertion 'GKD_SECRET_IS_OBJECTS (self)' 
failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: GLib-GIO: 
g_dbus_interface_skeleton_get_object_path: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: 
g_dbus_interface_skeleton_get_object_path: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: GLib-GIO: 
g_dbus_interface_skeleton_get_connection: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: 
g_dbus_interface_skeleton_get_connection: assertion 
'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: GLib-GIO: 
g_dbus_connection_emit_signal: assertion 'G_IS_DBUS_CONNECTION (connection)' 
failed
Sep 17 17:00:41 gnome-keyring-daemon[6397]: g_dbus_connection_emit_signal: 
assertion 'G_IS_DBUS_CONNECTION (connection)' failed

This seems to at least prevent automatic unlocking of the keyring on
login from Gnome.

Do let me know if any other information would be useful. Thanks!


-- System Information:
Debian Release: forky/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 7.1.13+deb14-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-keyring depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.16.2-5+b1
ii  dconf-gsettings-backend [gsettings-backend]   0.49.0-4+b1
ii  gcr                                           3.41.2-6+b1
ii  libc6                                         2.43-5
ii  libgck-1-0                                    3.41.2-6+b1
ii  libgcr-base-3-1                               3.41.2-6+b1
ii  libgcrypt20                                   1.12.3-2
ii  libglib2.0-0t64                               2.90.0-1
ii  libsystemd0                                   262~rc3-1
ii  p11-kit                                       0.26.5-1
ii  pinentry-gnome3                               1.3.3-3

Versions of packages gnome-keyring recommends:
ii  gnome-keyring-pkcs11  51.0-1
ii  libpam-gnome-keyring  51.0-1

gnome-keyring suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 51.0-2

Similar to https://bugs.debian.org/1147940 I can duplicate this issue
with evolution and gnome-keyring 51.0-1 but not with gnome-keyring
51.0-2 so I'm closing this bug.

Thank you,
Jeremy BĂ­cha

--- End Message ---

Reply via email to