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 743620 - 30-bit Color: All mouse clicks fail
30-bit Color: All mouse clicks fail
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2015-01-28 05:42 UTC by troy.sobotka
Modified: 2020-02-18 20:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
pick-buffer-MetaStage-view (15.21 KB, application/x-xz)
2018-01-06 13:46 UTC, Richard
Details

Description troy.sobotka 2015-01-28 05:42:12 UTC
Summary: When using a 30-bit desktop setting, all mouse clicks appear to fail. If an application is launched via the search and keyboard, the mouse clicks work normally.
Comment 1 drago01 2015-01-28 09:28:12 UTC
Do you mean clicks on applications work but clicks on gnome-shell's UI (top panel, overview) don't work?
Comment 2 troy.sobotka 2015-01-28 15:09:09 UTC
Correct. All interactions fail to receive mouse clicks, from top panel, to sides, to notifications and popups of devices.
Comment 3 troy.sobotka 2015-01-28 15:10:34 UTC
Possible confirmation from another person: http://askubuntu.com/questions/156057/why-doesnt-my-mouse-work-in-gnome-shell-at-30-bit-color-depth
Comment 4 Jasper St. Pierre (not reading bugmail) 2015-01-28 17:03:40 UTC
This probably breaks Clutter's picking in some interesting way. I've never seen 10-bit-color-depth support, what drivers are you using?
Comment 5 drago01 2015-01-28 17:04:37 UTC
(In reply to comment #4)
> This probably breaks Clutter's picking in some interesting way. I've never seen
> 10-bit-color-depth support, what drivers are you using?

The link from comment 3 says nvidia.
Comment 6 troy.sobotka 2015-01-28 17:09:48 UTC
I believe both AMD and NVidia support deep color now. In this instance, tested with NVidia.
Comment 7 Jasper St. Pierre (not reading bugmail) 2015-01-28 17:12:23 UTC
https://git.gnome.org/browse/clutter/tree/clutter/clutter-main.c#n641

This *looks* like it should work for 10-bit framebuffers, but I'm not 100% sure. You might want to run it with CLUTTER_PICK=dump-pick-buffers and see what comes out of that. I don't have any NVIDIA or AMD HW to test on right now.
Comment 8 Greg Kraynov 2017-10-14 16:09:21 UTC
I can confirm the same issue with amdgpu-pro driver. Keyboard works fine and Krita shows 30-bit images well, but all the GNOME shell is irresponsible to mouse clicks. Apps react on clicks as usual.
Comment 9 Richard 2018-01-04 13:58:49 UTC
I have the same problem, please someone mark the bug as confirmed
Comment 10 Richard 2018-01-04 18:16:05 UTC
OK, I have tried doing what is written on comment 7 and it didn't solve the problem, it just introduced screen corruption and slowdown.
Anything more I can do to help with?
Comment 11 Richard 2018-01-06 13:46:13 UTC
Created attachment 366420 [details]
pick-buffer-MetaStage-view

This are png images created by using the env variable described on comment 
7
Comment 12 Eric Work 2018-01-17 09:25:58 UTC
I'm also seeing the same issue with GNOME 3.26.2 and NVIDIA driver 387.34.  No response from the shell UI but applications work fine.  When I remove my depth changes it works as normal again.
Comment 13 itzexor 2018-01-22 01:21:03 UTC
This is confirmed for mesa git now as well. 30 bit configs are currently disabled by default for intel, but not for radeonsi/gallium so this will occur on the next mesa release for AMD open source users and possibly nouveau.

For affected mesa users, a workaround is to launch the problematic application with "allow_rgb10_configs=false <app>"

https://lists.freedesktop.org/archives/mesa-dev/2017-September/168921.html
https://bugs.freedesktop.org/show_bug.cgi?id=104599
Comment 14 Florian Müllner 2018-07-14 09:06:20 UTC
This was fixed in mutter:
https://gitlab.gnome.org/GNOME/mutter/issues/2
Comment 15 Eric Work 2018-10-20 18:58:42 UTC
This is not fixed in GNOME/mutter 3.28.3 despite having the 3 commits mentioned in mutter issue 2 (from #14).  I'm using an NVIDIA Titan V with driver version 396.54.
Comment 16 Kishore 2018-11-28 02:39:30 UTC
How do we get this fix? upgrade mesa to 19.0 and llvm to 7.0?
or we get this via latest mutter which is still in beta phase or both?
Comment 17 Eric Work 2019-03-28 02:26:03 UTC
FYI, this is still not fixed with GNOME 3.30.2 on Fedora 29 with NVIDIA driver 418.56.  I'm guessing the fix mentioned above only applies to wayland which I haven't tried although there is some NVIDIA support for wayland.  Surprisingly totem can be moved and resized, but I didn't find any other windows to be movable.  Within a window everything appears to work fine.
Comment 18 flip phillips 2020-02-18 20:21:30 UTC
As another FIY, still not fixed in Ubuntu 18.04, Gnome 3.28.3, NVIDIA 440.59. Just piling on the whole not-quite-fixed bandwagon.