mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1419] can't switch to server screen on manjaro X11 i3 #1094
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1094
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ExpandingMan on GitHub (Nov 11, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1419
What happened?
I can connect to the server just fine, but I can't use the mouse or keyboard on the server at all.
Version
v2.3.3
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
pacman(Manjaro)What OSes are you seeing the problem on? (Check all that apply)
Linux
What OS versions are you using?
Manjaro Linux 21.1.6 (both machines)
Relevant log output
Any other information
Tried multiple screen arrangement configurations, nothing works.
Currently using config:
@ExpandingMan commented on GitHub (Nov 12, 2021):
I'm not sure if this is a clue but I have noticed that I only get log output when I run in the foreground with
-f. Doesn't change the situation, still can't get it to work, but I don't understand why it would do this.@ExpandingMan commented on GitHub (Nov 12, 2021):
Oh man, 🤦
Despite having read repeated admonitions about what "client" and "server" means in the barrier context, I just could not get it through my thick skull. The cognitive dissonance with the use of those terms in my most common use cases of
sshwas obviously way too much for me to handle.Sorry.