bradhs
Active Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Re: MacOS Big Sur host: no mouse click or keyboard input accepted from client
HiAshC, This is what a majority of people are discussing in the Rescue message board. This is the thread:https://community.logmein.com/t5/LogMeIn-Rescue-Discussions/Mac-OS-Big-Sur-file-manager-compatibility-issue/m-p/258055#M5468 I know it's in the wrong place, but the OP in that chat is discussing this very issue that is being brought up by this OP. Thanks, Bradley11KViews0likes0CommentsRe: Mac OS Big Sur compatibility issue
I'm getting the same error since the installing Big Sur beta, to moving to production on a MacBook Pro 2018. AND now on a MacBook Pro M1. AND so far everyone else that has moved to BigSur as well. Also, I dare to ask when will native M1 code be available. This is what it looks like on an M1. Process: LogMeIn Client [48478] Path: /private/var/folders/*/LogMeIn Client.app/Contents/MacOS/LogMeIn Client Identifier: com.logmein.ignition Version: 4.1.7585 (4.1.0.7585) Code Type: X86-64 (Translated) Parent Process: ??? [1] Responsible: LogMeIn Client [48478] User ID: 502 Date/Time: 2020-11-23 07:01:37.461 -0800 OS Version: macOS 11.1 (20C5048k) Report Version: 12 Time Awake Since Boot: 53000 seconds Time Since Wake: 1400 seconds System Integrity Protection: enabled Notes: Translocated Process Crashed Thread: 0 TLMIApplicationMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x000007fa3c47dd0f Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [48478]6.8KViews0likes23Comments