Highlighting not saving to a notes document
Hi All,
Upgraded to L8 yesterday for my MacBook Pro (running latest OS).
Most everything is working fine. However, my highlights that previously automatically saved to a notes document no longer work. When I try to go to my highlighting templates and tell it to save to a notes document, Logos crashes.
Anyone else having this issue? Can someone from Logos respond and let us know if they're aware of the issue?
Please see the attached image for reference. These highlights used to save to my "Daily Bible Reading" notes document, but don't any longer. When I try to click on "no notebook" to change that, Logos crashes.
Rev. Ben Hein
Shady Grove Presbyterian Church (PCA)
Reformed Theological Seminary, M.Div (2017)
www.shadygrovepca.org
Comments
-
Please ensure diagnostic logging is enabled and post logs after a crash. Details at https://support.logos.com/hc/en-us/articles/360015776171-Report-a-Problem-in-Logos-Mac
0 -
Here you go. I am attaching the zip file. Thanks!
Rev. Ben Hein
Shady Grove Presbyterian Church (PCA)
Reformed Theological Seminary, M.Div (2017)
www.shadygrovepca.org
0 -
Thanks
But there is no indication of a crash in the Logos.log file.
Did you upload these after a crash and before starting Logos again?
0 -
I'm having the same problem Ben described, too. I open the highlighter tool palette, attempt to associate a palette with a notebook, and the app quits suddenly.2262.LogosLogs.will.20181030-144322.zip
0 -
Again there is no crash information in the Logos.log file
but the console message log for both of you has an entry of the form:
2018-10-30 07:16:48 Bens-MBP Logos[12846] <Error>: objc[12846]: Class FIFinderSyncExtensionHost is implemented in both /System/Library/PrivateFrameworks/FinderKit.framework/Versions/A/FinderKit (0x7fff9a9a51d0) and /System/Library/PrivateFrameworks/FileProvider.framework/OverrideBundles/FinderSyncCollaborationFileProviderOverride.bundle/Contents/MacOS/FinderSyncCollaborationFileProviderOverride (0x13455ddc8). One of the two will be used. Which one is undefined.
2018-10-30 07:16:48 Bens-MBP Logos[12846] <Error>: assertion failed: 18A391: libxpc.dylib + 92361 [0A8747D1-33AA-37E1-B97A-BA9B95FE4E8C]: 0x89
2018-10-30 07:16:48 Bens-MBP com.apple.xpc.launchd[1] <Warning>: Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklook
2018-10-30 07:16:48 Bens-MBP com.apple.xpc.launchd[1] <Warning>: Caller wanted oneshot behavior for pre-existing instance: caller = Logos
2018-10-30 07:16:48 Bens-MBP com.apple.xpc.launchd[1] <Warning>: Unknown key for integer: _DirtyJetsamMemoryLimit
2018-10-30 07:18:35 Bens-MBP com.apple.xpc.launchd[1] <Warning>: Endpoint has been activated through legacy launch(3) APIs. Please switch to XPC or bootstrap_check_in(): com.apple.quicklookI have no idea if that is relevant - I don't use Mac platforms.
But hopefully either a Mac expert or someone from Faithlife will be able to comment further
0 -
There is a folder in the zip file titled Logos_2018-10-30-144233-1_xxxxxx.crash where xxxxxx is the network name of the computer. The app exits suddenly without any pause for cleanup/sync or error message. MacOS itself responds with an error message that Logos crashed. In part, the error report reads:
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007ffeeca63fd8
Exception Note: EXC_CORPSE_NOTIFYTermination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [2263]VM Regions Near 0x7ffeeca63fd8:
MALLOC_SMALL 00007feb9ee39000-00007feb9f000000 [ 1820K] rw-/rwx SM=ZER
--> STACK GUARD 00007ffee9264000-00007ffeeca64000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0
Stack 00007ffeeca64000-00007ffeed259000 [ 8148K] rw-/rwx SM=SHM thread 00 -
A brother on Facebook reported the issue and called customer service to report it. Apparently they are aware of the issue now, although I haven't seen them acknowledge it on the forums. If this is common to Mac users, then Notes are quite broken right now for Macs.
Rev. Ben Hein
Shady Grove Presbyterian Church (PCA)
Reformed Theological Seminary, M.Div (2017)
www.shadygrovepca.org
0 -
Thanks for reporting this issue. I've reported this to our team, and they're looking into it.
0
