In <[🔎] 20101014013309.GA25499@khazad-dum.debian.net>, Henrique de Moraes Holschuh wrote: >On Wed, 13 Oct 2010, Celejar wrote: >> Interesting, thanks. The look I don't really care about, and switching >> users isn't relevant for me, since I'm the only user of the system. >> The xscreensaver author has a low opinion of gnome-screensaver: >> >> http://www.jwz.org/xscreensaver/faq.html#gnome-screensaver >> http://www.jwz.org/xscreensaver/toolkits.html >> >> But I have no idea how serious his concerns are, and whether they are >> uptodate for current gnome-screensaver. > >I am not sure about the gnome screensaver, but he is spot on about >bells-and-whistles-focused unsafe dekstop environment crap being a security >hazard, and it DOES apply to KDE4's screensaver. > >I've seen the KDE4 screensaver: > >1. Fail to activate, especially if there is a large IO load in 2.6.32's crap >CFQ io scheduler + ext4. This is not surprising, as KDE4 fails to even >switch window *focus* in a heavy IO load, which is utterly insane. Why the >heck does the window manager have to hit the disk to change windows focus?! +1 >2. Leak information (i.e. show the workspace) both when activating (blinks), >and when going out of DPMS or redrawing the screen. Doesn't happen always, >but still... +1 >4. delay its activation for weird reasons, leaving everything unlocked. +1; I've come back to my system HOURS later to find it either unlocked or doesn't require a password to unlock. >The KDE4 screensaver has more race conditions than multithreaded code >written by someone who thinks "volatile int" a semasphore make. And they aren't "theoretical" problems, I've definitely seen all three of the above on my own hardware. Perhaps I should switch to XScreenSaver instead. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.