Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
X
xinput
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • xorg
  • app
  • xinput
  • Issues
  • #4

Closed
Open
Opened Dec 09, 2015 by Bugzilla Migration User@bugzilla-migration

xinput doesn't recognize Logitech G600's side buttons as keyboard buttons but a mouse ones which leads to strange behavior

Submitted by kam..@..sik.in

Assigned to Xorg Project Team

Link to original bug (#93303)

Description

As in summary - When I checked while it was working, G600's (http://gaming.logitech.com/pl-pl/product/g600-mmo-gaming-mouse) side buttons were seen as a keyboard from xinput, and then, they worked. Now they are recognized as mouse buttons and cursor instantly goes to left side of screen when I click any normal mouse button which makes it unusable until I disable secondary "pointer".

I am not sure on which version it started, but now I am on: local/xorg-server 1.18.0-3 (xorg) local/xorg-xinput 1.6.2-1 (xorg-apps xorg) and problem is still present.

xinput

⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ id=10 [slave pointer (2)] ⎜ ↳ id=12 [slave pointer (2)] ⎜ ↳ Logitech Gaming Mouse G600 id=13 [slave pointer (2)] ⎜ ↳ Logitech Gaming Mouse G600 id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Power Button id=7 [slave keyboard (3)] ↳ id=8 [slave keyboard (3)] ↳ id=9 [slave keyboard (3)] ↳ id=11 [slave keyboard (3)]

there's a xorg.conf section template that fixes it by enforcing to see side buttons as keyboard ones. It's discussed here: https://bbs.archlinux.org/viewtopic.php?id=204830

It's possible that this is how xinput should see that mouse by default as it's not typical mouse and then it's not bug of course - but I am not sure what's expected behaviour of xinput when such device is present.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: xorg/app/xinput#4