>> xscreensaver does not use the MIT SCREEN-SAVER server extension
>> because it is a flaky, unreliable piece of shit that tends to cause
>> the sever to crash.
>
> Is it still the case after 7 years?
I suppose somewhere in the multiverse there is a world where the
MIT-SCREEN-SAVER extension is
Jamie Zawinski :
> xscreensaver does not use the MIT SCREEN-SAVER server extension
> because it is a flaky, unreliable piece of shit that tends to cause
> the sever to crash.
Is it still the case after 7 years?
Also, the workaround given by the submitter no longer works, I use this
instead:
$ c
On Mon, Jan 05, 2015 at 01:51:14PM -0800, Jamie Zawinski wrote:
> xscreensaver does not use the MIT SCREEN-SAVER server extension because it is
> a flaky, unreliable piece of shit that tends to cause the sever to crash.
Good to know. What about a conditional on DPMS state (and then not
ever sett
xscreensaver does not use the MIT SCREEN-SAVER server extension because it is a
flaky, unreliable piece of shit that tends to cause the sever to crash.
> which is ugly.
Does it work? Yes? Then it's not ugly.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
Package: xscreensaver
Version: 5.30-1+b1
Severity: wishlist
It would be nice if, on systems that support it, xscreensaver could
check XScreenSaverQueryInfo() and avoid blanking/locking accordingly.
This would allow me to stop using
mpv --heartbeat-cmd="xscreensaver-command -deactivate"
which
5 matches
Mail list logo
