See Kodi WIKI for skin development commands in key map or via kodi-send.
You can use e.g. WinSCP on Windows or sshfs from Linux to remote edit the installed files.
Posts by mglae
-
-
-
After installing the LE mariadb addon you can test the access to your db with mariadb/mysql command line tool via ssh.
-
Detailed kernel error messages are viewable with dmesg or journalctl -k
-
How do I access the ir-keytable output log?
Log in via ssh to get a console: user root password libreelec (if not changed at installation).
And what's an mce-kbd protocol?
Likely the protocol to access the MCE keyboard, but I don't know any details either.
-
There is an open tone map issue on Kodi GitHub.
-
This thread is more than five years old, you may have to consider the current Wiki
-
Is anything that I'm missing?
Google did remove Chrome 109.0.5414.74 from their servers.
Work around: edit /storage/.kodi/addons/browser.chrome/bin/chrome-downloader and replace Chrome version with current 122.0.6261.94. Please report if it is working.
-
The higher version number always win. If version numbers are equal the addon below ~/.kodi is used.
-
-
According to the kodi2mqtt support thread a Python 3 version is available.
-
Busybox ash is not as feature complete as bash.
cd /storage/music/Prince\ -\ Xenophobia\ \(2003\)/ will work, Omit the quote when using tab completion.
-
-
How can I access the logs without CLI (e.g. via GUI) on second boot? B
You can use the gbmshell development addon
-
Small development addon to replace running Kodi with a shell on GBM. Attached keyboard is required.
Can be installed from ZIP using an USB stick e.g. on networking issues.
Generate logs without network:
Add an USB stick and type pastekodi -c >/media/"Stick Name"/my.log. Then upload the file to a pastebin site from a different machine.
History
2025-05-22 1.0.3 support changed os-release variables too
-
For a test without changing your installation create an install stick and use the run option at boot.
You can even import a LE system backup of your 11.0.6 installation on the stick.
Whatever you do, a system backup of the working system is always recommended.
-
For reference there is a kernel bugzilla report. Different behavior description but maybe some ideas are helpful.
-
As a guess the issue likely can be fixed by building Kodi with #22222
