Package: libpam-gnome-keyring Version: 51.1-3 Severity: normal X-Debbugs-Cc: [email protected]
Dear Maintainer, I'm running greetd and labwc. Over the last few days, after logging in as a regular user, when I run 'su -' to become root and when I run 'exit' to return to my user the switch to root succeeds and the root session closes normally but the following messages are reproduced: "The gnome keyring socket is not owned with the same credentials as the user login: /run/user/1000/keyring/control gkr-pam: couldn't unlock the login keyring." The warnings appear twice, when opening and closing the root session. The session itself works normally. - `gnome-keyring` 51.1-3 - `libpam-gnome-keyring` 51.1-3 - `greetd` 0.10.3-7 - `libpam0g` 1.7.0-8 Steps to reproduce: 1. Log in through greetd. 2. Run `su -` in a terminal and authenticate as root. 3. Exit the root shell. 4. Check journalctl. This may be related to Debian bug [#1142693], although I cannot confirm that it has the same cause. Please clarify whether this behaviour is expected or indicates a PAM integration issue. Thanks! -- System Information: Debian Release: forky/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 7.2.9+deb14-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CPU_OUT_OF_SPEC Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to es_ES.UTF-8), LANGUAGE=es_ES:es Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libpam-gnome-keyring depends on: ii libc6 2.43-7 ii libpam-runtime 1.7.0-8 ii libpam0g 1.7.0-8 ii libselinux1 3.11-2.1 Versions of packages libpam-gnome-keyring recommends: ii gnome-keyring 51.1-3 libpam-gnome-keyring suggests no packages. -- no debconf information
