Bug 106109

Summary:	Touchpad and Trackpoint locked together
Product:	Wayland	Reporter:	Kadir <fd>
Component:	libinput	Assignee:	Wayland bug list <wayland-bugs>
Status:	RESOLVED NOTOURBUG	QA Contact:
Severity:	normal
Priority:	medium	CC:	peter.hutterer
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Kadir 2018-04-17 18:03:41 UTC

Hi,

This is the bugreport I also reported at the Red Hat Bugzilla, https://bugzilla.redhat.com/show_bug.cgi?id=1559632.


When in a Wayland session disabling the touchpad also disables the trackpoint. Only when enabling the touchpad in gnome-settings (in Xorg) and returning to Wayland session the trackpoint works.

Version-Release number of selected component (if applicable):

Libinput 1.10.2-4.fc27 

How reproducible:


Steps to Reproduce:
1. disable touchpad in Xorg
2. try to use trackpoint in Wayland
3. trackpoint does not work

Actual results:


Expected results:

The trackpoint should work regardless of the touchpad settings. In Xorg this is the behaviour, in Wayland the touchpad and trackpoint are locked together. 

Additional info:

This is on a Dell Latitude 7480

Comment 1 Peter Hutterer 2018-04-17 23:41:29 UTC

https://wayland.freedesktop.org/libinput/doc/latest/reporting_bugs.html has list of information I need, in this case specifically the evemu of the touchpad and the trackpoint, and a libinput debug-events --verbose output (of the initial blurb it posts, without input events).

Comment 2 Kadir 2018-04-18 18:12:40 UTC

Thank you Peter for your response!

I have the following information:

On Gnome Wayland with the touchpad disabled and an external mouse connected (on Xorg the trackpoint works with the touchpad disabled, on Wayland the trackpoint does NOT work when the touchpad is disabled):

$ xinput list

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:13                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:13            	id=7	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ xwayland-keyboard:13                    	id=8	[slave  keyboard (3)]

$ udevadm info /sys/class/input/event9

P: /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-DLL07A0:01/0018:044E:120B.0003/input/input10/event9
N: input/event9
S: input/by-path/pci-0000:00:15.1-platform-i2c_designware.1-event-mouse
E: DEVLINKS=/dev/input/by-path/pci-0000:00:15.1-platform-i2c_designware.1-event-mouse
E: DEVNAME=/dev/input/event9
E: DEVPATH=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-DLL07A0:01/0018:044E:120B.0003/input/input10/event9
E: ID_INPUT=1
E: ID_INPUT_MOUSE=1
E: ID_INPUT_POINTINGSTICK=1
E: ID_PATH=pci-0000:00:15.1-platform-i2c_designware.1
E: ID_PATH_TAG=pci-0000_00_15_1-platform-i2c_designware_1
E: ID_SERIAL=noserial
E: LIBINPUT_DEVICE_GROUP=18/44e/120b:i2c-DLL07A0:01
E: MAJOR=13
E: MINOR=73
E: SUBSYSTEM=input
E: USEC_INITIALIZED=2679075

$ udevadm info /sys/class/input/event10

P: /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-DLL07A0:01/0018:044E:120B.0003/input/input8/event10
N: input/event10
S: input/by-path/pci-0000:00:15.1-platform-i2c_designware.1-event-mouse
E: DEVLINKS=/dev/input/by-path/pci-0000:00:15.1-platform-i2c_designware.1-event-mouse
E: DEVNAME=/dev/input/event10
E: DEVPATH=/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-DLL07A0:01/0018:044E:120B.0003/input/input8/event10
E: ID_INPUT=1
E: ID_INPUT_HEIGHT_MM=46
E: ID_INPUT_TOUCHPAD=1
E: ID_INPUT_WIDTH_MM=99
E: ID_PATH=pci-0000:00:15.1-platform-i2c_designware.1
E: ID_PATH_TAG=pci-0000_00_15_1-platform-i2c_designware_1
E: ID_SERIAL=noserial
E: LIBINPUT_DEVICE_GROUP=18/44e/120b:i2c-DLL07A0:01
E: MAJOR=13
E: MINOR=74
E: SUBSYSTEM=input
E: USEC_INITIALIZED=2693454

$ sudo libinput debug-events --verbose

