Assigning CTRL to "Show location of pointer" (now "Pointer Location") means that applications cannot capture CTRL

[Wise Melon]

I have recently noticed that when one turns on the option in the gnome-tweak-tool in order to "Show location of pointer" when CTRL is pressed, application are no longer able to capture the CTRL key. For instance VMs in Virtual Box no longer do anything when CTRL is pressed simply because they do not know it is being pressed, so I can't copy and paste stuff in VMs, nor cancel commands in Terminal, so it is very annoying. It also means that in Virtual Box if I press my right CTRL key instead of my left one (as they have different features where the left acts as the guest key, and the right one as the host key - the host key would normally be used to toggle Virtual Box capturing) it still does nothing, even though it's Virtual Box that should do something rather than the VM.

Turning off the option in gnome-tweak-tool resolves the problem, but I would still like to be able to have it on without side-effects.

---

OS Information:

    No LSB modules are available.
    Distributor ID: Ubuntu
    Description: Ubuntu 15.10
    Release: 15.10
    Codename: wily
    Flavour: GNOME
    GNOME Version: 3.18

Package Information:

    gnome-tweak-tool:
      Installed: 3.18.0-1~wily1
      Candidate: 3.18.0-1~wily1
      Version table:
     *** 3.18.0-1~wily1 0
            500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ wily/main amd64 Packages
            100 /var/lib/dpkg/status
         3.16.2-2 0
            500 http://archive.ubuntu.com/ubuntu/ wily/universe amd64 Packages

[Wise Melon (wise-melon-deactivatedaccount)]

I have also filed a report on this issue upstream: https://bugzilla.gnome.org/show_bug.cgi?id=761563

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bruce Pieterse (octoquad)]

Wily is end of life now. This doesn't seem to be a problem any more with Ubuntu GNOME 17.04 and GNOME 3.22. This is possibly fixed, but I am unable to confirm if it is fixed in 16.04 and 16.10.

[Paul White (paulw2u)]

Noted that the reporter no longer uses Launchpad and that the upstream report was closed on 2017-10-28 as not reproducible.

This issue has sat incomplete for over three years now without any response or further reports of the issue so I'm closing this as "Invalid".

Please feel free to re-open this bug report if this is still an issue when using a currently supported release of Ubuntu.