[GH-ISSUE #634] cursor passes/travels only in front of opened browser window #503

New issue

Closed

opened 2026-05-05 06:33:09 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:33:09 -06:00

Owner

Originally created by @AWHubGit on GitHub (Apr 23, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/634

I installed/use Barrier on

Arch Linux Barrier version 2.3.2
Kernel: x86_64 Linux 5.6.6-arch1-1 Resolution: 3840x2160 DE: GNOME 3.36.1
GPU: Mesa Intel(R) Iris(R) Plus Graphics 655 (CFL GT3)
macOS Mojave 10.14.6 on iMac 2017 Barrier 2.3.2-Release-210c2b70

Arch Linux is the server and Mojave the client.

The cursor moves from Arch Linux to macOS only in front of an opened browser window. When no browser window is open or browser window is minimized, then the cursor on Arch Linux gets stuck on the border of the monitor of Arch Linux. Browser doesn't matter: Chromium or Firefox.

How to get the cursor always passed?

Log on barrier server:
INFO: leaving screen
INFO: switch from "imac" to "arch" at 76,1086
INFO: entering screen
INFO: switch from "arch" to "imac" at 2047,220
INFO: leaving screen
INFO: screen "arch" updated clipboard 0
..................only infos ....................................

log client has the same infos, but with warnings "cursor may not be visible".

Edit: I use Gnome on Wayland.

Rgds
AW

Originally created by @AWHubGit on GitHub (Apr 23, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/634 I installed/use Barrier on - Arch Linux Barrier version 2.3.2 Kernel: x86_64 Linux 5.6.6-arch1-1 Resolution: 3840x2160 DE: GNOME 3.36.1 GPU: Mesa Intel(R) Iris(R) Plus Graphics 655 (CFL GT3) - macOS Mojave 10.14.6 on iMac 2017 Barrier 2.3.2-Release-210c2b70 Arch Linux is the server and Mojave the client. The cursor moves from Arch Linux to macOS only in front of an opened browser window. When no browser window is open or browser window is minimized, then the cursor on Arch Linux gets stuck on the border of the monitor of Arch Linux. Browser doesn't matter: Chromium or Firefox. How to get the cursor always passed? Log on barrier server: INFO: leaving screen INFO: switch from "imac" to "arch" at 76,1086 INFO: entering screen INFO: switch from "arch" to "imac" at 2047,220 INFO: leaving screen INFO: screen "arch" updated clipboard 0 ..................only infos .................................... log client has the same infos, but with warnings "cursor may not be visible". Edit: I use Gnome on Wayland. Rgds AW

gitea-mirror closed this issue

2026-05-05 06:33:11 -06:00

gitea-mirror commented

2026-05-05 06:33:14 -06:00

Author

Owner

@toryano0820 commented on GitHub (May 26, 2020):

I also have this issue on Ubuntu 20.04 using GNOME Wayland.

@toryano0820 commented on GitHub (May 26, 2020): I also have this issue on Ubuntu 20.04 using GNOME Wayland.

gitea-mirror commented

2026-05-05 06:33:16 -06:00

Author

Owner

@simons-public commented on GitHub (May 26, 2020):

@AWHubGit @toryano0820 That happens because Wayland isn't supported by Barrier yet. You can still use the cursor when it passes over a window that uses X11 on Wayland but it isn't really functional.

@simons-public commented on GitHub (May 26, 2020): @AWHubGit @toryano0820 That happens because Wayland isn't [supported by Barrier yet](https://github.com/debauchee/barrier/projects/1). You can still use the cursor when it passes over a window that uses X11 on Wayland but it isn't really functional.

gitea-mirror commented

2026-05-05 06:33:18 -06:00

Author

Owner

@p12tic commented on GitHub (Sep 22, 2020):

Closing as a duplicate of #247. The bug for actual Wayland support is in #109.

@p12tic commented on GitHub (Sep 22, 2020): Closing as a duplicate of #247. The bug for actual Wayland support is in #109.

gitea-mirror referenced this issue

2026-05-05 07:58:39 -06:00

[PR #533] [MERGED] Fix #503 - Clarify on README how to report issues #1653