HenrikC
Active Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: "LogMeIn Client" is not optimized for your Mac.
Been saying the same for years myself but haven’t find anything with user/groups/host management that can compete price wise. The new Mojave issue isn’t the most pressing issue for me though. Extreme slowness of remote sessions within Sweden and an ancient LMI central that haven’t evolved for 10 years is what I’m disappointed in.5.5KViews0likes10CommentsRe: "LogMeIn Client" is not optimized for your Mac.
Yes. Crashes as soon as any other windows is given focus. ocess: LogMeIn Client [87473] Path: /Applications/LogMeIn Client.app/Contents/MacOS/LogMeIn Client Identifier: com.logmein.ignition Version: 4.1.6927 (4.1.0.6927) Code Type: X86-64 (Native) Parent Process: ??? [1] Responsible: LogMeIn Client [87473] User ID: 501 Date/Time: 2018-09-25 04:31:24.293 +0200 OS Version: Mac OS X 10.14 (18A389) Report Version: 12 Bridge OS Version: 3.0 (16P375) Anonymous UUID: A2C62898-FB58-35F0-BDC5-314A9B739EB9 Sleep/Wake UUID: 3A355626-1CDA-4A75-AF00-57608CE676FF Time Awake Since Boot: 230000 seconds Time Since Wake: 590 seconds System Integrity Protection: enabled Crashed Thread: 0 TLMIApplicationMain Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_INSTRUCTION (SIGILL) Exception Codes: 0x0000000000000001, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Illegal instruction: 4 Termination Reason: Namespace SIGNAL, Code 0x4 Terminating Process: exc handler [87473] Application Specific Information: *** CFRelease() called with NULL *** Thread 0 Crashed:: TLMIApplicationMain Dispatch queue: com.apple.main-thread 0 com.apple.CoreFoundation 0x00007fff2e59e55e CFRelease + 109 1 com.logmein.remctrlplugin 0x0000000114779656 0x11468e000 + 964182 2 com.logmein.remctrlplugin 0x00000001146ad769 0x11468e000 + 128873 3 com.logmein.remctrlplugin 0x00000001146ad5fd 0x11468e000 + 128509 4 com.logmein.remctrlplugin 0x00000001146afc6b 0x11468e000 + 138347 5 com.logmein.remctrlplugin 0x00000001146b14a5 0x11468e000 + 144549 6 com.logmein.remctrlplugin 0x0000000114777d7c 0x11468e000 + 957820 7 com.logmein.remctrlplugin 0x000000011477029a 0x11468e000 + 926362 8 com.apple.AppKit 0x00007fff2bc51205 _NSViewDrawRect + 66 9 com.apple.AppKit 0x00007fff2bc4fabd -[NSView(NSInternal) _recursive:displayRectIgnoringOpacity:inContext:shouldChangeFontReferenceColor:stopAtLayerBackedViews:] + 1545 10 com.apple.AppKit 0x00007fff2bc4f4a2 __46-[NSView(NSLayerKitGlue) drawLayer:inContext:]_block_invoke + 192 11 com.apple.AppKit 0x00007fff2bc4f201 -[NSView(NSLayerKitGlue) _drawViewBackingLayer:inContext:drawingHandler:] + 1769 12 com.apple.QuartzCore 0x00007fff39563aaf CABackingStoreUpdate_ + 577 13 com.apple.QuartzCore 0x00007fff395c5325 invocation function for block in CA::Layer::display_() + 53 14 com.apple.QuartzCore 0x00007fff39562c90 -[CALayer _display] + 1839 15 com.apple.AppKit 0x00007fff2bc4e75a _NSBackingLayerDisplay + 531 16 com.apple.AppKit 0x00007fff2bc32cc9 -[_NSViewBackingLayer display] + 811 17 com.apple.QuartzCore 0x00007fff395621bc CA::Layer::display_if_needed(CA::Transaction*) + 634 18 com.apple.QuartzCore 0x00007fff39550447 CA::Context::commit_transaction(CA::Transaction*) + 319 19 com.apple.QuartzCore 0x00007fff3954fd20 CA::Transaction::commit() + 576 20 com.apple.AppKit 0x00007fff2bc298f5 __65+[CATransaction(NSCATransaction) NS_setFlushesWithDisplayRefresh]_block_invoke + 274 21 com.apple.CoreFoundation 0x00007fff2e62d95d __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23 22 com.apple.CoreFoundation 0x00007fff2e62d892 __CFRunLoopDoObservers + 452 23 com.apple.CoreFoundation 0x00007fff2e5cf3c5 __CFRunLoopRun + 1166 24 com.apple.CoreFoundation 0x00007fff2e5cece4 CFRunLoopRunSpecific + 463 25 com.apple.HIToolbox 0x00007fff2d868895 RunCurrentEventLoopInMode + 293 26 com.apple.HIToolbox 0x00007fff2d8684d4 ReceiveNextEventCommon + 371 27 com.apple.HIToolbox 0x00007fff2d868348 _BlockUntilNextEventMatchingListInModeWithFilter + 64 28 com.apple.AppKit 0x00007fff2bb2595b _DPSNextEvent + 997 29 com.apple.AppKit 0x00007fff2bb246fa -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1362 30 com.apple.AppKit 0x00007fff2bb1e75d -[NSApplication run] + 699 31 com.apple.AppKit 0x00007fff2bb0de97 NSApplicationMain + 780 32 LogMeIn Client 0x0000000107b57864 0x107b4b000 + 51300 33 libdyld.dylib 0x00007fff5b668085 start + 15.7KViews0likes1CommentRe: "LogMeIn Client" is not optimized for your Mac.
Yes. But it will crash if you command tab out from it or in any other way don't leave it as top front window. As long as you have the remote session and/or another LMI remote session active you're fine. Well... Except the normal LMI **bleep**tyness, flaws and shortcomings of the mac version. Like that hosts all of a sudden are renamed to 'localhost', lack of feautres in central like the windows clients and all that have... But that have only been a problem for like forever so I guess we need to have more patience and send them more money. =/5.6KViews1like3CommentsRe: Why are most hosts listed as restrictive all of a sudden...?
Hello yes, I called them today. Apparently some sort of mishap and that our accounmd had been downgraded. Not sure why it didn't state in clear text that there wasn't enough "liceses" or something. But we're back now. Thanks Ash3.4KViews1like0CommentsRe: Why are most hosts listed as restrictive all of a sudden...?
Nothing have changed in our installations. This is affecting not only computers spread out in the country but also in the same building. Two computers on the same VLAN with the same version of LMI have different status, one is normal and online while the other one has this "restricted" mode. THose two computers are identical in HW-sepc and macOS version. No response from support either... =(3.4KViews0likes2Comments