[GH-ISSUE #50] Problems after rotating the screen. #41

New issue

Closed

opened 2026-05-05 04:50:35 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 04:50:35 -06:00

Owner

Originally created by @c-mauderer on GitHub (May 27, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/50

Operating System (server and client): Arch Linux with 4.16.10-1-ARCH Kernel
Barrier Version: 2.1.0 (from Arch AUR)

My client is a tablet. If I rotate the screen (for example via xrandr -o right), barrier has problems after the rotation. The mouse cursor (moved via barrier) is hanging at one edge of the screen and I can't reach any positon. I can move the cursor normal with a directly connected mouse or with the touchscreen. Keyboard input works normal.

Note that I also had that problem with an (old) synergy version on some other hardware. On synergy I have been able to just killall synergyc to get a running instance again. It seems that this workaround doesn't work with barrier any more.

Edit: I totally forgot: A big thanks for continuing the development of synergy in this fork. I really like it a lot more than the "new" synergy.

Originally created by @c-mauderer on GitHub (May 27, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/50 Operating System (server and client): Arch Linux with 4.16.10-1-ARCH Kernel Barrier Version: 2.1.0 (from Arch AUR) My client is a tablet. If I rotate the screen (for example via `xrandr -o right`), barrier has problems after the rotation. The mouse cursor (moved via barrier) is hanging at one edge of the screen and I can't reach any positon. I can move the cursor normal with a directly connected mouse or with the touchscreen. Keyboard input works normal. Note that I also had that problem with an (old) synergy version on some other hardware. On synergy I have been able to just `killall synergyc` to get a running instance again. It seems that this workaround doesn't work with barrier any more. Edit: I totally forgot: A big thanks for continuing the development of synergy in this fork. I really like it a lot more than the "new" synergy.

gitea-mirror closed this issue

2026-05-05 04:50:40 -06:00

gitea-mirror commented

2026-05-05 04:50:43 -06:00

Author

Owner

@c-mauderer commented on GitHub (Jun 9, 2018):

Found out some more details about that problem: It seems that it isn't with rotating the screen but with rotating the touch of the tablet. My method for that recently changed (as did my synergy / barrier usage). Some time back I used a script that rotated specifically one touch device. My new script rotates every device that has a "Coordinate Transformation Matrix" via (for example)

xinput set-prop 2 150 0 -1 1 1 0 0 0 0 1

That works well as long as there is only a touch screen. But for some reason the "Virtual core XTEST pointer" has a "Coordinate Transformation Matrix" too that shouldn't be rotated. So it's not a bug of barrier but one of my rotation script. I'll fix that there.
Sorry for the wrong bug.

@c-mauderer commented on GitHub (Jun 9, 2018): Found out some more details about that problem: It seems that it isn't with rotating the screen but with rotating the touch of the tablet. My method for that recently changed (as did my synergy / barrier usage). Some time back I used a script that rotated specifically one touch device. My new script rotates every device that has a "Coordinate Transformation Matrix" via (for example) ``` xinput set-prop 2 150 0 -1 1 1 0 0 0 0 1 ``` That works well as long as there is only a touch screen. But for some reason the "Virtual core XTEST pointer" has a "Coordinate Transformation Matrix" too that shouldn't be rotated. So it's not a bug of barrier but one of my rotation script. I'll fix that there. Sorry for the wrong bug.

No labels

Rows
Columns