• Mouse on Wayland is broken


    Hey guys,

    I ran into some problems playing fps(xonotic, insurgency, left4dead2, cs:go) games under wayland. Menu navigation with mouse mostly works except xonotic. After game loads mouse axis seem to grabble up resulting looking downward and spinning 360. Any trick for setting this up or is it a bug?

    my xbox 360 controller works perfectly with dirt showdown and grid and also dota2 works perfectly fine with mouse.

    i am on mesa wayland gdm gnome
    logitech g500 mouse

    thanx in advance

  • @r1kkHUN

    Hi

    Have you g500-git installed ?

    yaourt -S g500-git
    
  • I installed it and it doesnt fix anything on its own. I see it has a few command in terminal but i need to check manual for changing any settings. It seems its quite useful tool, but in my case mouse works fine in any other application even in dota2. On xorg everything worked fine out of the box. I ve tried a few linux distro in the past but mouse never been an issue since its a plug n play device. I would like to know if others are having the same problem on wayland, before i start screw things up :) i would report this if I would be certain that its a bug and who to report it.

  • @r1kkHUN said in Mouse on Wayland is broken:

    I installed it and it doesnt fix anything on its own. I see it has a few command in terminal but i need to check manual for changing any settings. It seems its quite useful tool, but in my case mouse works fine in any other application even in dota2. On xorg everything worked fine out of the box. I ve tried a few linux distro in the past but mouse never been an issue since its a plug n play device. I would like to know if others are having the same problem on wayland, before i start screw things up :) i would report this if I would be certain if its a bug and who to report it.

    Hi:
    I use a wayland session gdm in ArchLinux vainilla haven’t mouse problems , is a simple and easy B-110 Logitech , but de g500 is a gaming mouse.
    Anyway we do not use pure wayland (weston), we use wayland by xwayland way
    Try:

    sudo nano  /etc/X11/xorg.conf
    

    Inside:

    Section "InputClass"
        Identifier "G500 misconfiguration fix"
        MatchProduct "G500"
        # Match just the keyboard section of the G500
        MatchIsKeyboard "true"
        # evdev assumes it's a mouse when it sees the absolute axis. Stop that from happening. 
        Option "IgnoreAbsoluteAxes" "on"  
    EndSection
    

    If the problem, is not the mouse, it may be the program running on wayland.

    Try before opening the program , open console:

    xhost +local:
    

    Cheers

  • @Archrysler
    dmesg spit this out:

    [    2.256406] hidraw: raw HID events driver (C) Jiri Kosina
    [    2.266312] usbcore: registered new interface driver usbhid
    [    2.266313] usbhid: USB HID core driver
    [    2.266899] input: Logitech G500 as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/0003:046D:C068.0001/input/input2
    [    2.266943] hid-generic 0003:046D:C068.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech G500] on usb-0000:00:1d.2-1/input0
    [    2.271238] input: Logitech G500 as /devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.1/0003:046D:C068.0002/input/input3
    [    2.325779] hid-generic 0003:046D:C068.0002: input,hiddev0,hidraw1: USB HID v1.11 Keyboard [Logitech G500] on usb-0000:00:1d.2-1/input1
    [    2.505473] usb 5-1: new low-speed USB device number 2 using uhci_hcd
    [    2.701738] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.0/0003:0603:00F2.0003/input/input4
    [    2.755603] hid-generic 0003:0603:00F2.0003: input,hidraw2: USB HID v1.10 Keyboard [NOVATEK USB Keyboard] on usb-0000:00:1a.2-1/input0
    [    2.788619] input: NOVATEK USB Keyboard as /devices/pci0000:00/0000:00:1a.2/usb5/5-1/5-1:1.1/0003:0603:00F2.0004/input/input5
    [    2.842427] hid-generic 0003:0603:00F2.0004: input,hiddev0,hidraw3: USB HID v1.10 Device [NOVATEK USB Keyboard] on usb-0000:00:1a.2-1/input1
    

    I havent added your line yet just I thought it might worth to share this. Why are the keyboard and mouse are listed twice? Why is the G500 mouse first then keyboard on second?

    also xorg.log

    [    23.263] (II) Using input driver 'evdev' for 'Logitech G500'
    [    23.263] (**) Logitech G500: always reports core events
    [    23.263] (**) evdev: Logitech G500: Device: "/dev/input/event1"
    [    23.320] (--) evdev: Logitech G500: Vendor 0x46d Product 0xc068
    [    23.320] (--) evdev: Logitech G500: Found 20 mouse buttons
    [    23.320] (--) evdev: Logitech G500: Found scroll wheel(s)
    [    23.320] (--) evdev: Logitech G500: Found relative axes
    [    23.320] (--) evdev: Logitech G500: Found x and y relative axes
    [    23.320] (II) evdev: Logitech G500: Configuring as mouse
    [    23.320] (II) evdev: Logitech G500: Adding scrollwheel support
    [    23.320] (**) evdev: Logitech G500: YAxisMapping: buttons 4 and 5
    [    23.320] (**) evdev: Logitech G500: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [    23.320] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.0/0003:046D:C068.0002/input/input3/event1"
    [    23.320] (II) XINPUT: Adding extended input device "Logitech G500" (type: MOUSE, id 10)
    [    23.320] (II) evdev: Logitech G500: initialized for relative axes.
    [    23.320] (**) Logitech G500: (accel) keeping acceleration scheme 1
    [    23.320] (**) Logitech G500: (accel) acceleration profile 0
    [    23.320] (**) Logitech G500: (accel) acceleration factor: 2.000
    [    23.320] (**) Logitech G500: (accel) acceleration threshold: 4
    [    23.320] (II) config/udev: Adding input device Logitech G500 (/dev/input/mouse0)
    [    23.320] (II) No input driver specified, ignoring this device.
    [    23.320] (II) This device may have been added with another device file.
    [    23.320] (II) config/udev: Adding input device Logitech G500 (/dev/input/event2)
    [    23.320] (**) Logitech G500: Applying InputClass "evdev keyboard catchall"
    [    23.320] (**) Logitech G500: Applying InputClass "system-keyboard"
    [    23.320] (**) Logitech G500: Applying InputClass "Keyboard Defaults"
    [    23.320] (II) Using input driver 'evdev' for 'Logitech G500'
    [    23.320] (**) Logitech G500: always reports core events
    [    23.320] (**) evdev: Logitech G500: Device: "/dev/input/event2"
    [    23.321] (--) evdev: Logitech G500: Vendor 0x46d Product 0xc068
    [    23.321] (--) evdev: Logitech G500: Found 1 mouse buttons
    [    23.321] (--) evdev: Logitech G500: Found scroll wheel(s)
    [    23.321] (--) evdev: Logitech G500: Found relative axes
    [    23.321] (II) evdev: Logitech G500: Forcing relative x/y axes to exist.
    [    23.321] (--) evdev: Logitech G500: Found absolute axes
    [    23.321] (II) evdev: Logitech G500: Forcing absolute x/y axes to exist.
    [    23.321] (--) evdev: Logitech G500: Found keys
    [    23.321] (II) evdev: Logitech G500: Configuring as mouse
    [    23.321] (II) evdev: Logitech G500: Configuring as keyboard
    [    23.321] (II) evdev: Logitech G500: Adding scrollwheel support
    [    23.321] (**) evdev: Logitech G500: YAxisMapping: buttons 4 and 5
    [    23.321] (**) evdev: Logitech G500: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [    23.321] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.2/usb8/8-1/8-1:1.1/0003:046D:C068.0003/input/input4/event2"
    [    23.321] (II) XINPUT: Adding extended input device "Logitech G500" (type: KEYBOARD, id 11)
    [    23.321] (**) Option "xkb_rules" "evdev"
    [    23.321] (**) Option "xkb_layout" "gb,us"
    [    23.321] (**) Option "xkb_variant" ","
    [    23.321] (**) Option "xkb_options" "terminate:ctrl_alt_bksp"
    [    23.321] (II) evdev: Logitech G500: initialized for relative axes.
    [    23.321] (WW) evdev: Logitech G500: ignoring absolute axes.
    [    23.321] (**) Logitech G500: (accel) keeping acceleration scheme 1
    [    23.321] (**) Logitech G500: (accel) acceleration profile 0
    [    23.321] (**) Logitech G500: (accel) acceleration factor: 2.000
    [    23.321] (**) Logitech G500: (accel) acceleration threshold: 4
    
  • I jumped back to a wayland session and it seems the mouse glich has been fixed.

    wayland 1.12.0-1
    libinput 1.6.1-1

mouse44 wayland40 Posts 6Views 1015
Log in to reply