[GH-ISSUE #1083] Ubuntu 20.04 host loses mouse and keyboard in xwindows when windows client is rebooted during windows update #864

Open
opened 2026-05-05 07:13:46 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @foftoogs on GitHub (Mar 2, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1083

Describe the bug
I use an Ubuntu 20.04 host and a windows 10 client machine.

I find that sometimes when I have focus on the client windows machine and I need to reboot that client machine (with a windows update or something), the mouse and keyboard is no longer working on the ubuntu host. It is like the barrier service dies on the windows machine and the focus remains on the client and does not switch back to the.

To Reproduce

Steps to reproduce the behavior:

  1. Configure barrier on the Ubuntu 20.04 host as the server
  2. Configre the barrier on the windows 10 client
  3. Once you have logged into windows make sure the focus of your mouse and keyboard is on the Windows 10 client machine
  4. Turn off the windows machine by doing a windows update or something that automatically reboots the machine. Ensure the the focus of the mouse and keyboard is still on that windows machine.
  5. Try and move your mouse and keyboard on the host machine.
  6. While you will see glimpses of the effect the cursor has in areas of the screen you expect it to be active on the host ubuntu desktop (host) you will not see the cursor itself. You will not be able to click on things or type into anything.

Expected behavior
I expect that once you turn off a client machine and the focus is gone (because the client machine is no longer connected to the host machine) that the focus should be put back onto the host machine so that the mouse and keyboard can be used on that host machine.

Desktop (please complete the following information):

  • HOST OS: Ubuntu 20.04 LTS vanilla install

  • Barrier version : v2.3.2-release-000000000

  • HOST OS: Windows 10 (build 19042.804)

  • Barrier version : v2.3.2-release-3395cca9

Additional context

I have tried this with straight restarting by clicking restart in windows but it does not have the same behaviour. You need to turn the machine off with a mechanism like windows update for the behaviour mentioned above.

Originally created by @foftoogs on GitHub (Mar 2, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1083 **Describe the bug** I use an Ubuntu 20.04 host and a windows 10 client machine. I find that sometimes when I have focus on the client windows machine and I need to reboot that client machine (with a windows update or something), the mouse and keyboard is no longer working on the ubuntu host. It is like the barrier service dies on the windows machine and the focus remains on the client and does not switch back to the. **To Reproduce** Steps to reproduce the behavior: 1. Configure barrier on the Ubuntu 20.04 host as the server 2. Configre the barrier on the windows 10 client 3. Once you have logged into windows make sure the focus of your mouse and keyboard is on the Windows 10 client machine 4. Turn off the windows machine by doing a windows update or something that automatically reboots the machine. Ensure the the focus of the mouse and keyboard is still on that windows machine. 5. Try and move your mouse and keyboard on the host machine. 6. While you will see glimpses of the effect the cursor has in areas of the screen you expect it to be active on the host ubuntu desktop (host) you will not see the cursor itself. You will not be able to click on things or type into anything. **Expected behavior** I expect that once you turn off a client machine and the focus is gone (because the client machine is no longer connected to the host machine) that the focus should be put back onto the host machine so that the mouse and keyboard can be used on that host machine. **Desktop (please complete the following information):** - HOST OS: Ubuntu 20.04 LTS vanilla install - Barrier version : v2.3.2-release-000000000 - HOST OS: Windows 10 (build 19042.804) - Barrier version : v2.3.2-release-3395cca9 **Additional context** I have tried this with straight restarting by clicking restart in windows but it does not have the same behaviour. You need to turn the machine off with a mechanism like windows update for the behaviour mentioned above.
Author
Owner

@lvzhaobing commented on GitHub (Apr 14, 2021):

I had the same problem, please help.

<!-- gh-comment-id:819220262 --> @lvzhaobing commented on GitHub (Apr 14, 2021): I had the same problem, please help.
Author
Owner

@tibmeister commented on GitHub (Apr 27, 2021):

I have the same issue with the only remedy is to SSH into the Ubuntu box and kill -9 all barrier processes.

<!-- gh-comment-id:827926726 --> @tibmeister commented on GitHub (Apr 27, 2021): I have the same issue with the only remedy is to SSH into the Ubuntu box and kill -9 all barrier processes.
Author
Owner

@kohend commented on GitHub (Dec 10, 2022):

I saw this with an Ubuntu client rebooting while the mouse was on the client's screen.

<!-- gh-comment-id:1345262509 --> @kohend commented on GitHub (Dec 10, 2022): I saw this with an Ubuntu client rebooting while the mouse was on the client's screen.
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#864
No description provided.