BUG: "Logos Quit Unexpectedly" warning (5.2a b5 - MAC OSX 10.9.2)
Seemingly every time Logos restarts, I receive the following warning. I did not, however, receive this warning after I grabbed the crash logs... [My zip file wouldn't upload, so I just attached the logos.log file]
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!
Comments
-
This is a regular occurrence for me as well.
Bob Deacon
Ipad Air 2 (ios 9.7 (0014)
Windows 11 inside edition
Samsung S23
0 -
That must be the new Logos Splash screen! I get it too even with the stable SR version. (See here: http://community.logos.com/forums/t/81947.aspx)
Is there any way of turning the new splash screen off? [;)]
Every blessing
Alan
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
alabama24 said:
Seemingly every time Logos restarts, I receive the following warning. I did not, however, receive this warning after I grabbed the crash logs... [My zip file wouldn't upload, so I just attached the logos.log file]
I truly thought this had been fixed, but it is now an every start occurrence. Logos, can we get some input on this as it is becoming quite irritating?
In another thread this morning, Dave reminded me of this post 568928.aspx by Tom Philpot
0 -
I think this should be fixed now. Can you repost here if it starts happening again?
Mobile Development Team Lead
0 -
OK, so it looks like this might be a new issue with Mavericks. We're investigating and should have a fix post 5.2a Beta 6
Mobile Development Team Lead
0 -
FWIW The error report on re-opening doesn't seem to happen if I sync before closing app. It only seems to happen if the sync runs during the exit of a multi-panel layout. When that happens the closing sequence is: main panel closes, sync message appears then finally secondary panel closes. After the sequence any reopening, whether or not the computer has been shut down or not, results in the error report dialog box appearing.
iMac Retina 5K, 27": 3.6GHz 8-Core Intel Core i9; 16GB RAM;MacOS 10.15.5; 1TB SSD; Logos 8
MacBook Air 13.3": 1.8GHz; 4GB RAM; MacOS 10.13.6; 256GB SSD; Logos 8
iPad Pro 32GB WiFi iOS 13.5.1
iPhone 8+ 64GB iOS 13.5.1
0 -
Tom Philpot (Logos) said:
OK, so it looks like this might be a new issue with Mavericks. We're investigating and should have a fix post 5.2a Beta 6
This should be fixed in 5.2a RC 1.
0 -
This is the same problem that I am having with L5 Mac. I am looking forward to the update and the problem fixed.
Thanks
0 -
Any update on this?
0 -
This is fixed in 5.2a, which is now available for Stable users. If you have the app running, you can enter "update now" in the Command Box to download the update. Here is the forum post.
0 -
Tom and Dylan:
I continue to have crashes/force quits, as well as these warning messages when I've not (knowingly) had any. I've had them on the SR that was supposed to have fixed them, I've had them on the RC, and I've had them on 5.2a. It's possible I have fewer than before, but I'm not sure as there's been quite a few weeks lately when I've hardly opened Logos. Could you check that all fixes were properly implemented for 10.6?
Also, if I remember correctly, two or three of the SR crashes or force quits took place in the background with both Logos and the computer fairly newly opened and no sleep involved.
Yes, I know, you need logs. Some day I'll take the time. For now, I just wanted you to know.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
Could you check that all fixes were properly implemented for 10.6?
This particular issue was introduced by Mavericks, so this case wouldn't affect you on 10.6. Mavericks threw in some extra files which Logos thought were crash reports. Those files aren't created in 10.6.
fgh said:Yes, I know, you need logs. Some day I'll take the time. For now, I just wanted you to know.
Since your issues aren't related to this particular case, we'd need the logs to have any idea what happened. [:(] They should also probably get a new thread.
0 -
