Bug 61718 - screensaver - lock screen problem
Summary: screensaver - lock screen problem
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: wdovlrrw
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-03-23 14:53 UTC by Michael Redinger
Modified: 2007-04-18 16:41 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-04-09 11:51:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Michael Redinger 2002-03-23 14:53:44 UTC
Description of Problem:

The screensaver (tried several, both normal and GL) seems to have a weird
problem. Whein logging in for the first time after starting the computer and
locking the screen, the screen flashes several times before a screensaver is
chosen. After locking the screen two times, everything seems to work fine.
This "works" when locking the screen using the kicker icon or the kmenu entry.
It does not happen when starting kcontrol and testing a screensaver.

The video card is Intel Corp. 82815 CGC (i815).

(I'm also experiencing random crashes of the KDE screensavers which completely
lock the screen - you have to reboot the computer to recover, even killing all X
processes doesn't work. However, I cannot cleanly reproduce this, it just
happens ... just thought this could be related)

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

kdebase-3.0.0-cvs20020314.4

How Reproducible:

100%

Steps to Reproduce:

1. boot
2. log into KDE
3. press the "lock screen" icon or choose "lock screen" from kmenu
4. repeat
5. repeat again - works fine now

Comment 1 Bernhard Rosenkraenzer 2002-04-09 11:51:37 UTC
Do you still see this in the current versions? I can't reproduce it, but couldn't 
reproduce it in the first place either.

Comment 2 Michael Redinger 2002-04-13 09:36:55 UTC
Works for me now too. Closing.


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