Bug 242266

Summary: Random screen saver, forbidden "manipulate screen", sometimes uses Flipscreen3d
Product: [Unmaintained] kscreensaver Reporter: Christopher Neufeld <kdebugs>
Component: generalAssignee: kscreensaver bugs tracking <kscreensaver-bugs-null>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In: 4.5.3
Sentry Crash Report:

Description Christopher Neufeld 2010-06-20 16:49:35 UTC
Version:           unspecified (using Devel) 
OS:                Linux

I have set my screensaver to "random", with the condition that it not include savers that manipulate the screen.  Recently, I've seen the screen saver start up with a saver that does retain the screen contents.  The screen saver is Flipscreen3d, or another one that behaves exactly the same way.  This screen saver should have been forbidden from starting up.  This is a potential security problem, as the settings were deliberately chosen to prevent the screen contents from being visible once the screen saver started up.

I note that kdeartwork/kscreensaver/kxsconfig/ScreenSavers/flipscreen3d.desktop has this line in it:
X-KDE-Type=OpenGL;ManipulateScreen

so either that line is not being correctly parsed, that setting is being ignored, or there is another screensaver that looks like flipscreen3d but which doesn't have this option set.

Reproducible: Sometimes

Steps to Reproduce:
Set up the screen saver for "random", adjust its options to forbid screen savers that manipulate the screen.  Set a low timeout on the screen saver, then watch it start up over and over again until it hits the Flipscreen3d.  When that happens, the desktop image will appear to recede, being surrounded by a dark border, after which time it will start to flip through the void like a playing card printed with the desktop contents.
Comment 1 Christopher Neufeld 2010-06-22 21:04:18 UTC
So, I've gone into the screen saver setup page, selected "random", excluded those savers that manipulate the screen, and then just started hitting 'test' over and over again.

Among the screen savers used were MirrorBlob and AntInspect, which also should have been excluded.
Comment 2 Oswald Buddenhagen 2010-10-23 18:52:25 UTC
SVN commit 1188997 by ossi:

fix terminally broken type exclusion logic

if a screensaver had multiple types, they'd all have to be forbidden to
actually exclude it.

BUG: 242266
FIXED-IN: 4.5.3



 M  +12 -18    random.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1188997