Stuck on Kodi screen after reboot

    I have LE 10.0.3 running on an RPi4 and have been using the same configuration for a few years (updating through various LE versions). I rebooted the RPi4 yesterday and am now stuck on the Kodi screen-- the one that comes after the "LibreElec Just enough OS for Kodi" screen. I attached a picture below so I'm clear. SSH into the RPi4 works, it has an internet connection as measured through response pings to external sites, and it has a proper wireguard connection to a VPN service. I have tried rebooting a few times, and executed a shutdown and power up. Same result, I am at stuck at the Kodi screen.

    Any advice you have for interrogating and/or resolving my situation are gladly appreciated.


    Have a look at /storage/.kodi/temp/kodi.log for errors/issues. My thoughts would be a corrupted DB file or something add-on related. Worst case stop Kodi and rename /storage/.kodi to /storage/.kodi-old and restart; then start copying back config/content items from the old install until you either find the problem or end up with a working install again.

    Thanks chewitt. There are three errors:


    Code
    2023-01-05 04:46:55.722 T:1014    ERROR <general>: DBus error: org.freedesktop.DBus.Error.ServiceUnknown - The name org.freedesktop.UPower was not provided by any .service files


2023-01-05 04:46:56.857 T:1029    ERROR <general>: SQL: [Textures13.db] SQLite error SQLITE_ERROR (no such table: version)
                                                   Query: SELECT idVersion FROM version


2023-01-05 04:46:56.858 T:1029    ERROR <general>: Process error processing job 

    There are also three warnings but all look inconsequential. The final two errors above are the final entries in the log file while the first one occurs earlier. I know just enough to be dangerous with Linux, so while I understand DBus is a logging system and SQLite is a database system I have a hard time interpreting the errors. You mention it may be a corrupted DB file; do these errors change your advice for a path forward or should I still do what you explained?

    Thanks

    Textures13.db has become corrupted so a query to the DB fails; this is shown in the second and third errors. The DBus error is harmless.

    Delete the Textures13.db file and the thumbnails folder. The DB will be recreated on Kodi restart, and thumbnails will be re-downloaded on access to GUI views that require artwork. If you don't remove the thumbs the cache references will be incorrect and you'll have blanks all over the GUI and you'll need to manually refresh everything to repopulate content.

    Quote from chewitt

    Have a look at /storage/.kodi/temp/kodi.log for errors/issues. My thoughts would be a corrupted DB file or something add-on related. Worst case stop Kodi and rename /storage/.kodi to /storage/.kodi-old and restart; then start copying back config/content items from the old install until you either find the problem or end up with a working install again.

    How do I look at that? I'm having the exact issue.

    I arrive at this thread because I think I have a similar problem. Stuck at splash screen - after power outage, so that's plausible. However, I don't find any pointer in the kodi.log to which file/area is the culprit.

    Any advice/insight appreciated, before I clear the complete config and configure everything from scratch. Thx!

    etc etc

    Please provide a full debug log.

    How to post a log (wiki)

    1. Enable debugging in Settings>System Settings>Logging
    2. Restart Kodi
    3. Replicate the problem
    4. 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

    I managed to fix the problem last night.

    What seemed to happen caused by the power-outage was that LibreELEC reset some of the configuration - namely the set refresh rate for the graphical output.

    Already when I initially set up the system I had the problem that in my setup (with AVR in between projector) for some reason the default refresh rate of 60 leads to that behaviour (splash screen). Only after hooking up the NUC to a monitor (where it immediately works), then setting the output to a different refresh rate (this time I tried 59,x instead of 50 like the last time), it also works in the desired setup. I just forgot this, but searching the forum and finding my own thread reminded me.