[GH-ISSUE #313] Alt+Tab and other Keycombos, Windows key and other special keys #251

Closed
opened 2026-05-05 05:51:13 -06:00 by gitea-mirror · 6 comments
Owner

Originally created by @lunainvictum on GitHub (May 18, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/313

Server:
OS: Arch Linux (Desktop Gnome 3)
Version Barrier: 2.0

Client:
OS: Windows 10 1809
Version Barrier: 2.0

I have following Problem: i have VM running with gpu passthrough wich connects to same monitor on another port. Now i want to use the same keyboard and mouse.

So i set up Barrier. But without the switching with move the cursor to the border. I let in the Server Settings a blank space between the both machines and maked two hotkeys in the settings. One to switch to Vm, and one to switch back (because i need to lock keyboard and mouse in one place). It works with few little problems:

  1. If i switch to windows, and press windows key or alt+tab, the action dont happens on the client, it happens on the server.

  2. The Hotkeys only works, if the window from barrier is in front on the server.

Originally created by @lunainvictum on GitHub (May 18, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/313 Server: OS: Arch Linux (Desktop Gnome 3) Version Barrier: 2.0 Client: OS: Windows 10 1809 Version Barrier: 2.0 I have following Problem: i have VM running with gpu passthrough wich connects to same monitor on another port. Now i want to use the same keyboard and mouse. So i set up Barrier. But without the switching with move the cursor to the border. I let in the Server Settings a blank space between the both machines and maked two hotkeys in the settings. One to switch to Vm, and one to switch back (because i need to lock keyboard and mouse in one place). It works with few little problems: 1) If i switch to windows, and press windows key or alt+tab, the action dont happens on the client, it happens on the server. 2) The Hotkeys only works, if the window from barrier is in front on the server.
Author
Owner

@noisyshape commented on GitHub (May 18, 2019):

It sounds like you're running Wayland. Barrier has issues with servers running under Wayland and clients don't work at all under Wayland.

<!-- gh-comment-id:493708505 --> @noisyshape commented on GitHub (May 18, 2019): It sounds like you're running Wayland. Barrier has issues with servers running under Wayland and clients don't work at all under Wayland.
Author
Owner

@lunainvictum commented on GitHub (May 18, 2019):

Dont know. I use archlinux with gnome 3 :-)

<!-- gh-comment-id:493709215 --> @lunainvictum commented on GitHub (May 18, 2019): Dont know. I use archlinux with gnome 3 :-)
Author
Owner

@noisyshape commented on GitHub (May 18, 2019):

I don't think Arch is a good distribution for people who don't know what software they're using. You can copy this into a terminal:

loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}') -p Type

and it will tell you whether you're inside an x11 session or Wayland session.

<!-- gh-comment-id:493710005 --> @noisyshape commented on GitHub (May 18, 2019): I don't think Arch is a good distribution for people who don't know what software they're using. You can copy this into a terminal: `loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}') -p Type` and it will tell you whether you're inside an x11 session or Wayland session.
Author
Owner

@lunainvictum commented on GitHub (May 18, 2019):

Wayland.

<!-- gh-comment-id:493710065 --> @lunainvictum commented on GitHub (May 18, 2019): Wayland.
Author
Owner

@noisyshape commented on GitHub (May 18, 2019):

There are no workarounds for Wayland as far as I know. You'll have to switch to X11 if you want to use Barrier.

<!-- gh-comment-id:493710700 --> @noisyshape commented on GitHub (May 18, 2019): There are no workarounds for Wayland as far as I know. You'll have to switch to X11 if you want to use Barrier.
Author
Owner

@AdrianKoshka commented on GitHub (May 18, 2019):

You are correct, we aren't wayland ready.

<!-- gh-comment-id:493710853 --> @AdrianKoshka commented on GitHub (May 18, 2019): You are correct, we aren't wayland ready.
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#251
No description provided.