Bug 73412 - KDE screensaver just blanks screen
Summary: KDE screensaver just blanks screen
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: kdeartwork
Version: null
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-04 10:52 UTC by Hans Schippers
Modified: 2007-04-18 16:46 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-09-25 19:30:12 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2002:220 0 normal SHIPPED_LIVE : Updated KDE packages fix security issues 2002-10-01 04:00:00 UTC

Description Hans Schippers 2002-09-04 10:52:29 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux)

Description of problem:
in kontrol center, testing screensavers works just fine, but locking the screen just results in a blank screen, no matter what screensaver is actually enabled...

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


How reproducible:
Always

Steps to Reproduce:
1.enable screensaver in KDE
2.lock screen
3.
	

Actual Results:  blank screen

Expected Results:  screensaver running

Additional info:

Comment 1 Nathan Murphy 2002-09-11 08:29:54 UTC
I have this problem as well, and did not happen in limbo.  I am now running 
Null with updated packages and the problem still exists.  I am running a 
GeForce2 GTS with the standard Xfree86 nv driver.  If that matters.  However 
xscreensaver in gnome works fine, and the KDE screensaver as noted above tests 
fine as well, but does not intialize.  I have tried many of the included 
screensavers in KDE and they are all affected.  This occurs regardless of the 
"Require Password" box being checked.

Comment 2 Ngo Than 2002-10-09 14:15:24 UTC
It's a bug in kdebase, which is now fixed in 3.0.3-14 or newer. You will find it
in the next rawhide release.


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