Baruch in NAB:RE crashes Logos 6
I've been going through a two-year reading plan of the New American Bible. I just finished Lamentations. Trying to advance to Baruch, the program crashes. This has happened at least three times in a row now, regardless if I open the Bible via the reading plan or library.
Logs attached.4251.Logos.log7888.LogosCrash.txt14782.LogosError.log6327.LogosError-2.log
Comments
-
This is the same crash reported here: https://community.logos.com/forums/t/126049.aspx
It will be fixed in 6.12. As a workaround, turn off both the Addressee and Speaker Labels visual filters in NAB:RE.
0 -
This is the same crash reported here: https://community.logos.com/forums/t/126049.aspx
It will be fixed in 6.12. As a workaround, turn off both the Addressee and Speaker Labels visual filters in NAB:RE.
Thanks, Bradley; that's doable.
It's funny that I've been reading in the NAB since 6.11 came out with no problems in either Jeremiah or Lamentations, but Logos just lost it when it came to Baruch. [:O]
0 -
It will be fixed in 6.12. As a workaround, turn off both the Addressee and Speaker Labels visual filters in NAB:RE.
I think you need to fix it rather more urgently. It crashed even just trying to open the Bible to get to the visual filter settings. Ultimately I had to open a different Bible, move to a different text, then switch to the NABRE in parallel. That's too much for the user to have to do to be able to use the product again.
0 -
Sean said:
It crashed even just trying to open the Bible to get to the visual filter settings.
Probably too late to check but from what you say above I would have thought you could have opened NABRE to somewhere other than Baruch and then turned off the filters
0 -
Graham Criddle said:
Probably too late to check but from what you say above I would have thought you could have opened NABRE to somewhere other than Baruch and then turned off the filters
Yes, but clicking on it from the library opened it where I was last, which was Baruch.
0 -
The Command Box would allow you to get around that - just type something like Open NABRE to Gen 1
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Bradley already indicated that it would be fixed in the next release, I believe.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:
Bradley already indicated that it would be fixed in the next release, I believe.
Yes, and I'm telling Bradley that if 6.12 is going to be a long time in coming out, they need to fix the bug before then.
New releases should not break the product. If they do, they should be patched ASAP. If that is not possible, then it should be optional to update to new versions when released (as in, let me download newly purchased books but not the update if I don't want to; this is yet another reason to restore the selective download capability enjoyed in Libronix).
0 -
Sean said:
Yes, and I'm telling Bradley that if 6.12 is going to be a long time in coming out, they need to fix the bug before then.
They are on a 6 week development and release cycle which a bug like this would normally not qualify to break as there is a simple workaround. I believe that the current beta is 4 which implies about 2 weeks before 6.12 goes gold. To ask for an emergency release is to ask for Quality Assurance problems as it breaks the orderly release of code to the final build.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
MJ. Smith said:Sean said:
Yes, and I'm telling Bradley that if 6.12 is going to be a long time in coming out, they need to fix the bug before then.
They are on a 6 week development and release cycle which a bug like this would normally not qualify to break as there is a simple workaround. I believe that the current beta is 4 which implies about 2 weeks before 6.12 goes gold.
Faithlife updates wiki pages => Logos 6 Release Notes and => Logos 6 Beta Release Notes
Guessing Mon 30 May 2016 for 6.12 stable release along with two 6.12 release candidates next week.
Keep Smiling [:)]
0 -
The thing is this was a known bug that cost me about 30 minutes on an extremely busy day; it wasn't a small cost in context. FaithLife could have pushed out a fix in the last week or at least sent a notice to people who own the resource to watch out for this problem. (Seriously. They could do that. They certainly send out enough marketing emails during the course of a day.) I shouldn't have to constantly comb the forums for potential upcoming hazards.
If Bradley et al. want to defend this practice, they are welcome to, and I'm sure they're capable of doing so on their own.
0 -
Sean said:
If Bradley et al. want to defend this practice, they are welcome to, and I'm sure they're capable of doing so on their own.
I am sure they can - as could most IT staff. As a retiree from IT I thought you might be interested in when and why the bug fix was coming. Sorry it wasn't helpful.
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0
