Package: xautolock
Version: 1:2.2-8
Followup-For: Bug #1070663
X-Debbugs-Cc: ajq...@debian.org


Hi Martin and Nathan,

I have tried to run the xautolock process manually with the xsecurelock
and also i3lock-fancy with both examples you provided on a clean
installed trixie rc1 lxqt desktop.

However I cannot reproduce the issue. Both example works and screen
locked with -locknow option. And the -time option also works when
the desktop idle in the minutes specify.

And this is duplicate with #1022781 that already has tags:
moreinfo, security, unreproducible.

The only different from #1022781 is the version was 1:2.2-7.

Here is the changelog:
xautolock (1:2.2-8) unstable; urgency=medium

  [ Debian Janitor ]
  * Fix day-of-week for changelog entry 1:2.2-5.3.
  * Remove constraints unnecessary since buster:
    + Build-Depends: Drop versioned constraint on dpkg-dev and xutils-dev.

  [ Santiago Ruano Rincón ]
  * Fix stray backslash in debian/tests/help (Closes: #1022971)

 -- Antoni Villalonga <ant...@friki.cat>  Sat, 29 Oct 2022 23:18:35 +0000

Doesnʼt look like any additional patch will change the behavior of the
screen locker.

I think itʼs better to merge this with #1022781 or at least lower the
severity to unblock for trixie.

Best regards,

-Andrew

Reply via email to