event3  - Power Button: is tagged by udev as: Keyboard
event3  - Power Button: device is a keyboard
event11 - Video Bus: is tagged by udev as: Keyboard
event11 - Video Bus: device is a keyboard
event1  - Power Button: is tagged by udev as: Keyboard
event1  - Power Button: device is a keyboard
event0  - Lid Switch: is tagged by udev as: Switch
event0  - Lid Switch: device is a switch device
event2  - Sleep Button: is tagged by udev as: Keyboard
event2  - Sleep Button: device is a keyboard
event5  - Microsoft Comfort Mouse 6000: is tagged by udev as: Keyboard Mouse
event5  - Microsoft Comfort Mouse 6000: device is a pointer
event5  - Microsoft Comfort Mouse 6000: device is a keyboard
event18 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
event18 - Integrated_Webcam_HD: Integrate: device is a keyboard
event9  - DualPoint Stick: is tagged by udev as: Mouse Pointingstick
event9  - DualPoint Stick: trackpoint device set to range 20
event9  - DualPoint Stick: device is a pointer
event10 - DLL07A0:01 044E:120B: is tagged by udev as: Touchpad
event10 - using pressure-based touch detection (6:7)
event10 - palm: pressure threshold is 130
event10 - DLL07A0:01 044E:120B: device is a touchpad
event10 - lid_switch: activated for DLL07A0:01 044E:120B<->Lid Switch
event12 - HDA Intel PCH Headphone Mic: is tagged by udev as: Switch
event13 - HDA Intel PCH HDMI/DP,pcm=3: is tagged by udev as: Switch
event14 - HDA Intel PCH HDMI/DP,pcm=7: is tagged by udev as: Switch
event15 - HDA Intel PCH HDMI/DP,pcm=8: is tagged by udev as: Switch
event16 - HDA Intel PCH HDMI/DP,pcm=9: is tagged by udev as: Switch
event17 - HDA Intel PCH HDMI/DP,pcm=10: is tagged by udev as: Switch
event7  - Intel HID events: is tagged by udev as: Keyboard
event7  - Intel HID events: device is a keyboard
event8  - Dell WMI hotkeys: is tagged by udev as: Keyboard
event8  - Dell WMI hotkeys: device is a keyboard
event4  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
event4  - AT Translated Set 2 keyboard: device is a keyboard
event0  - lid: keyboard paired with Lid Switch<->AT Translated Set 2 keyboard
event10 - palm: dwt activated with DLL07A0:01 044E:120B<->AT Translated Set 2 keyboard
-event3   DEVICE_ADDED     Power Button                      seat0 default group1  cap:k
-event11  DEVICE_ADDED     Video Bus                         seat0 default group2  cap:k
-event1   DEVICE_ADDED     Power Button                      seat0 default group3  cap:k
-event0   DEVICE_ADDED     Lid Switch                        seat0 default group4  cap:S
-event2   DEVICE_ADDED     Sleep Button                      seat0 default group5  cap:k
-event5   DEVICE_ADDED     Microsoft Comfort Mouse 6000      seat0 default group6  cap:kp left scroll-nat scroll-button
-event18  DEVICE_ADDED     Integrated_Webcam_HD: Integrate   seat0 default group7  cap:k
-event9   DEVICE_ADDED     DualPoint Stick                   seat0 default group8  cap:p left scroll-nat scroll-button
-event10  DEVICE_ADDED     DLL07A0:01 044E:120B              seat0 default group8  cap:pg  size 99x47mm tap(dl off) left scroll-nat scroll-2fg-edge dwt-on
-event12  DEVICE_ADDED     HDA Intel PCH Headphone Mic       seat0 default group9  cap:
-event13  DEVICE_ADDED     HDA Intel PCH HDMI/DP,pcm=3       seat0 default group9  cap:
-event14  DEVICE_ADDED     HDA Intel PCH HDMI/DP,pcm=7       seat0 default group9  cap:
-event15  DEVICE_ADDED     HDA Intel PCH HDMI/DP,pcm=8       seat0 default group9  cap:
-event16  DEVICE_ADDED     HDA Intel PCH HDMI/DP,pcm=9       seat0 default group9  cap:
-event17  DEVICE_ADDED     HDA Intel PCH HDMI/DP,pcm=10      seat0 default group9  cap:
-event7   DEVICE_ADDED     Intel HID events                  seat0 default group10 cap:k
-event8   DEVICE_ADDED     Dell WMI hotkeys                  seat0 default group11 cap:k
-event4   DEVICE_ADDED     AT Translated Set 2 keyboard      seat0 default group12 cap:k

Comment 3 Peter Hutterer 2018-04-18 22:42:28 UTC

> In Xorg this is the behaviour

sorry, I must have read over this bit initially. Simply said - this is not a libinput problem then because libinput doesn't know whether its used under wayland or xorg and always does the same thing.

So the most likely issue here is with gnome somehow disabling both devices though I honestly couldn't guess at why. The code paths are mostly identical in gnome too. Either way, I'm going to have to punt this to mutter, sorry.

Comment 4 Kadir 2018-04-20 08:47:14 UTC

Thank you Peter, should I file a bugreport at the Gnome bugzilla or Mutter Gitlab? I don't no which one is more appropiate/active

Comment 5 Peter Hutterer 2018-04-23 05:59:38 UTC

start with mutter and let's see how we go from there. Please CC me on it (@whot on gitlab)

Comment 6 Kadir 2018-04-23 15:42:02 UTC

(In reply to Peter Hutterer from comment #5)
> start with mutter and let's see how we go from there. Please CC me on it
> (@whot on gitlab)

I submitted the bug at Gitlab, https://gitlab.gnome.org/GNOME/mutter/issues/128

I don't know how to CC you on Gitlab :)

Comment 7 Peter Hutterer 2018-04-23 22:47:34 UTC

all good, I CC'd myself (I think :). iirc Gitlab automatically adds someone
if you mention them by their handle.

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.