The GoTo Community is currently experiencing some technical issues affecting new posts and comments. We are actively working with our service provider and apologize for the frustration.
Forum Discussion
Solved
Mac OS Big Sur compatibility issue
With Mac OS 11 I can control the the Screen of the remote Mac, but when I click on the File manager Logmein crashes. Any Help would be greatly appreciated.
Hey everyone, thanks for your patience.
We've made the Mac beta version available for download publicly here (Big Sur compatible): https://beta.logmeinrescue.com/Files/TechConsoleMAC/LogMeInRescueTechnicianConsoleMAC.dmg
Full release depends upon how stable this is, so please let us know if you see any new issues.
We see the exact same problem. It's only the File Transfer that's experiencing this. Here is the Error :
Crashed Thread: 0 TLMIApplicationMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000001fc
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [12132]
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]
Looks like we're using Technician Console v7.12.3306 (64 bit) and listed as a Standard "Per Seat" License
We're working on some Mac enhancements currently, hope to have more info on the updates in the coming days...
- Oh, ok. I was wondering if we were on the same page. The Technician Console is running on Windows 10 and the clients we have issues with (hit or miss) are running Big Sur.
I'll have to request the information on that one as we're limited on access at my level and I'm not Quite familiar with what component an EndPoint is.
Where are we on the full release? We're still having hit/miss on connections with Big Sur.
Great! Thanks for confirming the new build compatibility.
I was able to open logmeinrescue.
Struggled with the regular process but your link allowed me to download an application that would open. Haven't used it yet, but it appears that it will work.
It's working for me now. Thank you!
Looks like the problem has now been fixed for me.
Thanks, will try it. Also need the File Transfer fixed in the LogMeIn Client.
Hey everyone, thanks for your patience.
We've made the Mac beta version available for download publicly here (Big Sur compatible): https://beta.logmeinrescue.com/Files/TechConsoleMAC/LogMeInRescueTechnicianConsoleMAC.dmg
Full release depends upon how stable this is, so please let us know if you see any new issues.
Thank You! I will contact them. I like your product but this has been very frustrating.
James
Thanks for your patience, I believe we will have a beta version available for testing in just a few days. The full release could be a couple of weeks after beta testing completes. Should you need to test early, please reach out to Customer Support next week to request individual upgrades.
Hey everyone,
Here's an updated support article explaining certain limitations on the client end: https://support.logmeinrescue.com/rescue/help/is-rescue-supported-on-macos-big-sur
I will work to get an ETA on the Technician delivery this week.
When approximately is "near future"? We rely heavily on this application and some functions are shut down.
Has there been a fix for this? It's been a while and I'm unable to do my work for my clients. Will have to look for another solution if not resolved.
I totally agree with jcaustin. This is poor performance from logmein - it's now been about week with absolutely no communication from logmein about progress report on a fix for File Manager on Macs. Will be definitely looking for alternative to logmein
This is a real mess for my employees working from home. Logmein does not care none of there updates have fixed this issue. Support is no help this was a great product. I am now looking for a change.
Per the email subject: Mac OS BigSur and Logmein Client
Tbh I think LogMeIn knows about this. It's widespread, not something isolated.
bradhs Credimus bradhs This community thread specifically references Rescue services. Are you all experiencing this with the Rescue endpoint, or another LogMeIn service such as Central/Pro ?
** With regards to Rescue services, remote access / control will fully work, though currently TC is not yet supported on Big Sur. It should be in the very near future: https://support.logmeinrescue.com/rescue/help/is-rescue-supported-on-macos-big-sur
Thanks for your patience while we patch this problem up.
