Bug 78871 - keyboard/mouse grabs prevent screensave from starting
Summary: keyboard/mouse grabs prevent screensave from starting
Alias: None
Product: ksmserver
Classification: Plasma
Component: lockscreen (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: HI major
Target Milestone: ---
Assignee: David Edmundson
: 77991 86935 124283 176637 189668 203649 334051 358859 373235 439416 (view as bug list)
Depends on:
Reported: 2004-04-01 18:38 UTC by Stephen
Modified: 2021-07-03 06:43 UTC (History)
17 users (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description Stephen 2004-04-01 18:38:57 UTC
Version:            (using KDE KDE 3.2.1)
Installed from:    Compiled From Sources
OS:          Linux

If you right click the desktop and bring up a menu, kscreensaver will not start at all. As soon as you close this menu, the screensaver fuctions correctly. This also happens if you right click an icon.
Comment 1 Lubos Lunak 2004-04-08 15:46:30 UTC
*** Bug 77991 has been marked as a duplicate of this bug. ***
Comment 2 Lubos Lunak 2004-08-16 16:55:28 UTC
*** Bug 86935 has been marked as a duplicate of this bug. ***
Comment 3 Lubos Lunak 2007-01-12 13:59:44 UTC
*** Bug 124283 has been marked as a duplicate of this bug. ***
Comment 4 Lubos Lunak 2009-04-28 18:42:05 UTC
*** Bug 189668 has been marked as a duplicate of this bug. ***
Comment 5 Lubos Lunak 2009-04-28 18:43:32 UTC
*** Bug 176637 has been marked as a duplicate of this bug. ***
Comment 6 Bernhard E. Reiter 2009-08-19 17:36:25 UTC
I can confirm the problem.

For Debian Lenny (with KDE 3.5 and our e35 client) or Etch
on a KDE desktop, if you keep the mouse within an open menu,
the screensaver will not start. This is a security problem as
the machine does not get locked if a person leaves the desk for a while.

How to reproduce: Enable the screensaver with password requirement
(e.g. 1min and 5 sec). Go to a menu and open it with the mouse and keep the 
mouse there. Just wait. Nothing happens.

This works with the KDE start menu as simplified test-case.
Comment 7 Oswald Buddenhagen 2009-10-04 21:49:42 UTC
why did you assign that to allen? even more so without ensuring that the default tracker address (which is being watched) stays in the loop?
Comment 8 Bernhard E. Reiter 2009-10-05 18:02:30 UTC
@Oswald: Because if nobody is going to fix this, Allen will do it - so I have assigned it to him. Sorry for not keeping the list in the loop - I did not know this custom. Can you assign it to Allen and keep the list in the loop as necessary? Thanks!
Comment 9 Oswald Buddenhagen 2009-10-05 18:33:22 UTC
would you bet that allen will fix it? ;)
anyway, i think the current cc: setup is just fine.
Comment 10 Bernhard E. Reiter 2009-10-07 11:29:33 UTC
@Oswald, yes I am pretty sure Allen will fix it - the question is only when he will do it. (Background: My company Intevation is a partner of KDAB and together we do paid work on KDE and the Kolab Client. This is a security related issue and we like to get it fixed.)
Comment 11 Oswald Buddenhagen 2009-10-07 13:05:53 UTC
well, then i should mention that this is a rather fundamental problem.
either you find a way to steal grabs (maybe the extension which controls the alt-ctrl-numpad-slash/asterisk provides that), hack around it by sending close events to popup windows, or implement the locker by opening a new x server and disabling virtual terminal switching (gdm wants to go the latter route in the middle run).
Comment 12 Alvaro Manuel Recio Perez 2011-06-14 12:52:31 UTC
I can confirm this still happens in KDE SC 4.6.4.

It's been already said but I must stress that, in my humble opinion, this is a fundamental security issue that should be given more attention.
Comment 13 Bernhard E. Reiter 2011-06-14 14:02:54 UTC
I've upgraded severity and priority.
Alvaro, thanks for testing this.

(The situation changed in that I cannot promisse and work of Allen on this right now.)
Comment 14 Martin Flöser 2015-01-23 13:52:02 UTC
*** Bug 334051 has been marked as a duplicate of this bug. ***
Comment 15 Martin Flöser 2015-11-16 14:18:31 UTC
*** Bug 203649 has been marked as a duplicate of this bug. ***
Comment 16 Martin Flöser 2015-11-16 14:52:09 UTC
I'm happy to announce that the upcoming Plasma 5.5 comes with a Wayland session which does no longer expose this sever issue.

As the problem described in this bug reports is unfixable with X11, I consider this bug as fixed on Wayland.
Comment 17 Martin Flöser 2016-02-01 10:09:50 UTC
*** Bug 358859 has been marked as a duplicate of this bug. ***
Comment 18 Martin Flöser 2016-12-04 08:07:36 UTC
*** Bug 373235 has been marked as a duplicate of this bug. ***
Comment 19 Bryan Habeck 2021-07-03 06:43:31 UTC
*** Bug 439416 has been marked as a duplicate of this bug. ***