Version: unspecified (using KDE 4.5.4) OS: Linux Originally reported here: http://bugs.gentoo.org/show_bug.cgi?id=333677 Problem: Webcollage screensaver (from xscreensavers) when installed is enabled in the default random screensaver mode in KDE-4.4.5. xscreensavers itself installs, but does not enable WebCollage in random mode because of the potential for illegal and/or inappropriate content it may display. KDE's handling of Webcollage screensaver is inconsistent with xscreensaver. Background: Webcollage works by downloading random images from the Internet and displaying them. The kinds of images Webcollage shows may include pornography and illegal images such as snuff and child porn. Webcollage is inappropriate as a screensaver for offices, schools, and any computer used by children. I found this out at work when porn images started displaying on my screen. Reproducible: Always Steps to Reproduce: Install of KDE. Install xscreensavers. Wait for Webcollage to run in random mode. Actual Results: Pornography was displayed on my computer screen. Expected Results: Webcollage should not run in KDE "random screensaver" mode. This is how the xscreensavers package behaves (where Webcollage comes from). https://bugzilla.redhat.com/show_bug.cgi?id=472061 http://www.fedoraforum.org/forum/showthread.php?page=1&t=147840 http://lists.debian.org/debian-project/2005/06/msg00031.html http://www.jwz.org/webcollage/explain.html
Created attachment 55776 [details] patch to disable "not safe for work" screensavers in random selection
Created attachment 55777 [details] patch to tag webcollage "not safe for work"
Please consider committing the attached patches (changing 5 lines of code). As you can see, disabling/enabling "not safe for work" screensavers could be trivially made configureable, similar to disabling/enabling OpenGL screensavers.
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more. I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.