Crash: install fails

I recently deleted Logos, then upgraded my Mac to Yosemite (10.10), and tried reinstalling Logos today. I downloaded the dmg fine and copied it to my Applications folder. However, when I try to run from the Applications folder, it immediately closes as soon as I open it (I see the icon on the doc for about 1 second). I never see a login window or any other window.

Per instructions at https://www.logos.com/support/logos5/mac/problem I am posting this as a crash report. I downloaded the Logos installer from this link today. I also tried installing the beta version, but to no avail. I also ran the logging utility before opening the app, and generated the attached zip file. (Although I'm not sure it will be of much help because when I tried to unzip it on my computer, it didn't seem to contain anything).

Thanks for your help!

It seems I'm not able to attach a file through the forum post either. I clicked on the paperclip icon and selected the zip file, but nothing happens when I

Find more posts tagged with

Comments

Rev Chris

Hmm - also looks like I can't post more than what's in the above post (had some weird text overlapping in the text field for the last few sentences, which didn't seem to make it on the posted result. Starting to think it's Yosemite still being buggy. Anyway, here's the rest of the post:

It seems I'm not able to attach a file through the forum post either. I clicked on the paperclip icon and selected the zip file, but nothing happens when I click "insert". Instead, I have to click "cancel" to return to the post. So, here's the Dropbox link to the file:

https://www.dropbox.com/s/ephu3dvgn79gx5y/LogosLogs.chris.20140929-211251.zip?dl=0

----

JT (alabama24)

Try downloading the app engine through the link in my signature line. Take screen shots of your efforts. Without logs, we don't have much to go on without sitting beside you... so screen shots might help.

It seems I'm not able to attach a file through the forum post either. I clicked on the paperclip icon and selected the zip file, but nothing happens when I

I don't know what the end of that sentence was supposed to say... Here are instructions:

Click on paper clip.

Rev Chris

https://community.logos.com/discussion/comment/634507#Comment_634507

Thank's Alabama. Please see my reply to my initial post for the remainder and the link to the log. I checked out the link in your signature line, but it seems to go to a page that uses the same link that I originally downloaded from.

JT (alabama24)

https://community.logos.com/discussion/comment/634506#Comment_634506

looks like I can't post more than what's in the above post (had some weird text overlapping in the text field for the last few sentences, which didn't seem to make it on the posted result. Starting to think it's Yosemite still being buggy.

It certainly is buggy in some areas, but I am unsure if any of your problems here have to do with the OS. I have not had these problems... but I did notice the bullet points missing above. Weird. I know that Logos is beefing up the website... the problems may be on Logos side rather than yours.

Rev Chris

https://community.logos.com/discussion/comment/634510#Comment_634510

Yeah - I'm also having issues with posting on the forums. Every time I post or reply it takes forever, then gives me an error page saying something went wrong and the error has been logged. But, it always seems to post still.

JT (alabama24)

I downloaded the dmg fine and copied it to my Applications folder. However, when I try to run from the Applications folder, it immediately closes as soon as I open it (I see the icon on the doc for about 1 second).

For clarification: You don't copy the .dmg file to the applications folder... You copy the application from the dmg file to the applications folder. Is that what you did? How large was the .dmg file?

Rev Chris

https://community.logos.com/discussion/comment/634512#Comment_634512

Correct - I opened the dmg from my downloads folder and copied the .app into my Applications folder. The .dmg was 150mb or so. The .app is sitting at 344mb right now.

JT (alabama24)

https://community.logos.com/discussion/comment/634513#Comment_634513

I know, I know. Trust me. Restart your computer and see what happens when you try opening the app again.

Rev Chris

https://community.logos.com/discussion/comment/634514#Comment_634514

lol - I hear ya. I tried that once already, but I'll give it another shot.

Rev Chris

https://community.logos.com/discussion/comment/634515#Comment_634515

One thing I love about Yosemite is it restarting really fast! But, still no luck with the problem...

JT (alabama24)

https://community.logos.com/discussion/comment/634514#Comment_634514

Another issue that may be at work here: Deleting the "app" really doesn't do anything. The underlaying .db files, etc. remain on your computer unless you explicitly delete them. This <could> be part of your issue.

Have you tried loading the app to a blank layout? Press and hold the command key immediately upon startup. Check the appropriate box.

Rev Chris

https://community.logos.com/discussion/comment/634519#Comment_634519

Just tried holding down command while trying to run the app, but it didn't do anything. I'm pretty sure I got the data files when I deleted the app previously - I was cleaning out my computer at the time and freed up around 20gb just from Logos.

I just tried looking at the log file again - got it to open. Looks like the issue is with the "ReportApplicationNotIdle" method of the OurApp class:

2014-09-29 19:44:42 ChristohersMBP2.attlocal.net Logos[894] <Warning>: An exception was thrown in managed code.
2014-09-29 19:44:42 ChristohersMBP2.attlocal.net Logos[894] <Warning>: (
0 CoreFoundation 0x00007fff9015346c __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff8ef986de objc_exception_throw + 43
2 libLogosWrappers.dylib 0x000000010d2d768e -[OurApp ReportApplicationNotIdle] + 0
3 Logos 0x0000000108993cc6 -[OurAppController showMainApplicationWindow] + 195
4 CrashReporter 0x000000010c9b8e51 -[BWQuincyManager startManager] + 129
5 Foundation 0x00007fff91404ceb __NSFireDelayedPerform + 364
6 CoreFoundation 0x00007fff900a6944 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
7 CoreFoundation 0x00007fff900a65d3 __CFRunLoopDoTimer + 1059
8 CoreFoundation 0x00007fff90119bbd __CFRunLoopDoTimers + 301
9 CoreFoundation 0x00007fff90063068 __CFRunLoopRun + 2024
10 CoreFoundation 0x00007fff90062638 CFRunLoopRunSpecific + 296
11 HIToolbox 0x00007fff8f7f645f RunCurrentEventLoopInMode + 235
12 HIToolbox 0x00007fff8f7f61da ReceiveNextEventCommon + 431
13 HIToolbox 0x00007fff8f7f601b _BlockUntilNextEventMatchingListInModeWithFilter + 71
14 AppKit 0x00007fff9696b5d1 _DPSNextEvent + 964
15 AppKit 0x00007fff9696ad80 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
16 AppKit 0x00007fff9695ed33 -[NSApplication run] + 594
17 AppKit 0x00007fff9694a1b4 NSApplicationMain + 1832
18 libdyld.dylib 0x00007fff968ea5c9 start + 1
)

JT (alabama24)

https://community.logos.com/discussion/comment/634520#Comment_634520

I am running out of suggestions. It sounds like a corrupted app file... or something. [:s]

Rev Chris

https://community.logos.com/discussion/comment/634523#Comment_634523

Don't think it's a corrupted file - probably just a bug in the code related to network procedures or looking for data that exists on apps that have been opened before but not on first launches. I'm better at reading crash logs from iOS apps than OSX apps though.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/634524#Comment_634524

Without complete log files (particularly Logos.log), we won't be able to troubleshoot this issue via the forums.

Rev Chris

https://community.logos.com/discussion/comment/634527#Comment_634527

Without complete log files (particularly Logos.log), we won't be able to troubleshoot this issue via the forums.

It should be linked to via Dropbox above. Let me know if you can't get it - I can email it to someone.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/634528#Comment_634528

It should be linked to via Dropbox above.

I should have been clearer. I already downloaded that, but it did not contain "Logos.log".

Rev Chris

https://community.logos.com/discussion/comment/634530#Comment_634530

Oh, well that's all that was generated. Perhaps the Logos.log generates after the crash point?

Rev Chris

https://community.logos.com/discussion/comment/634532#Comment_634532

Here's a demo video showing just how quickly the crash appears, and exactly what it looks like from a UX perspective:

https://www.dropbox.com/s/8vtcz39j2wv7t69/crash_video.mov?dl=0

Here's the resulting crash log that was generated:

https://www.dropbox.com/s/z6u46uzmhw3sn0n/LogosLogs.chris.20140929-222029.zip?dl=0

JT (alabama24)

https://community.logos.com/discussion/comment/634532#Comment_634532

Oh, well that's all that was generated. Perhaps the Logos.log generates after the crash point?

Using the diagnostic tool (you are using that, right? If not, see link in my signature line), make sure diagnostic logging is enabled. Once it is enabled, start up logos, allow it to crash, then grab the logs via the tool.

Rev Chris

https://community.logos.com/discussion/comment/634536#Comment_634536

Yeah - I believe I had that tool running properly. See the video I made showing exactly what steps I performed. If I need to do something different, let me know.