Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I believe this happens since the upgrade from bookworm to trixie


   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Unlock my screen, providing my password.

   * What was the outcome of this action?
The screen is unlocked and the following error is logged to auth.log:
xscreensaver-auth: pam_unix(xscreensaver:account): setuid failed: Operation not
permitted

   * What outcome did you expect instead?
No error to be logged, as unlocking seems to work as normal, and
/usr/libexec/xscreensaver/xscreensaver-auth _is_ already setuid. I also tried
to unlock with the wrong password, which fails. So the xscreensaver software
and package seems to work find, regardless of the error that is logged.

Thanks for the work on Debian.