Summary: | Mouse buttons aren't listed correctly and can't be reassigned | ||
---|---|---|---|
Product: | Wayland | Reporter: | Sergio Costas <raster> |
Component: | libinput | Assignee: | Wayland bug list <wayland-bugs> |
Status: | RESOLVED NOTABUG | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | peter.hutterer, raster |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Sergio Costas
2017-10-05 22:31:51 UTC
https://who-t.blogspot.com.au/2016/12/the-future-of-xinput-xmodmap-setxkbmap.html in short: xmodmap/xinput have no real effect under wayland. any remapping would only work in X applications, not in wayland-native ones. You need to remap the button using the compositor's facilities (if any). Oh, ok... I supposed that xmodmap was the tool for Xorg, but xinput was the equivalent for libinput... Ok, thanks. But wait... I remapped one of the recognized buttons in my mouse, and the remap works in wayland applications... Specifically, I remapped the thumb button that can be remapped to the middle button, and the paste function works in a gnome terminal or in Gedit :-? I honestly don't know how this would work. xinput only talks to the x server which updates its internal button mapping. In theory it's possible to have this configuration forwarded to the compositor to apply across Wayland applications, but we don't have a protocol for that. So... No idea what's going on there. Ok, I found the reason: I don't know what's happening with my Debian system, but when I ask it to run Gnome Shell under Wayland, it still launches the X version. That's why it worked. If I manually launch gnome shell from a tty with --wayland, and try to use xinput to remap the mouse, it doesn't work. Sorry. |
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.