I've noticed my Logos for Mac 5.0a quitting unexpectantly a couple of times this past week. Should I post any Apple Crash Report logs of it just so the Logos team can have them for the record? Restarting Logos usually seems to be fine.
Thanks!
Wiki has => http://wiki.logos.com/Diagnostic_Logging#Logos_5_for_OS_X
Logos diagnostic log files with Apple crash report would be appreciated since the Logos diagnostic log files provide context for crash report.
Keep Smiling [:)]
Wiki has => http://wiki.logos.com/Diagnostic_Logging#Logos_5_for_OS_X Logos diagnostic log files with Apple crash report would be appreciated since the Logos diagnostic log files provide context for crash report. Keep Smiling
Keep Smiling
Sounds good. If it happens again, I'll definitely post some, or I may try to post some tomorrow.
BTW, someone can update the wiki because there's a workaround for Gatekeeper in Mountain Lion without having to change the setting. Just control+click the AppleScript app and click Open. It'll prompt with a message and allow the person to open it.
Here's my console logs. If I can get some Logos logs, I'll post those as well. Last time it happened, I was trying to load a layout.
6675.consolelogs.zip
Nathan - Please don't post the content of any logs in the forums. Logos logs can be attached directly via the paperclip icon. If it is an apple log, it would be better to paste the info into a document and attach it. This is for at least two reasons:
Nathan - Please don't post the content of any logs in the forums. Logos logs can be attached directly via the paperclip icon. If it is an apple log, it would be better to paste the info into a document and attach it. This is for at least two reasons: Logos are easier to read in an appropriate app Placing the log in the thread makes the thread more difficult to navigate and the conversation is more difficult to maintain.
Sounds good. Next time around I'll sure do that. Thanks for the tip.
One option is using More menu in forum editor to edit post so contents can be replaced with a file attachment. Ideally zip file attachment would include Logos diagnostic log files plus crash report.
Apologies: personally have a tendency to gloss over threads with crash report content posted.
Ideally zip file attachment would include Logos diagnostic log files plus crash report.
For example, after using the Close All command in Logos 5.0a SR-1 on OS X 10.8.2, an unexpected crash happened:
0753.03-Crash-Close-All.zip
The zip file includes Apple crash report that was copied from ~/Library/Logs/DiagnosticReports folder along with Logos diagnostic log files.
Ideally zip file attachment would include Logos diagnostic log files plus crash report. For example, after using the Close All command in Logos 5.0a SR-1 on OS X 10.8.2, an unexpected crash happened: 0753.03-Crash-Close-All.zip The zip file includes Apple crash report that was copied from ~/Library/Logs/DiagnosticReports folder along with Logos diagnostic log files. Keep Smiling
Just edited it and gave it a try. It's the same old Apple logs for now, but if I have time to do Logos ones later I will. Today's been a crazy and busy and and my computer's aren't cooperating with me in terms of speed today. :-)
The most convenient way to enable logging is to use the Applescript LogosLogging by KS4J. (Restart of Logos needed after enabling)
Then use Logos Log Scribe to create an archive of the logs on your desktop.
