mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #276] Virtualbox Seamless mode causes edge hopping issue #223
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#223
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 @bdowling on GitHub (Apr 2, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/276
Operating Systems
Server: Windows 10
Client: MacOS 10.13.6
VirtualBox: 6.0
Barrier Version
2.1.0
Steps to reproduce bug
I'm running VirtualBox on the Windows server in seamless mode with a Linux guest. It appears there is an interaction with VirtualBox in this mode and Barrier where edge detection doesn't work (mouse does not move to client).
I found that in Scaled mode this issue is not present, digging further I did also find that turning on the setting "Don't take foreground window on Windows servers" and this seems to fix this issue. Not precisely clear what that setting means, but it seems to work.
The only issue that remains is that if a Seamless Virtualbox window had focus before going to the barrier client, the keyboard focus remains on the VM window while the mouse has moved to the guest. Clicking in the client doesn't change focus, first have to click to a native windows app before going to remote.
Other info
This is not a showstopper. It does work, clicking away from vm on server is a workaround. I'm just wondering if anyone else has experienced this, perhaps that setting helps others in this situation and if you can think of any fixes for that last issue.
Looking back in history I see others have reported similar issues in the older upstream versions.
Oh, and thanks for letting me remap Meta/Ctrl for the MacOS since most of the common keys are opposite windows interaction. Three different OS nuances is enough to contend with. :)