BUG: Logos fails to open (unless Ctrl held down)

3252.LogosLogs_AllenBrowne_2023-08-05.zip

Logos Bible Software no longer opens on my PC.

It starts, shows the splash screen, then the “Preparing your library” screen. When it tries to open the main screen, it silently disappears (no error message). The Windows Task Manager does not list Logos as running.

I can start Logos by holding down Ctrl and signing in. I can then load a Layout, and use Logos as normal.

Is there any point uploading the logs, since it doesn’t crash with Ctrl held down?

This is Logos 27.1.20, on Windows 11 Pro (22H2, 22621.1992).

Thanks.

Find more posts tagged with

Desktop App

Comments

Rosie Perera

Is there any point uploading the logs, since it doesn’t crash with Ctrl held down?

Yes, since you should be able to open it without Ctrl held down, so it might help to troubleshoot what is going wrong.

Allen Browne

Is there any point uploading the logs, since it doesn’t crash with Ctrl held down?

Yes, since you should be able to open it without Ctrl held down, so it might help to troubleshoot what is going wrong.

Thanks Rosie. Attached the log files that have today's date.

Allen Browne

Okay, I've turned on permanent logging. Here's the log file from today's crash.

Same symptoms: Logos still crashes to desktop, unless I hold down Ctrl, sign in, and load a layout. Suggestions?

1030.LogosLogs_AllenBrowne_2023-08-08.zip

Rosie Perera

I'm no longer an MVP and am leaving today on a 3-week trip, so I don't have time to look into it. Hopefully one of the current MVPs who knows log files better than I do will see this and take a look.

Allen Browne

I'm no longer an MVP and am leaving today on a 3-week trip, so I don't have time to look into it. Hopefully one of the current MVPs who knows log files better than I do will see this and take a look.

Enjoy the break, Rosie. Sure appreciate what you have done for me and for others over so many years.

JT (alabama24)

I am not a master log reader... I tried to read yours, but nothing was there which I knew how to fix. I saw something about expected downloads which weren't there, and also something about an unexpected link set in the NIV.

However, your situation isn't fully clear, so for clarification:

When you try to start the app normally, it crashes (on its own).
You are able to load to a blank layout.

Are both of those fully true? Have you restarted the computer with the same results? What does Logos normally open to with your settings? (for example, I open to "most recent layout: local".). If you normally open to a layout, have you tried using a different layout? Building a simple one from scratch and opening to it?

JT (alabama24)

Is there any point uploading the logs, since it doesn’t crash with Ctrl held down?

You should be providing the logs where you DON'T hold control down. If you didn't already, you need to 1) make sure logging is turned on, 2) start logos, 3) allow it to CRASH, 4) grab the logs 5) upload here.

The point is to get the logs where the app crashed.

Darren Miner

Microsoft updated the .NET Framework today. The update is preventing Logos from opening on my computer as well. I am running Windows 11 Pro.

Darren Miner

I ran the setup for today's version update, and that fixed the problem for me. Good luck!

Bruce Dunning

Just for reference, I was experiencing the same thing that Allen was describing but today's update seems to have fixed the issue.

Allen Browne

I am not a master log reader... I tried to read yours, but nothing was there which I knew how to fix. I saw something about expected downloads which weren't there, and also something about an unexpected link set in the NIV.
However, your situation isn't fully clear, so for clarification:

When you try to start the app normally, it crashes (on its own).

You are able to load to a blank layout.

Are both of those fully true? Have you restarted the computer with the same results? What does Logos normally open to with your settings? (for example, I open to "most recent layout: local".). If you normally open to a layout, have you tried using a different layout? Building a simple one from scratch and opening to it?

Thanks for checking JT.

Yes: both points are true. Logos crashes (disappears from the screen, and is not shown as a runnig app in the Windows Task Manager). But it does start to a blank layout (by holding down Ctrl). I can then I can load any saved layout and it works fine.

This has been happening for several days. I've restarted the PC several times.

Will try the patch Tuesday updates and report back as to whether that helps.

Thanks again.

Allen Browne

RESOLVED.

The problem wasn't solved by the .NET updates.

But it has stopped crashing after Logos downloaded version 27.2.21.

I've restarted 3-4 times now, and it looks reliable.

Thank you, community, for checking the logs and making suggetions. Appreciate you having our back.

Allen Browne

NOT RESOLVED: my Logos crashes are back.

Logosd 27.2.21 loads successfully if I set “At Startup Open To: Blank Layout” (under program settings). I can then open my preferred layout, and continue as normal.

If the At Startup Open To is set to “Most recent layout: Local” then I see the splash screen, the synching notification, the main window opens briefly and then disappears. Then I don’t have Logos on screen, and it’s not listed as a running app in the Windows Task Manager.

That may be a hint that the crash has to do with the timing of the attempt to load my layout?

The layout isn't particularly complex (screenshot below, with logs).

The laptop is pretty standard:Dell G7 (17 7790), i7 9750H, 32 GB RAM. 2 x SSDs (Logos is on with 1TB free). All updates for Windows, Intel, and Dell applied (no betas). The crashes occur even with all external devices unplugged (mouse, keyboard, 2nd screen, audio DAC).

Startup list is minimal: drivers for Logitech mouse &keyboard, FiFO audio, Intel graphics, and Microsoft Defender. (Disabled: Terminal, Cortana, Phone Link, and OneNoteM.)

Today's Logs:

7103.LogosLogs_AllenBrowne_2023-08-12.zip

My normal layout looks like this:

Allen Browne

Logos Bible Software no longer opens on my PC.

The 27.3 update seems to have resolved this issue. I'm able to start directly to my normal layout today.

Thank you to the Logos team. Bug hunting is not always easy, but I knew you could do it. :-)

Appreciated.

Don Jenkins

Thank you Logos. Mine is now fixed too. This is the first issue I've had in a long, long time. Very happy with the software in more ways than I can count