github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #358] Mouse cursor invisible in Linux/Gnome 3.30.2 on Wayland client #287

New issue

Closed

opened 2026-05-05 05:57:22 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 05:57:22 -06:00

Owner

Originally created by @LIII-XXII on GitHub (Jul 9, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/358

Operating Systems

Server: Windows 10 1809 17763.557

Client: Gentoo / Gnome 3.30.2 on Wayland

Barrier Version

2.1.2 from pixlra overlay: qt5, openSSL

Steps to reproduce bug

The mouse cursor does not appear on the Linux/Wayland client.
I can click things, type text, etc, but the mouse cursor is not visible...

Other info

I saw that there is a possible workaround by enabling mouse cursor even with touch screens in Gnome, but the setting does not seem to be there in my Gnome version.

gsettings set org.gnome.settings-daemon.plugins.cursor active false
No such schema “org.gnome.settings-daemon.plugins.cursor”

Originally created by @LIII-XXII on GitHub (Jul 9, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/358 ### Operating Systems ### Server: Windows 10 1809 17763.557 Client: Gentoo / Gnome 3.30.2 on Wayland ### Barrier Version ### 2.1.2 from pixlra overlay: qt5, openSSL ### Steps to reproduce bug ### The mouse cursor does not appear on the Linux/Wayland client. I can click things, type text, etc, but the mouse cursor is not visible... ### Other info ### I saw that there is a possible workaround by enabling mouse cursor even with touch screens in Gnome, but the setting does not seem to be there in my Gnome version. ``` gsettings set org.gnome.settings-daemon.plugins.cursor active false No such schema “org.gnome.settings-daemon.plugins.cursor” ```

gitea-mirror

2026-05-05 05:57:22 -06:00

closed this issue
added the
windows

linux
labels

gitea-mirror commented

2026-05-05 05:57:27 -06:00

Author

Owner

@AdrianKoshka commented on GitHub (Jul 9, 2019):

There is no wayland support unfortunately.

@AdrianKoshka commented on GitHub (Jul 9, 2019): There is no wayland support unfortunately.

gitea-mirror commented

2026-05-05 05:57:30 -06:00

Author

Owner

@LIII-XXII commented on GitHub (Jul 19, 2019):

I have XWayland libraries though, which claim to be downwards compatible with X server interfaces. I believe the mouse cursor not being visible is actually caused by some gnome usb tablet settings disabling the cursor icon, because everything works besides that.

@LIII-XXII commented on GitHub (Jul 19, 2019): I have XWayland libraries though, which claim to be downwards compatible with X server interfaces. I believe the mouse cursor not being visible is actually caused by some gnome usb tablet settings disabling the cursor icon, because everything works besides that.

gitea-mirror commented

2026-05-05 05:57:32 -06:00

Author

Owner

@LIII-XXII commented on GitHub (Jul 19, 2019):

is something from Barrier supposed to show up in xinput? It's a laptop, I have a mouse and a touchpad.
This is the output with the Barrier client connected to a server.

xinput
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ xwayland-pointer:17                     	id=6	[slave  pointer  (2)]
⎜   ↳ xwayland-relative-pointer:17            	id=7	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ xwayland-keyboard:17                    	id=8	[slave  keyboard (3)]

@LIII-XXII commented on GitHub (Jul 19, 2019): is something from Barrier supposed to show up in xinput? It's a laptop, I have a mouse and a touchpad. This is the output with the Barrier client connected to a server. ``` xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ xwayland-pointer:17 id=6 [slave pointer (2)] ⎜ ↳ xwayland-relative-pointer:17 id=7 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ xwayland-keyboard:17 id=8 [slave keyboard (3)] ```

gitea-mirror commented

2026-05-05 05:57:34 -06:00

Author

Owner

@frohro commented on GitHub (Apr 11, 2021):

I just installed Ubuntu 21.04, and it uses Wayland by default. I noticed this behavior too. You can click on things, and it works. It is just you cannot see the position of the mouse cursor. For example, some programs change the display when the mouse hovers over something. You can click on that and it work fine. When I saw "no Wayland support," I didn't expect it to look so very close to working. I can even type things just fine. It is just difficult to figure out what will receive the text.

@frohro commented on GitHub (Apr 11, 2021): I just installed Ubuntu 21.04, and it uses Wayland by default. I noticed this behavior too. You can click on things, and it works. It is just you cannot see the position of the mouse cursor. For example, some programs change the display when the mouse hovers over something. You can click on that and it work fine. When I saw "no Wayland support," I didn't expect it to look so very close to working. I can even type things just fine. It is just difficult to figure out what will receive the text.

gitea-mirror commented

2026-05-05 05:57:37 -06:00

Author

Owner

@pangyuteng commented on GitHub (Oct 2, 2021):

I updated from Ubuntu 20.04 to 21.04, cursor and keyboard both do not work (cannot click, cannot type), but barrier can detect the cursor coming into the client - based on the logs.

Below is one solution for those using Ubuntu and is not constrainted to Wayland.
You could just opt for Xorg during login - during the password prompt, click Ubuntu on Xorg at the bottom right corner. cheers.

@pangyuteng commented on GitHub (Oct 2, 2021): I updated from Ubuntu 20.04 to 21.04, cursor and keyboard both do not work (cannot click, cannot type), but barrier can detect the cursor coming into the client - based on the logs. Below is one solution for those using Ubuntu and is not constrainted to Wayland. You could just opt for Xorg during login - during the password prompt, click `Ubuntu on Xorg` at the bottom right corner. cheers.

gitea-mirror commented

2026-05-05 05:57:39 -06:00

Author

Owner

@nicecil commented on GitHub (Mar 17, 2022):

jjjj

@nicecil commented on GitHub (Mar 17, 2022): jjjj

gitea-mirror referenced this issue

2026-05-05 07:57:08 -06:00

[PR #287] [MERGED] Windows installer fix #1593