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
Comments
- When you try to start the app normally, it crashes (on its own).
- You are able to load to a blank layout.
- When you try to start the app normally, it crashes (on its own).
- You are able to load to a blank layout.
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?
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.
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:
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?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!
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:
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.
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:
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.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!
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.