4.3 Beta 5: CRASH: Selecting LRS System 1 as Default Font

Page 1 of 1 (3 items)
This post has 2 Replies | 0 Followers

Posts 18867
Rosie Perera | Forum Activity | Posted: Sun, May 22 2011 12:40 AM | Locked

Unfortunately I did not save the log file before starting up Logos again to try to reproduce this, so all I have is the Logos4Crash.txt.

I had The New Unger's Bible Dictionary open in the left tile and Program Settings in the right (along with a bunch of other resources in other tabs). I had New Unger's scrolled to around the section of the transliteration table with Half-vowels (trying to see if changing the font to something else besides Default would fix the box that shows up there instead of a schwa -- see other bug report for that). First I selected Default Sans Serif, next Arial, and finally LRS System 1. When I clicked on the latter, Logos crashed. Here's a partial screenshot:

And here's the crash log: 12545.Logos4Crash.txt

Hopefully there's enough to go on in there to figure out what's causing the crash.

I have not been able to reproduce it, but if I do I'll post a full log file.

Posts 4077
Melissa Snyder | Forum Activity | Replied: Mon, May 23 2011 8:16 AM | Locked

I was able to reproduce the crash when I chose "LRS System 1" from the font selector in Program Settings with the New Unger's open. I'll include my full log in the report.

Update:  This will be fixed in the next beta. Note that when the program is restarted after the LRS System font has been selected and the font is changed back to default, the resource characters may change to boxes. Closing and reopening the resource panel will resolve this.

Posts 18867
Rosie Perera | Forum Activity | Replied: Mon, May 23 2011 4:35 PM | Locked

Melissa Snyder:

Note that when the program is restarted after the LRS System font has been selected and the font is changed back to default, the resource characters may change to boxes. Closing and reopening the resource panel will resolve this.

Yes, I had noticed this too but hadn't gotten around to reporting it because I couldn't reproduce the underlying crash problem.

Page 1 of 1 (3 items) | RSS