Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65950 - Rotating screen messes up stylus under wayland.

Attached to Project: Arch Linux
Opened by Volker Weißmann (volker_weissmann) - Monday, 23 March 2020, 14:56 GMT
Last edited by freswa (frederik) - Monday, 23 March 2020, 15:58 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

If you are using Gnome and the iio-sensor-proxy package is installed (as explained here: https://wiki.archlinux.org/index.php/Tablet_PC#With_GNOME), the screen will rotate if you rotate the device. Obviously, the axes of the touchscreen and the stylus also need to rotate. This works fine under Xorg, but under Wayland the stylus axes do not rotate correctly. I suspect that the reason for this is that gnome uses
xinput set-prop id --type=float "Coordinate Transformation Matrix" matrix
to rotate the stylus axes. The command above only works under Xorg as written in the xinput manpage:

XWAYLAND
Xwayland is an X server that uses a Wayland Compositor as backend. Xwayland acts as translation layer be‐
tween the X protocol and the Wayland protocol but does not have direct access to the hardware. The X Input
Extension devices created by Xwayland ("xwayland-pointer", "xwayland-keyboard", etc.) map to the Wayland
protocol devices, not to physical devices.

These X Input Extension devices are only visible to other X clients connected to the same Xwayland process.
Changing properties on Xwayland devices only affects the behavior of those clients. For example, disabling
an Xwayland device with xinput does not disable the device in Wayland-native applications. Other changes may
not have any effect at all.

In most instances, using xinput with an Xwayland device is indicative of a bug in a shell script and xinput
will print a warning. Use the Wayland Compositor's native device configuration methods instead.
This task depends upon

Closed by  freswa (frederik)
Monday, 23 March 2020, 15:58 GMT
Reason for closing:  Upstream
Additional comments about closing:  Thank you for filling this report. I don't see where this is a packaging issue in Arch. If I missed something, please fill the re-open request. Otherwise please fill a bugreport upstream to get this fixed. Thank you :)

Loading...