[GH-ISSUE #1732] Lagging/Freezing for many seconds before actually switching, when running VirtualBox on the server #1280

Open
opened 2026-05-05 07:41:32 -06:00 by gitea-mirror · 0 comments
Owner

Originally created by @Ra0EL on GitHub (Aug 2, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1732

What happened?

Hi,
I am a user of Synergy for decades and happy to jump at Barrier 😄


Issue

Everything is working fine, except when I run VirtualBox on my server machine to run a VM.
Under some circumstances, it can takes dozens of seconds before I can actually switch to the client machine.


Steps to reproduce the issue

  1. I work on my server machine within a VirtualBox VM (NB: the VM does not run Barrier at all. It is not a Barrier client, not a Barrier server)
  2. Move the mouse to edge of screen to reach the client machine. Nothing happens:
    • mouse cursor is not visible anymore on server machine
    • mouse cursor is still not visible on client machine
  3. do not move the mouse, wait for 5-30 seconds ; eventually the mouse cursor appears on client machine.
  4. From then on, everything is working fine on client machine, and I can switch instantly to server machine. But switching again to client machine brings me back to step 2 above…

Further info

  • There is no delay at all when focus is switching in/out between the VM and KDE desktop on my Barrier server.
  • Additionally, I did notice that issue is strongly happening when focus (my mouse) is within the VM environment on my server machine and I want to switch to my client machine. By strongly, I mean it will take dozens of seconds.
  • Whereas, if the focus on server machine is outside the VM, there is still a delay but shorter (5-10s).
  • And finally, it seems that if on my server machine, I am working in a different (virtual) desktop in KDE than the one hosting the running VM, the delay might be even shorter - or no delay at all, after a while without focusing on running VM.
  • Moreover, after closing VM and VirtualBox (including daemons), the issue is still there for a couple of minutes I would say and then it works smoothly as expected, no more delay to switch to Barrier client.

What I have tried

  1. Use the Host key in VirtualBox, before switching to Barrier client machine, in order for the VM to release ownership of keyboard/mouse. Still facing the issue.
  2. Disable automatic kbd/mouse grabbing by the VM (i.e. you need to click within VM window for the kbd/mouse to be usable within the VM). Still facing the issue.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

  • on server, from Solus OS repo
  • on client, from GitHub, release for Windows BarrierSetup-2.4.0-release.exe

What OSes are you seeing the problem on? (Check all that apply)

Linux, Windows

What OS versions are you using?

  • server : Solus 4.3 + KDE Plasma 5.25.3 (X11, no Wayland)
  • client: Windows 10 Enterprise 21H2 - Build 19044.1766 + VirtualBox 6.1.36
  • VM: any OS (Windows, Linux…) having VirtualBox Guest Additions tools installed.

Relevant log output

## ----- From terminal
[2022-08-02T10:40:25] DEBUG2: mapping state: 8321
[2022-08-02T10:40:25] DEBUG2: |= modifier: 8[2022-08-02T10:41:40] WARNING: can't leave screen
[2022-08-02T10:41:41] WARNING: can't leave screen
[2022-08-02T10:41:42] WARNING: can't leave screen
[2022-08-02T10:41:43] WARNING: can't leave screen
[2022-08-02T10:41:44] WARNING: can't leave screen
[2022-08-02T10:41:45] WARNING: can't leave screen
[2022-08-02T10:41:46] WARNING: can't leave screen
[2022-08-02T10:41:47] WARNING: can't leave screen
[2022-08-02T10:41:48] WARNING: can't leave screen
[2022-08-02T10:41:49] WARNING: can't leave screen
[2022-08-02T10:41:50] WARNING: can't leave screen
[2022-08-02T10:41:51] WARNING: can't leave screen
[2022-08-02T10:41:52] WARNING: can't leave screen
[2022-08-02T10:41:53] WARNING: can't leave screen
[2022-08-02T10:41:54] WARNING: can't leave screen
[2022-08-02T10:41:56] WARNING: can't leave screen
[2022-08-02T10:41:57] WARNING: can't leave screen
[2022-08-02T10:41:58] WARNING: can't leave screen
[2022-08-02T10:41:59] WARNING: can't leave screen
[2022-08-02T10:42:00] WARNING: can't leave screen

## From Barrier log file
2022-08-02T10:40:25] DEBUG1: logging to file (/tmp/barrier-2022-08-02.log) enabled
[2022-08-02T10:40:25] DEBUG: opening configuration "/tmp/barrier.conf"
[2022-08-02T10:40:25] DEBUG: configuration read successfully
[2022-08-02T10:40:25] DEBUG1: starting server
[2022-08-02T10:40:25] DEBUG: XOpenDisplay(":0")
[2022-08-02T10:40:25] DEBUG1: thread 0x00000002 entry
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e282c0
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00f99cec
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e0002b
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e00031
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e227d1
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e227d8
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03a00004
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03c00001
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0320000c
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03e00000
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04000001
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04000003
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04c00004
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03e00004
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04e00004
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04e00006
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e2a6dd
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03200057
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05200001
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04000008
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05600004
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05600008
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e81b27
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05800001
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05606aa9
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05606b10
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05606b75
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0140001f
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05000001
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0140000e
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x01400013
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0140002b
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03800004
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03800005
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03800009
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0380002a
[2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04a00004
[2022-08-02T10:40:25] DEBUG: screen shape: 0,0 3120x1600 (xinerama)
[2022-08-02T10:40:25] DEBUG: window is 0x04a00004
[2022-08-02T10:40:25] DEBUG: adopting new buffer
[2022-08-02T10:40:25] DEBUG: opened display
[2022-08-02T10:40:25] DEBUG1: registered event type error as 4
[2022-08-02T10:40:25] DEBUG1: registered event type suspend as 5
[2022-08-02T10:40:25] DEBUG1: registered event type resume as 6
[2022-08-02T10:40:25] DEBUG1: creating primary screen
[2022-08-02T10:40:25] DEBUG1: registered event type connecting as 7
[2022-08-02T10:40:25] DEBUG1: binding listen socket
[2022-08-02T10:40:25] DEBUG1: listening for clients

Any other information

No response

Originally created by @Ra0EL on GitHub (Aug 2, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1732 ### What happened? Hi, I am a user of Synergy for decades and happy to jump at Barrier :smile: --- ### Issue Everything is working fine, except when I run VirtualBox on my server machine to run a VM. Under some circumstances, it can takes dozens of seconds before I can actually switch to the client machine. --- ### Steps to reproduce the issue 1. I work on my server machine within a VirtualBox VM (_NB: the VM does not run Barrier at all. It is not a Barrier client, not a Barrier server_) 2. Move the mouse to edge of screen to reach the client machine. Nothing happens: - mouse cursor is not visible anymore on server machine - mouse cursor is still not visible on client machine 3. **do not** move the mouse, wait for 5-30 seconds ; eventually the mouse cursor appears on client machine. 4. From then on, everything is working fine on client machine, and I can switch instantly to server machine. But switching again to client machine brings me back to step 2 above… --- ### Further info * There is no delay at all when focus is switching in/out between the VM and KDE desktop on my Barrier server. * Additionally, I did notice that issue is strongly happening when focus (my mouse) is **within the VM environment** on my server machine and I want to switch to my client machine. By strongly, I mean it will take dozens of seconds. * Whereas, if the focus on server machine is **outside the VM**, there is still a delay but shorter (5-10s). * And finally, it seems that if on my server machine, I am working in a **different (virtual) desktop** in KDE than the one hosting the running VM, the delay might be even shorter - or no delay at all, after a while without focusing on running VM. * Moreover, after **closing VM and VirtualBox (including daemons)**, the issue is still there for a couple of minutes I would say and then it works smoothly as expected, no more delay to switch to Barrier client. --- ### What I have tried 1. Use the `Host key` in VirtualBox, before switching to Barrier client machine, in order for the VM to release ownership of keyboard/mouse. Still facing the issue. 2. Disable automatic kbd/mouse grabbing by the VM (i.e. you need to click within VM window for the kbd/mouse to be usable within the VM). Still facing the issue. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? - on **server**, from Solus OS repo - on **client**, from GitHub, release for Windows `BarrierSetup-2.4.0-release.exe` ### What OSes are you seeing the problem on? (Check all that apply) Linux, Windows ### What OS versions are you using? - **server** : Solus 4.3 + KDE Plasma 5.25.3 (X11, no Wayland) - **client**: Windows 10 Enterprise 21H2 - Build 19044.1766 + VirtualBox 6.1.36 - **VM**: any OS (Windows, Linux…) having _VirtualBox Guest Additions tools_ installed. ### Relevant log output ```shell ## ----- From terminal [2022-08-02T10:40:25] DEBUG2: mapping state: 8321 [2022-08-02T10:40:25] DEBUG2: |= modifier: 8[2022-08-02T10:41:40] WARNING: can't leave screen [2022-08-02T10:41:41] WARNING: can't leave screen [2022-08-02T10:41:42] WARNING: can't leave screen [2022-08-02T10:41:43] WARNING: can't leave screen [2022-08-02T10:41:44] WARNING: can't leave screen [2022-08-02T10:41:45] WARNING: can't leave screen [2022-08-02T10:41:46] WARNING: can't leave screen [2022-08-02T10:41:47] WARNING: can't leave screen [2022-08-02T10:41:48] WARNING: can't leave screen [2022-08-02T10:41:49] WARNING: can't leave screen [2022-08-02T10:41:50] WARNING: can't leave screen [2022-08-02T10:41:51] WARNING: can't leave screen [2022-08-02T10:41:52] WARNING: can't leave screen [2022-08-02T10:41:53] WARNING: can't leave screen [2022-08-02T10:41:54] WARNING: can't leave screen [2022-08-02T10:41:56] WARNING: can't leave screen [2022-08-02T10:41:57] WARNING: can't leave screen [2022-08-02T10:41:58] WARNING: can't leave screen [2022-08-02T10:41:59] WARNING: can't leave screen [2022-08-02T10:42:00] WARNING: can't leave screen ## From Barrier log file 2022-08-02T10:40:25] DEBUG1: logging to file (/tmp/barrier-2022-08-02.log) enabled [2022-08-02T10:40:25] DEBUG: opening configuration "/tmp/barrier.conf" [2022-08-02T10:40:25] DEBUG: configuration read successfully [2022-08-02T10:40:25] DEBUG1: starting server [2022-08-02T10:40:25] DEBUG: XOpenDisplay(":0") [2022-08-02T10:40:25] DEBUG1: thread 0x00000002 entry [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e282c0 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00f99cec [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e0002b [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e00031 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e227d1 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e227d8 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03a00004 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03c00001 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0320000c [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03e00000 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04000001 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04000003 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04c00004 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03e00004 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04e00004 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04e00006 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e2a6dd [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03200057 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05200001 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04000008 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05600004 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05600008 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x00e81b27 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05800001 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05606aa9 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05606b10 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05606b75 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0140001f [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x05000001 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0140000e [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x01400013 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0140002b [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03800004 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03800005 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x03800009 [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x0380002a [2022-08-02T10:40:25] DEBUG2: can't read property 547 on window 0x04a00004 [2022-08-02T10:40:25] DEBUG: screen shape: 0,0 3120x1600 (xinerama) [2022-08-02T10:40:25] DEBUG: window is 0x04a00004 [2022-08-02T10:40:25] DEBUG: adopting new buffer [2022-08-02T10:40:25] DEBUG: opened display [2022-08-02T10:40:25] DEBUG1: registered event type error as 4 [2022-08-02T10:40:25] DEBUG1: registered event type suspend as 5 [2022-08-02T10:40:25] DEBUG1: registered event type resume as 6 [2022-08-02T10:40:25] DEBUG1: creating primary screen [2022-08-02T10:40:25] DEBUG1: registered event type connecting as 7 [2022-08-02T10:40:25] DEBUG1: binding listen socket [2022-08-02T10:40:25] DEBUG1: listening for clients ``` ### Any other information _No response_
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#1280
No description provided.