Barrier: client connects, but no sharing

[timeweaver]

Operating Systems

Server: RHEL 8

Client: Windows 10

Barrier Version

2.3.2

Steps to reproduce bug

My client connects, log on the client shows connected to server, log on server shows client connecting. But mouse won't travel between screens.

Other info

This is a first time setup - I disabled selinux and shut down firewalld on my redhat server in order to allow the client to connect. Not seeing errors in either log.

[timeweaver]

Ok - I guess you can close this - It just magically started working - I have no idea why. I disabled ssl on both and nothing changed, so I re-enabled it. boom. working.

[timeweaver]

And now it's not - not idea - help!!

[the-wes]

Can you provide some log output? Turn it up to debug1 and see if you get any messages when trying to switch screens? Attach a screenshot of your server config?

[timeweaver]

Ok, here's a log file with debug turned on. The txt file is the saved config. I don't see anything showing up when I move my mouse against the edge of the screen like it is even trying to switch. I've had two occasions where it started working for about 10 minutes or so, then just stopped. Sadly, I couldn't get it to work during this log capture.

barrier.log

barrier.txt

[nsclong]

I have the same issue. I am running Debian 10 (server) and Windows 10 (client), both on Barrier version 2.2.0.

The machines are connecting to each other fine and talking to each other. Debug1 level log attached. However mouse just will not share. It stops at the edges of the server screen.

When I move my mouse to the edge of the screen to attempt to move to the client machine, nothing changes in the log.

barrier-server.log

If it's relevant, server screen size is 4K, whereas client is standard HD.

[timeweaver]

Turns out my company won't let me use this software anyway. Thanks for your efforts, I'm gonna go cry in my milk now.

[ik3umt]

Same issue here, server win10 + barrier 2.3.2 , client latest debian10 + barrier 2.2.0
Client connects to server, both ok on logs, logs tell entering and leaving screens at relative position, keyboard OK but no control over mouse

[nsclong]

OK. I had this fixed briefly. I found that I had an old copy of 'Mouse Without Borders' on my Windows 10 machine. After uninstalling and rebooting, Barrier worked once...Debian server connecting to Windows client. But after rebooting both machines again, I can't get the darn thing to work again :(

[geertdobbels]

Seems to be the same as #589 where I posted, but in the meantime I read this thread and also captured the log file with debug1.

Server : Linux Fedora 31 (installed via flatpak)
Client: Windows 10
Barrier Version 2.3.2 on both computers.

I had barrier working on the same configuration (though I do not remember the barrier version number) for several months without problems but then due to a technical problem, I had to reinstall Fedora31, and since then I have the following issue:
Barrier server clearly sees the client, as can be seen in the logfile. After changing the log level to Debug1, I only once could see a couple of messages related to leaving the screen on the bottom (which I even do not remember having done), but after that no more messages to that effect appear, no matter how and on which border I try to leave the server screen.
Server has dual screen, but I tried with single screen: no change.
I also tried with and without SSL, no difference.
barrier.log

[geertdobbels]

After starting barrier from the command shell, I saw a message related to a missing wayland-egl plugin, which made me think that wayland might be the problem (wayland is on by default in gnome 3.4 or at least in fedora31). This made me think that on my previous fedora31 install, I used to login under Xorg gnome, and not under wayland .....
So I logged out and logged back in but under xOrg gnome instead of the default wayland, and now barrier seems to be working. The question now is how to make barrier working under wayland....

[scottajohnson]

I had the same problem with a Win7 Server and raspian clients. Scroll lock was turned on and that locked the mouse to the windows screens.

[deisi]

I can confirm:
Server: 20.04 Ubuntu Xorg
Client: Arch linux Gnome 3.36.1 Wayland

Connection is handled correctly, and scrolling on client in open window on client works. However the mouse pointer on the client is not moved.

[2020-05-07T10:58:35] INFO: switch from "serv" to "mtop" at 1919,787
[2020-05-07T10:58:35] INFO: leaving screen
[2020-05-07T10:58:35] INFO: screen "serv" updated clipboard 1
[2020-05-07T10:58:40] INFO: switch from "mtop" to "serv" at 69,1328
[2020-05-07T10:58:40] INFO: entering screen

[andybiss]

I can confirm as well:
Server: 20.04 Ubuntu Desktop (Xorg)
Client: Fedora Workstation 32 (Xorg, installed via flatpak)

connects and enters screen but no mouse or keyboard

[marzukia]

In the same boat, both machines Fedora32 running x11. Connects and logs reflect correct screen detection but both keyboard and mouse don't work

Edit: seems that during the process of updating my laptop to fedora 32 it reverted back to wayland. Works primo now thanks @simons-public

[simons-public]

For any of the people using Wayland in this thread (i.e. RHEL 8 uses Wayland by default now) Wayland isn't supported by Barrier as of right now.

[CurtisDyer]

So when I had this issue, it was actually user error. I had pressed scroll lock at some point, which locked the cursor to my server's screen. Just a heads-up for anyone else who's spacing out over the obvious (or maybe it's just me).

[p12tic]

Closing as a duplicate of #247. The bug for actual Wayland support is in #109.

[frohro]

This has been plaguing me for a good while. I have a touch screen, and found that touching the touch screen allowed me to get into the other screen. Here is the debug messages I was getting:
[2020-09-29T15:43:36] DEBUG1: try to leave "frohro-260" on right
[2020-09-29T15:43:36] DEBUG: locked by mouse buttonID: 0