Choose a receiving location you can inspect
On a television device, Kodi’s log may be harder to reach through the operating system than on a desktop. Kodi documents a File Manager route that exposes its log directory from inside the application. This task retrieves a file; it does not automatically upload it or decide who should receive it.
First choose a destination you control and can inspect outside Kodi, such as an accessible local folder or an authorized share. Confirm that this destination is writable using the device’s supported route. Do not enter a stranger’s share address from a forum response. The log can contain private device and source information, so the receiving location matters.
Add the documented special path in File Manager
Kodi’s File Manager uses separate source entries from its normal media-source screens. Open File Manager, add a source and use the documented special://logpath address for the log location. Give this entry a recognizable local name. Adding it does not add the log as a film or change the content type of your video library.
Use the other File Manager pane for the destination. Confirm which pane represents the log source and which represents the receiving folder before copying. A television remote can make similar folder names easy to confuse. Read the selected filename and destination together rather than relying only on the currently highlighted icon.
Copy the session file that contains the reproduction
Choose the current or previous log according to when the failure occurred. If you just reproduced the problem in the current session, the current log is the starting point. If Kodi was restarted afterward, check the previous-session file. Do not keep restarting while trying to decide: log rotation can replace the session you need.
Copy rather than move the diagnostic file. Once it reaches the chosen destination, open the copy with an appropriate text viewer outside Kodi and check that it contains the expected session and reproduction time. A visible filename alone does not establish that the transfer completed or that you selected the correct log.
Review the copy before a separate support submission
Keep an unmodified private original and review a sharing copy for credentials, tokens, private hostnames and other unnecessary personal details. Preserve enough surrounding context for the technical sequence to remain understandable. If you remove a sensitive value, use a consistent replacement so repeated requests can still be recognized.
Only after that review should you choose a support destination and follow its requested upload route. Kodi’s optional uploader and an ordinary file copy are separate actions. This procedure ends with a readable private diagnostic file that can be assessed before disclosure. It does not certify the source, add-on or IPTV Europe account involved in the captured session.
Questions answered
Does adding special://logpath add a video library source?
No. This documented path is added within Kodi File Manager to access logs. File Manager entries and media-library source configuration serve different purposes.
Why copy instead of moving the log?
A copy preserves the original diagnostic file while you inspect and prepare a separate sharing version. It also makes the destination easier to verify without altering the source.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.