:: Re: [DNG] Question re: screen blank…
Inizio della pagina
Delete this message
Reply to this message
Autore: o1bigtenor
Data:  
To: Devuan ML
Oggetto: Re: [DNG] Question re: screen blanking and shutoff
On Sat, Sep 3, 2022 at 6:26 AM onefang <onefang_devuan@???> wrote:
>
> For what it's worth I just discovered that xscreensaver now has
> xscreensaver-systemd, and is running on my Chimaera desktop. "The
> xscreensaver-systemd program is a helper program to integrate
> xscreensaver with systemd(1)."
>


I dunno if this will help mr onefang but here is a present day report.

I have found that there is a large difference in screensaver operation
depending upon the browsers being used.
There are 'only' some 7 - - - or is that 8 different browsers available for
use in my system. Four of which I use most all the time.

Perhaps my use of system resources also adds to the issue so will also
describe this.

I have some 5 monitors (4 - 1920x1080s and 1 4k) running from a
Ryzen 570X. I have a plethora of desktops (well over 25!!!).

Firefox allows me to use browser windows on more than one desktop
and only occasionally causes issues (usually when there is a version
update but that's a different peeve). The other three all use a
Chrome (maybe a Chromium but their literature says Chrome) backend
with their 'stuff' as a frontend. For these three the windows are only used
one 1 (!!!!) desktop as a reboot does NOT place the windows on the
previous desktops used. These three browser are Opera, Brave and
Vivaldi. Opera is the most pita out of the three in that it likes blocking
the use of a screensaver (will not allow a screen shut off just goes
to the pretty blips part of the screen saver).

When I first reported this behavior the suggestion was given to just
use a 'kill' on the browsers, followed by a restart on each, to get the
screensaver system operational. Well for the last about month I
just kill Opera and restart it and my screensaver system is back.

IMHO the programming to requires this kind of usage - - - well its
most definitely NOT good.

I do have a relatively easy work around (as outlined in this email)
but it sure would be nice if it were fixed.

I'm guessing that it never will be fixed as that would require putting
some limits on Javascript - - - and why would anyone want that - -
- - - right.

Thank you to monsieur Ludovic Bellière and this community for
their assistance.

Keep on keeping on!