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 690055 - Move "locate pointer" feature to the shell
Move "locate pointer" feature to the shell
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
triaged
: 708204 738159 774486 776214 777277 782431 783509 (view as bug list)
Depends on:
Blocks: 747513
 
 
Reported: 2012-12-11 17:07 UTC by Bastien Nocera
Modified: 2019-06-06 09:40 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bastien Nocera 2012-12-11 17:07:30 UTC 
It currently lives in gnome-settings-daemon, but it would be more appropriate for it to be implemented in the compositor to avoid catching the key when using fullscreen override-redirect windows, such as games.
Comment 1 Bastien Nocera 2014-10-11 09:30:03 UTC 
*** Bug 738159 has been marked as a duplicate of this bug. ***
Comment 2 Bastien Nocera 2015-04-08 15:18:39 UTC 
This move will be needed, if we want to keep the feature, as the mouse plugin in gnome-settings-daemon is only there for the obsolete evdev/synaptics input drivers.

Also affected might be gnome-tweak-tool, gsettings-desktop-schemas and gnome-control-center, if we want to make the feature a first-class citizen.
Comment 3 Bastien Nocera 2015-11-03 18:06:06 UTC 
In bug 123462, a way to change the key to use was requested, and bug 668360 and bug 104058 are bugs that could impact the implementations.
Comment 4 Bastien Nocera 2015-11-19 16:34:30 UTC 
*** Bug 708204 has been marked as a duplicate of this bug. ***
Comment 5 Florian Müllner 2017-01-19 15:28:37 UTC 
*** Bug 776214 has been marked as a duplicate of this bug. ***
Comment 6 Florian Müllner 2017-01-19 15:29:24 UTC 
*** Bug 777277 has been marked as a duplicate of this bug. ***
Comment 7 Micah Yoder 2017-01-20 13:23:58 UTC 
Since this is required for the feature to work in Wayland, and it can be very difficult for someone with visual impairments to find the mouse pointer without this feature, could this possibly be prioritized?  Thank you!
Comment 8 Bastien Nocera 2017-05-10 11:43:00 UTC 
*** Bug 782431 has been marked as a duplicate of this bug. ***
Comment 9 Inactive account 2017-06-07 19:00:17 UTC 
I've got friend and this also doesn't work on his system with Fedora 26 and GNOME 3.24. Regardless though of whether he uses Xorg or Wayland.
Comment 10 Inactive account 2017-06-07 19:00:50 UTC 
*** Bug 783509 has been marked as a duplicate of this bug. ***
Comment 11 Florian Müllner 2017-11-24 18:18:22 UTC 
*** Bug 774486 has been marked as a duplicate of this bug. ***
Comment 12 Alberto Ruiz 2018-05-15 15:34:15 UTC 
We just came across this in the performance hackfest while looking at reducing the amount of gsd-*

This is also broken on Wayland, so if we move it to shell we fix several things.

Is this really that hard to implement? I'd assume it could reuse the hotcorner animation and place it where the pointer is?
Comment 13 Bastien Nocera 2018-05-15 15:36:11 UTC 
(In reply to Alberto Ruiz from comment #12)
> We just came across this in the performance hackfest while looking at
> reducing the amount of gsd-*

The way to reduce the amount of gsd-* daemons is to use systemd in the session.

> This is also broken on Wayland, so if we move it to shell we fix several
> things.
> 
> Is this really that hard to implement? I'd assume it could reuse the
> hotcorner animation and place it where the pointer is?

It's hard because modifiers handling is always difficult.
Comment 14 Daniel van Vugt 2019-06-06 06:35:06 UTC 
This bug has moved to https://gitlab.gnome.org/GNOME/gnome-shell/issues/981
Comment 15 Bastien Nocera 2019-06-06 09:40:00 UTC 
Closing this bug.