[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 58033] New: Predictable but wrong screensaver behavior in
From:       Jeff Riley <jeff.riley () quantum ! com>
Date:       2003-05-02 19:49:57
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
     
http://bugs.kde.org/show_bug.cgi?id=58033     
           Summary: Predictable but wrong screensaver behavior in dual-head
                    mode and VMware running
           Product: kscreensaver
           Version: unspecified
          Platform: RedHat RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: screensavers
        AssignedTo: howells@kde.org
        ReportedBy: jeff.riley@quantum.com


Version:            (using KDE KDE 3.1.1)
Installed from:    RedHat RPMs
OS:          Linux

I have no idea if VMware has anything to do with this or not.  Here is the basic \
stream of events...

1. I login and let the screensaver activate.  It comes up on both screens (I'm \
running dual-head mode) as it should.  Then I hit a key or move the mouse and they \
both wake up as expected.

2. I let it timeout again, and only the 2nd screen starts up the screensaver while \
the 1st remains active.  I can move the mouse and type in the 1st screen and the \
screensave will stay on in the 2nd screen.  If I move the mouse in to the other \
screen it will wake up.

3. At this point it will no longer fire up the screensaver after the timeout period, \
I've left it overnight.  The only way to get it to come on is by hitting the Lock \
button on the taskbar on the 2nd screen.  The Lock button on the 1st screen does \
nothing at all.  When I hit the Lock button on the second screen, the screensaver \
fires up on both screens, consistently, and any movement will bring up the password \
box.

I've got two relatively expensive monitors and I keep forgetting to manually turn on \
the screen saver.  Here's the thing, if I log out and log back in again, this \
procedure starts over at step 1 above.


[prev in list] [next in list] [prev in thread] [next in thread]