Logos 5 crashes when selecting Library tab

I just upgraded to Logos 5 last night. Now, when I click on the
Library tab Logos 5 crashes. The issue can be reproduced by simply
launching the application and once the application is up, with the news
pages, clicking on the Library tab.

I have tried rebooting my PC and reindexing to no avail.

I have attached the Log File from after the reindexing.

Please advise.

Find more posts tagged with

Comments

Rich DeRuiter

I just upgraded to Logos 5 last night. Now, when I click on the
Library tab Logos 5 crashes. The issue can be reproduced by simply
launching the application and once the application is up, with the news
pages, clicking on the Library tab.

I have tried rebooting my PC and reindexing to no avail.

I have attached the Log File from after the reindexing.

Please advise.

Not seen this one before. It looks like one of your resources has corrupted, or non-existent data in the title data field. (Well, that's my guess after trying to figure out what the error is.)

I'm not sure what to suggest that you haven't already done. Rebuilding the index would be my suggestion, but you say you did that already. You did type rebuild index right (and not rebuild library index, or another similar command) into the command bar to rebuild your index, right?

If so, this is going to require a tech to fix.

Graham Criddle

Hi Geir

Others are seeing this - see http://community.logos.com/forums/p/58350/415366.aspx for a discussion

Graham

Geir Hunsbedt

https://community.logos.com/discussion/comment/415685#Comment_415685

Richard, yes, I did use 'rebuild index' in the command bar. I've also run the fonts check using LINQPad in another post, which came back successful.

The problem happens as soon as I left-click or right-click on the Library tab, with or without 'Use blank layout" on startup.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/415697#Comment_415697

Geir, Bradley from Logos knows about the problem already and I hope he will come with some advice. Before they find a solution, you can use a WORK-AROUND and work with Logos with just avoiding clicking the Library tab. You can open your Library however by right clicking on Library tab and opening it as a Floating Window

Geir Hunsbedt

https://community.logos.com/discussion/comment/415717#Comment_415717

Unfortunately, right-clicking causes the same problem. So, hopefully they find a solution soon.

Rich DeRuiter

https://community.logos.com/discussion/comment/415720#Comment_415720

Unfortunately, right-clicking causes the same problem. So, hopefully they find a solution soon.

Another work-around, if you know the name of the book you want to open, you can type it in the Logos command bar. For example, I just typed "word biblical luke" and it offered me 3 options: volumes 35a, 35b, and 35c of that series. If you know the short name (abbreviation) you can just type that (for example: LEB for Lexham English Bible). You know you're close when Logos begins to offer you some options in the drop down list.

Hopefully they can get this fixed for you soon.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/415720#Comment_415720

Unfortunately, right-clicking causes the same problem. So, hopefully they find a solution soon.

Sorry for hearing that. My library was able to open by that work-around method. The other thing is it stopped for me after some time and a couple of restarts of Logos.

I hope Logos will come with the solution ASAP.

Anonymous

We are looking into this issue, but have yet to track down what is causing it.

Do you get a crash if you open the collections tool?

If not does it crash when you create a collection with the filter rating:>=0?

If it doesn't crash in either of these situations as a work around you can use the collections tool to browse your books with the above collection. If it does crash I'd appreciate the logs from that crash as well.

Sorry for the inconvenience and thanks for helping us track this down.

Anonymous

https://community.logos.com/discussion/comment/415732#Comment_415732

Sorry for hearing that. My library was able to open by that work-around method. The other thing is it stopped for me after some time and a couple of restarts of Logos.

Does it crash for you if you right click open in new tab? or does it only crash when left clicking?

Geir Hunsbedt

https://community.logos.com/discussion/comment/415734#Comment_415734

Do you get a crash if you open the collections tool?

If not does it crash when you create a collection with the filter rating:>=0?

Todd, accessing the collection and using the filter does not crash the application. I can use this as a workaround for now. Thank you.

Bohuslav Wojnar

https://community.logos.com/discussion/comment/415741#Comment_415741

Sorry for hearing that. My library was able to open by that work-around method. The other thing is it stopped for me after some time and a couple of restarts of Logos.

Does it crash for you if you right click open in new tab? or does it only crash when left clicking?

Todd, thank you for looking into it. As I said in my thread about the same problem, I was able to open Library by right click. I answered your other questions there already: http://community.logos.com/forums/t/58350.aspx

Just for you to know, it works for me now - but in the time the problem occurred, it was repeatable many times after restarting Logos and just trying to click Library tab.

EDITED: just one more thing, the collection my Library attempted to open was Five Stars Books with the string: "rating:5"

Rosie Perera

Here's another person who is seeing this problem and has a reproducible case and a workaround.

http://community.logos.com/forums/t/58644.aspx

Brisa Davis

https://community.logos.com/discussion/comment/417393#Comment_417393

http://community.logos.com/forums/p/58350/415366.aspx

http://community.logos.com/forums/t/58384.aspx

This issue should be fixed in 5.0 SR-4. Please let us know if you continue to see this crash after that update is released.

Geir Hunsbedt

https://community.logos.com/discussion/comment/418205#Comment_418205

I can confirm that today's release has corrected this issue! Thank you, Logos!