2425.LogosError.logLogs attached.2821.LogosCrash.txt
It would help to enable logging and upload the compressed log files folder.
Looks like it is a problem with a profile.
Got around this using <ctrl> on startup
Work Offline
If I load my last shutdown profile Logos crashes.
More important things to do right now that debug this.
Looks like it is a problem with a profile. Got around this using <ctrl> on startup Work Offline If I load my last shutdown profile Logos crashes. More important things to do right now that debug this.
Graham,
Once you are able to get us logs please post them here so we can take a look.
Thanks,
Philana
Once you are able to get us logs please post them here so we can take a look. Thanks, Philana
Thanks Philana
It looks like as long as I don't open my old layout I am OK. I have only tried the last two versions so I'm not sure when the corruption or bug occurred. Support have suggested a reinstall which I am reluctant to do as every time I have done this in the past it takes me days to get everything sorted out.
My plan is to recreate my layout rather than try and reload the ones that are crashing Logos as this seems like the quickest route to getting back to normal.
Frustrating thing is that because Logos does not seem to remember that the last startup failed it took a while and a couple of reboots to get a system up and running. Having an easily accessible "safe mode" would really have helped.
Took me over an hour to start Logos to do my daily reading, not the best advert for software efficiency.
Frustrating thing is that because Logos does not seem to remember that the last startup failed it took a while and a couple of reboots to get a system up and running.
It loads the the last "safe" layout after a crash but the dynamic elements of a panel could be responsible e.g. things that changed with a resource before the crash.
It looks like as long as I don't open my old layout I am OK.
The log file indicates the crash comes from a search panel for NASB95. If you can't load an older version of the layout without error then it is best to reconstruct it without using NASB95. If you subsequently get a crash opening/searching NASB95 then create a new thread with logs.
If you can't load an older version of the layout without error then it is best to reconstruct it without using NASB95.
So this is crazy as the first thing that I did when I opened to a clean layout is open the NASB95, which is my Bible of choice, without problems.
Given that I went back a week there are at least 7 saved layouts on my system created at shutdown that Logos has successfully opened but which now cause a crash. My conclusion here is that the latest update introduced this problem.
I don't have a problem opening my saved layouts.
If you can't load an older version of the layout without error then it is best to reconstruct it without using NASB95. So this is crazy as the first thing that I did when I opened to a clean layout is open the NASB95, which is my Bible of choice, without problems.
Try to recreate the layout with NASB95 and see if you can reproduce the problem.
I have many saved layouts that work Dave
The point is that either at least 7 days of my ever evolving "shutdown" layout have become corrupted or the update that automatically downloaded immediately prior to the error has a bug. The logs might suggest that the NASB95 is the issue but based on the way it fails I think that the new courses view is the more likely candidate.
I already have a new version of my "layout" working with the NASB95. Recreating what I have lost is not that easy I use the "shutdown" layout as a way of picking up my thinking from the day before so its not a static layout that I can easily recreate. Whilst I would have liked to get a back when I first reported the problem the reality for me now is that it is lost. Of course as my layout evolves the error might reoccur at which point the suspect list will be a lot smaller.
This is the same problem as I just responded to here. I think you need to avoid having a Search Panel and Bible Browser in your layout at the same time until we get a release with the bug fix. Sorry for all the trouble.
EDIT: I was wrong. Your crash is different, but I'll take a look at it too.EDIT2: It turns out I was wrong and I was right. It looks like you've been affected by both crashes, so my earlier advice also applies.EDIT3: I got to the bottom of it. The two crashes were caused by the same code, so my fix works for both. Essentially the one crash happened when the search was run and Bible Browser didn't have resource text, and the other happened when it did have resource text.
Unfortunately this means until the service release with the fix is ready you can't use Bible Browser at the same time as a search.
This should be fixed by 7.2 SR-1
2425.LogosError.logLogs attached.2821.LogosCrash.txt This should be fixed by 7.2 SR-1
Fixed by today's update, thanks.
[Y][:)]
