Logos 5.1.0.0950 Crashing
I have emailed support several times about this, and Logos essentially ruined my weekend of sermonizing with the 5.1.0.0950 update.
The long-and-short: 5.1.0.0950 crashes. I have spent way too much of my time trying to figure out what the problem is, and it seems to be related to Personal Books. I did a fresh install, and a fresh download of all resources, and Logos ran fine until I rebuilt a Personal Book ... then it started crashing. So I did another fresh download of all resources, and Logos ran fine for about 24 hours. Now it is crashing again, even though I have not rebuilt any personal books.
Logos is mission-critical for my ministry, and it would help me to know that someone at Logos is aware of these issues and is working on them. So far, I have only received automated responses and "canned" answers from unhelpful support staff who didn't even read the emails I sent.
I am NOT attaching my logs to this post, although I do have the Logos Logging Utility. I have already emailed them more than once, and no one seems to be paying attention to that fact.
Someone, please help!
Comments
-
You have cross-posted.
I feel your pain. I can only suggest what I said in the other thread you posted in:
[quote user=""]Mac or Windows? You might as well detail your experience and submit your crash log here. Lots of expert users and even devs themselves seem to read the threads.
Since this thread has been opened by you specifically for this purpose, you may want to discontinue your post in the other thread, or delete it if you can.
0 -
Some additional info:
After a reboot, Logos runs without crashing until I run Audacity (the free audio editing software). If I run Audacity and then launch Logos, Logos crashes. I didn't think it would be possible for two packages on a Unix-based OS to conflict unless they are using a shared library or something. I'm only speculating, so I'll leave the details to the developers at Logos.
0 -
For good measure, I would suggest you submit the crash-log here. I think that would really help.
0 -
Ed said:
After a reboot, Logos runs without crashing until I run Audacity (the free audio editing software).
That is significant and such conflicts are not unknown. Logos should be able to confirm that is the cause (it doesn't affect me on Windows).
Dave
===Windows 11 & Android 13
0 -
Audacity is not the culprit. Rebooted and launched Logos ... no problem. Waited 2 hours, launched Logos and it crashed. Hadn't run anything other than MS Word and Mac Mail.
I am using Time Machine, iDrive Backup, but iDrive hasn't run yet. I also use a MOTU Audio Express (MagicJack crashes because of the audio interface, but Logos hasn't had any trouble with it since V4).
Anyway, still waiting for some assistance.
0 -
Ed, follow the link in this post and run install the code to run diagnostic logs and then upload them. There are persons on this forum who are able to read them and hopefully help you solve the problem. http://wiki.logos.com/Diagnostic_Logging#Mac
Mission: To serve God as He desires.
0 -
Hi, Lynden,
Thank you for the help, but I have already sent the logs to Logos customer support staff. Before full-time ministry, I was actually a software engineer and Unix admin, so I can read the logs, as well. But I think I will need Logos development staff to actually solve the problem.
I am truly grateful for your suggestion ... thank you!
0 -
Hope you get sorted out soon.
Mission: To serve God as He desires.
0 -
Having messed around with audio interfaces before, I'm just making a stab in the dark here:
Have you downloaded the latest driver for the AE (Version 1.6.57985) or updated the firmware (Version 1.04)? Might be worth a shot. (Disclaimer: your gear, your risk.)
0 -
Would you mind sending your logs to logosfeedback@logos.com ? That way, I can route the to Development as soon as I receive them. Thank you!
0 -
Lee said:
Having messed around with audio interfaces before, I'm just making a stab in the dark here:
Have you downloaded the latest driver for the AE (Version 1.6.57985) or updated the firmware (Version 1.04)? Might be worth a shot. (Disclaimer: your gear, your risk.)
Good advice ... I updated the driver and firmware a while back, but I am slightly out of date. I'll update and report if necessary.
0 -
Kelly Flones said:
Would you mind sending your logs to logosfeedback@logos.com ? That way, I can route the to Development as soon as I receive them. Thank you!
FYI ... I have recreated the crash, and re-emailed fresh logs.
0 -
Just an FYI ...
Logos is still crashing even after updating the audio drivers and firmware. In fact, Logos crashes even when the audio interface isn't connected, fresh reboot and all.
The strange thing is, immediately after a reboot, Logos will run once or twice just fine. But after the first or second launch--which is to say, after 5-10 minutes--Logos begins crashing again.
I realize that this is a "weird one," and the Logos development staff has my pity.
0 -
Ed said:
The strange thing is, immediately after a reboot, Logos will run once or twice just fine. But after the first or second launch--which is to say, after 5-10 minutes--Logos begins crashing again.
Wondering if Logos is being opened and closed a lot ? Personally launch Logos and leave open for many days.
Wonder if logs have networking errors ? If network is not stable, may want to consider offline use. On a MacBook Air, personally disable WiFi then launch Logos 5 for a friend. When want to update Logos, then close application, enable WiFi, and launch Logos, which takes awhile to sync items covering many days, followed by updating resources and software.
Keep Smiling [:)]
0 -
Wondering if Logos is being opened and closed a lot ? Personally launch Logos and leave open for many days.
Wonder if logs have networking errors ? If network is not stable, may want to consider offline use. On a MacBook Air, personally disable WiFi then launch Logos 5 for a friend. When want to update Logos, then close application, enable WiFi, and launch Logos, which takes awhile to sync items covering many days, followed by updating resources and software.
Keep Smiling
Very good thoughts, but network is very stable: wired Ethernet with wifi disabled...also tried with wifi and with Ethernet disconnected. I tried offline use yesterday to no avail.
I should mention that I have been using Logos since version 1 (yes, the old 16-bit Version 1 on Windows 3.1), then Libronix 3, Logos 4, and now Logos 5, and the problems I'm experiencing didn't happen until the 5.1.0.0950 update. In other words, Logos 5 has been working fine until the 5.1.0.0950 update (hence, probably nothing wrong with my computer, software, or peripherals). And what's worse is that I can't even roll back to the previous version of Logos 5 because apparently my cloud resources at Logos have been upgraded and refuse to work with the previous version. [sigh]
0 -
Ed said:
And what's worse is that I can't even roll back to the previous version of Logos 5 because apparently my cloud resources at Logos have been upgraded and refuse to work with the previous version. [sigh]
Technically a bit challenging to roll back. Once a newer version of Logos has launched, local Logos SQLite database files are upgraded so older Logos application will crash immediately after checking database version. If want to keep using an older version, automatic updates may be problematic.
Personally have Logos 5.1 and 4.6c installed on a computer by using two user accounts (with two copies of resource files). Due to known sync issues between 5.1 and 4.6 (e.g. series customization), Logos 4.6c installation is only used offline. Thankfully can replace license data, then scan resources to expand Logos 4.6c library plus manually install software updates.
Wiki => http://wiki.logos.com/The_Logos_5_Beta_Program with RSS feeds that have links to download some older releases. Wiki also has => http://wiki.logos.com/Quick_Installation_onto_Multiple_Macs#Copy_Logos_Resources_to_Mac_OS_X and => http://wiki.logos.com/Quick_Installation_onto_multiple_computers
Keep Smiling [:)]
0 -
I wanted to mention that I found another thread where the user's log seems to report the same error in my logs:
http://community.logos.com/forums/p/67084/467462.aspx
Perhaps my crashes are related?
0 -
Ed said:
I wanted to mention that I found another thread where the user's log seems to report the same error in my logs:
http://community.logos.com/forums/p/67084/467462.aspx
Perhaps my crashes are related?
I followed the workaround instructions from Seth Copeland at the bottom of the above thread, and Logos seems to be behaving now. I have started/restarted the app, rebuilt a personal book, launched various other software, and successfully launched Logos three times without a crash. I am cautiously optimistic that the problem is resolved. And if indeed the problem is resolved, it might suggest a problem in preferences migration.
0
said: