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

Quack,

For some reason I did not find that out during my tests, sorry.

There is already a bug for this, #1142693 (but you cannot see it because
of #636689, so I won't merge it), and it was reassigned because there's
no reason this config is only half available in common-* and we should
not have to add this manually in all login managers.

Regards.
\_o<

Hi,
unsurprisingly, this has broken the unlock in kwallet, as well.

Besides the failed regression tests, does this mean that
libpam-gnome-keyring and libpam-kwallet5 are now expected to ship such
PAM configuration themselves?

Kind regards
Marco

Quack,

Some information about the current course of action.

I was surprised GNOME keyring did not work as the configuration is there
but it is incomplete and it is being fixed in #1142693.

As for kwallet I opened #1144267 and hopefully it will be solved soon.

Regards.
\_o<