Bug 461926 - webcollage screen saver displaying pornography
Summary: webcollage screen saver displaying pornography
Alias: None
Product: Fedora
Classification: Fedora
Component: kdeartwork
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
Depends On: 472061
TreeView+ depends on / blocked
Reported: 2008-09-11 13:56 UTC by Darryl L. Pierce
Modified: 2015-06-22 00:06 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-11-18 14:48:24 UTC
Type: ---

Attachments (Terms of Use)

Description Darryl L. Pierce 2008-09-11 13:56:04 UTC
Description of problem:
On a development machine I use KDE. I had the screensaver set to random. 

This morning I came back to that machine to find that the screensaver had kicked in and was running web collage. And the images being displayed were pornographic and very explicit. 

I do *not* browse porn sites on that machine, and it does not share any data with other machines and is used solely for testing code. 

Version-Release number of selected component (if applicable):

How reproducible:
Not sure how to get it to redisplay those images, but I would prefer that the app allow the user to decide what sites to visit rather than randomly downloading images.

Comment 1 Rex Dieter 2008-09-11 14:51:48 UTC
Ugh, this problem existed in kde3 (and we hacked around it), and I thought it was addressed in kde4.

Comment 2 Steven M. Parrish 2008-09-28 21:12:30 UTC
Bumped the priority up.  Need to address this before Fedora gets a NC17 rating.

Comment 3 Rex Dieter 2008-09-29 01:49:17 UTC
I think the approach we're going to take is
1.  include a temporary hack/workround (as we did with kde3)
2.  bug xscreensaver maintainer to make webcolloage choose a better default for itself, so that xscreensaver users/consumers (like kscreensaver) don't need to add workarounds forever.

Comment 4 Than Ngo 2008-11-18 14:48:24 UTC
drop webcollage screen saver in kdeartwork-4_1_3-2_fc10/fc9

Note You need to log in before you can comment on or make changes to this bug.