Barrier doesn't work if the workspace which Barrier is on is not in use

debauchee / barrier

Open-source KVM software

Other

27.46k stars 1.51k forks source link

Barrier doesn't work if the workspace which Barrier is on is not in use #689

Open n0toose opened 4 years ago

n0toose commented 4 years ago

Operating Systems

Server: Debian Sid

Client: Gentoo Linux (amd64 17.1)

Barrier Version

2.3.2

Steps to reproduce bug

Set up a working connection between client and server
Change workspace

Other info

When did the problem start to occur? See "Steps to reproduce bug"
Is there a way to work around it? No
Does this bug prevent you from using Barrier entirely? No

Just in case I didn't make it clear enough, the server's desktop environment in question is Gnome.

github-actions[bot] commented 4 years ago

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.

p12tic commented 3 years ago

Let's not close valid bug reports.

Rockburner commented 2 years ago

I'm getting the same issue. Server: Ubuntu 22 (using Wayland) Client Ubuntu 20 (using Unity)

Symptom: Mouse can only travel to Client from 1 workspace on server. Mouse can travel BACK to server regardless of which workspace server is currently showing Interesting quirk: if Mouse is on Client desktop, switching workspaces on Server seems to disable 'SHIFT' key for client, until mouse has gone back to Server and then back to client. Also - using keyboard to switch workspaces only works on server, even when mouse is on client desktop.

symposion commented 2 years ago

Yes, I also have this issue. Arch Gnome Wayland on both ends. Waynergy as a client.