[GH-ISSUE #1241] When I drag my mouse from laptop 1 to laptop 2 the mouse disappears halfway on laptop 1 and appears on laptop 2

gitea-mirror commented

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

Owner

Originally created by @jansaasman on GitHub (Aug 4, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1241

Describe the bug
A clear and concise description of what the bug is.

To Reproduce

Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue.

Desktop (please complete the following information):

OS: [e.g. Windows]
Barrier version [e.g 2.3.3]

Additional context

Add any other context about the problem here.

Originally created by @jansaasman on GitHub (Aug 4, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1241 **Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. Please do not link to image hosting sites, as these can be ephemeral. Instead, attach them to the issue. **Desktop (please complete the following information):** - OS: [e.g. Windows] - Barrier version [e.g 2.3.3] **Additional context** Add any other context about the problem here.

gitea-mirror commented

2026-05-05 07:22:11 -06:00

Author

Owner

@jansaasman commented on GitHub (Aug 4, 2021):

I'm running on Windows 10
My main laptop is a Dell XPS 15 (2020) -> let's call it DellNew
My second laptop is also a Dell XPS 15 (2017) -> let's call it DellOld

I use a Dell 34 inch curved screen as my main working screen. It is attached to DellNew
The general physical Layout is: BigCurvedScreen -> DellNew --> DellOld

I installed barrier on both Dells and the installation was very easy.
I can even move the mouse from BigCurvedScreen to DellNew to DellOld

The big problem is: when I move from DellNew to DellOld the cursor on DellNew only goes to halfway the screen and then
instantly appears on DellOld. So I can't do anything anymore on the right part of DellNew.

Thanks for helping out,
cheers, Jans

@jansaasman commented on GitHub (Aug 4, 2021): I'm running on Windows 10 My main laptop is a Dell XPS 15 (2020) -> let's call it DellNew My second laptop is also a Dell XPS 15 (2017) -> let's call it DellOld I use a Dell 34 inch curved screen as my main working screen. It is attached to DellNew The general physical Layout is: BigCurvedScreen -> DellNew --> DellOld I installed barrier on both Dells and the installation was very easy. I can even move the mouse from BigCurvedScreen to DellNew to DellOld The big problem is: when I move from DellNew to DellOld the cursor on DellNew only goes to halfway the screen and then instantly appears on DellOld. So I can't do anything anymore on the right part of DellNew. Thanks for helping out, cheers, Jans

gitea-mirror commented

2026-05-05 07:22:12 -06:00

Author

Owner

@bahdan commented on GitHub (Aug 16, 2021):

Hi @jansaasman @p12tic, I've faced a similar issue with the latest version 2.3.3 on my laptops (similar screens configuration to yours). The only reverting to f2bf7cb7e1 commit helps to resolve this strange behavior (as I understand the bug is inside some commit starting from Jan 3, 2021 till today). It works for me because I need only the changes from #910 pull request to be applied on the old release (which works well as well).

@bahdan commented on GitHub (Aug 16, 2021): Hi @jansaasman @p12tic, I've faced a similar issue with the latest version 2.3.3 on my laptops (similar screens configuration to yours). The only reverting to f2bf7cb7e1c501424909da7e744d242a6715d437 commit helps to resolve this strange behavior (as I understand the bug is inside some commit starting from Jan 3, 2021 till today). It works for me because I need only the changes from #910 pull request to be applied on the old release (which works well as well).

gitea-mirror commented

2026-05-05 07:22:13 -06:00

Author

Owner

@jansaasman commented on GitHub (Aug 16, 2021):

Hi: I'm very happy that you found the problem. Given that I'm not very
good at git and rebuilding c system. Is there an executable version that
I should download. It seems anything before Jan 3 would help? cheers, Jans

On 8/16/2021 6:13 AM, bahdan wrote:

Hi @jansaasman https://github.com/jansaasman @p12tic
https://github.com/p12tic, I've faced a similar issue with the
latest version 2.3.3 on my laptops (similar screens configuration to
yours). The only reverting to f2bf7cb
https://github.com/debauchee/barrier/commit/f2bf7cb7e1c501424909da7e744d242a6715d437
commit helps to resolve this strange behavior (as I understand the bug
is inside some commit starting from Jan 3, 2021 till today). It works
for me because I need only the changes from #910
https://github.com/debauchee/barrier/pull/910 pull request to be
applied on the old release (which works well as well).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1241#issuecomment-899499938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB4C7WP2BDTKC4E3IN77ZLT5EFJPANCNFSM5BRXGV7Q.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email.

@jansaasman commented on GitHub (Aug 16, 2021): Hi: I'm very happy that you found the problem. Given that I'm not very good at git and rebuilding c system. Is there an executable version that I should download. It seems anything before Jan 3 would help? cheers, Jans On 8/16/2021 6:13 AM, bahdan wrote: > > Hi @jansaasman <https://github.com/jansaasman> @p12tic > <https://github.com/p12tic>, I've faced a similar issue with the > latest version 2.3.3 on my laptops (similar screens configuration to > yours). The only reverting to f2bf7cb > <https://github.com/debauchee/barrier/commit/f2bf7cb7e1c501424909da7e744d242a6715d437> > commit helps to resolve this strange behavior (as I understand the bug > is inside some commit starting from Jan 3, 2021 till today). It works > for me because I need only the changes from #910 > <https://github.com/debauchee/barrier/pull/910> pull request to be > applied on the old release (which works well as well). > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1241#issuecomment-899499938>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAB4C7WP2BDTKC4E3IN77ZLT5EFJPANCNFSM5BRXGV7Q>. > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email>. >

gitea-mirror commented

2026-05-05 07:22:14 -06:00

Author

Owner

@bahdan commented on GitHub (Aug 17, 2021):

I did not find the executable here, that is why I've built it from the
source code. You should forward other questions to the maintainers. Here is
an installation executable from my build
https://drive.google.com/file/d/1ZFtG3u4AiksEg5gacCz6vR-r3qBpD3Ee, you can
try it if you want. Cheers, Bohdan

On Mon, Aug 16, 2021 at 6:35 PM jansaasman @.***> wrote:

Hi: I'm very happy that you found the problem. Given that I'm not very
good at git and rebuilding c system. Is there an executable version that
I should download. It seems anything before Jan 3 would help? cheers, Jans

On 8/16/2021 6:13 AM, bahdan wrote:

Hi @jansaasman https://github.com/jansaasman @p12tic
https://github.com/p12tic, I've faced a similar issue with the
latest version 2.3.3 on my laptops (similar screens configuration to
yours). The only reverting to f2bf7cb
<
f2bf7cb7e1>

commit helps to resolve this strange behavior (as I understand the bug
is inside some commit starting from Jan 3, 2021 till today). It works
for me because I need only the changes from #910
https://github.com/debauchee/barrier/pull/910 pull request to be
applied on the old release (which works well as well).

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1241#issuecomment-899499938,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AAB4C7WP2BDTKC4E3IN77ZLT5EFJPANCNFSM5BRXGV7Q
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>

or Android
<
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1241#issuecomment-899607875,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIBMCGT6CULC3EEBHM6XLDT5EV5TANCNFSM5BRXGV7Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@bahdan commented on GitHub (Aug 17, 2021): I did not find the executable here, that is why I've built it from the source code. You should forward other questions to the maintainers. Here is an installation executable from my build https://drive.google.com/file/d/1ZFtG3u4AiksEg5gacCz6vR-r3qBpD3Ee, you can try it if you want. Cheers, Bohdan On Mon, Aug 16, 2021 at 6:35 PM jansaasman ***@***.***> wrote: > Hi: I'm very happy that you found the problem. Given that I'm not very > good at git and rebuilding c system. Is there an executable version that > I should download. It seems anything before Jan 3 would help? cheers, Jans > > On 8/16/2021 6:13 AM, bahdan wrote: > > > > Hi @jansaasman <https://github.com/jansaasman> @p12tic > > <https://github.com/p12tic>, I've faced a similar issue with the > > latest version 2.3.3 on my laptops (similar screens configuration to > > yours). The only reverting to f2bf7cb > > < > https://github.com/debauchee/barrier/commit/f2bf7cb7e1c501424909da7e744d242a6715d437> > > > commit helps to resolve this strange behavior (as I understand the bug > > is inside some commit starting from Jan 3, 2021 till today). It works > > for me because I need only the changes from #910 > > <https://github.com/debauchee/barrier/pull/910> pull request to be > > applied on the old release (which works well as well). > > > > — > > You are receiving this because you were mentioned. > > Reply to this email directly, view it on GitHub > > <https://github.com/debauchee/barrier/issues/1241#issuecomment-899499938>, > > > or unsubscribe > > < > https://github.com/notifications/unsubscribe-auth/AAB4C7WP2BDTKC4E3IN77ZLT5EFJPANCNFSM5BRXGV7Q > >. > > Triage notifications on the go with GitHub Mobile for iOS > > < > https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > > > or Android > > < > https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email > >. > > > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1241#issuecomment-899607875>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AAIBMCGT6CULC3EEBHM6XLDT5EV5TANCNFSM5BRXGV7Q> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> > . >

gitea-mirror commented

2026-05-05 07:22:16 -06:00

Author

Owner

@kslen commented on GitHub (Sep 7, 2021):

Can confirm this exact issue between two machines running Arch.

@kslen commented on GitHub (Sep 7, 2021): Can confirm this exact issue between two machines running Arch.

gitea-mirror commented

2026-05-05 07:22:17 -06:00

Author

Owner

@mirh commented on GitHub (Oct 7, 2021):

Can confirm downgrading the server from the latest git to "stable" 2.3.3, fixed the issue.
This is really strange given that there are basically all cosmetic changes since then.

@mirh commented on GitHub (Oct 7, 2021): Can confirm downgrading the server from the latest git to "stable" 2.3.3, fixed the issue. This is really strange given that there are basically all cosmetic changes since then.

gitea-mirror commented

2026-05-05 07:22:18 -06:00

Author

Owner

@aden16rus commented on GitHub (Nov 6, 2021):

i can't confirm that downgrade to 2.3.3 fixed the problem. at first i installed default versions for windows 10 as server 2.4.0 version of barrier and snap package 2.4.0 to ubuntu as client. It works and changes screens but when i toggle to ubuntu mouse cursor works but hidden and keyboard dosn't work at all.
I tried to downgrade windows 10 barrier server application to 2.3.3, nothing changes.
i tried to remove snap package and install 2.3.3 from ubuntu deb packages, nothing changes again.
hotkeys not helps.

next changes:
i switch roles ubuntu to server and windows to client, it doesn't work at all, log shows that client connected but mouse not jumped to another screen on border.
it start to work with hotkeys but not fully correct because mouse jumps randomly on client's[windows] screen

@aden16rus commented on GitHub (Nov 6, 2021): i can't confirm that downgrade to 2.3.3 fixed the problem. at first i installed default versions for windows 10 as server 2.4.0 version of barrier and snap package 2.4.0 to ubuntu as client. It works and changes screens but when i toggle to ubuntu mouse cursor works but hidden and keyboard dosn't work at all. I tried to downgrade windows 10 barrier server application to 2.3.3, nothing changes. i tried to remove snap package and install 2.3.3 from ubuntu deb packages, nothing changes again. hotkeys not helps. next changes: i switch roles ubuntu to server and windows to client, it doesn't work at all, log shows that client connected but mouse not jumped to another screen on border. it start to work with hotkeys but not fully correct because mouse jumps randomly on client's[windows] screen

gitea-mirror commented

2026-05-05 07:22:18 -06:00

Author

Owner

@erikderzweite commented on GitHub (Jan 27, 2023):

Confirming the issue for 2.4.0.
[edited] It depends on the scaling of the Windows client in my case. I have two monitors connected on the windows 11 client. When the scaling settings are different, e.g. external monitor at 150% and laptop's monitor at 125%, then I see the issue.

@erikderzweite commented on GitHub (Jan 27, 2023): Confirming the issue for 2.4.0. [edited] It depends on the scaling of the Windows client in my case. I have two monitors connected on the windows 11 client. When the scaling settings are different, e.g. external monitor at 150% and laptop's monitor at 125%, then I see the issue.

Rows
Columns

[GH-ISSUE #1241] When I drag my mouse from laptop 1 to laptop 2 the mouse disappears halfway on laptop 1 and appears on laptop 2 #1002