so i updated to nightly (just updated, not clean install) on 4/24 and i have not had an error since (currently 5/2). it hasn't glitched or restarted at all. i'm sure i DO have filesystem errors, but it isn't affecting anything so far. i do have a backup so in case it does crash completely, i can reformat and fix the filesystem at that time. i guess my go to from now on will be to update to current no matter what and not try to stick it out on a stable build. thank you all for taking the time to help me.
Posts by eliaslear
-
-
There are two major issues in the log.
1. Kodi is crashing when closing the video database. May be a broken sqlite DB file.
2. The file systems on your HDs (except the NVME) are broken.
I do recommend a system backup (via LE settings) to an external media first, then fixing the errors before trying any larger updates.
okay. can you recommend a good way to prepare the drives? i used ubuntu to do a fresh format in ext4 on all drives. i do have minitool partition wizard i can use. i just figured doing through an actual linux distro would be better. they were all brand new drives and all were formatted back to back in ubuntu. do you think i may have done something incorrectly or with the wrong setting? or could the filesystems have just become corrupted this quick from crashing (3 months)? this is my first time using ext4. previously i've only used ntfs. i do have backups of all drives, i just hate to wipe and copy everything back over. not the end of the world just takes days. i see it says "running e2fsck is recommended". is there a tool to repair the filesystem to avoid formatting? i have Parted Magic and UBCD. would those help me at all?
I'd suggest updating to an LE13 nightly before doing anything else. If there's a bug/issue related to UPnP the issue is with Kodi not the OS layer (LE) and all Kodi development moved onto K22 more than a year ago. See if anything changes with the update.
i will update today. i fresh installed 11 after having issues with 12 to see if it fixed anything but i had same issues so i reinstalled 12. then again, i guess the crashing and database issues can be completely separate and i never noticed one because of the other? do you think the database errors could be caused by the corrupted filesystems? and i don't mind leaving upnp disabled. it doesn't affect access on the network in the house anyway. and nothing ever gets plugged into it.
just an update. i got this on screen today. first time i got to see in real time what just happened. i can see all the ext4 errors you're talking about.
-
If you want support from experienced users or from experts like chewitt , you shouldn't skim with information. Snippets of logs are in 99.99 percent are pointless and and results into same as if you post "something is going wrong" - nothing more, no helpful content. Please provide a full debug log like described above.
i understand. i thought i was posting the required log. here is per the instructions. but it didn't give me an ix.io link. it gave me this url: https://paste.libreelec.tv/discrete-stallion.log
-
If you read the code you'll find that in lots of scenarios Kodi tests for capabilities and makes code-path decisions based on whether something succeeds (is supported) or fails (is not supported). Both 'errors' are normal and harmless.
i understand. that's why i'm posting this issue for help.
-
these are the 2 errors i get. i googled them but didn't find a solution:
Code
Display More2025-04-09 00:34:17.837 T:1534 error <general>: CDRMAtomic::DrmAtomicCommit - test commit failed: (Invalid argument) - falling back to last successful atomic request 2025-04-09 00:34:17.837 T:1534 error <general>: Object: plane ID: 52 Object: plane ID: 58 Object: plane ID: 40 Object: plane ID: 64 Object: plane ID: 46 Object: crtc ID: 73 Object: connector ID: 87 Object: plane ID: 70 Object: plane ID: 78 Object: plane ID: 74 Object: plane ID: 82 2025-04-09 00:34:17.837 T:1534 error <general>: CDRMAtomic::DrmAtomicCommit - atomic commit failed: Invalid argument ------------------------------------------------------- 2025-04-09 00:34:28.087 T:1801 error <general>: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files 2025-04-09 00:34:28.087 T:1801 info <general>: LogindUPowerSyscall - UPower not found, battery information will not be available 2025-04-09 00:34:28.091 T:1801 info <general>: CKeyboardLayoutManager: loading keyboard layouts from special://xbmc/system/keyboardlayouts... 2025-04-09 00:34:28.652 T:1801 error <general>: [xkb] couldn't find a Compose file for locale "C" (mapped to "C") 2025-04-09 00:34:28.652 T:1801 warning <general>: CLibInputKeyboard: Failed to compile localized compose table, composed key support will be disabled -
i tired disabling upnp. i'll know in a day if it works or not. now when i restart, i'm getting a message "libreelec configuration error."
-
Do you have an LG TV and does that also happen if you disable UPnP?
i do not. it's a vizio. and i dont' see any upnp settings. were they disabled in the tv or in kodi?
-
i get this usually daily. a reboot sometimes works and sometimes doesn't. it's too large for attachments and pastebin is down so here's a link to the log from my drive:
-
loaded fine in windows and ran check disk. no issues. rolled back to previous build, all drives work. updated again and no drives. rolled back once again and they work fine. it's definitely an 11 software issue.
-
i've been on 10 from release to today. updated to 11 and lost hard drive access. i have an asus j4005. small samsung ssd for os, and an 8tb hdd, both in ntfs format. both plugged into sata ports on motherboard. i can see both in in bios, but when i load kodi, it doesn't show large drive in system info or file manager. i downgraded back to 10 and everything works great again. seems like software issues. maybe someone left out something simple in the latest build?
-
i've read through many threads on my same issue, but nobody seems to have solved it.
i have an intel build connected over wireless. any transfers (read or write) over network (from windows 10) are limited to 10MB. doesn't matter if wired (gigabit) or wireless. the storage drive is a sata 2 spinning drive. when i transfer from usb it usually floats around 60MB, so i know it's not a drive or controller issue. i can transfer over ssh or ftp and get same speeds. kodi has the drive shared over samba under zeroconf browser (if that helps).
ifconfig shows this
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
collisions:0 txqueuelen:1000
RX bytes:122943352 (117.2 MiB) TX bytes:82816110 (78.9 MiB)
i can see my speed is capable, but for whatever reason limited to 10MB.
any suggestions to restore my speed to it capabilities or at least open it up a little more?
-
-
какой выход установлен для аудио в настройках системы?
what output is set for audio in system settings?
-
i've had the same setup for 5 years now. i have updated through each release, skipping betas, and everything has functioned as is. everything was working fine on 9.0.2. after updating to 9.2, i lose voices (and ui sound) after a while, but still have music in videos. upon booting, everything works fine. i can watch videos encoded in multiple codes (video and audio) just fine. but after letting it idle for a while or power cycling the amp or tv, i lose voices. the amount of time is random. if the surround sound goes to sleep and i wake it back up, sometimes i'll have voices , sometimes only background music. i'm assuming kodi is having issues with audio decoding, sending it through the TV into the amp. it's an asrock j4205 build, running through hdmi into tv, then into sony 5.1 surround sound (pl2 or basic filter). passthru or not, it does the same thing. i have downgraded back to 902 and the issue is no more. i tried upgrading again and the issue returns. for now i'm staying on 9.0.2 until issue is resolved or the next release.
UPDATE:
i decided to try the betas between the two stable release. 9.1.001 and 9.1.002 work as should. the audio outputs with voices as it should. however anything past those two have the same no voice issue. UPDATE AGAIN: never mind. they eventually started doing the same thing. i'm back on 9.0.2 now with no issues.
