github-starred/barrier

Fork 0

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

[GH-ISSUE #1149] Client screen never shows on server #923

New issue

Open

opened 2026-05-05 07:17:10 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

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

Owner

Originally created by @jbedgood on GitHub (Apr 28, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1149

I've done this now multiple times with different computers (4 in total). All running windows 10. I installed barrier 2.3.3 on them and everything seems fine. The client shows it connected to the server and the server shows it sees the client. But when I try to move my mouse off screen it disappears and the client shows entering screen the server shows leaving screen but the client screen never shows on my server screen. i always just see my server screen.

Not sure what else to try at this point.

But here are some debug files.
client-barrier.log
server-barrier.log

Originally created by @jbedgood on GitHub (Apr 28, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1149 I've done this now multiple times with different computers (4 in total). All running windows 10. I installed barrier 2.3.3 on them and everything seems fine. The client shows it connected to the server and the server shows it sees the client. But when I try to move my mouse off screen it disappears and the client shows entering screen the server shows leaving screen but the client screen never shows on my server screen. i always just see my server screen. Not sure what else to try at this point. But here are some debug files. [client-barrier.log](https://github.com/debauchee/barrier/files/6388453/client-barrier.log) [server-barrier.log](https://github.com/debauchee/barrier/files/6388454/server-barrier.log)

gitea-mirror commented

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

Author

Owner

@Benchwork commented on GitHub (Apr 30, 2021):

not sure that I am understanding..... are you expecting the clients screen to show up on the server? because thats not the intended outcome. the intended outcome is when your move the mouse passed the edge of the server screen, it moves onto the screen of the client.

can you clarify more please?

@Benchwork commented on GitHub (Apr 30, 2021): not sure that I am understanding..... are you expecting the clients screen to show up on the server? because thats not the intended outcome. the intended outcome is when your move the mouse passed the edge of the server screen, it moves onto the screen of the client. can you clarify more please?

gitea-mirror commented

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

Author

Owner

@jbedgood commented on GitHub (Apr 30, 2021):

Then I guess I totally misunderstand the program as a whole. You're saying
each client has to have its own screen? That being the case it didn't work
that way either but that won't work for me as most my clients tend to run
headless.

On Fri, Apr 30, 2021, 11:31 AM Peter Christenson @.***>
wrote:

not sure that I am understanding..... are you expecting the clients screen
to show up on the server? because thats not the intended outcome. the
intended outcome is when your move the mouse passed the edge of the server
screen, it moves onto the screen of the client.

can you clarify more please?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/1149#issuecomment-830177260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AI3EU5FBDC5PO32UUZ7V3RTTLLEOZANCNFSM43WB2JTA
.

@jbedgood commented on GitHub (Apr 30, 2021): Then I guess I totally misunderstand the program as a whole. You're saying each client has to have its own screen? That being the case it didn't work that way either but that won't work for me as most my clients tend to run headless. On Fri, Apr 30, 2021, 11:31 AM Peter Christenson ***@***.***> wrote: > not sure that I am understanding..... are you expecting the clients screen > to show up on the server? because thats not the intended outcome. the > intended outcome is when your move the mouse passed the edge of the server > screen, it moves onto the screen of the client. > > can you clarify more please? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/1149#issuecomment-830177260>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AI3EU5FBDC5PO32UUZ7V3RTTLLEOZANCNFSM43WB2JTA> > . >

gitea-mirror commented

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

Author

Owner

@Benchwork commented on GitHub (Apr 30, 2021):

yes every computer has its own screen. barrier is used to allow the keyboard and mouse to move between them instead of using multiple devices or a kvm switch. if your running windows headless I would assume you would use something like RDP to manage them.

@Benchwork commented on GitHub (Apr 30, 2021): yes every computer has its own screen. barrier is used to allow the keyboard and mouse to move between them instead of using multiple devices or a kvm switch. if your running windows headless I would assume you would use something like RDP to manage them.

No labels

Rows
Columns