B 3 Crash on macOS 10.12.1
I've attached my logs, B 3 crashes consistently. It logs into my Logos accound, draws initial windows and populates them, then the beachball spins and everything disappears. No joy using this at the moment. I've booted into safe mode and get the same crash.I can bring up a blank layout and open books. English and Hebrew resources, but Greek resources (NA28, UBS 4, LXX) crash immediatly. All my Greek lexicons and dictionaries open fine. I've changed the default Greek font from SBLBibLit to Arial Unicode just in case it was a font issue. The "no Greek text" problem takes out all my layouts since I'm always workiing in some kind of Greek text.
Comments
-
Did you ever enable the new search engine ("set use new search engine to yes"). If so, does the crash stop if you disable it?We believe we've identified the cause of this crash and will have a fix in the next beta. Until then, you will have to avoid opening your Greek resources.
0 -
Is there another choice since I'm in New Testament texts. Any way to walk back to the previous beta? If I uninstall the engine and reinstall the production version, will it reindex everything?
0 -
Clint Cozier said:
Is there another choice since I'm in New Testament texts. Any way to walk back to the previous beta?
You can work around this problem with a little effort. You will need to open a resource that contains tagging for both Greek and Hebrew lemmas (such as a reverse interlinear Bible like ESV). Then open the visual filter menu. In the Notes and Highlights section, right click on every Notes Document that might contain attachments to non-Greek lemmas and select the "Do not show in any resources" option. This will ensure that it is also turned off for your Greek resources. Once these have all been turned off, you should be able to safely open your Greek resources.
Andrew Batishko | Logos software developer
0 -
Andrew,
I've done as you outlined above from the ESV and am still crashing Logos every time I open a greek text resource.
0 -
Clint Cozier said:
Andrew,
I've done as you outlined above from the ESV and am still crashing Logos every time I open a greek text resource.
That means there is still some Notes Document that is turned on for the Greek text resource that contains attachments to non-Greek lemmas. If you know which document that might be, you can add a new note to that document that is attached to text in the ESV. This will allow it to be visible in the ESV's visual filters menu, which will let you turn it off for all resources. After you get it turned off, you can remove the note created above.
If you aren't sure which document might be causing the problem, then you'll need to do this for all of your notes documents that aren't showing up in the ESV's visual filters menu until you manage to turn off the one that is triggering the crash.
Andrew Batishko | Logos software developer
0 -
Andrew,
I've just gone through all 66 of my book notes and inserted a note into the ESV so they show up then turned them off. Still crashing. I've got dozens of other notes scattered on all kinds of topics and don't have the time to run them all down. Will the release of the next beta solve this, or will I need to continue to work through all my notes? Would reverting to the stable version solve the problem, and can I do that without reindexing everything?
0 -
Clint Cozier said:
Andrew,
I've just gone through all 66 of my book notes and inserted a note into the ESV so they show up then turned them off. Still crashing. I've got dozens of other notes scattered on all kinds of topics and don't have the time to run them all down. Will the release of the next beta solve this, or will I need to continue to work through all my notes? Would reverting to the stable version solve the problem, and can I do that without reindexing everything?
We've already got a fix for the problem. This will be available in the next beta, which is currently scheduled to ship on Monday (Dec 5th).
As stated in our instructions here: https://community.logos.com/forums/t/52967.aspx the beta cannot be downgraded to a stable version without completely uninstalling the application and deleting all of the Logos folders. However, method 3 from the following instructions could allow you to get back up and running again without needing to download all of your resources again (you would still need to reindex): https://wiki.logos.com/quick_installation_onto_multiple_computers
Andrew Batishko | Logos software developer
0 -
Clint Cozier said:
Would reverting to the stable version solve the problem, and can I do that without reindexing everything?
This should now be fixed in 7.3 Beta 4
0 -
B 4 fixes it. Thanks!
0
