[GH-ISSUE #793] Mouse cursor hides with Ubuntu and Kali #625

Closed
opened 2026-05-05 06:48:16 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @rios0rios0 on GitHub (Jul 12, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/793

Operating Systems

Server: Ubuntu 18.04.4 LTS (GNOME 3.28.2)
Client: Kali GNU/Linux Rolling (GNOME 3.36.3)

The cursor on the server hides, and on the client doesn't show.
The log on DEBUG2, show some errors like this:

DEBUG2: want to read, error=2, attempt=1
DEBUG2: can't read property 471 on window 0x00600008

But the messages aren't cleary.
I tried the installation on Kali by the source and tried with the rolling package.
On Ubuntu, I installed the package from snap repositories.

Barrier Version

On Ubuntu: 2.3.2-snapshot-9080ce45
On Kali: 2.3.2-Release-00000000

Steps to reproduce bug

  1. Installed dependencies on both: sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev libavahi-compat-libdnssd-dev libssl-dev libx11-dev libqt4-dev qtbase5-dev
  2. Just install on two machines;
  3. Configure the client and the server;
  4. Try to move the mouse between screens. And mouse cursor hides from the server, and doesn't appear on the client.
  5. Move the mouse back (a lot of logs about this movement with DEBUG2), and mouse return to the server;
  6. Nothing keypress works on the client. But logs exist.

Other info

  • When did the problem start to occur? Always
  • Is there a way to work around it? No
  • Does this bug prevent you from using Barrier entirely? Yes

Running with terminal (on Kali), I have this information:

Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

It can be occur because on Kali 2020.2 doesn't have libqt4-dev. I installed qt5-default, but it's not solved the problem.

Originally created by @rios0rios0 on GitHub (Jul 12, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/793 ### Operating Systems ### Server: Ubuntu 18.04.4 LTS (GNOME 3.28.2) Client: Kali GNU/Linux Rolling (GNOME 3.36.3) The cursor on the server hides, and on the client doesn't show. The log on DEBUG2, show some errors like this: ``` DEBUG2: want to read, error=2, attempt=1 DEBUG2: can't read property 471 on window 0x00600008 ``` But the messages aren't cleary. I tried the installation on Kali by the source and tried with the rolling package. On Ubuntu, I installed the package from snap repositories. ### Barrier Version ### On Ubuntu: 2.3.2-snapshot-9080ce45 On Kali: 2.3.2-Release-00000000 ### Steps to reproduce bug ### 0. Installed dependencies on both: `sudo apt install git cmake make xorg-dev g++ libcurl4-openssl-dev libavahi-compat-libdnssd-dev libssl-dev libx11-dev libqt4-dev qtbase5-dev` 1. Just install on two machines; 2. Configure the client and the server; 3. Try to move the mouse between screens. And mouse cursor hides from the server, and doesn't appear on the client. 4. Move the mouse back (a lot of logs about this movement with DEBUG2), and mouse return to the server; 5. Nothing keypress works on the client. But logs exist. ### Other info ### * When did the problem start to occur? Always * Is there a way to work around it? No * Does this bug prevent you from using Barrier entirely? Yes Running with terminal (on Kali), I have this information: `Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.` It can be occur because on Kali 2020.2 doesn't have `libqt4-dev`. I installed `qt5-default`, but it's not solved the problem.
Author
Owner

@rios0rios0 commented on GitHub (Jul 17, 2020):

Hello there.
This problem is caused by Wayland.
Barrier isn't supported on Wayland yet (work in progress here). I can close this issue, because switching GNOME of Kali to use Xorg, worked fine.
Thank you.

<!-- gh-comment-id:660385736 --> @rios0rios0 commented on GitHub (Jul 17, 2020): Hello there. This problem is caused by Wayland. **Barrier** isn't supported on Wayland yet (work in progress [here](https://github.com/debauchee/barrier/projects/1)). I can close this issue, because switching GNOME of Kali to use Xorg, worked fine. Thank you.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#625
No description provided.