search

debauchee / barrier

Open-source KVM software
Other
27.39k stars 1.51k forks source link

Cursor stuk on the side of client but doesn't move beyond that #333

Open PAGuardado opened 5 years ago

PAGuardado commented 5 years ago

Operating Systems

Server: Windows 10 Version1809 (SO compilation 1776.503)

Client: Windows 10 Version1809 (SO compilation 17763.437)

Barrier Version

2.1.0-RELEASE-0b2dfd80

Steps to reproduce bug

I connect the client with the server using 'Auto config' and wait until the log reads that the computers are connected (I don't even know how to get the computers connected everytime)

After somehow achieving the connection I move the mouse from the server to the client, but on the first attempts the mouse bounces back when reaching the side of the screen.

After a few tries the log on both computers say "enter screen" and "leave sceen" respectively, but I don't see the mouse everywhere on the client screen.

I right click and get the menu right on the edge of the client's screen, but mouse is stuck there.

(Keyboard works alright on the client. I manage to test this using arrow keys)

I´m able to return the mouse to the server, but I'm unabe to use it on the client

noisyshape commented 5 years ago

Unless I'm missing something, it sounds like the server has a high DPI setting which doesn't work correctly in 2.1.0. Try installing a more recent release.

infinitempg commented 5 years ago

I'm having a similar issue here, but with a Windows/Mac server/client setup. When I connect my external display to my server and then try to move from the external display left to the client, the cursor gets stuck in the top left.

Not sure what to do since there's no 2.2.0 release for OSX.

noisyshape commented 5 years ago

@infinitempg that's a different problem. Try restarting the server after connecting the new display. If that doesn't fix it, open a new issue.

infinitempg commented 5 years ago

@noisyshape I managed to solve it by downgrading my Windows server down to 2.1.0.

miguelangel-nubla commented 5 years ago

For me it was fixed by building and using the 2.2 linux client

urugang commented 1 year ago

same to me. both 2.4.0-release on arch(server) and macbook(client). when i ssh to arch(server), and kill barriers. it back to normal.