/etc/xdg/autostart/lxqt-xscreensaver-autostart.desktop - really?

[agaida]

Expected Behavior

Until now i thought that we was indipendend of xscreensaver and use xdg-screensaver in all places.

Current Behavior

It seems that we give a damn to any other screensaver

Possible Solution

No clue, but - maybe we should refine this

Context

I have no problem with xscreensaver - beside the fact that the screensaver jump in to late - so it is theoretical possible to see the locked user screen (data leak, worst case an open confidential document or open passwordmanager with the passwords in cleartext). If possible i would like to have this issue solved before the next release.

System Information

Current

[Vladimir-csp]

Suggestion: handle this directly in lxqt-session. With configurable commands. Defaults would be: screensaver daemon: xscreensaver -no-splash screensaver activation: xdg-screensaver activate lock screen: xdg-screensaver lock

If a command is empty, associated function would be disabled. User could put alternative lockers, screensavers, etc, with benefit of lxqt-session caring about events and sequences. Like using just i3lock directly as a locker, or xss-lock as a daemon + loginctl as a locker.