Bug 102396

Summary: Editing xorg.conf DefaultDepth and Depth to 30 makes the mouse buttons stop working
Product: xorg Reporter: Steve <stevensuper5>
Component: Driver/nVidia (proprietary)Assignee: Aaron Plattner <aplattner>
Status: NEEDINFO --- QA Contact: Aaron Plattner <aplattner>
Severity: normal    
Priority: high CC: peter.hutterer, work.eric
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
URL: https://bugzilla.gnome.org/show_bug.cgi?id=743620
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
xorg.conf
none
xorg.log none

Description Steve 2017-08-24 18:10:13 UTC
Created attachment 133761 [details]
xorg.conf

I have a really weird problem when setting my display collor depth to 30 bit, first I create a xorg.conf file using nvidia X server settings, save to X configuration file, I restart the computer and everything works including the mouse in the new server settings, after that I edit the xorg.conf file and change DefaultDepth and Depth to 30 and restart (my monitor supports 10 bit per collor), then the mouse left and right button stops working in gnome shell.

I am using an nvidia 1060 6GB on Ubuntu gnome 17.04 amd64 and nvidia drivers 384.69 provided by ubuntu.
Comment 1 Steve 2017-08-24 18:44:20 UTC
Created attachment 133762 [details]
xorg.log
Comment 2 Alan Coopersmith 2017-08-25 22:38:09 UTC
Even though xorg.conf specifies the "mouse" driver, the log file shows:
[     3.412] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.

[     4.116] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event2)
[     4.116] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
[     4.116] (II) Using input driver 'libinput' for 'Logitech USB Receiver'

so moving from "mouse" driver to "libinput" driver bug category.
Comment 3 Peter Hutterer 2017-08-26 07:48:46 UTC
I'm going to say that unless you can reproduce this with a free driver, it's unlikely that this will get fixed. I can't even imagine what could trigger this but given that the libinput driver doesn't know about the display at all, it's either a server bug or a bug in the nvidia driver.
Comment 4 Steve 2017-08-26 18:52:26 UTC
I have removed the nvidia driver and tried with nouveau, although I couldn't get pass GDM with 30 bit precision, the mouse buttons worked on GDM unlike the nvidia drivers, so this is a nvidia bug?
Comment 5 Peter Hutterer 2017-08-27 22:03:24 UTC
(In reply to monterro from comment #4)
> I have removed the nvidia driver and tried with nouveau, although I couldn't
> get pass GDM with 30 bit precision, the mouse buttons worked on GDM unlike
> the nvidia drivers, so this is a nvidia bug?

Note that gdm these days runs on Wayland and ignores the xorg.conf. It then starts the server and if it drops you back to gdm this means the the xorg.conf with nouveau most likely didn't work. I'm still blaming the nvidia driver for this bug though :)
Comment 6 Aaron Plattner 2017-08-29 00:44:07 UTC
We ran into the same problem and determined that it's a GNOME bug, although I don't recall what steps were taken to investigate it.

It also crashes trying to start xterm at depth 30 due to some sort of icon thumbnail bug, for what it's worth.

Doesn't xf86-video-intel support depth 30? Maybe someone could try it with that.
Comment 7 Steve 2017-08-29 01:22:09 UTC
I've found a bug report on gnome bugzilla https://bugzilla.gnome.org/show_bug.cgi?id=743620
Comment 8 Greg Kraynov 2017-10-14 16:12:03 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 Huseyin Fahri Uzun 2019-04-09 00:25:06 UTC
Having the same issue on Ubuntu 18.04.02 (5.0.7) with 418 Nvidia drivers. I can't enable 30 bit color depth or HDR on my monitor either. Very same pc can activate it on Windows 10.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.