GNOME Bugzilla – Bug 709475
Add "last-used-device" signal to IdleMonitor API
Last modified: 2021-07-05 13:50:17 UTC
This is trivial to implement for wayland: the backend handles all the input devices, and would simply change a dbus property telling us which is the last used input device.
This is harder for X11, because the X implementation of per-device IDLETIME has some bugs for negative transitions:
There's an example implementation for X11 in the cursor gnome-settings-daemon plugin, which is affected by the above X bug:
There would be a lot of bus traffic when you switch between mouse and keyboard, unless you're talking about only having the master device for the device pair.
What's the point of this property?
(In reply to comment #2)
> There would be a lot of bus traffic when you switch between mouse and keyboard,
> unless you're talking about only having the master device for the device pair.
The code in the cursor plugin already does that using X, so it must not be that much traffic. In any case, it doesn't remove the need for an API.
> What's the point of this property?
Knowing whether the last pointer device used is a touchscreen or a mouse/touchpad for example. For symmetry, I would also add such a property for the keyboard device used, and update a "last used" timestamp, so that we know when the keyboard was used last to hide the OSK when it was shown previously.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).
If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
and create a new ticket at
Thank you for your understanding and your help.