Posts: 57
Joined: Jul 2011
Reputation:
1
2024-04-17, 21:40
(This post was last modified: 2024-04-18, 18:51 by HydroDiOxide. Edited 1 time in total.)
I'm running Kodi on a Series X with a shared library (advancedsettings.xml) on a RPi and the files on an NFS share. Since the auto update to Omega I can't scrape to my library. After adding the source trying to play any of the files crashes Kodi.
Any clues on how to fix this?
Posts: 57
Joined: Jul 2011
Reputation:
1
I figured out today that I'm having the same issues with Kodi on Windows. I can browse the NFS shares just fine, setting content works it just doesn't 'stick'. The initial db migration runs and MyVideos131 is present, but somehow there is no library in Kodi. Browsing using files does not lead to a crash as on my Xbox. Did something change in the way Mysql works? What am I missing here...?
Posts: 1,257
Joined: Apr 2010
Reputation:
92
CrystalP
Team-Kodi Developer
Posts: 1,257
Is the issue that you cannot add new videos to the library, or that the library was empty after migration from v20?
A debug log wouldn't hurt.
Posts: 57
Joined: Jul 2011
Reputation:
1
2024-04-21, 18:17
(This post was last modified: 2024-04-21, 19:03 by HydroDiOxide. Edited 3 times in total.)
Both actually. Even though I can see the db entries are there in MyVideos131. I'll post a debug.
debug:https://paste.kodi.tv/mibizuhiwi.kodi (did I do this the right way?).
Posts: 57
Joined: Jul 2011
Reputation:
1
2024-04-21, 20:18
(This post was last modified: 2024-04-22, 13:05 by HydroDiOxide. Edited 1 time in total.)
So I dropped both the 121 and 131 dbase after exporting my library in Kodi 20.5. Restarted 20.5 instance (Linux) and let it rebuild the library from local files. No issues there. Then I started Kodi 21 (Windows) and let it migrate the dbase. MyVideos131 is created, but there is no library in Kodi. Trying to open movies results in error about the path: remote share, path not found or invalid.
Posts: 1,257
Joined: Apr 2010
Reputation:
92
CrystalP
Team-Kodi Developer
Posts: 1,257
There are signs in the log that something went wrong in the migration to 131 and the database cannot be opened for normal use.
Please delete the 131 database and try the migration again, with Kodi in debug log mode so we can see what happens.
Posts: 57
Joined: Jul 2011
Reputation:
1
The obvious solution is to drop both 121 and 131 and start the Kodi 21 instance first (Windows, Xbox) and Kodi 20 (Linux) after that. So this is what I did. This creates a usable 131 and 121 database and everything runs fine on Xbox also.
The reason I'd rather use Kodi 20 is because my preferred skin, Pellucid, is not yet ported to Kodi 21.
