Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cursor passes/travels only in front of opened browser window #634

Closed
AWHubGit opened this issue Apr 23, 2020 · 3 comments
Closed

cursor passes/travels only in front of opened browser window #634

AWHubGit opened this issue Apr 23, 2020 · 3 comments

Comments

@AWHubGit
Copy link

AWHubGit commented Apr 23, 2020

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

@toryano0820
Copy link

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

@simons-public
Copy link

@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.

@p12tic
Copy link
Member

p12tic commented Sep 22, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants