mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1713] Cursor disappears on server and client #1265
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1265
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @dot19408 on GitHub (Jul 9, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1713
What happened?
Windows 10 server - 4k display scaled 100%
Tested with 2nd display and without.
Ubuntu 22.04 Desktop client - 1080p single display
Removed the 2nd display from server to test.
Moving from server to client, cursor disappears before hitting the display edge. Cursor disappears on client too and never is visible. I cannot get back to the server screen. I have to use the client's mouse and stop Barrier to recover the cursor on the server.
If server has scaling enabled, the distance from the edge of the display that the cursor disappears is greater.
If I use a 2nd display (between server and client) the cursor disappears 50% across the 2nd display.
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
Downloaed .exe from Github (https://github.com/debauchee/barrier)](https://github.com/debauchee/barrier/releases/tag/v2.4.0)
apt install barrier on Ubuntu 22.04 desktop
What OSes are you seeing the problem on? (Check all that apply)
Linux, Windows
What OS versions are you using?
Windows 10 Pro 21H2 19044.1766 Windows Feature Experience Pack 120.2212.4180.0
Ubuntu 22.04 x64 GNOME 42.2 Wayland
Relevant log output
Any other information
No response
@shinhwas commented on GitHub (Jul 15, 2022):
I have the same issue. I lost the cursor and can't go back to the server.
The server is on the windows 10 pro with a dual 4k monitor.
The client is on macbook pro with m1.
@iggut commented on GitHub (Jul 24, 2022):
Same here Windows and Mac Monterey 12.5. Was working perfectly until I swapped monitors from left to right and did the corresponding changes in the setting gui positioning window.
@Ridri commented on GitHub (Jul 30, 2022):
I have the same problem with a windows 10 client and server.
@mkostersitz commented on GitHub (Aug 8, 2022):
I found that pressing CTRL-ALT-DEL on the Windows Server "pulls" the cursor back to the server screens. After that it works again for some time before disappearing again.
Also make sure on the Windows Server to set the main display to one that has 100% scale factor. There is an issue with scales >100% that makes the cursor not move as intended
@Ankitchan commented on GitHub (Aug 9, 2022):
@mkostersitz Thanks for the solution it seems to work when I reduce the scale factor to 100% on windows server. I'm curious how did you figure it out?
@mkostersitz commented on GitHub (Aug 9, 2022):
@Ankitchan I realized that when my main screen is set to one that has 100% scale everything works if it is my device display (200%) it fails.
@Veggie13 commented on GitHub (Aug 9, 2022):
I'll pile on and describe my configuration where this issue happens. Server (S) is laptop (1) + 2 monitors, client (C) is laptop.
I've configured it as so:
S1 (3840x2400 @ 250%)
S2 & S3 (1920x1080 @ 100%)
C (3000x2000 @ 200%)
S1 - S3 - S2 -|- C
@dmchmk commented on GitHub (Aug 10, 2022):
Hi! Same issue here:
Server: Win10 Home 21H2, 2k screen, 125% scaling
Client: MacBook Pro 14", MacOS 12.5
Barrier version: 2.4.0
If I switch server scaling down to 100%, everything's fine, but with scaling enabled cursor just disappears to the farmost downright angle of the client (client is configured to be on the right side of the server's screen)
@Feneck91 commented on GitHub (Aug 29, 2022):
I have the same problem. Is a way to workaround this problem?
@mkostersitz commented on GitHub (Aug 29, 2022):
The only workaround I know is to select a screen with 100% scale as the main screen on your server. That seems to reduce the occurrences of the issue
@Feneck91 commented on GitHub (Aug 29, 2022):
Probably but with 100% scale we must change eyes: too small to be correctly used, we cannot see nothing on the 4K 28'' screen.
Hope it will be patched on the future.
@hannesrudolph commented on GitHub (Sep 26, 2022):
Also confirmed error was remedied when I set to 100%. I have good eyes but damn this stuff is tiny. im good with 150% most of the time. Oh well.
@mikesmichael commented on GitHub (Oct 14, 2022):
I found that only the main monitor need to be scale 100%, so I change my main monitor to one where it's okay to be 100% and let the laptop to 150%. Working well.
@ghost commented on GitHub (Oct 18, 2022):
I am experiencing this issue too with Scaling > 100% on 4K monitors
@zpengcom commented on GitHub (Nov 12, 2022):
Barrier version: 2.4.0
----Everything is fine---------------
Server: Win11 21H2, 1920X1080p 100% scaling
Client: Win11, 22H2 surface lptop studio 2400X1600p 150% scaling
----BUT-------------------------
Server: Win11, 22H2 surface laptop studio 2400X1600p 150% scaling
Client: Win11 21H2, 1920X1080p 100% scaling
Client does not show mouse pointer，Tried to fix cursor but it doesn't work
@tof0074 commented on GitHub (Nov 28, 2022):
I had the same issue. I cannot change scaling and be able to read text on my monitor. Only way I was able to resolve is to go back to version 2.3.4 on windows server. Everything is working now.
@zpengcom commented on GitHub (Nov 30, 2022):
I tried the version of 2.3.4; after setting the firewall port in the system, it was perfectly running ~
@njboom01 commented on GitHub (Dec 1, 2022):
I had the same issue though I have a Linux ubuntu 22.04.1 and a Mac OS Ventura both with barrier 2.4.0 installed.
@gcyangxin commented on GitHub (Dec 5, 2022):
i slove the problem by adjusting scale of window to 100%
@dmchmk commented on GitHub (Dec 5, 2022):
@gcyangxin just walking away from the bug conditions isn't really a solution of the bug:)
@santospaulm commented on GitHub (Jan 1, 2023):
Can confirm that version 2.3.4 does not have this issue. Maybe hope then this will be resolved in a future release.
@mattroyal commented on GitHub (Jan 10, 2023):
I'm also affected.
Server: Win10 22H2, 100% scaling
barrier 2.4.0
Client: Ubuntu 22.04.1 LTS, 100% scaling, Wayland
barrier 2.4.0
I did not have this problem before a recent upgrade from Ubuntu 20.04.
I just discovered that this doesn't appear to be a problem when logging into an Xorg session; only a Wayland session.
I see this issue was opened about six months ago; do we think it will be worked on?
@deanrobin333 commented on GitHub (Feb 23, 2023):
This worked perfectly for me as well.. I tried disabling wayland which didn't work, but noticed it fixed the auto-rotation problem. It also brought back the auto-rotation setting. So I shall probably have Wayland disabled for now. Am using ubuntu on an old surface, the microsoft surface pro 2.
Scaling was not an option I was going to consider. I have 3 monitors set up and all of them have to be scaled up at least to 125% otherwise viewing becomes a problem
To disable wayland
open terminal (ctr + alt + t) then type
sudo nano /etc/gdm3/custom.confuncomment this
#WaylandEnable=falsepress (ctrl + x) then run
sudo systemctl restart gdm3it can be undone by going through the same procedure and commenting again. (to uncomment just remove the "#" at the begining of
#WaylandEnable=false.@deanrobin333 commented on GitHub (Feb 23, 2023):
Kept having issues with by disabling wayland. easiest thing to do to achieve the same, is by selecting "ubuntu on xorg" when you log in. it will allow you to use x11 instead of the wayland, without going through the process of changing the file.
when you click your username to log in, you should see a settings icon at the bottom right; clicking this should allow you to select xorg.
However version 2.4 will still not work, you have to use version 2.3.4
@p6002 commented on GitHub (Apr 1, 2023):
Is there a solution or debian distro where this works?
I can't disable Wayland because then the screen doesn't work afterwards.
@ashishanand7 commented on GitHub (Apr 3, 2023):
I confirm that #1506 has solved the issue for me.
@kipz commented on GitHub (Apr 20, 2023):
+1 from me too.
@p6002 commented on GitHub (Apr 20, 2023):
This doesn't fix the issue, it just moves it to the side.
Currently there is no way to control ubuntu on proxmox using windows computer.
I solved this problem in your style and installed windows on vm.
@SarahSmitho commented on GitHub (Apr 23, 2023):
I solve this problem with this article , maybe it can help
https://linuxconfig.org/how-to-enable-disable-wayland-on-ubuntu-22-04-desktop
The important point is this:
WaylandEnable=true
The other answer maybe can help you:
https://askubuntu.com/questions/1409533/barrier-does-not-work-for-linux-to-windows-connection
@p6002 commented on GitHub (Apr 23, 2023):
That won't work, because ubuntu won't boot into proxmox without wayland and will crash on startup.
@mcarp0 commented on GitHub (May 11, 2023):
Changing the scale to 100% worked for me. I did not even know this setting existed. Thank you.
@JPir-Pt commented on GitHub (May 25, 2023):
Windows 10 build 19045.2965 (server)
iMac macOS Ventura ver 13.4 (client)
Barrier v2.4.0 on both (dowloaded from GitHub)
If scale is 125% on Windows, cursor disapears when moving to iMac (scale 100% works fine)
@elseasama commented on GitHub (Jun 14, 2023):
This is the best solution!
@p6002 commented on GitHub (Jun 14, 2023):
The barrier is slowly dying. Currently, it only works on windows, where there are more convenient tools of this type. I myself was forced to abandon the Ubuntu VM in favor of a buggy W10.
@gaieges commented on GitHub (Jan 25, 2024):
This problem started for me when I upgraded my windows box to 2.4.0. Reverting to 2.3.4 fixed it for me, even with 150% scaling:
https://github.com/debauchee/barrier/releases/tag/v2.3.4
@carvakaguru commented on GitHub (Jan 27, 2024):
The binaries provided in the post below resolves the issue. Copy the two executables "barrierc.exe" and "barriers.exe" from the executables.zip file to the installation directory of barrier and restart barrier. That should fix the issue.
https://github.com/debauchee/barrier/pull/1506#issuecomment-1013758495
@Veggie13 commented on GitHub (Jan 28, 2024):
Seems weird that we're passing around binary downloads in the comments to fix the issue, rather than the fix going into a true release. It looks like it's been merged to
masterin 2022, so why does the latest release not work?@carvakaguru commented on GitHub (Jan 29, 2024):
Because the last (latest) release v2.4.0 is from Nov 1st 2021 and this fix went in on the 3rd of Feb 2022. Actually there have been at least 30-40 verified commits since the last release v2.4.0 so perhaps it is time for building v2.4.1? Not sure who is responsible for doing the releases.
@gaieges commented on GitHub (Jan 29, 2024):
I would presume the owner of the repo: @debauchee .. perhaps they have some thoughts here. I can't see the other maintainers anywhere in this repo, if there are any.
Is another possible option if they don't see this message here.
@zhenniqi commented on GitHub (Mar 23, 2024):
This solve my problem , thank you!
@gh0stisic commented on GitHub (Apr 15, 2024):
I had a similar issue where no matter which machine was acting as server/client (MacOS or Win) I would lose the cursor upon moving from environment to environment.
My setup was the issue: I had a 50" TV mounted above my 2 27" monitors. I was extending the display of my windows machine to the TV which was causing the scale to go from 100% to 300% on the TV screen. I simply removed the HDMI and disconnected the TV from my PC and windows automatically changed the scaling back to 100% on the main screen. Now I have two monitors sitting side-by-side: left is MacOS and the right transfers into Windows without any issues.
Problem solved. Sad that I can't use the TV as an extended monitor if I want to use a single keyboard and mouse, but it's a trade off I'm willing to make considering I don't have the space for two keyboard and 2 mice - and the logi options just sucks.
@harsh-lodhi commented on GitHub (May 25, 2024):
Thanks
@bobatgit commented on GitHub (Jul 4, 2024):
Same issue here!
I have two WIndows devices both on 150% scaling running Barrier 2.4.0. The cursor / mouse pointer disapears the moment a connection is made. But, when I go back to 100% scaling the cursor re-appears.....
Appreciate the 'workaround' to make it work, but I can't use my devices well enough at low scaling 😅
@carvakaguru commented on GitHub (Jul 5, 2024):
@bobatgit, see my https://github.com/debauchee/barrier/issues/1713#issuecomment-1913340994 for a permanent fix for this issue.
@farhansolodev commented on GitHub (Jul 19, 2024):
FWIW, you can find build artifacts produced as late as July 2022 on Azure Pipelines. These do include the fixes introduced in #1506, and it works for me just fine.
@vsouto commented on GitHub (Feb 4, 2025):
Wow.
After debugging my Windows - Mac connection for nearly 1hour now, I've found this gentlement's post falling from heaven like an angel.
Changed my Windows to 100% display scale and worked just fine.
Thanks!
@jiluoxingren commented on GitHub (Apr 7, 2025):
with build artifacts produced as late as July 2022 on Azure Pipelines, download url :
https://dev.azure.com/debauchee/169cf39a-492c-408a-aacd-827752119933/_apis/build/builds/782/artifacts?artifactName=Windows%20Release%20Installer&api-version=7.1&%24format=zip
@nbolton commented on GitHub (Apr 7, 2025):
Please try Deskflow or Input Leap as Barrier is no longer in development.
https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap
Both are compatible with Barrier client/server so you can try on one of your computers.
If this is still an issue in those projects, we would appreciate a cross-post of this issue.
Not sure which to use? The 'Insights' tab of each project may help you decide.