Linux: Is it possible to somehow invert mouse motion in Amyberry?

[Braintoe]

I am trying to use Amiberry (7.1.0 installed) on my MX Linux KDE here instead of WinUAE+Lutris, but for some reason I fail miserably to get my mouse running correctly:

• if I use a normal mouse (which is what I use in WinUAE and it works fine there - ) the pointer is stuck some random area of the screen. It moves exactly one pixel to the opposite direction the mouse is moved, and that's it. (Edit: If I move the mouse rapidly, the pointer inside Amiberry moves 2..3px but jumps back to 1 pixel when the motion has ended)
• if I use my Wacom tablet (which I use as a mouse replacement at times to give my hand some rest), the mouse moves as it should if I set mouse speed in Amiberry down to 5...10% - but inside Amiberry, the pointer moves in the opposite direction (up instead of down, right instead of left) than it does anywhere else.

Input settings are:

• Port 0 : System mouse / No autofire (normal) / Default (tried "Mouse" and "Wheel Mouse" as well, no effect)
• Port 1, 2 and 3: "none"
• Virtual Mouse driver not active (if I activate it using the "both" setting, the mouse gets stuck at the lower right edge inside Amiberry while the KDE Mouse pointer moves as it ought to inside the Amiberry window but does do anything)

Is there some way to solve this? MX uses the X Window system, which means Amiberry should only have to handle X mouse events...

[Braintoe]

In case it might help anyone: the xev event testing program tells me that the top left of the window is the coordinate 0,0 here. An mouse motion event yields this result:

MotionNotify event, serial 37, synthetic NO, window 0x8c00001, root 0x1e0, subw 0x0, time 14571050, (159,122), root:(1816,477), state 0x10, is_hint 0, same_screen YES

with "159,122" being the current horizontal and vertical coordinate of the mouse pointer relative to the top left edge of the window.

[Braintoe]

Update: might have solved itself for some reason - after several restarts of Amiberry without doing something special apart from trying if a game would start the problem simply seems to have vanished O.o