On 1/4/19 9:24 AM, Frédéric Pierret wrote:

On 1/4/19 1:51 AM, unman wrote:
On Fri, Jan 04, 2019 at 12:03:49AM +0100, Frédéric Pierret wrote:
We built the upstream package of xscreensaver in current-testing for
both Qubes 3.2 and 4.0.

Welcome back to XFCE Chris :D !

On 1/3/19 11:56 PM, Chris Laprise wrote:
On 01/03/2019 02:00 PM, Achim Patzner wrote:
Am Mittwoch, den 02.01.2019, 20:42 -0800 schrieb pixel fairy:
xscreensaver complains about being an old version. doubt this
matters, but might scare some users.
There are worse problems with it (and some of them depend on X and the
hardware you're running on) which might also warrant finding something
different. I just have to find some time for constant rebooting of my
system to create a meaningful bug report.

(To give you an idea: Imagine a machine (let's call it Lenovo P52) with
multiple GPUs where certain output channels are connected to one of the
GPUs only starting a screen server. If you connect your second monitor
to the right port the screen saver will not blank one of them if you
start X without an appropriately xorg.conf... And to make things worse
it also depends on the GPU you are using and the phase of the moon.)
The bad screensaver is one of the reasons I switched back to KDE, and
why I recommend it to other Qubes users. The default environment
doesn't rise to the level of an every day functional desktop.

I fully agree - xscreensaver has lots of issues. Many of the screensavers do though. E.g. most won't survive an X server crash due to e.g. OOM killer, but your X server will probably be restarted automatically and leave your screen unprotected...

In total it's not wise to trust one's screensaver for anything sincere.

Is this a thing now? Is Qubes going to provide updated packages for any
other software?

Absolutely not. It is just because it is annoying, at least, under XFCE.


--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/fa3bf1a3-9d4d-b859-746b-89e7a7c029eb%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to