Package: greetd
Version: 0.10.3-6
Severity: normal
Due to the removal of the common setup
812b3b6 ("Use PAM common-session and remove all custom entries")
greetd no longer unlocks the keyring for the user.
Using
@include common-auth
@include common-account
auth optional pam_gnome_keyring.so
@include common-session
session optional pam_gnome_keyring.so auto_start
gets things back to normal again.
A NEWS.Debian entry explainging that
[general]
service = ….
allows to bring back the old behavior would be useful.
Cheers,
-- Guido
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable-debug'), (500,
'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64
Kernel: Linux 7.0.12+deb14.1-amd64 (SMP w/22 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 greetd depends on:
ii debconf [debconf-2.0] 1.5.92
ii libc6 2.42-17
ii libgcc-s1 16.1.0-2
ii libpam0g 1.7.0-6
ii systemd [systemd-tmpfiles] 261.1-3
greetd recommends no packages.
Versions of packages greetd suggests:
pn wlgreet <none>
-- debconf information excluded
