You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not A Bug, but a documentation issue. It appears that if one system is running X and the other Wayland, the mouse does not appear as it crosses over. They both have to be running the same display server.
Other info
I have barrier running on two laptops. Both of them are Fedora 32 and initially I had challenges making it work. I would start barrier on both systems, one will be the server and the other the client. Although I would see the mouse move out of the server and should have appeared in the client, it did not. It was after some poking around that I realized that one system was running X and the other Wayland. I switched both to X and it worked like a charm.
On my server laptop, i have an external monitor attached but on the client, there isn't. In order for the mouse to move from the server to the client, the mouse must first be on the external monitor and then to the client. The mouse does not go directly from the server's laptop screen to the client's laptop screen. I don't have a 2nd external monitor to test, but that would be something I would do soon.
The text was updated successfully, but these errors were encountered:
Operating Systems
Server: Fedora 32 64-bit
Client: Fedora 32 64-bit
Barrier Version
2.3.2-2.fc32
Steps to reproduce bug
Not A Bug, but a documentation issue. It appears that if one system is running X and the other Wayland, the mouse does not appear as it crosses over. They both have to be running the same display server.
Other info
I have barrier running on two laptops. Both of them are Fedora 32 and initially I had challenges making it work. I would start barrier on both systems, one will be the server and the other the client. Although I would see the mouse move out of the server and should have appeared in the client, it did not. It was after some poking around that I realized that one system was running X and the other Wayland. I switched both to X and it worked like a charm.
On my server laptop, i have an external monitor attached but on the client, there isn't. In order for the mouse to move from the server to the client, the mouse must first be on the external monitor and then to the client. The mouse does not go directly from the server's laptop screen to the client's laptop screen. I don't have a 2nd external monitor to test, but that would be something I would do soon.
The text was updated successfully, but these errors were encountered: