Logos 4.0a SR-1 & SR-2 Release Notes
Comments
-
MarkSwaim said:
Someone suggested not installing an update in the future until a few days have passed. Is this suggestion wise? It would mean once a permanent fix is given to this problem, we should turn off automatic update? Can anyone comment?
If nobody installed updates until a few days after they'd been released, then there would be no guinea pigs to find out if there were problems in them. Some people are by nature early adopters and don't mind dealing with the consequences if something goes wrong. Other people by nature prefer to play it safe. I say go with your gut on this one. No one answer will be right for everyone. It depends on how mission-critical your use of Logos is, how much spare time you have, how far developed you are in the virtue of patience, etc.
0 -
Just for interest sake. I have two computers running Logos4 one is is using 4a (build .4533), and the other up to date with sr2 and the newly updated resources.
Both are acting the same way (I have lost some of my interlinears, and biblical people, places and things, etc.).
This means that the problems probably aren't related to either SR-2 or the recent updates, but some other preexisting problem.
Again to be clear. On my system that is still on 4a with the old resources (that was working fine several days ago as I definitely used my NKJV interlinear and biblical people function), I am now having the same problems as described in this thread.
0 -
Greg Gray said:
Again to be clear. On my system that is still on 4a with the old resources (that was working fine several days ago as I definitely used my NKJV interlinear and biblical people function), I am now having the same problems as described in this thread.
Very interesting!
Would you mind reporting this in this thread as well:
http://community.logos.com/forums/t/8544.aspx
Curiouser and curiouser.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Greg Gray said:
Again to be clear. On my system that is still on 4a with the old resources (that was working fine several days ago as I definitely used my NKJV interlinear and biblical people function), I am now having the same problems as described in this thread.
Interesting Greg, so RC 1&2 might not be the underlying cause of this bug but something else....
Boy I sure hope Logos explains what happened after they fix it, this is sure making me curious.
Prov. 15:23
0 -
Dave Hooton mentioned SQLite problems earlier in this thread. I reported a crashing bug with an SQLiteException error in my log file a couple of days ago and Bradley Grainger (Logos developer) said he'd been able to reproduce it and he fixed it. But he said that on Dec 31 after SR-2 had been released, so it appears that this bug fix has not been built into a new release yet and we'll have to wait until whenever they do SR-3 (hopefully sometime early next week) for a fix. I wonder if the bug Bradley found and fixed is the one responsible for all the problems people have been seeing? I wonder why these problems only started showing up on Dec 31? (I can't guarantee that mine wasn't there earlier; I'd simply never tried that scenario before.)
Anyway, hope that helps!
0 -
Wow, amazing, it works!
Looks like a developer hardcoded the Dec 31 midnight date/time somewhere.
Hopefully this will be a relatively easy fix for Team Logos since the user community already did a lot of troubleshooting for them.
Thanks all!
Peter
0 -
PeterLi said:
Wow, amazing, it works!
Peter, please quote the context of your reply because I've no idea what "works".
Dave
===Windows 11 & Android 13
0 -
Rosie Perera said:
I reported a crashing bug with an SQLiteException error in my log file a couple of days ago and Bradley Grainger (Logos developer) said he'd been able to reproduce it and he fixed it. But he said that on Dec 31 after SR-2 had been released,
I'd been wondering whether there is a connection between SQLite errors discovered and the resource issues. One log had many recoverable errors on resources during re-indexing. How many might appear where people did not receive an unrecoverable error during re-indexing or might be waiting to be discovered during indexing??
Dave
===Windows 11 & Android 13
0 -
Kevin Becker said:Greg Gray said:
Again to be clear. On my system that is still on 4a with the old resources (that was working fine several days ago as I definitely used my NKJV interlinear and biblical people function), I am now having the same problems as described in this thread.
Interesting Greg, so RC 1&2 might not be the underlying cause of this bug but something else....
Boy I sure hope Logos explains what happened after they fix it, this is sure making me curious.
As a clarification, Greg's 4.0a (4533) is RC2. So SR-1 (4737) and SR-2 (4767) may not be the underlying cause!
Dave
===Windows 11 & Android 13
0 -
Damian,
Yes, been there done that too... LSS the only viable solution I found for ME and my situation for a FRESH and FULLY FUNCTIONAL (UPATE) install was my previous instructions which for some could also include removal of the 'install folder' IF Revouninstaller does not get it. In my case this folder was ALSO included in the REVO option and still there was directories and folders left behind outside of the INSTALL folder that would not allow a clean install...
EVEN LSS, remove the variables (wipe everything off that says or gives a linger of Logos or Libronix) and then a fresh install without ANY residual variables (as I mentioned) brought me toa 9.20gb full download and completed successfully install. The rest of the issues listed here and all over the FORUMS, I will let folks beta test and work out and can wait until SR-448 (I have been submitting the copying and pasting 'citations' issues I have had continually, but I can copy and paste that stuff until it gets fixed....), again, I wanted WORKING, FUNCTIONAL library, and for me, with no response from support, anxiously waiting around in forums and being in bondage to my email without my resource... this is what worked... thanks for clarifying.... hope it helped.... and don't see me coming back here (forums) and will be unsubscribing.... [8-|]
0 -
Richard DeRuiter said:Derek R. Iannelli-Smith said:
Richard it appears that others see that I have sinned against you. It was not my intention, and I do ask your forgiveness.
Your forgiven.
For any way any of my responses have tended to diminished you or your concerns, I also ask your forgiveness.
Can I just say that both of you are examples of Christ-like behavior in this?
I'm reminded of my own shortcomings in this area...God bless you both...
bob
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
Richard DeRuiter said:
Curiouser and curiouser.
The issues have been acknowledged by Logos - see http://community.logos.com/forums/t/8660.aspx
Dave
===Windows 11 & Android 13
0 -
Rosie Perera said:
Dave Hooton mentioned SQLite problems earlier in this thread. I reported a crashing bug with an SQLiteException error in my log file a couple of days ago and Bradley Grainger (Logos developer) said he'd been able to reproduce it and he fixed it. But he said that on Dec 31 after SR-2 had been released, so it appears that this bug fix has not been built into a new release yet and we'll have to wait until whenever they do SR-3 (hopefully sometime early next week) for a fix. I wonder if the bug Bradley found and fixed is the one responsible for all the problems people have been seeing? I wonder why these problems only started showing up on Dec 31? (I can't guarantee that mine wasn't there earlier; I'd simply never tried that scenario before.)
The SQLiteException I fixed probably won't make it into SR-3 because it doesn't fix an extremely common problem (it's been there for months, and you're the first one to report it), and we want to keep the bar high for commits that are merged to the SR branch. However, it will be in 4.0b Beta 1, which should begin testing this week.
0 -
Bradley Grainger said:
The SQLiteException I fixed probably won't make it into SR-3 because it doesn't fix an extremely common problem (it's been there for months, and you're the first one to report it), and we want to keep the bar high for commits that are merged to the SR branch. However, it will be in 4.0b Beta 1, which should begin testing this week.
Thanks for that explanation. I can wait, because obviously the thing I was doing when I got the SQLiteException wasn't something I really need to be doing.
BTW, any hints about what new features might be in 4.0b? Anything from the "coming soon" list? [:)]
Also did you notice the two blocking bugs that MikeM wanted to bring to someone's attention as being really in the way of getting productive work done? See his post here with links to them. It wasn't in a bug-report post, and no Logos employee has weighed in on those other two bug reports he was linking to yet, so I just wanted to make sure they don't get overlooked.
Also: Thank you for finding a workaround for the expired beta licenses problem, even on a weekend from home! You are to be commended, though I do hope you're not taking away from your much-deserved Sabbath break. Blessings to you!
0
