lzch1 I don't think that's the right message that was sent by support. Just because we don't know what the issue is currently does not mean we can't fix it in subsequent releases. From your case filed with us it looks like there is movement on the details to bring engineering into the fray. I would then expect more knowledge around the problem in the coming weeks...
Unfortunately it's not something we recreated during initial testing so the fix will not be immediate. I apologize for the delay in recognition.
Several days have passed by. I have yet to receive any communication regarding an update on where we stand on this?
Hi lzch1
I apologize for the frustration. After a quick look into your case and from the log files you provided the host has webroot installed, has it been disabled?
Glen, Yes Webroot is installed. This is a corporate security package that is required. This same package is on all Mac's that have Mojave running. Interesting.. that you point to that and I disabled it temporarily and it works fine. Meaning.. I can remote connect and enage keyboard. Webroot has installed another layer of security called "Secure Keyboard Entry" I was not aware of this till you pointed me to look at if i have Webroot installed. Once, I disabled "Secure Keyboard Entry" I can gain control of my remote keyboard.
After several weeks I finally got a solid solution and answer. THANK YOU!!
When is their going to be a Mac LogMeIn update for Majave. I don't need it to work in HD or Dark Screen Mode. Whatever your developers can do so that I have remote Keyboard and Mutitasking with other programs on my Mac that is all I care about. I know others want a a full fix but whatever you can give me now would be greatly appreciated.
