[Milhouse]

I was not aware that I was. My apologies. What I do, and did in the past, is enabling debugging in the Kodi UI, optionally selecting additional components. After that I reproduce the issue, go to the logfiles share, open the latest log zip and paste the contents of 01_KODI.log.
Is this not the way logs should be created and provided?

01_KODI.log will contain *every* log that is found in /storage/.kodi/temp. This means it will contain your kodi.log, kodi.old.log and up to 10 crash logs.

If you're going to use 01_KODI.log as your source, it would just be better if you didn't post the other logs that aren't relevant, otherwise I don't know where to start and I'm left to wonder why you've posted crash logs and whether I need to look at them or not, etc.

Be aware that the ZIP files in the logfiles directory are created automatically whenever a new SMB connection is made to OpenELEC, and the latest ZIP may not always contain the very latest kodi.log details if you're using an SMB connection that you established some time previously.

My method is to use ssh, and then run the command:

Code:

paste /storage/.kodi/temp/kodi.log

which posts only the current log, and is always going to be posting the very latest details.

I was under the impression that this would create a new log again.

A new log file (/storage/.kodi/temp/kodi.log) will be created when Kodi is restarted, and the previous log file will be renamed to /storage/.kodi/temp/kodi.old.log.