GNOME Bugzilla – Bug 743620
30-bit Color: All mouse clicks fail
Last modified: 2020-02-18 20:21:30 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.
Do you mean clicks on applications work but clicks on gnome-shell's UI (top panel, overview) don't work?
Correct. All interactions fail to receive mouse clicks, from top panel, to sides, to notifications and popups of devices.
Possible confirmation from another person: http://askubuntu.com/questions/156057/why-doesnt-my-mouse-work-in-gnome-shell-at-30-bit-color-depth
This probably breaks Clutter's picking in some interesting way. I've never seen 10-bit-color-depth support, what drivers are you using?
(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.
I believe both AMD and NVidia support deep color now. In this instance, tested with NVidia.
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.
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.
I have the same problem, please someone mark the bug as confirmed
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?
Created attachment 366420 [details] pick-buffer-MetaStage-view This are png images created by using the env variable described on comment 7
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.
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
This was fixed in mutter: https://gitlab.gnome.org/GNOME/mutter/issues/2
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.
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?
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.
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.