As long the reason is not known there is nothing that can be done. If SID files are important use LE13 as a work around.
Posts by mglae
-
-
This is fixed, see post #3 of this thread.
For further testing you can update your fresh install first to current LE12 nightly and them to LE13 nightly. Both are available from https://test.libreelec.tv, check the date to get the most recent ones.
-
SID audio decoder was started in thread 26 but kodi is crashing in some python code in thread 1
Code
Display MoreProgram terminated with signal SIGSEGV, Segmentation fault. #0 0x76ed8198 in strlen () from /usr/lib/libarmmem-v7l.so [Current thread is 1 (Thread 0x631fd240 (LWP 761))] Thread 26 (Thread 0x67cee240 (LWP 752)): #0 0x5b7a4240 in __sidplay2__::Player::readMemByte_sidplaybs(unsigned short) () from /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.21.0.2 #1 0x5b79428c in MOS6510::FetchEffAddrDataByte() () from /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.21.0.2 #2 0x5b7a4bbc in __sidplay2__::Player::play(void*, unsigned int) () from /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.21.0.2 #3 0x5b788350 in ?? () from /storage/.kodi/addons/audiodecoder.sidplay/audiodecoder.sidplay.so.21.0.2 #4 0x00f09e88 in CAudioDecoder::ReadSamples(int) () #5 0x00f1ce28 in PAPlayer::QueueNextFileEx(CFileItem const&, bool) () #6 0x00f1db08 in ?? () #7 0x00775fec in CJobWorker::Process() () #8 0x007e9080 in CThread::Action() () #9 0x007ebef4 in ?? () #10 0x735aca20 in ?? () from /usr/lib/libstdc++.so.6 #11 0x733b8740 in ?? () from /usr/lib/libc.so.6 Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x631fd240 (LWP 761)): #0 0x76ed8198 in strlen () from /usr/lib/libarmmem-v7l.so #1 0x00faddd8 in ?? () #2 0x00483090 in ?? () #3 0x769be5fc in ?? () from /usr/lib/libpython3.11.so.1.0 Backtrace stopped: previous frame identical to this frame (corrupt stack?)
But even debug logging does not show which python code was called.
I'm unsure what to recommend. Maybe testing a fresh install on a spare SD card.
-
Please enable debug logging (again), reboot and post the complete log including system log as requested in post #6
For the repo issue force a manual update via addon options.
-
a) Installing from LibreELEC repo for Ganeric-legacy LE12 works for me
b) A reboot is unlikely, usually kodi is crashing and restarted. In this case a crashlog is generated. Reboot, reproduce the crash and upload crash log via LE Settings Addon or pastecrash
-
Doesn't this ^^^^ makes new config file?
You can save any time or are asked at the end.
Other kernel *config options do work too.
-
-
10 sec is the default compromise to not delay the boot to log without having network. I'm interested how log it takes on your side. Please provide a log even it is working using pastekodior the LE Settings Addon - a debug log is not required.
For the Jellyfin issue better ask in the addon thread of Kodi of Jellyfin forum.
-
connman dhcp is always requesting the recent "IPv4.DHCP.LastAddress" first.
As long the dhcp server accept this request the address will not change.
-
Check if kodi is muted or having low volume:
Then I would start with TV settings of Audio quickstart guide
-
What if you play local media e.g. from an USB stick?
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Go to Addons -> LibreELEC Settings -> Network -> Wait for network before starting Kodi -> Maximum Wait Time (Sec.) and increase time to 60sec.
If still failing provide a log.
-
Addons -> LibreELEC Settings -> Network -> Wait for network before starting Kodi -> Maximum Wait Time (Sec.)
-
time-sync.target is an overkill.
When removed there is still the dependency chain network-online.target -> kodi-waitonnetwork.service.
kodi-waitonnetwork.service is implemented as wait for time-sync with timeout. Using this with a larger timeout configured (default is 10sec) e.g. 60sec will very likely connect to wireguard if there is a network but also start kodi after the timeout without.
-
Try increasing the wait for network timeout in LE settings.
System Log requited if no improvement.
-
Remove time-sync.target from the original dependencies.
-
Just a guess:
If working put the first two lines into autostart.sh
-
Reinstallation does not change the state of the disks but start with an empty database.
You can do disk setup and maintenance from LE using SSH. Enable SSH in LE settings and use a SSH client to connect.
To e.g. check your sda file system stop Kodi to avoid any disk access, unmount the fs and perform the fsck:
After successful check use udevil umount /dev/sda to get access again.
When done with /dev/sdb and /dev/sdc1 too start kodi with systemctl restart kodi again.
To get healt_h information about the disk install System Tools Addon from LE Repo and use e.g. smartctl -a /dev/sda|paste and post the URL.