Logos 8 app not opening

Hello,

Just to let someone know, my Logos 8 desktop app would not open today. There was no error message, it just didn't respond to my clicking on it to launch it from either the dock or the Applications folder. I tried restarting my computer several times with no change in response. I tried the Font Test and there were no errors there either. My Mac software is up to date, macOS Mojave 10.14.3.

I had to uninstall Logos and reinstall it to get it to open, based on this support page that I found somewhere in a forum: https://support.logos.com/hc/en-us/articles/360007923512-What-to-do-if-Logos-Crashes-Mac

I lost an hour's work to this issue, so I thought I'd let you know about it and log it here in case anyone else was having issues as well.

I noticed when Logos finally opened that it had updated to 8.3 SR-3, so not sure if that was the cause or not.

Find more posts tagged with

Desktop App

Comments

JT (alabama24)

Welcome! [:)] Sorry you had troubles. [:s]

I had to uninstall Logos and reinstall it to get it to open, based on this support page

I don't know if I agree with FL's suggestions on that page, although I do agree in your case. I am curious, however, that you mentioned that you did step #2 (check fonts) but the fix came with step #1 (update Logos). Is there a reason you went out of order?

There was no error message, it just didn't respond to my clicking on it to launch it from either the dock or the Applications folder.

That is indicative of a corrupted (or failed) installation. Reinstalling should be the first thing to try. If a crash occurs (which isn't what happened to you), trying to load to a blank layout should be the first step. Second, would be to enable and read the logs to see if a .db file has become corrupted.

Kimberly Tenhor

https://community.logos.com/discussion/comment/1042774#Comment_1042774

Hi JT,

Thanks for your response.

Is there a reason you went out of order?

I was trying to avoid an uninstall/reinstall as much as possible since I've never had to do that yet since I've had the software since 2015. I had read about the fonts being a potential issue on other threads, and though I didn't recently add any fonts, I thought a simple test was easy to eliminate.

trying to load to a blank layout should be the first step

The application wouldn't even "bounce" when I tried to launch it, let alone having it open and loading a layout.

Second, would be to enable and read the logs to see if a .db file has become corrupted.

I did try to enable the logs and tried to open it again, but I could not find any log files had been generated. It may have been something I did wrong in enabling them (I followed this page: https://wiki.logos.com/diagnostic_logging) or maybe it was because it wouldn't even launch so it didn't even start any logging? Not sure. And since there was no support on Sunday, and my assignment is still due, it was at this point I decided to try the uninstall/reinstall, which thankfully worked.

Now that I know the uninstall/reinstall worked so easily, and everything rebuilt perfectly, I know to do that first in the future.

JT (alabama24)

https://community.logos.com/discussion/comment/1042825#Comment_1042825

Now that I know the uninstall/reinstall worked so easily, and everything rebuilt perfectly, I know to do that first in the future.

In your case, reinstalling the app was the right step. Since it didn’t bounce, it wasn’t crashing and logs would not have been produced. It was a corrupted or failed installation. For an actual crash, however, reinstalling is seldom the best solution. I should point out that reinstalling the app as you did is fairly simple and was not a full reinstall. That would have been a much more significant process and should be done as a last resort.

Kimberly Tenhor

https://community.logos.com/discussion/comment/1042870#Comment_1042870

Thanks JT! Glad to have validation that I ultimately did the right thing, and understood correctly why logs weren't being produced. So that corruption would have occurred during the update process? If so, it's probably not possible now to know if it happened during the download process while the app was open, or if it happened upon opening when the update was being installed, correct?

I am curious though, because the "much more significant process" was exactly my hesitation to drag the app to the Trash (uninstall it) and then redownload and install it from their website. But if that wasn't the "full" reinstall, where are the instructions to do so and in what instances would that be warranted? So, what is the difference between what I did, and what a "full" reinstall is?

Thanks so much,

Kim

Jack Caviness

https://community.logos.com/discussion/comment/1042944#Comment_1042944

I am curious though, because the "much more significant process" was exactly my hesitation to drag the app to the Trash (uninstall it) and then redownload and install it from their website.

Deleting the app from the Applications folder does not remove your resources which are stored in the Library folder of your Home directory. Deleting and reinstalling that is a major project—depending on the size of your library.

Kimberly Tenhor

https://community.logos.com/discussion/comment/1042963#Comment_1042963

Ah, got it. Thanks Jack!

JT (alabama24)

https://community.logos.com/discussion/comment/1042966#Comment_1042966

In addition to what Jack wrote, deleting the app also does not remove the .db files and indices. In my experience, crashes most often occur when those become corrupted. Reinstalling the app would not fix the problem. That does not appear to have been your problem. When a .db file becomes corrupted, grabbing logs of a crash should point those out. Often deleting the corrupted file and allowing Logos to rebuild is a much less painful operation than redownloading and reindexing everything!

Kimberly Tenhor

https://community.logos.com/discussion/comment/1042973#Comment_1042973

Great to know, thanks JT!

So, if that ever happens to me (and I would know this because the app would open but not build my resources, correct?) then I would turn on the logging using the instructions in that support page I found? https://support.logos.com/hc/en-us/articles/360007923512-What-to-do-if-Logos-Crashes-Mac

Then I would contact support before attempting to delete the corrupted file (and hope that wouldn't happen on a Sunday!)?

Thank

JT (alabama24)

https://community.logos.com/discussion/comment/1042976#Comment_1042976

I would know this because the app would open but not build my resources

No... You would open the app and it would crash (shut down). In your case, it never even opened (so it didn't "crash").

Then I would contact support before attempting to delete the corrupted file (and hope that wouldn't happen on a Sunday!)?

For "official" help, you will need to contact FL directly (preferably by phone). Otherwise, you can create a thread in the forums, explain your issue clearly, and upload logs. I am a "quasi techie" and can sometimes diagnose issues... but there are often others who will be able to diagnose the issue quickly. The forums are not a primary means of communication with FL, but rather is a "crowd sourced" help from fellow users like us.

Christian

Thank you for your post Kimberly! I had the very same issue. The uninstall/reinstall took me less than 10 minutes.

Kimberly Tenhor

https://community.logos.com/discussion/comment/1042995#Comment_1042995

No... You would open the app and it would crash (shut down). In your case, it never even opened (so it didn't "crash").

Okay, very good to know the difference.

Thanks so much for your help JT, I appreciate it!

Kimberly Tenhor

https://community.logos.com/discussion/comment/1043228#Comment_1043228

Sorry to hear you had the same issue Christian, but so very glad you were able to find this thread and get it resolved so quickly! That's the main reason I posted it!