(*** This bug was imported into bugs.kde.org ***) Package: kcmscreensaver Version: 2.0 (using KDE 2.1.0 ) Severity: normal Installed from: compiled sources Compiler: gcc version 2.95.2 19991024 (release) OS: Linux 2.2.14 i686 OS/Compiler notes: I enabled the screensaver (Lines with 5 minutes). Then I browsed (with netscape) a website: http://www.heise.de/newsticker where I only needed to click at the same position on the "Next >>" link. After the 5 minutes delay the screensaver started even I clicked and browsed a lot around with netscape but I did no mouse moving and no scrolling with the wheel neither keyboard input. Regards Klaus. (Submitted via bugs.kde.org) (Called from KBugReport dialog)
I'm adding now some more information: I changed the screensaver from Lines to Morph(GL) and it is still reproduceable. I'm not sure if I moved the mouse and therefore this is the reason of this behaviour. But during the last test it didn't take 5 minutes (as set in my preferences for activation time of the screensaver) to activate the screensaver it took longer: around 7-9 minutes. Regards Klaus. -- .-. | Klaus Singvogel GPG-Key-ID: 1024R/5068792D 1994-06-27 oo| | Caldera (Deutschland) GmbH Naegelsbachstr. 49c 91052 Erlangen /`'\ | email: ks@caldera.de internet: http://www.caldera.de (\_;/) | phone: ++49 9131 7192-300 fax: ++49 9131 7192-399
The problem is still existing (KDE 3.0.1). I just wanted to add that not online mouse-clicks are unrecognized by the= =20 screensaver-timer but also scrolling with the mouse-wheel. It looks like only mouse-movements get recognized. servus Michael
*** Bug 28626 has been marked as a duplicate of this bug. ***
This is still a problem in 3.1 branch
Subject: kdebase/kdesktop CVS commit by howells: This should finally fix bug 25209. Huge huge huge huge thanks to kawil who helped me with the scary xlib stuff and actually worked out how to fix the problem :) CCMAIL: 25209-done@bugs.kde.org M +1 -1 xautolock.cc 1.10 --- kdebase/kdesktop/xautolock.cc #1.9:1.10 @@ -241,5 +241,5 @@ void XAutoLock::selectEvents(Window wind XSelectInput(d, window, SubstructureNotifyMask | ((attribs.all_event_masks | attribs.do_not_propagate_mask) - & KeyPressMask) | attribs.your_event_mask); + & KeyPressMask) | attribs.your_event_mask | ButtonMotionMask | ButtonPressMask); /*
Changes reverted because it broke stuff.
This bug has been fixed in HEAD by Lubos by using some new xautolock code. I'm contemplating backporting this to KDE_3_1_BRANCH so the fix will be in KDE 3.1.2.