[GH-ISSUE #689] Barrier doesn't work if the workspace which Barrier is on is not in use #549

Open
opened 2026-05-05 06:39:38 -06:00 by gitea-mirror · 4 comments
Owner

Originally created by @n0toose on GitHub (May 24, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/689

Operating Systems

Server: Debian Sid

Client: Gentoo Linux (amd64 17.1)

Barrier Version

2.3.2

Steps to reproduce bug

  1. Set up a working connection between client and server
  2. 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.

Originally created by @n0toose on GitHub (May 24, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/689 ### Operating Systems ### Server: Debian Sid Client: Gentoo Linux (amd64 17.1) ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### 1. Set up a working connection between client and server 2. [Change workspace](https://help.gnome.org/users/gnome-help/stable/shell-workspaces-switch.html.en) ### 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.
gitea-mirror added the
bug
linux
labels 2026-05-05 06:39:38 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Sep 22, 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.

<!-- gh-comment-id:696466398 --> @github-actions[bot] commented on GitHub (Sep 22, 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.
Author
Owner

@p12tic commented on GitHub (Jan 10, 2021):

Let's not close valid bug reports.

<!-- gh-comment-id:757535605 --> @p12tic commented on GitHub (Jan 10, 2021): Let's not close valid bug reports.
Author
Owner

@Rockburner commented on GitHub (Aug 10, 2022):

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.

<!-- gh-comment-id:1210631631 --> @Rockburner commented on GitHub (Aug 10, 2022): 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.
Author
Owner

@symposion commented on GitHub (Sep 7, 2022):

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

<!-- gh-comment-id:1239627906 --> @symposion commented on GitHub (Sep 7, 2022): Yes, I also have this issue. Arch Gnome Wayland on both ends. Waynergy as a client.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#549
No description provided.