You are not logged in.
Pages: 1
So I suspect this is connected to the recent update to Gnome 40. Previously I could map the
Wacom Tablet to a designated screen. Now GUI wise I can still do this but it has no effect.
I was following then this gist.
The settings indeed have been changed when again querying with xinput list-props device-id, but have no effect.
I get a warning 'WARNING: running xinput against an Xwayland server. See the xinput man page for details.'
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.
leads me to believe that I'm not changing the settings of the actual thing. But here I am lost, what Xwayland is even doing.
I just don't know what command to use (xsetwacom is for Xorg, which most of the arch wiki regarding wacom tablets is based upon),
and I am lacking fundamental knowledge of the underlying structure.
xinput output
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ xwayland-pointer:18 id=6 [slave pointer (2)]
⎜ ↳ xwayland-relative-pointer:18 id=7 [slave pointer (2)]
⎜ ↳ xwayland-tablet stylus:18 id=9 [slave pointer (2)]
⎜ ↳ xwayland-tablet eraser:18 id=10 [slave pointer (2)]
⎜ ↳ xwayland-tablet cursor:18 id=11 [slave pointer (2)]
⎜ ↳ xwayland-tablet-pad:18 id=12 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ xwayland-keyboard:18 id=8 [slave keyboard (3)]
Offline
Ah, hoped to find an answer to this.
Recently bought the Intous Medium and noticed that the sensitivity of the tablet is totally off since it tries to stretch out the surface across the 3 monitors i use.
Have you found a solution the past month?
Offline
Pages: 1