Logos Shuts Down After Choosing Layout

Hey everyone,

Logos just had an automatic updat last night with the latest release and worked fine, but this morning when I open it everything starts up like normal, but when I choose a precreated layout it suddenly shuts down. Usually when this happens my Mac will ask if I want to send an accident report to Mac, but this morning it's just acting like nothing ever happened. I can open Logos after this and Logos opens and then when I select a layout it behaves the exact same way. Any ideas on whats going on?

Thank you!

Find more posts tagged with

Comments

Jack Caviness

Does this happen with multiple layouts, or with just the one?

Those who can help will need log files; do you need instruction on gathering and posting?

Hunter Clagett

https://community.logos.com/discussion/comment/396868#Comment_396868

Just in case, follow the directions here http://wiki.logos.com/Diagnostic_Logging to gather your log files and post them to this thread.

Thanks!

Liam

https://community.logos.com/discussion/comment/396903#Comment_396903

It's just one layout. The rest work. Very strange. I'll check out the wiki on the log file. I recreated the layout already, so it's not an urgent thing anymore, but does anyone know why a particular layout would do this?

Jack Caviness

https://community.logos.com/discussion/comment/396928#Comment_396928

does anyone know why a particular layout would do this?

I can think of a couple of possibilities:

1) The layout is corrupted. Does it work after you rebuilt the layout?

2) There is a corrupt resource in the layout. In this case, it will crash again with the new layout. Logs can help identify the resource. You can then remove it, and Logos will download it again.

Logs may reveal additional possibiulities

Liam

https://community.logos.com/discussion/comment/396947#Comment_396947

Thanks Jack,

I think it was a PB resource that I changed the file location for.

Jack Caviness

https://community.logos.com/discussion/comment/397311#Comment_397311

I think it was a PB resource that I changed the file location for.

Don't think L4 likes that, but I did not know that it could cause a crash.