github-starred/barrier

Fork 0

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

[GH-ISSUE #696] Windows10x64 failure #553

New issue

Closed

opened 2026-05-05 06:40:10 -06:00 by gitea-mirror · 8 comments

gitea-mirror commented

2026-05-05 06:40:10 -06:00

Owner

Originally created by @DaveNF2G on GitHub (May 26, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/696

Operating Systems

Server: Windows 10x64 Pro

Client: Windows 10x64 Pro

Barrier Version

1.9.π?

Just downloaded today.

Steps to reproduce bug

Install on server
Install on client
Move mouse
Mouse does not leave server screen. No visible effect on client machine.

Other info

When did the problem start to occur? When I ran it for the first time.
Is there a way to work around it? None that I aware of
Does this bug prevent you from using Barrier entirely? Yes

Put anything else you can think of here.

Installed per video posted to Facebook. No other instructions found.

Originally created by @DaveNF2G on GitHub (May 26, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/696 ### Operating Systems ### Server: Windows 10x64 Pro Client: Windows 10x64 Pro ### Barrier Version ### 1.9.π? Just downloaded today. ### Steps to reproduce bug ### 1. Install on server 2. Install on client 3. Move mouse 4. Mouse does not leave server screen. No visible effect on client machine. ### Other info ### * When did the problem start to occur? When I ran it for the first time. * Is there a way to work around it? None that I aware of * Does this bug prevent you from using Barrier entirely? Yes Put anything else you can think of here. Installed per video posted to Facebook. No other instructions found.

gitea-mirror

2026-05-05 06:40:10 -06:00

closed this issue
added the
bug

windows

question
labels

gitea-mirror commented

2026-05-05 06:40:18 -06:00

Author

Owner

@shymega commented on GitHub (May 26, 2020):

You should really be using an up-to-date version of Barrier first of all. By 'per video posted to Facebook', I'm not sure what you mean by that?

EDIT: Sorry, I just realised that version was the template! Whoops.

@shymega commented on GitHub (May 26, 2020): You should really be using an up-to-date version of Barrier first of all. By 'per video posted to Facebook', I'm not sure what you mean by that? EDIT: Sorry, I just realised that version was the template! Whoops.

gitea-mirror commented

2026-05-05 06:40:21 -06:00

Author

Owner

@DaveNF2G commented on GitHub (May 26, 2020):

Sorry about not reporting the version. I am using v2.3.2.

Here is a link to the video:
https://www.facebook.com/raspberrypi/videos/294061781629794/

@DaveNF2G commented on GitHub (May 26, 2020): Sorry about not reporting the version. I am using v2.3.2. Here is a link to the video: https://www.facebook.com/raspberrypi/videos/294061781629794/

gitea-mirror commented

2026-05-05 06:40:24 -06:00

Author

Owner

@shymega commented on GitHub (May 26, 2020):

Alright. You need to configure Barrier and 'link' the screens together. Have you done that?

@shymega commented on GitHub (May 26, 2020): Alright. You need to configure Barrier and 'link' the screens together. Have you done that?

gitea-mirror commented

2026-05-05 06:40:25 -06:00

Author

Owner

@DaveNF2G commented on GitHub (May 26, 2020):

As far as I know, I have completed the configuration.

I set the first computer as a Server and added the second as Client to the screen with the boxes and entered its name. Then I configured the second computer as Client and pointed it to Server's name. I got the trust query for the fingerprint and accepted it. Both copies of Barrier said to close the window and leave it running in the background. The "hidden icons" list on both machines shows the Barrier icon as a running app.

When the mouse cursor on the Server computer failed to leave the screen area or appear on the Client's monitor, I unplugged the mouse and keyboard from Client and tried again. Still no apparent cross connection.

@DaveNF2G commented on GitHub (May 26, 2020): As far as I know, I have completed the configuration. I set the first computer as a Server and added the second as Client to the screen with the boxes and entered its name. Then I configured the second computer as Client and pointed it to Server's name. I got the trust query for the fingerprint and accepted it. Both copies of Barrier said to close the window and leave it running in the background. The "hidden icons" list on both machines shows the Barrier icon as a running app. When the mouse cursor on the Server computer failed to leave the screen area or appear on the Client's monitor, I unplugged the mouse and keyboard from Client and tried again. Still no apparent cross connection.

gitea-mirror commented

2026-05-05 06:40:28 -06:00

Author

Owner

@zedascouves commented on GitHub (May 27, 2020):

I've noticed that behaviour when I have a 2nd monitor attached to the server (which is a laptop). If I remove it, it works. It still works if I connect the 2nd monitor do the client (which is also a laptop).

@zedascouves commented on GitHub (May 27, 2020): I've noticed that behaviour when I have a 2nd monitor attached to the server (which is a laptop). If I remove it, it works. It still works if I connect the 2nd monitor do the client (which is also a laptop).

gitea-mirror commented

2026-05-05 06:40:32 -06:00

Author

Owner

@DaveNF2G commented on GitHub (May 27, 2020):

Both of the machines with Barrier installed are desktops and each has a single monitor.

@DaveNF2G commented on GitHub (May 27, 2020): Both of the machines with Barrier installed are desktops and each has a single monitor.

gitea-mirror commented

2026-05-05 06:40:35 -06:00

Author

Owner

@the-wes commented on GitHub (May 31, 2020):

@DaveNF2G would you be able to post a screenshot of the Configure Server screen from your Barrier server system?

@the-wes commented on GitHub (May 31, 2020): @DaveNF2G would you be able to post a screenshot of the Configure Server screen from your Barrier server system?

gitea-mirror commented

2026-05-05 06:40:38 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 21, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 21, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror referenced this issue

2026-05-05 07:58:44 -06:00

[PR #553] [MERGED] Disable wayland support in the snap #1654