BUG: Faithlife Study Bible crashes Logos
I tried to open FSB and Logos crashed. Restarted and tried again and it crashed again. Did this multiple times.
Then I went to a different computer and it did the same thing. Perfectly repeatable, over and over.
I can no longer open FSB.
Here is a screenshot:
https://recordit.co/fiCUOLF2uO
I have "Send Feedback" set to ALL, so I would imagine it sends a report?
If I had to guess, I would say that it is trying to open it to whatever location I used last and for some reason that makes it crash. ???
What else could cause this to happen on two different computers, but apparently not affect everyone else?
Comments
-
-
Done. Thanks for the tip!
0 -
Done.
Where did you post the logs?
0 -
This gets more interesting.
So I tried a third computer (laptop) and did the following:
- Turned off wifi
- Opened Logos and successfully opened FSB (it was open to a sidebar on the Prophets).
- Moved FSB to the first page, just to be safe.
- Was able to open and close it repeatably.
- Turned on wifi. Synced laptop, then desktop, hoping it would fix the problem (did not work).
- Let Logos update from 23.0.23 to 23.0.30.
Now laptop crashes when trying to open FSB just like the other two.
0 -
0
-
It might be good for you to post logs. See my signature line below.
On that page, it says Step 1. Enable Logging . . .
But then all it says to do is to close Logos and then restart with the control key.
Does simply starting with the control key "enable logging"? Does it stay enabled? Or do I have to do this every time I start?
Thanks.
0 -
Does simply starting with the control key "enable logging"?
yes
Does it stay enabled?
no
do I have to do this every time I start?
there EDIT: is a script file on https://wiki.logos.com/Diagnostic_Logging /EDIT to permanently enable logging.
Many users (including myself) run Logos with logging enabled all the time, especially those who do beta versions.
Have joy in the Lord!
0 -
Does simply starting with the control key "enable logging"?
Yes it does
Does it stay enabled?
No - this method only enables it for that session
To enable it permanently, see the section in the article headed Logging problems installing Logos
0 -
I have attached them now.
I'm afraid the Logos.log file included is old - from November last year.
Can you try again and see if you get a current logfile?
0 -
0
-
Ok, this should be the correct one.
It is the correct log file and it shows the crash - but I'm afraid I can't work out the reason behind it.
I was wondering if you had an old version of the FSB but the log shows it is current.
I would recommend contacting Customer Service and seeing if they can help.
0 -
I sent it in. Still waiting to hear back from them.
I am also getting crashes related to reading plans, which I posted on another page.
Thanks everyone for your help.
0 -
I sent it in. Still waiting to hear back from them.
I am also getting crashes related to reading plans, which I posted on another page.
These are connected. Try using the Command box and opening to a random passage (not in the Reading Plan if possible) e.g. open fsb to Rev 12
Dave
===Windows 11 & Android 13
0 -
-
Try using the Command box and opening to a random passage (not in the Reading Plan if possible) e.g. open fsb to Rev 12
Sorry just now getting back. So I tried what you said, same crash.
Like I said above, a separate computer worked fine in 23.0.23 but once I updated to 23.0.30 it started doing the same thing. I tested 3 different computers. I cannot use FSB at all anymore.
0 -
-
When I deleted it and re downloaded it FSB worked and didn’t crash
0 -
Willy, did this work for you, as well?
Ali Pope | Logos Desktop and Mobile Program Manager
0 -
Sorry. No it did not. I tried blank layout. I tried deleting FSB both in Logos and in Windows. Still the same thing. 3 different computers. All crash when I try to open FSB.
I think this is the version number: 2023-02-17T19:53:47Z
Now, although I seem to be the only one with the FSB crash, Matt was able to replicate the layout crash I mentioned on another thread and they might be related. ??
No way for me to roll back to 23.0.23, huh? j/k
0 -
I think this is the version number: 2023-02-17T19:53:47Z
I have the same version, and Graham seemed to indicate you were up to date, so I think you are good... except for the part where it crashes. [:s]
I think the next option might be for you to rebuild your index... but only do so when you have an excess of time.
0 -
This still persists in 27.1, even when I use a new computer.
I cannot use Faithlife Study Bible at all. It crashes my computer every time I try to open it.
Can I really be the only one this bug affects?
0 -
This still persists in 27.1, even when I use a new computer.
I cannot use Faithlife Study Bible at all. It crashes my computer every time I try to open it.
Can I really be the only one this bug affects?
It has to be the environment or Visual Filters it uses.
- Start Logos with CTRL key held (this will generate logs) and work in the blank layout.
- In Docs menu search for Reading Plan and delete any for the FSB.
- Open FSB
- if Logos crashes, save the logs and restart with CTRL key
- In Docs menu delete any Visual Filter for FSB.
- If Logos still crashes, upload the logs before you restart.
Your deleted docs can be recovered from https://documents.logos.com/
Dave
===Windows 11 & Android 13
0 -
Wow! That did the trick. Thanks Dave.
I had created several group reading plans that had FSB as part of the reading. I deleted them all and now I can open FSB. Oh I missed that guy, almost forgot what he looked like!
I guess this is still a bug that should be addressed?
Either way, I'm glad it's working now.
And thanks to everyone else who gave some input. [:)]
0 -
I had created several group reading plans that had FSB as part of the reading. I deleted them all and now I can open FSB. Oh I missed that guy, almost forgot what he looked like!
I guess this is still a bug that should be addressed?
Recover one Plan for FSB and see how it goes.
Dave
===Windows 11 & Android 13
0
