Bug#921835: xfce4-screensaver: wastes CPU while the display is off
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
[adding Jonathan to CC just in case]
On Sat, 2019-02-09 at 11:53 +0100, Adam Borowski wrote:
> Package: xfce4-screensaver
> Version: 0.1.3-2
> Severity: normal
>
> I left home for the weekend, just ssh-ed in and I see:
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 2375 root 20 0 823412 223376 169752 R 96.3 2.7 1946:54 Xorg
> 24967 kilobyte 20 0 31540 5736 4496 R 34.9 0.1 1:26.92 zoom
> 24966 kilobyte 20 0 31144 5188 4320 S 28.2 0.1 1:11.75 zoom
>
> The screen has been locked for nearly a day, thus it's obviously off (which
> I can't verify). For further information, I left this bug report
> half-written for while; the screensaver has in the meantime rolled over to
> something else that takes just 20% X + 2*7% for screensavers proper, then to
> euler3d at 27% X + 2*13%. That's better than nearly two full cores as for
> zoom, but the question is: why?
I think you should be able to disable the screensavers or to just select
“blank screen” instead of letting xfce4-screensaver select a random one.
>
> Once the monitor gets suspended/slept/powered off, there's completely no
> point in drawing anything. On the other hand, a computer with two cores
> worth of activity for a prolonged time wastes a significant amount of
> electricity, which is bad both for the environment and for users' wallets.
>
> Thus: could you please stop spawning new "draw something" processes once
> the saver has gone past the first (visual) stage?
Agreed, but this is likely a bug in mate-screensaver (or whatever the code
originally comes from). Jonathan, could you take a look?
Honestly I'd be just fine in just disabling all the screensavers and only keep
blank screen.
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlxunWsACgkQ3rYcyPpX
RFt3GQgApKbQikJenbR7HWxDzZxsIG5LvMbcXcIWht5F9H6Oh/rE738OrrRFK6gi
DrrajXUfPTw/wCCNDIcP7Jb/kGpjtCK2kmAyNyecgpEwuz1xibWtcgg+0L0wdN79
I/xvt5v9fVHyPG+J4G+IZ4D0LUwy3aByL0MYfXLL8jqH27v6jPhczRB8Va6D59yK
bGhpzN7YGINroL7/6p8lBvXjNBVw2Z0sD0Rb71L34320A2GbYkyjJ5sNzFVfyJwk
2v35TOVST4touwHIQQdUIgC3Qckg4IoVN7OF2HtolJLhXXPZASRsXLbdoX0NEVIV
I5TdbN5duJJvX8BQ5DBQoQbEW3HP4A==
=8kOA
-----END PGP SIGNATURE-----
Reply to: