Crash When Opening Logos
Hello,
I am running OS X 10.10.5 (14F27). For the last several days, when I click the logos icon in the doc or in the application folder, the application does not open. I am not aware of any updates in the last week, though I do have automatic updates turned on. Attached is the log file detailing my issues. Please note, when I exported the log file using Logos Logging Utility, it seems to have grabbed all logs on my computer dating back about a week. I deleted everything prior to 26 Sep, but as you will see in the log, there are still several instances of the crash over the last several days. The repeating error I see deals with a failure to load the framework.
Thanks for your help!
Comments
-
Hi Michael - and welcome to the forums
Sorry to hear you are having problems.
We would really need to see some Logos logs.
Please enable diagnostic logging (if not already) and upload logs in a reply to this thread after a failed start attempt. Details at https://www.logos.com/support/logos6/mac/report-problem
Do you know what version of Logos 6 software you are running?
Graham
0 -
Michael Scott said:
Attached is the log file detailing my issues. Please note, when I exported the log file using Logos Logging Utility, it seems to have grabbed all logs on my computer dating back about a week.
I think you likely have the problem several users have experienced. If you can try to grab new logs it would be appreciated by the developers. Either way, once you have tried that you should download and install the newest engine. See the link in my signature line. Let us know how that goes.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Graham,
The log file attached in my original post was the result of following the steps at the 'report-problem' link. I tried it again just now to be sure I did everything right; same results. If you search the log file for "logos" the error appears in several instances.
According to the Logging Utility, I am running 6.6.0.56.
Thanks, Mike
0 -
Hi Mike
Michael Scott said:The log file attached in my original post was the result of following the steps at the 'report-problem' link
Apologies - I would have expected to see more (and Logos-specific) logs after going through the steps at that link.
I would go ahead with Alabama's suggestion above and download the latest engine and see if that works
Graham
0 -
Graham,
No worries, I was confused about the odd results as well! [:)]
I was just working to re-install the engine, which did solve the problem, and just to be sure, the engine problem wasn't somehow causing a problem with the logging utility, I tried the logger one more time, with the same results. Weird. Anyways; original problem solved, and logos works again. Thank you both for your help!
Mike
0 -
Michael Scott said:
Anyways; original problem solved, and logos works again
Glad its working - but it would be helpful if someone could help work out why you aren't getting full logs (they might be needed if you get problems in the future)
I don't use a Mac so don't have anything to add as to why full logs might not being produced.
0 -
If it is any help...
Running the OS X beta and the Logos beta I get this from the Archive button...
tootle pip
Mike
Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS
0 -
Michael Scott said:
According to the Logging Utility, I am running 6.6.0.56.
Did you enable logging via the Logging Utility prior to the crash?
0 -
All,
Thanks for the continued desire to solve the logging problem! Let me walk thru the steps I was taking:
- Logos 6 was not running (verified no processes running in Activity Monitor)
- Open Logos Logging Utility
- Select "Logging Enabled" radio button
- Click on the Logos 6 icon to attempt to open the application.
- Application immediately fails to run
- In logging utility, click "Archive Logs" and save the Zip file to my hard drive.
- As a measure for validating what was exported into the logs I open the zip file (which in all cases has contained only one file "console message.log") and changed the file extension to .txt; open the txt file in text editor to ensure I wasn't somehow mixing general logs with the logos logs.
- Changed the file extension back to .log and uploaded to the forum
Is there a step I'm missing?? Thanks again for the help!
0 -
Michael Scott said:
Is there a step I'm missing??
Not that I can see. Possibly Logos logging was never activated because the application made no attempt to start. At this point, i would fall back on Bama's recommendation and manually install a fresh L6 engine. See the Install link in my signature.
0 -
I reinstalled the engine and the software worked great for about 24 hours, but I'm back to (almost) the same problem. The application now opens and goes through the loading/synchronizing steps, opens the Logos application window, and then immediately minimizes and shuts down.
I am still getting the same results with the logging tool. I took a screen capture video of my problem and loaded it to a dropbox folder along with both sets of logs that I took this morning.
Thanks for your help!
Mike
0 -
Michael Scott said:
Thanks for your help!
Thanks for the screen shot. I think you need to contact customer service directly. I don't believe your issue is the same thing that others are experiencing. I wonder if you have a conflict with some other software... Let us know what they find. Curious minds want to know! [:s]
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Hi Michael,
Delete the application file in the Applications folder and replace it with a fresh copy from your order that brought you Logos 6.
Everyone: What Michael Scott is experiencing seems to be an update problem that has cropped up. It seems to be happening to people that have skipped 6.6 and jumped to 6.6 SR-1. I was able to replicate the behavior and Martin is looking into it.
If Logos 6 refuses to open after the update, and when you click "archive logs" from the logging utility* a .txt file is created rather than a zipped folder, replace the application file with a new.
0
