Instructions for submitting L5 Logs?
I crashed L5 Mac tonight while clicking on a link in Exegetical Summaries. This is the third crash I have encountered in 24 hours. The other one was running a search and I can't remember what caused the third.
Anyhow, it's time to start submitting logs again. I went to the usual folder look for the logs, but I can only find them for my old Logos 4 install. Can someone point me to the instructions on how L5 logs should be obtained and submitted? Thanks!
Comments
-
Donovan R. Palmer said:
I crashed L5 Mac tonight while clicking on a link in Exegetical Summaries. This is the third crash I have encountered in 24 hours. The other one was running a search and I can't remember what caused the third.
Anyhow, it's time to start submitting logs again. I went to the usual folder look for the logs, but I can only find them for my old Logos 4 install. Can someone point me to the instructions on how L5 logs should be obtained and submitted? Thanks!
The standard question to ask when Logos crashes while running a search is: Did indexing finish?
As for submitting logs, read the instructions carefully, don't restart Logos before submitting your logs, and submit all the "logos" logs (you can ignore the "logos4" logs, if you're running Logos 5).
Look here for enabling logging: http://wiki.logos.com/Diagnostic_Logging
And here for uploading them to this forum: http://wiki.logos.com/Uploading_Logs
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Donovan R. Palmer said:
Can someone point me to the instructions on how L5 logs should be obtained and submitted?
Wiki page has Logos 5 for OS X => http://wiki.logos.com/Diagnostic_Logging#Logos_5_for_OS_X since the command to enable/disable logging in Logos 5 for OS X is a bit different than Logos 4 Mac.
Keep Smiling [:)]
0 -
Donovan R. Palmer said:
Can someone point me to the instructions on how L5 logs should be obtained and submitted?
Surprised KS4J did not mention this. He has updated his Applescript to work with both L4 and L5
Also 6403.Logos Log Scribe R2.zip does an excellent job of assembling logos and placing then in a archive on your desktop.
0 -
Jack Caviness said:Donovan R. Palmer said:
Can someone point me to the instructions on how L5 logs should be obtained and submitted?
Surprised KS4J did not mention this. He has updated his Applescript to work with both L4 and L5
Wiki => http://wiki.logos.com/Diagnostic_Logging#Logos_5_for_OS_X includes link to updated Applescript (in Logos 4 Mac and Logos 5 for OS X sections)
Note: the updated Applescript application that works with Logos 4 Mac and Logos 5 for OS X has a different name.
Keep Smiling [:)]
0 -
I was really hoping these days were over on our Mac user end with L5 (which I do really like), but alas I too must start submitting crash logs in hopes of resolving the cause(s). Too many crashes happening and for what seem to be varying circumstances. I would think that L5 underwent stringent beta testing before its release so these issues are both surprising and a bit disappointing.
Mark Nigro
Pastor/Teacher/Student/Writer
www.calvarychapelbiblecollege.com
0 -
Note: the updated Applescript application that works with Logos 4 Mac and Logos 5 for OS X has a different name.
Oops, have the correct version on my desktop, but the wrong version in the Text Edit document [:$] Now corrected
Will edit the above post, if possible
0 -
Mark Nigro said:
I would think that L5 underwent stringent beta testing before its release so these issues are both surprising and a bit disappointing.
It did undergo Beta Testing, but there are far more people using this application now. No software is ever completely bug-free.
Mark Nigro said:Too many crashes happening and for what seem to be varying circumstances
Have not experienced very many crashes, either now or during Beta testing. What are your specific problems?
0 -
Hi Mark
During the Beta testing - there were very few (if any) reports of crashing that were not resolved very quickly by either downloading a fresh engine or re-indexing some or all of the databases.
It is rough that you are going through these troubles (again) and I hope it gets sorted for you soon. Partly because if it gets sorted for you it gets sorted, potentially, for me.[:)]
tootle pip
Mike
Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS
0 -
Thanks Mike and Jack. The crashes come randomly. Working in "Notes" is one cause of them. Seems I can guarantee a crash if a work long enough in notes. While creating notes in a string of verses L5 crashed 3 times, once just because I was changing the font size. Thankfully, very little of the note edits were lost. Prioritizing my library also crashed L5 twice. I stopped prioritizing at that point. Switching a parallel resource generated a crash. Shut down gets stuck and requires a "force quit" every time, unless I manually "Sync" before hand. Entering a morphological/syntactical command crashed it. Working in "Biblical Facts" generated a crash (there are also bugs with that as I mentioned in another thread). All that said, I love what Logos has done with L5 and the direction they are continuing in. developing innovative features that save us time in our workflow. For the time being, I'm just a little paranoid about losing work until these crashes are sorted [:^)]
Mark Nigro
Pastor/Teacher/Student/Writer
www.calvarychapelbiblecollege.com
0 -
I am still very positive about L5, but have had three crashes and found one UI error. Next week when my schedule settles I will start submitting logs here and for the fun of it, I am going to keep a personal crash log. I'm hoping that it will be short, but if not it might be of use to see patterns of why it crashes for me maybe more than compared with others.
0 -
Mark Nigro said:
Thanks Mike and Jack. The crashes come randomly. Working in "Notes" is one cause of them. Seems I can guarantee a crash if a work long enough in notes. While creating notes in a string of verses L5 crashed 3 times, once just because I was changing the font size. Thankfully, very little of the note edits were lost. Prioritizing my library also crashed L5 twice. I stopped prioritizing at that point. Switching a parallel resource generated a crash. Shut down gets stuck and requires a "force quit" every time, unless I manually "Sync" before hand. Entering a morphological/syntactical command crashed it. Working in "Biblical Facts" generated a crash (there are also bugs with that as I mentioned in another thread). All that said, I love what Logos has done with L5 and the direction they are continuing in. developing innovative features that save us time in our workflow. For the time being, I'm just a little paranoid about losing work until these crashes are sorted
This is not typical behavior.
Please enable logging and post your logs as described here: http://community.logos.com/forums/p/59359/422589.aspx#422589
This may be able to tell us what is going on, and then maybe how to fix it.
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Mark Nigro said:
While creating notes in a string of verses L5 crashed 3 times
As Richard noted, none of these crashes are normal. In order to have them repaired, development must be able to determine the cause. That requires logs.
KS4J has created an Applescript that allows Mac users to easily enable/disable logging 5516.LogosLogging.app.zip
Another forum member created a small app that will asemble log files, create an archive, and place it on your desktop, ready for attachment to a forum post 6403.Logos Log Scribe R2.zip
To be noticed, it is best to start a new thread, describe the actions immediately preceding the crash and attach the log archive. Most attention can be gained by prefixing the thread name with BUG:
Hoping to see these bugs rectified soon.
0 -
My Logos just crashed as wel., maybe third time. But I noticed something that says: "awesomium.log," in the logs folder. Is this something you all (when your Logos crashed) noticed? All the rest of the files says: Logoslog, Logos4Error-2.log and so on....
Thanks
Joel
0 -
Alright... It crashed again... Here are the logs:
0 -
Thanks for the link. Got logging turned on and will post in an appropriate thread if I encounter a crash. Must say that I have done a couple of hours worth of work this evening in L5 and had no problems at all. Even did extensive library organization and collections, searches etc. not a crash or bug arose. I noticed on the homepage that Logos released an update and it installed a day or two ago so some of my problems may have corrected in that update.
Mark Nigro
Pastor/Teacher/Student/Writer
www.calvarychapelbiblecollege.com
0 -
Mark Nigro said:
Must say that I have done a couple of hours worth of work this evening in L5 and had no problems at all. Even did extensive library organization and collections, searches etc. not a crash or bug arose.
Good News [8-|]
0 -
Where should I post log files? Is there are separate "thread" for that?
Thanks
0 -
Joel Madasu said:
Where should I post log files? Is there are separate "thread" for that?
Thanks
Hi Joel
When you crash, or encounter a bug, that requires logs it is best to start a new thread.
You should entitle the thread with the first word being 'BUG – ' followed by a short description of the problem and the operating system you are using.
e.g. 'BUG – all text in commentary turns yellow on right click – OSX 10.8'
The developers will spot this type of thread and even some of the MVP can decipher the logs quite well.
Resist the urge to add your problem to the end of an existing thread unless you are really really sure that you have the same underlying problem rather than just the same symptoms.
tootle pip
Mike
Now tagging post-apocalyptic fiction as current affairs. Latest Logos, MacOS, iOS and iPadOS
0 -
Sure
Thank you for your help!0 -
Well, I am up to six crashes. My road trip is over, so I'll start documenting and submitting logs. My most recent was yesterday on the plane working in offline mode when I added another column to the library view. Without warning, poof! Logos crashed. Here's hoping some of the things I have encountered have been documented already or I will get them fixed in the next release!
0 -
Somewhere in all these posts, I had a similar experience that happened twice. After that, I was not able to duplicate.
0
