Arch Linux

realloc

Member

Registered: 2016-09-05

Posts: 6

Surface Pro 2 Type Cover - Problems with right-click on GNOME

Hi,

First, here is my story:
I've got a MS Surface Pro 2 and when using Ubuntu 15.10 in the past with Unity Desktop a weird symbol showed up when using the touchpad buttons. I switched to gnome desktop, the symbol (a notification I guess) still showed up, but in addition to that, the right click button stopped working in some gnome applications. For example: Firefox worked just fine, but in nautilus I wasnt able to open the context menu with a right click. This is the symbol: http://bit.ly/25QlfIQ . (By the way: None of these bugs show up when using a usb mouse). (I'm telling you the Ubuntu story because GNOME and Unity are related and somehow right-click worked in Unity. I don't know if this information is helpful...).

Later on I switched to Arch Linux (hoping that a newer GNOME version would fix it). As this still happens in the new gnome version I wanted to ask if you have any idea, what could be done about it.

Sadly I've no knowledge of the inner workings of gnome, but if you could point me in the right direction, I would also try to solve this on my own.
Here I've got the output of xev of some actions: http://pastebin.com/SNzuykG4   You might see that the mouse click events are a lot different from the touch pad click events.

Thank you for your help.

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Surface Pro 2 Type Cover - Problems with right-click on GNOME

Make sure you're using xf86-input-libinput as you xorg input driver.
Gnome only supports libinput, so you could expect this kind of issues if you use other input drivers.

Welcome to arch forums :)

realloc

Member

Registered: 2016-09-05

Posts: 6

Re: Surface Pro 2 Type Cover - Problems with right-click on GNOME

Thanks for your answer (and the warm welcome)!

... but I guess I'm already using libinput:
$ pacman -Qs xf86-input-
local/xf86-input-libinput 0.19.0-1 (xorg-drivers xorg)
    Generic input driver for the X.Org server based on libinput
local/xf86-input-synaptics 1.8.99.1-1 (xorg-drivers xorg)
    Synaptics driver for notebook touchpads

(Is this the correct way for checking whether the driver is in use?)

Last edited by realloc (2016-09-05 13:29:24)

ooo

Member

Registered: 2013-04-10

Posts: 1,638

Re: Surface Pro 2 Type Cover - Problems with right-click on GNOME

The correct way to check which driver is being used, is to check your Xorg.0.log.
See https://wiki.archlinux.org/index.php/xorg#Input_devices (note that the your current Xorg.0.log could also be located in /var/log if X is being run as root, e.g. when using graphical login managers).

I'm not sure which driver will be used if you have both xf86-input-libinput and xf86-input-synaptics installed. You could just remove the synaptics driver, and your input devices should continue to work using libinput.

realloc

Member

Registered: 2016-09-05

Posts: 6

Re: Surface Pro 2 Type Cover - Problems with right-click on GNOME

Well it seems I am using libinput for all devices:

$ grep -e "Using input driver " ~/.local/share/xorg/Xorg.0.log
[    18.274] (II) Using input driver 'libinput' for 'Power Button'
[    18.290] (II) Using input driver 'libinput' for 'Video Bus'
[    18.292] (II) Using input driver 'libinput' for 'Power Button'
[    18.294] (II) Using input driver 'libinput' for 'MICROSOFT SAM'
[    18.304] (II) Using input driver 'libinput' for 'MICROSOFT SAM'
[    18.306] (II) Using input driver 'libinput' for 'Atmel Atmel maXTouch Digitizer'
[    18.307] (II) Using input driver 'libinput' for 'Front LifeCam'
[    18.309] (II) Using input driver 'libinput' for 'Rear LifeCam'
[    18.318] (II) Using input driver 'libinput' for 'MICROSOFT SAM'

MICROSOFT SAM seems to be a combination of the touchpad and keyboard (Type Cover).

By the way: https://wiki.archlinux.org/index.php/Mi … g_Touchpad suggests using the Synaptics  driver, at least for Surface Pro 3. What do you think about this?

Some more information on the input devices:

$ sudo evemu-describe
Available devices:
/dev/input/event0:    Lid Switch
/dev/input/event1:    Power Button
/dev/input/event2:    Power Button
/dev/input/event3:    HDA Intel PCH Mic
/dev/input/event4:    HDA Intel PCH Headphone
/dev/input/event5:    PC Speaker
/dev/input/event6:    Video Bus
/dev/input/event7:    MICROSOFT SAM
/dev/input/event8:    Atmel Atmel maXTouch Digitizer
/dev/input/event9:    MICROSOFT SAM
/dev/input/event10:    Front LifeCam
/dev/input/event11:    Rear LifeCam
/dev/input/event12:    HDA Intel HDMI HDMI/DP,pcm=3
/dev/input/event13:    HDA Intel HDMI HDMI/DP,pcm=7
/dev/input/event14:    HDA Intel HDMI HDMI/DP,pcm=8

My device configurations:

$ cat /usr/share/X11/xorg.conf.d/60-libinput.conf
# Match on all types of devices but tablet devices and joysticks
Section "InputClass"
        Identifier "libinput pointer catchall"
        MatchIsPointer "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
EndSection

Section "InputClass"
        Identifier "libinput keyboard catchall"
        MatchIsKeyboard "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
EndSection

Section "InputClass"
        Identifier "libinput touchpad catchall"
        MatchIsTouchpad "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
EndSection

Section "InputClass"
        Identifier "libinput touchscreen catchall"
        MatchIsTouchscreen "on"
        MatchDevicePath "/dev/input/event*"
        Driver "libinput"
EndSection

I posted the whole XOrg log here: http://pastebin.com/nbRe3jXt

I also found these interesting things, although it should have nothing to do with the problem at hand:
---------------------------------------------------------------------------------------------------------------------------------------------------
[    18.291] (II) config/udev: Adding input device Lid Switch (/dev/input/event0)
[    18.291] (II) No input driver specified, ignoring this device.
[    18.291] (II) This device may have been added with another device file.

(It's true, that the Lid Switch does not work properly, but I wanted to clear the most annoying problems first )

[    18.293] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=3 (/dev/input/event12)
[    18.293] (II) No input driver specified, ignoring this device.
[    18.293] (II) This device may have been added with another device file.
[    18.293] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=7 (/dev/input/event13)
[    18.293] (II) No input driver specified, ignoring this device.
[    18.293] (II) This device may have been added with another device file.
[    18.293] (II) config/udev: Adding input device HDA Intel HDMI HDMI/DP,pcm=8 (/dev/input/event14)
[    18.293] (II) No input driver specified, ignoring this device.
[    18.293] (II) This device may have been added with another device file.

(No idea what this means, but my HDMI output works)

[    18.310] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event3)
[    18.310] (II) No input driver specified, ignoring this device.
[    18.310] (II) This device may have been added with another device file.
[    18.310] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event4)
[    18.310] (II) No input driver specified, ignoring this device.
[    18.310] (II) This device may have been added with another device file.
[    18.310] (II) config/udev: Adding input device PC Speaker (/dev/input/event6)
[    18.310] (II) No input driver specified, ignoring this device.
[    18.310] (II) This device may have been added with another device file.

(My speakers work too... weird)