-
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
Mouse Keyboard Intermittently freezes and hits enter about 600 times #298
Comments
I have the same issue on Ubuntu/Ubuntu setup. I think in my case the culprit was IIRC clipboard retrieval was blocking occasionally which happened because I ran libvirt VMs. |
I'm experiencing the same issue and I suspect it's the same as these two issues in synergy-core: |
Same issue. Server: Manjaro 64-bit (stable branch) |
Also seeing this quite frequently on a manjaro-server ubuntu-client setup. |
Still happening with release 2.3.1, client=Ubuntu 18.04LTS 64 bit, server=Windows 7 64 bit and SSL disabled. |
Same thing happening to me. SSL enabled. Server: Client: |
@TitanFail Interesting. With regards to the client, can you try building from the v2.3.1 tag? Thanks. We're aware of this issue, but the codebase is in serious need of 'TLC', and its proving to be tricky... |
@shymega - Built from the 2.3.1 tag, same thing. When I set the logging to Debug2, everything seems to go normally. When it hangs, I still see the information flowing in the server-side logs, and nothing seems amiss. It's like the server still sees everything that's going on, but the updates just aren't pushing out to the client for some reason (best way I know how to explain it). It knows exactly where the cursor is, etc., but it isn't reflected in the client until several seconds later. |
@TitanFail OK, thanks for letting me know. Again as I say, the codebase is really needing a major refactoring/TLC/improvements, and once we have the resources/time/manpower, then I surely hope it can happen. My apologies again for this. |
Just an additional data-point that I hope is useful: It can (and does) happen at any time, but seems to be much more frequent if I'm doing anything with Nemo, and to a lesser extent GIMP. |
Thanks. We'll bear this in mind. |
Issue is present on my setup as well:
Server: Client: Logs on both the server and the client do not indicate anything is wrong when the freeze occurs. In my case, I hadn't had any issues up until this week when Pop! OS updated from 19.04 to 19.10. The cursor and/or the keyboard will freeze every 10-15 seconds or so for a brief 2-3 second period when on the client screen. Three or four times the issue with ENTER getting stuck has occurred as well. The amount of running processes on either the server or the client doesn't seem to be a factor in when or how often it freezes. It has been consistently freezing every 10-15 seconds no matter what, while the ENTER key getting stuck has been much more sporadic and unpredictable except each time it has occurred I was in the Terminal executing commands. |
Have the same issue. Server: Client: SSL Enabled / Clipboard Enabled Keyboard/mouse freezes frequently and randomly. Logs show nothing useful. |
my keyboard is hanging in debian |
This bug should be fixed on Barrier 2.3.3. See PR #679. |
This is still an issue for me. Server running Manjaro 22.0.0 Sikaris with kernel 5.4.221, |
Operating Systems
Server: Windows 10 64-bit 1809
Client: Ubuntu 18.04
Barrier Version
barrierc 2.2.0-snapshot
Protocol version 1.6
Steps to reproduce bug
Occasionally (and seemingly randomly) I will have my mouse just kind of "freeze". If I am only moving the mouse at this point in time, it seems to only affect the mouse. But if I happen to be typing at the moment this happens, it seems to be pressing the enter key around 600 times. It seems to resolve itself after about 10-15 seconds, at which point everything starts to function normally. I've tried to start the barrier client in my lightdm configuration file with logging turned on, but the client does not seem to start with lightdm when I have the options to turn on logging.
The text was updated successfully, but these errors were encountered: