Barrier: Keyboard not being shared since macOS update (10.14.6 (18G87))

[domparry]

Operating Systems

Server: macOS Mojave 10.14.6 (18G87)

Client: macOS High Sierra 10.13.6

Barrier Version

2.1.0 and 2.3.0

Steps to reproduce bug

1. Open Barrier on both machines
2. Move the mouse into the screen of the client.
3. Mouse control is transferred and works normally.
4. Keyboard still active on server, but not on client

Other info

• When did the problem start to occur? Since running the latest macOS update (on 7-08-2019)
• Is there a way to work around it? No
• Does this bug prevent you from using Barrier entirely? No

[domparry]

Just as an update, I've tested this on 2.3.1 and it still persists.

[domparry]

Something I see in the logs when I switch to the other machine:

2019-08-30 17:28:53.195 barriers[1353:12766] pid(1353)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!!

[AdrianKoshka]

That's a long-time warning, iirc it's doesn't interfere with anything.

[metadave]

I'm experiencing the same issue. I added a bunch of traces throughout the source to log events (EventQueue, OSXKeyState, OSXScreen etc), and it appears that only mouse events are being fired. If anyone has pointers on where I should be looking in the source, I'd be happy to debug some more.

[domparry]

Any work around on your side to get it going again @metadave ?

[jbirthisel]

This is happening to me off and on all the time.

Example: Today quit working in morning. Reset both server and client side. Rebooted client even. No fix. Then 5 minutes ago (14:00) the keyboard just started working again.

[metadave]

Any work around on your side to get it going again @metadave ?

not yet, still debugging and learning about iokit. All signs currently point to keyboard events not being fired on the server.

edit:

All signs currently point to keyboard events not being fired on the server.

control/option/command appear to fire events, letter/number keys do not

[noisyshape]

I couldn't reproduce this with VMware guests and I'm not seeing any difference in behavior with 10.14.6. This may be identical to https://github.com/symless/synergy-core/issues/6513 where supposedly it's something to do with input source settings.

When all else fails, post full debug logs.

[domparry]

I've double checked the keyboard input source settings as described in that issue, and that's not the case here. @noisyshape When you say full debug logs, are you referring to something more than the logs shown from the show log function? If there's a way to turn on more detailed logs, let me know and I'll happily do so.

[noisyshape]

@domparry In the settings dialog (F4) there is a logging level option. Set it to Debug2 and restart the client/server. If you can log a short session with a couple of failed keystrokes that could be helpful. You can use pastebin for this.

[domparry]

* Edit - I didn't restart barrier after setting the debug level, so re-pasting the logs *

Here you go @noisyshape . I've included both the client and server logs below.

Client Log: https://pastebin.com/EcCyjHMR
Server Log:https://pastebin.com/1VwreTTK

[domparry]

Please let me know if there is anything else I can provide to help find the cause of this. It essentially makes barrier unusable.

[metadave]

As barrier and synergy aren't working for me because of this bug, I tried using https://www.sharemouse.com/. It has the same problem with keyboard sharing, _however, it also shows an orange icon when running that says "Keyboard not working?". Clicking on the icon takes you to the ShareMouse support page that describes apps that leave MacOS Secure Input enabled.

tl;dr I started killing apps until my keyboard worked again. Some possibly useful info here and here.

also, props to the sharemouse folks for showing that helpful warning.

~edit - I should mentioned that I think Evernote is the culprit, but I'll have to observe over a few days to verify.~

edit: one more doc that's helpful

cc @domparry

[domparry]

@metadave, you're awesome. Spot on. My issue was secureinput locked by a startup app (workflowy). Huge Thank you.

[domparry]

I'm closing this because it's solved (And not a Barrier issue)

[iulo]

@metadave thanks bro, save my life.
for other who face on this problem, a possiable solution is just: locking and unlocking your system.