Bug 75919 - kscreensaver "Random" theme shows blank screen
kscreensaver "Random" theme shows blank screen
Product: Red Hat Linux
Classification: Retired
Component: kdebase (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Ngo Than
Ben Levenson
Depends On:
  Show dependency treegraph
Reported: 2002-10-14 19:44 EDT by Joel Doerr
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-10-16 05:11:56 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joel Doerr 2002-10-14 19:44:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020830

Description of problem:
When selecting a single screensaver, such as "The Matrix", screen saver works
properly, but when selecting "Random" theme, screen goes blank.

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

How reproducible:

Steps to Reproduce:
1.Right-click on Desktop, select "Configure Desktop..."
2."X Settings - KDE Control Module" window pops up. Select 
  "Screensaver" from left panel.
3.Select "Random"screen saver from the list box.
4.Click "Test" to verify screen saver works. (Screen goes blank).
5.Leave setting "Wait for" at 5 min. (Timeout does not matter).
6.Click "OK"
7.Wait 5 minutes, and screen will go blank.

Actual Results:  Screen saver "Random" theme does not work. Screen goes blank.

Expected Results:  Screen should have shown one of the available screen savers.

Additional info:

Results found AFTER installing following packages:

Comment 1 Rafael Wysocki 2002-10-16 05:11:50 EDT
This applies to _all_ kscreensaver themes, on all the _three_ RH 8.0 systems I 
Comment 2 Ngo Than 2002-10-16 07:11:16 EDT
It's fixed in 3.0.4-2 or newer, which will be in next rawhide release.
Many thanks for your bug report.

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