mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #326] No Waiting Channel = No cursor? #261
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#261
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 @Snerken on GitHub (May 29, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/326
Operating Systems
I'm running Ubuntu 18.10 on two laptops (call them tosh-ubuntu and hp-ubuntu) and FerenOS (call it tosh-ferenOS) on a third. I have installed Barrier version 2.2.0 on all three machines. The hp-ubuntu machine is the nominated server, while tosh-ubuntu and tosh-ferenOS are clients.
Barrier Version
2.2.0
Steps to reproduce bug
The connection between hp-ubuntu and tosh-ferenOS is working fine, with the server keyboard and mouse functioning on both machines. There is connection between the hp-ubuntu and the tosh-ubuntu, however the mouse cursor is not visible on the tosh-ubuntu. The log indicates that the mouse is entering and leaving the screen on tosh-ubuntu.
Other info
The Processes tab under the System Monitor says both barrier and barrierc are up and running. The only difference I can see between the two clients is that the tosh-ubuntu has no Waiting Channel. The Waiting Channel for the server machine (hp-ubuntu) is poll_schedule_timeout.constprop.15, whereas for the tosh-ferenOS it is poll_schedule_timeout.constprop.11.
Is this a fixable issue?
@AdrianKoshka commented on GitHub (May 29, 2019):
Are any of these machines using wayland?
@Snerken commented on GitHub (May 29, 2019):
As a matter of fact, yes--tosh-ubuntu was. Now it ain't and barrier works across all three machines! Too easy! Still no Waiting Channel on that machine but that doesn't seem to matter.