Logos 5.1 beta 2 and 3 no longer working

Every time I launch Logos 5, I get the message: Logos is no longer working.

This occured when I was working with Beta 2. So I installed Beta 3 from scratch. But the problem remained. Even when I deinstalled Logos and reinstalled it again.

The problem occured after I resized the Logos windows and pinned it to the right side of my screen (I pinned Word on the left side).

Any ideas?

Hans

Configuration

Windows 8 Pro, 64 bit

Find more posts tagged with

Comments

kelly.flones

In order to assist you with this issue we will need to see your log files. Please see http://wiki.logos.com/Diagnostic_Logging#Enable_Mac_logging_always for instructions, and submit your logs.

JT (alabama24)

https://community.logos.com/discussion/comment/475451#Comment_475451

Kelly gave you a link to the MAC instructions… In my signature is a link to the PC (WIN) ones.

Hans van den Herik

https://community.logos.com/discussion/comment/475525#Comment_475525

It seems that the problem is over now. I don't know exactly what I did during the startup, but it seems that the problem was caused by opening the homepage.

Thanks for your quick answer. I really appreciate that!

Hans

JT (alabama24)

https://community.logos.com/discussion/comment/475629#Comment_475629

it seems that the problem was caused by opening the homepage.

I know that there were several other windows users who had a similar problem… perhaps a blog or advertisement had a bad link? In any case, I am glad you have things working now. [:)]

Hans van den Herik

https://community.logos.com/discussion/comment/475655#Comment_475655

Alas the same error occurred again.

Again after resizing the logos Window and pinning it to the right of the screen.

I resolved the problem by Starting in Logging mode (and checking ‘use blank layout').

Thanks Alabama24!

Attached are my logs.

Hans1803.Logos Log Files.zip

kelly.flones

This looks like the same bug that was reported here: http://community.logos.com/forums/t/68271.aspx . There is an active case for this issue. Thanks!