Crash: Logos 5.2b Beta 3 crashes *every* time on startup
Logs attached
7041.LogosLogs.stuart.20140629-091135.zip
Previous thread was: http://community.logos.com/forums/t/86303.aspx
Comments
-
Hi Stuart - thanks for the logs
From the logs there are two different things which seem to be going on.
The first is a problem opening a version of "Institutes of Christian Religion" - there seems to be some form of version mismatch going on. Are you opening Logos to a layout which includes that resource? If so, try opening to a blank layout - hope CMD when starting Logos and select "use blank layout" and see how you get on. This doesn't cause the crash (at least directly) as far as I can see
The actual error associated with the crash is:
2014-06-29 09:11:21.432 Logos[23930:707] ERROR - Failed to find [Light.InnerPaneDropShadow1] in the Light theme
[0629/091121:WARNING:resource_bundle.cc(283)] locale_file_path.empty()
[0629/091121:FATAL:main_delegate.cc(495)] Check failed: !loaded_locale.empty(). Locale could not be found for en-CAI have never seen this before and don't know what it means. But it looks as though it may be locale-related. Hopefully someone can advise on this further
Stuart Robertson said:Previous thread was: http://community.logos.com/forums/t/86303.aspx
In future, please post replies to the same thread. It helps when trying to keep things clear.
Graham
0 -
Graham Criddle said:
The first is a problem opening a version of "Institutes of Christian Religion" - there seems to be some form of version mismatch going on. Are you opening Logos to a layout which includes that resource?
I think it's more likely caused by a reading plan of the old version of the Institutes. If possible it may be better to delete the reading plan.
But that's only if opening to a blank layout doesn't help (which is the best place to start, certainly).
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
In System Preferences => Language & Text => Language
What is the first language in the list ?
Using terminal, what is the output for locale ? (should list eight variables with values)
localeGraham Criddle said:The actual error associated with the crash is:
2014-06-29 09:11:21.432 Logos[23930:707] ERROR - Failed to find [Light.InnerPaneDropShadow1] in the Light theme
[0629/091121:WARNING:resource_bundle.cc(283)] locale_file_path.empty()
[0629/091121:FATAL:main_delegate.cc(495)] Check failed: !loaded_locale.empty(). Locale could not be found for en-CAI have never seen this before and don't know what it means. But it looks as though it may be locale-related. Hopefully someone can advise on this further
Observation: en-CA for crash is different than en-US auto-detected language (second line of Logos.log file):
06/29/2014 09:10:48 | INFO | 1 | OurApp | Auto-detected UI language: en-US
Keep Smiling [:)]
0 -
Hi Graham,
I tried starting holding down Cmd and Logos ran for a while, but the moment I tried to edit reading plans (Institutes, for example) Logos crashes.
Also, I started a new thread (with the prefix "Crash:") as this is what was requested in the instructions for posting crash logs.
I will post additional logs as/when time permits.
Stuart.
0 -
[:)]
Hi Stuart
Stuart Robertson said:I tried starting holding down Cmd and Logos ran for a while, but the moment I tried to edit reading plans (Institutes, for example) Logos crashes.
Which suggests the issue might be with the reading plan as per Mark's post above. How feasible is it to delete the plan in question?
Stuart Robertson said:Also, I started a new thread (with the prefix "Crash:") as this is what was requested in the instructions for posting crash logs.
That s fair point!
It is still, in my opinion, better to post logs into a thread where you were already discussing the problem. I will suggest to Logos that they change theor instructions - but they might disagree with me!
Stuart Robertson said:I will post additional logs as/when time permits.
That would be helpful.
Graham
0 -
Hi Graham,
I've deleted each of the reading plans (all but one caused a crash) that were causing trouble (5 different plans).
It's no big loss---I've stopped using Logos for keeping notes, etc some months back after I lost data. I rarely use Logos now, mostly because of dissatisfaction (irritation with slowness, spinning pizzas and somewhat-too-frequent crashes) and only use it when I truly have to. I hadn't used Logos for a number of months. When I launched it a few days back I thought that perhaps the crashing days were gone and, naively, I admit, updated to the latest beta. Yes, I know it's a beta---I've run betas from other software packages without the "Logos experience".
Anyway, the problem seems to be "fixed" now. Thank you for your assistance and time.
0 -
Hi Stuart
Stuart Robertson said:I've deleted each of the reading plans (all but one caused a crash) that were causing trouble (5 different plans).
Stuart Robertson said:Anyway, the problem seems to be "fixed" now. Thank you for your assistance and time.
That's good news - and I've flagged the "create new thread" question to Logos for their consideration.
Stuart Robertson said:I hadn't used Logos for a number of months.
That's interesting - it maybe something to do with out of date resources but I don't know
Graham
0 -
Graham Criddle said:
I've flagged the "create new thread" question to Logos for their consideration.
Where did you find the "create new thread" instructions?
0 -
https://www.logos.com/support/logos5/mac/problem
No explicit request to "Start a new thread", but point 3 of step 4 of the above-linked page says:
Put "Bug", "Crash" or "Hang" (Freezing) in the title.
I could find no way to change the title of the existing thread so created a new one.
0 -
Bradley Grainger (Logos) said:Graham Criddle said:
I've flagged the "create new thread" question to Logos for their consideration.
Where did you find the "create new thread" instructions?
Just to expand on Stuart's post, step 2 of the article he references does have 'Click on "Write a New Post"' as below
Step 4: Make a Report
- Visit the Logos 5 Forum.
- Using Logos 4? Visit the instead.
- Click on "Write a New Post".
- Put "Bug", "Crash" or "Hang" (Freezing) in the title.
0 - Visit the Logos 5 Forum.
