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.
Comments
-
Allen Browne said:
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.
0 -
Rosie Perera said:
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.
0 -
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?
0 -
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.
0 -
Rosie Perera said:
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.
0 -
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?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Allen Browne said:
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!0 -
Microsoft updated the .NET Framework today. The update is preventing Logos from opening on my computer as well. I am running Windows 11 Pro.
0 -
I ran the setup for today's version update, and that fixed the problem for me. Good luck!
0 -
Just for reference, I was experiencing the same thing that Allen was describing but today's update seems to have fixed the issue.
Using adventure and community to challenge young people to continually say "yes" to God
0 -
JT (alabama24) said:
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.
0 -
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.
0 -
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:
0 -
Allen Browne said:
Today's Logs:
This log shows you accessing NIV 2011 with no evidence of a layout and a normal termination of the app.
When the app crashes as indicated, you must zip and upload the folder of logs before restarting the app.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
When the app crashes as indicated, you must zip and upload the folder of logs before restarting the app.
Thanks, Dave. I'm using EnableLogging.js to toggle logging on/off, and I'm not sure if it's currently on or off.
The only file in the Logs folder that has the current date and time is LogosError.log, so I've attached that.
0 -
Allen Browne said:
Thanks, Dave. I'm using EnableLogging.js to toggle logging on/off, and I'm not sure if it's currently on or off.
The only file in the Logs folder that has the current date and time is LogosError.log, so I've attached that.
Just run (double-click) Enablelogging.js and it will confirm that logging is enabled.
I need a zipped folder of logs after a crash and before you restart (selecting files is not sufficient).
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Just run (double-click) Enablelogging.js and it will confirm that logging is enabled.
I need a zipped folder of logs after a crash and before you restart (selecting files is not sufficient).
Thanks for your help, and sorry the delay.
When I double-click EnableLogging.js I see a security warning but no report of whether logging is on or off. So I've uploaded the logs twice, running the js in between.
6278.LogosLogs_AllenBrowne_2023-08-15a.zip
7041.LogosLogs_AllenBrowne_2023-08-15b.zip
Both times immediately after running the javascript, Logos opened successfully to a blank screen (even though I've set "At Startup Open to" to "Most recent layout-local." So I closed it and it crashed next time. The logs are from after each crash.
0 -
Allen Browne said:
When I double-click EnableLogging.js I see a security warning but no report of whether logging is on or off. So I've uploaded the logs twice, running the js in between.
OK, I can't run it anymore. And it has not worked for you, so enable logging by starting Logos with CTRL key held. After crashing, upload the logs before you restart.
EDIT: I got it to run via right-click and Open with Microsoft Windows Based Script Host.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
And it has not worked for you, so enable logging by starting Logos with CTRL key held. After crashing, upload the logs before you restart.
EDIT: I got it to run via right-click and Open with Microsoft Windows Based Script Host.
Thank you. Using right-click and open with wscript.exe, I got the dialog saying logging is on. Logs attached.
0755.LogosLogs_AllenBrowne_2023-08-15c.zip
(If I hold down Ctrl, it opens to a blank screen without crashing, so I don't think that would generate a log of a crash.)
0 -
Allen Browne said:
Thank you. Using right-click and open with wscript.exe, I got the dialog saying logging is on. Logs attached.
This shows a normal exit and not a crash! Are you uploading before you restart Logos?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
This shows a normal exit and not a crash! Are you uploading before you restart Logos?
Trying again:
0 -
Allen Browne said:
Trying again:
This shows the main window being opened at 7s (probably blank) and then panels being loaded: 2 for NIV 2011 and 1 for ESV Catholic and 2 others. The log finishes 1 second after that. Is that what you mean by "fails to open" in that you started Logos normally (without the CTRL key)?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
This shows the main window being opened at 7s (probably blank) and then panels being loaded: 2 for NIV 2011 and 1 for ESV Catholic and 2 others. The log finishes 1 second after that. Is that what you mean by "fails to open" in that you started Logos normally (without the CTRL key)?
What I see is the splash window, the synching dialog, then the main screen with a blank layout for maybe half a second. Then the blank Logos window disappears (crash to desktop), and Logos is not running (not listed as running in the Windows Task Manager).
My current workarouns is to set Program Settings | At Startup Open to: "Blank Layout." I can then load a layout, and use Logos as normal, so it's not a desperate problem at present.
0 -
Allen Browne said:
What I see is the splash window, the synching dialog, then the main screen with a blank layout for maybe half a second. Then the blank Logos window disappears (crash to desktop), and Logos is not running (not listed as running in the Windows Task Manager).
Thanks - that confirms we now have the correct log.
Allen Browne said:My current workarouns is to set Program Settings | At Startup Open to: "Blank Layout." I can then load a layout, and use Logos as normal, so it's not a desperate problem at present.
Hopefully, Faithlife will enter the discussion.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
Hopefully, Faithlife will enter the discussion.
Thanks, David. I have every hope they will track this down and address it in time.
0 -
Allen Browne said:
Thanks, David. I have every hope they will track this down and address it in time.
Allen, you are NOT alone! This bug showed up for me today. I opened yesterday and everything was fine. I tried today and an update downloaded. indexing paused because of low disk space. I moved some stuff off my main drive, tried to reopen & index Logos and got the flash, then starts to open last layout, then everything shuts down and goes away.
logs attached!3386.Logos (2).zip
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
David Thomas said:
Allen, you are NOT alone! ...
logs attached!3386.Logos (2).zip
Yup. Similar to Allen's last log
Dave
===Windows 11 & Android 13
0 -
Thanks for the information and the logs. We have had a number of reports about this problem, but we haven't yet been able to reproduce the bug. We are continuing to investigate.
It might be useful to know exactly what panels are in the layout you are opening at startup. It's too difficult to tell from the screenshot that was posted.
Andrew Batishko | Logos software developer
0 -
In my case, four panels are open: Library; BHW/WHM 4.2; Nestle-Aland Greek New Testament, 28th Edition; and New Revised Standard Version: Updated Edition.
0 -
Andrew Batishko said:
Thanks for the information and the logs. We have had a number of reports about this problem, but we haven't yet been able to reproduce the bug. We are continuing to investigate.
It might be useful to know exactly what panels are in the layout you are opening at startup. It's too difficult to tell from the screenshot that was posted.
Thansk for checking this out. My panels include:
- NIV, ESV (Catholic Ed) as panes on the left;
- NIV, Lexham Hebrew-English Interlinear, Greek NT 4th Rev Ed (internliean with Morphology), a notebook (Allen's Bible Notes) in the center pane.
- Info & Copy Bible tools in a narrow pane on the right.
The Bibles are all linked as set A, except fo the second copy of the NIV.
0 -
I am having the same issues. I set the layout to blank to see if that would help, but it does not. Attached are logs after attempting to open Logos without holding down the control button.
If I hold the control button, I can start logos with a blank screen. If I do not hold the control buttton down and try to open Logos with a blank layout saved as the default, the program still crashes.
0 -
Andrew Batishko said:
It might be useful to know exactly what panels are in the layout you are opening at startup
In my situation (logs above), here is what I'm trying to open.
ESV/ESV Audio Bible
Prayer List
Faithlife Study Bible/NIV Biblical Theology Study Bible/Moody Bible Commentary
NOTES:Journal notebook.
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0 -
Today's update seems to have resolved the issue for me
0 -
Allen Browne said:
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.
0 -
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
0 -
27.3 is THE fix! Thanks Logos Development team!!
Making Disciples! Logos Ecosystem = LogosMax on Microsoft Surface Pro 7 (Win11), Android app on tablet, FSB on iPhone & iPad mini, Proclaim (Proclaim Remote on Fire Tablet).
0
