To immediately update to the current beta enter the Update Now command. Otherwise, the app will automatically update the next time it's scheduled to check for updates.
Release Notes
Mac
Windows
My windows 10 surface pro 6 is NOT updating to beta 4.
Bob
My windows 10 surface pro 6 is NOT updating to beta 4. Bob
Bob,
Can we get logs? I'm not sure why it's not updating for you.
I tried numerous times to "update now" only to be told "no updates available". I looked at your last post and followed the instructions to enable logging. I restarted L8 and viola! beta 4! Not sure what when or how but I do now have beta 4.
Had you restarted Logos before? Your computer?
JT, all is good! Not sure why or how. I have never had a problem updating before but I am good now! Thank you!
JT, all is good!
Yes, I understood that... and glad [:)]
Not sure why or how.
That was what I was trying to get at. "Enabling Logging" would not have fixed the issue... but restarting the app (and/or computer) might. If you are in a similar pickle in the future, make sure to try both.
Will do, thanks again.
Really unstable for me. Just updated to the above, and whenever I switch to Romans 13 in NIV84, Logos goes into a spinny cursor for a few seconds then crashes. 100% reproducible. Will try restarting.
Win 7x64 Pro.
Really unstable for me. Just updated to the above, and whenever I switch to Romans 13 in NIV84, Logos goes into a spinny cursor for a few seconds then crashes. 100% reproducible.
Sounds like the bug affecting link sets. In my experience, having resources linked and choosing to navigate outside the current book results in a short hang and then crash (I'm on macOS). Try unlinking your resources to avoid the crash. IMO, this is a really serious bug that needs to have top priority.
According to the normal release schedule, 8.9 ships to stable on the 11th, but this bug HAS to be addressed before going golden!
Sounds like the bug affecting link sets.
Yes, I'd tried to report it ... but gotten little reaction.
Really unstable for me. Just updated to the above, and whenever I switch to Romans 13 in NIV84, Logos goes into a spinny cursor for a few seconds then crashes. 100% reproducible. Sounds like the bug affecting link sets. In my experience, having resources linked and choosing to navigate outside the current book results in a short hang and then crash (I'm on macOS). Try unlinking your resources to avoid the crash. IMO, this is a really serious bug that needs to have top priority. According to the normal release schedule, 8.9 ships to stable on the 11th, but this bug HAS to be addressed before going golden!
Removing all link sets seems to have circumvented the issue, allowing me to restore functionality.
One of my linked resources was a serial association between Lexham Hebrew Interlinear and NA27, so maybe the navigating to a different resource during a link update was indeed the issue. I'm pretty sure the NIV84 was located somewhere in the OT when I attempted to navigate to Romans, and the NIV84 is in a linked set with the LHI\NA27.
However, this issue, in its current form, has mostly likely arisen with 8.9b4 as I was using the same Layout for quite a while without any crashes, and had regularly been navigating between OT & NT with that same Link Set in place, so maybe it's a separate, but clearly related issue?
We are aware of the issue and investigating it.
As Ruben says, unlinking your resources will avoid the issue.
We are aware of the issue and investigating it. As Ruben says, unlinking your resources will avoid the issue.
Thanks Owen.
This has been fixed in 8.9 RC1.
On another note, my 8.9.0.0023 highligting has ceased working.
1. Restarted multiple times.
2. Rebooted.
3. Shut down other running copies of Logos (on other computers).
4. Repeated #1 & #2
5. Tried highlighting in various documents and documents types (I.E. Monographs, Bibles, etc.)
5. Tried keyboard shortcuts, highlighter panel, and the popup. No highlighting is working.
Note: I had sporadic episodes of highlighting acting strange before this. Could this be related to this update (??) Anyone else?
It would be better to start a new thread as FL believes this one to be resolved.
Thanks, MJ. I am not asking for assistance. Just sharing the issue in case anyone who cares might see it. This may or may not be the best place.
//==================
More info: The matter is Layout related and I have been able to reproduce it. Killing the layout and starting over fixes the issue.
