-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Input freezes or gets stuck, losing control for a few seconds #617
Comments
I'm seeing the exact same behavior. I haven't managed to isolate the issue, but there is one scenario I can repeatedly reproduce:
Using the hotkey assigned to switch desktops back and forth "releases" it. Anecdotally it feels like it occurs often when typing & using shift. I haven't noticed any pattern yet on the occurrence of the second issue mentioned, in which seemingly randomly I also loose control of both keyboard & mouse. It seems to be related to this issue on the synergy-core repository. -- Operating Systems Barrier Version Other Info |
I'm also experiencing this issue. |
It looks like this was fixed in synergy-core. Do fixes like this typically get pulled down into barrier? I've applied this patch to my install of barrier to see if it helps, but curious if these fixes get pulled into barrier at some point.. |
No, they don't AFAIK. |
The issue seems to be fixed by https://github.com/symless/synergy-core/pull/6685 I have same issue: sometimes the mouse freezes and movements are delayed by a few seconds. Operating Systems Barrier Version Other Info |
That patch applies fine to the current Barrier version. I'm not sure what the official position is about using upstream patches from Symless's Synergy core though. @walker0643 Thoughts? |
After running barriers with the upstream patch for over a day, I can confirm the issues (lag, input freezes, etc) I was seeing have been resolved. |
Thanks for confirming. I'm keen to get it merged, but I need to check a few factors first. Will keep this updated. |
I think the upstream fix is a total hack. We could as well just throw away most of the X11 event queue code :-) It will cause higher power usage on laptops even when barrier is not actively used (i.e. no event) as the event polling will be a thousand times more frequent. |
I looked into this issue and have a preliminary fix that I'm testing. The problem in my case is that's the occasions when the input is stuck are very rare, maybe once an hour or so, but so far I have not seen the issue return. |
Hm, interesting. Mind sharing the patch so far @p12tic? Thanks 👍 |
Been running 2.3.3 for about 2.5 hours now and haven't had a single hickup yet. So far it seems the changes are working! |
Not sure what could be causing this or if it's even a bug, perhaps someone has pointers as I can't find any related issues on google. A lot of times, and I'm talking 10~50 times per hour, I have either of the following issues:
Operating Systems
Server: Win 10 (1909)
Client: Ubuntu 18.04
Barrier Version
2.3.2-snapshot-210c2b70 (server) 3 oct 2019
2.3.2-snapshot-9080ce45 (client) 10 nov 2019
I'm not sure how to get the exact same versions, as the linux version is installed via the software manager, and this gives me a newer version than available here in releases.
Steps to reproduce bug
Use the software
Other info
Connected via WiFi because Dell refuses to give support for this particular USB-C dongle, LAN not working so I can't test if that fixes it
The text was updated successfully, but these errors were encountered: