BUGS: 2 UI malfunctions + a crash

fgh
fgh Member Posts: 8,948 ✭✭✭
edited November 2024 in English Forum

This happened a week ago:

1) Logos opened to a little miniature window below the bottom left corner of the screen:

2) Later that session it crashed. No Logos crash log, and I restarted to quickly to get the others. I've got the Apple crash log if anyone wants it.

3) When I opened again I encountered the 'no layouts' bug (a first for me, but I know it's happened to others):

This time I did remember to duplicate the logs before I restarted. Let me know if you want any.

 

Mac Pro (late 2013) OS 12.6.2

Comments

  • Martin Potter
    Martin Potter Member, Logos Employee Posts: 378

    Logs are always helpful and appreciated. The more information we can gather about the cause of the issue the better.

    Mac Developer
    Faithlife

  • fgh
    fgh Member Posts: 8,948 ✭✭✭

    Logs are always helpful and appreciated. The more information we can gather about the cause of the issue the better.

    OK, now that I know someone's reading:

    2) 4834.Logos Bible Software 4_2012-03-09-144525.crash.zip

    3) 2287.Logos logs 120309.zip

    While you look at the indexer log, check out the lines about LLS:EXBBL... as well, will you. Those resources were returned in January, disappeared, but then suddenly downloaded again when the software was updated. They won't install, of course, since they're locked, but I also can't get rid of them, and they seem to re-download again and again with every single download I do. It's getting a bit annoying. I reported it here, in a thread where someone else seemed to have a similar problem (with all of Perseus!), but I see now that is was a General thread.

    (To get 5 minutes work done on Logos takes me approximately 8-10 hours: 2-3 fighting with bugs and issues, plus another 5-8 reporting them -- which most of the time leads to absolutely zero response from Logos. So forgive me if I generally can't be bothered to report bugs anymore, and even less to waste even more of my time by also attaching logs to reports that are seemingly never read, especially, like in this case, when I know the issues have been reported multiple times before, so there's a good chance you already have all the logs you need. I know you don't set the priorities and it's not your fault, but I'm really tired of spending 100 times more time on fighting the program than on using it! And, no, I'm not exaggerating, unfortunately.)

     

    Mac Pro (late 2013) OS 12.6.2