A20 - Crash on Startup

Around A16 or so the Alpha version stopped working on both my Macbook and Mac Mini. I haven't had time to trouble shoot until today and thought maybe a newer Alpha version would work, no luck. I click on the program to startup and it has the spinning circle type logo going and then crashes to an Apple crash log report screen. I even tried a new install by trashing the two preference files and the Logos folder in the Support Applications folder, it still crashes on both computers. I have attached the appropriate logs, the new install never created the index.log file.

Respectfully,

JD Busch

3731.A20 - JD Crash Logs.zip

Find more posts tagged with

Comments

Mike Binks

Warning - Man who knows nothing about Logs has looked at your Logs.

And this chap wonders if anything to do with Logos has ended up in your iwork09 folder in applications.

this is really a long shot but you might like to take a look - if it is so then it is unlikely to help matters.

Tootle pip

Mike

Keep Smiling 4 Jesus :)

Warning - Man who knows nothing about Logs has looked at your Logs.

And this chap wonders if anything to do with Logos has ended up in your iwork09 folder in applications.

Looks like knowing nothing about Logs found root cause of A20 Crash on Startup.

Console messages has couple interesting lines from earlier crash:

5/30/10 10:27:43 AM [0x0-0x219018e].com.logos.Logos_Bible_Software_4[86401] 05/30/2010 10:27:43 | INFO | 1 | IndexerProcess | Launching indexer because the Bible index needs to be updated.

5/30/10 10:27:43 AM [0x0-0x219018e].com.logos.Logos_Bible_Software_4[86401] Stacktrace:

Observation: Logos 4 uses ~/Library/com.logos.LogosIndexer.plist file to launch Indexer process. The parameter list (plist) specifies location of Logos4Indexer executable:

"/Applications/Logos Bible Software 4.app/Contents/MacOS/Logos4Indexer.app/Contents/MacOS/Logos4Indexer"

Around A16 or so the Alpha version stopped working on both my Macbook and Mac Mini. ... the new install never created the index.log file.

Indexer.log file created by Logos4Indexer - highly suspect crashes occurring due to "Logos Bible Software 4" being inside "iWorks '09" instead of "Applications" - unable to load Logos4Indexer.

By the way, likewise curious about Tools (for NiXPS) also in "iWorks 09". Wonder if applications relocated into "iWorks '09" around A16 or so.

Mac historical observation: prior to Mac OS X, moving applications around usually not cause problems since file system tracked locations (type and creator). Like other *nix flavors, moving applications in Mac OS X not good idea.

AppleInsider has article about Mac file system evolution (from type and creator to UTI):

http://www.appleinsider.com/articles/09/09/22/inside_snow_leopards_uti_apple_fixes_the_creator_code.html

Keep Smiling [:)]

J Busch

I move my "Office" type applications into my iWorks Folder to keep everything in order. I have been running the alpha version of L4 from this folder from the start. I know some other applications get grumpy not running out of the applications folder so I tried a clean install to just the applications folder and still the program would crash at startup. I did notice when I rebooted the computer, the indexer started and indexed my files. I have attached it for reference.0257.Indexer.log

Keep Smiling 4 Jesus :)

... tried a clean install to just the applications folder and still the program would crash at startup. ... when I rebooted the computer, the indexer started and indexed my files. I have attached it (indexer.log) for reference ...

Wonder about console messages, log files, and crash report (if one is created) for program startup crash when Logos is in Applications folder ?

Comparing posted indexer.log file with my own after rebooting computer, noticed posted log file did not have data type registrations (mine has many messages), but did have some resource checking:

05/31/2010 14:20:03 | INFO | 3 | LogosIndexerWorker | Checking resource ID '{A664EA2D-D387-40FC-9C2D-D8967E5B1E88}' for update 'Resource {A664EA2D-D387-40FC-9C2D-D8967E5B1E88}' to see if version '2009-10-20T20:36:34Z' is available.

05/31/2010 14:20:03 | INFO | 3 | LogosIndexerWorker | Checking resource ID '{868BA74B-1BCC-4AE1-BE5C-570F30514045}' for update 'Resource {868BA74B-1BCC-4AE1-BE5C-570F30514045}' to see if version '2009-10-20T20:36:34Z' is available.

05/31/2010 14:20:03 | INFO | 3 | LogosIndexerWorker | Checking resource ID '{46E5F823-F019-4FC3-9A71-4C1F08A9EBDF}' for update 'Resource {46E5F823-F019-4FC3-9A71-4C1F08A9EBDF}' to see if version '2009-10-20T20:36:34Z' is available.

05/31/2010 14:20:03 | INFO | 3 | LogosIndexerWorker | Checking resource ID '{B9686678-A9EE-4621-9C61-198273704307}' for update 'Resource {B9686678-A9EE-4621-9C61-198273704307}' to see if version '2009-10-20T20:36:34Z' is available.

05/31/2010 14:20:03 | INFO | 3 | LogosIndexerWorker | Checking resource ID '{577D86DA-892A-4EC7-8744-1EB3193EB27E}' for update 'Resource {577D86DA-892A-4EC7-8744-1EB3193EB27E}' to see if version '2009-10-20T20:36:34Z' is available.

Keep Smiling [:)]

Tom Philpot (Faithlife)

It looks like the application is having some trouble with the name of the iWork Folder. Try renaming it to "iWork 09" instead of "iWork '09" and it should work.