Cmd-Q to exit.
The sync dialog appeared ... should not be much to do .. I only loaded L5 by mistake!
The sync dialogue did not want to go.
Logs attached together with apple error report.
3288.Apple Error Report.txt
0871.LogosLogs Martin 20130108-161823.gz
There is no logos.log that covers this and the last error log entry may or may not be relevant, assuming this happened on Jan 8
Time: 2013-01-08 16:13:13 +00:00 (2013-01-08T16:13:13Z)Error handling response (GET https://notesapi.logos.com/v1/popularhighlights/exist?resourceId=LLS:EXPEPH2&resourceVersion=2010-10-20T16:12:37Z).System.Net.WebException: Error getting response stream (Write: The authentication or decryption has failed.): SendFailure ---> System.IO.IOException: The authentication or decryption has failed. ---> Mono.Security.Protocol.Tls.TlsException: Bad record MAC
Another crash on exit ...
4162.Apple Error Text.txt
1346.LogosLogs Martin 20130202-195323.gz
Again, there is no crash report. The Logos.log has lots of messages:-
namedmutex_prewait: error looking up named mutex handle 0x280d
Were you were following the procedure at http://wiki.logos.com/Diagnostic_Logging#Logos_5_for_OS_X
I believe so ...
I reported a different crash a couple of days ago and I presume that the logs recorded a crash then ... so I think that my logging is in order ... Could there be a point during the the exit logic beyond which logging does not occur?
On the screen, I exited L5Mac using cmd-Q. I came back to the same windows 20/30 minutes later because I noticed that it was still present ... except that it was only the standard grep speckled background. Switching to a different space, I force quit L5Mac using the menu in the system tray icon.
We'll have to see what Logos can make of it.
I can reproduce this issue and have created a case for Development.
Thanks Kelly
If you need more information, here it is:
3021.LogosSampleLogs.jackcav.20130516-215559.zip
4370.Apple Crash Report.rtf
2620.LogosLogs.jackcav.20130516-215754.zip
Note that Logos did not request an automatic error report upon restart. After restart—and closing a couple of floating windows—Logos quit normally.
I have seldom experienced this refusal to quit in recent weeks.
