Page 1 of 1 (8 items)
This post has 7 Replies | 1 Follower

Posts 6588
Forum MVP
Lynden Williams | Forum Activity | Posted: Wed, Dec 12 2012 9:05 PM

Uploaded to the latest beta, 1. loaded a layout

2. clicked on the word wine

3. Selected the information pane. 

4. Application crashed.

2161.LogosError.log

5148.LogosCrash.txt

1016.Logos.log

Lynden Williams Commu

Posts 6588
Forum MVP
Lynden Williams | Forum Activity | Replied: Wed, Dec 12 2012 9:13 PM

1. Started the software, and then opened my mail program.

2. Selected the software to start working, and crash.

5460.LogosCrash.txt

8508.LogosError.log

2804.Logos.log6406.LogosIndexer.log

Lynden Williams Commu

Posts 6588
Forum MVP
Lynden Williams | Forum Activity | Replied: Wed, Dec 12 2012 9:13 PM

This was the second saved layout that caused the crash.

Lynden Williams Commu

Posts 6588
Forum MVP
Lynden Williams | Forum Activity | Replied: Wed, Dec 12 2012 9:17 PM

Loaded a different layout, and immediately the software crashes.

Lynden Williams Commu

Posts 6588
Forum MVP
Lynden Williams | Forum Activity | Replied: Wed, Dec 12 2012 9:29 PM

Tried changing Bibles and the app crashes.

Lynden Williams Commu

Posts 8251
LogosEmployee
Bradley Grainger (Faithlife) | Forum Activity | Replied: Wed, Dec 12 2012 11:25 PM

This appears to be  a crash in the Information Panel; we'll look into it.

As a workaround, please close the Information Panel (or set it to update on click instead of hover).

Posts 5321
DIsciple II | Forum Activity | Replied: Thu, Dec 13 2012 1:24 PM

After updating my install would crash almost immediately upon loading.  I could not do anything in the program. Not sure if I had an info window open or not.  I was able to work around that problem by the old hold down the ctrl key when starting and change to a blank layout.  No crash after that.  So i've taken advantage of new feature and set it to always load to a blank layout for now.  Logs attached.

8206.Logos20121214.zip

Posts 1432
Tonya J Ross | Forum Activity | Replied: Wed, Jan 2 2013 3:06 PM

This issue should be resolved in 5.0b Beta 2.

Page 1 of 1 (8 items) | RSS