Capture a specific failure rather than a general session
LibreELEC support can need both Kodi logs and system configuration to understand a failure. Begin with the shortest reproducible action and record the LibreELEC and Kodi versions. Keep a known source and the relevant hardware route constant during that action.
If the problem requires debug logging, enable it through the documented Kodi logging controls before reproducing. Note the time and exact visible symptom. A long normal session captured before the failure occurred may provide less useful evidence than a short complete session containing the actual event.
Choose collection and sharing as separate actions
The LibreELEC log guide documents a built-in paste function that sends logs and configuration to a remote service, and a Samba route that packages diagnostic data into a ZIP. Read the actual control before pressing it. Retrieving a private file and publishing a paste are different operations.
If you want to review first, use an appropriate supported private collection route. Preserve the original bundle and identify the main Kodi log inside it. Keep the collection time attached to the file so it is not confused with an older automatically generated package.
Inspect the contents needed for the case
Open the relevant log in a text viewer and confirm it contains the intended reproduction. Review source URLs, account identifiers, filenames and network details before sharing. Keep surrounding technical context intact while redacting sensitive values consistently.
Do not upload a whole archive to an unrelated destination simply because it is easier than reading its contents. Use the current project support instructions for the appropriate artifact and recipient. A paste URL can make a report convenient, but it also identifies remotely accessible content that should have been reviewed.
Retain a concise support record
Keep the reproduction, versions, capture time and chosen sharing artifact together. If the fault concerns Safe Mode, verify whether the log came from the preserved failed setup or the current recovery session. These can answer different questions even on the same device.
Return logging and temporary administration services to their intended everyday state after the investigation. The expected outcome is useful, reviewed diagnostic evidence. It does not certify that all private values are automatically masked or establish that a log-upload action repairs the underlying player, source or hardware problem.
Questions answered
Does Paste system logs merely save a private local file?
The documented paste route sends information to a remote service. Read the actual control and choose a private collection route if review is needed first.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.