After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 709475 - Add "last-used-device" signal to IdleMonitor API
Add "last-used-device" signal to IdleMonitor API
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2013-10-05 16:01 UTC by Bastien Nocera
Modified: 2021-07-05 13:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2013-10-05 16:01:20 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:
https://bugs.freedesktop.org/show_bug.cgi?id=59644
Comment 1 Bastien Nocera 2013-10-05 16:06:37 UTC
There's an example implementation for X11 in the cursor gnome-settings-daemon plugin, which is affected by the above X bug:
https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/cursor/gsd-cursor-manager.c
Comment 2 Jasper St. Pierre (not reading bugmail) 2014-12-30 02:22:32 UTC
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?
Comment 3 Bastien Nocera 2015-01-05 09:12:06 UTC
(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.
Comment 4 GNOME Infrastructure Team 2021-07-05 13:50:17 UTC
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
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.