Bug 51504 - On dual head machine, screensaver locks both screens but allows mouse actions on screen 2
Summary: On dual head machine, screensaver locks both screens but allows mouse actions...
Status: RESOLVED INTENTIONAL
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kscreensaver bugs tracking
URL:
Keywords:
: 58033 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-12-04 23:03 UTC by Mark
Modified: 2015-01-26 07:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark 2002-12-04 23:03:38 UTC
Version:            (using KDE KDE 3.0.4)
Installed from:    SuSE RPMs
OS:          Linux

Using a Matrox G400 on Suse 8.1 in traditional (not xinerama) mode.

The screensaver starts at the appropriate time and starts with the screen lock applet from either screen.

BUT,

moving the mouse over to screen 2 causes the desktop to appear.  I can use the mouse to interact with whatever windows are on the screen, or start new applications from the menu.  I cannot use the mouse, when I try to type, the screensaver password prompt appears on screen 1 and the keystrokes go into that dialog.
Comment 1 Mark 2002-12-04 23:04:36 UTC
Sorry, the last sentence should not read "I cannot use the mouse" but should
read "I cannot use the keyboard"
Comment 2 Chris Howells 2003-08-26 12:17:58 UTC
I can reproduce this with KDE 3.1.90. If you start kdesktop_lock on one of the heads, 
even though it becomes impossible to use the other head, you don't see the 
screensaver so your screen content is not hidden. Kinda weird... will try and 
investigate. Thanks. 
Comment 3 George Goldberg 2007-12-19 03:55:11 UTC
Is this bug still there in a recent version of KDE, such as 3.5.8 or KDE4.0 RC2?
Comment 4 Oswald Buddenhagen 2010-10-23 23:57:47 UTC
*** Bug 58033 has been marked as a duplicate of this bug. ***
Comment 5 Martin Flöser 2015-01-26 07:33:21 UTC
The screen locker architecture changed with Plasma 5. The classic screen savers are no longer supported. The 4.x series won't see any further feature development, so this bug report won't be implemented as it doesn't apply to our current version any more.

I want to thank you for your bug report and for helping improving the quality of our software and I'm sorry that we were not able to provide a fix before we retired the affected component.