[GH-ISSUE #326] No Waiting Channel = No cursor? #261

New issue

Closed

opened 2026-05-05 05:52:19 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 05:52:19 -06:00

Owner

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?

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?

gitea-mirror closed this issue

2026-05-05 05:52:20 -06:00

gitea-mirror commented

2026-05-05 05:52:23 -06:00

Author

Owner

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

Are any of these machines using wayland?

@AdrianKoshka commented on GitHub (May 29, 2019): Are any of these machines using wayland?

gitea-mirror commented

2026-05-05 05:52:25 -06:00

Author

Owner

@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.

@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.

gitea-mirror referenced this issue

2026-10-02 22:14:33 -06:00

[GH-ISSUE #261] client uses wrong server ip address with auto config #210

gitea-mirror changed title from ~~[GH-ISSUE #326] No Waiting Channel = No cursor?~~ to [GH-ISSUE #326] No Waiting Channel = No cursor?

2026-10-02 22:14:52 -06:00