For those who want to reproduce the "null name".
I was able to get such broken state on an unstable server with Skia update (the one that crashes).
When you create a library, the server creates a folder for it (in /data/root/default/) and crashes. We see the new library, but it has no id (="null name").

Btw, #1012

Ran into this as well using the latest unstables (10.9.0, build version 2024041505) after upgrading my instance from 10.8.13 (and previous versions).

The issue was that the Path entries in the TypedBaseItems table of the library.db for each library did not match the actual filesystem paths.

My data is in /srv/jellyfin, with a symlink from /var/lib/jellyfin to /srv/jellyfin, which seemed to be enough in 10.8.z. But this resulted in TypedBaseItems entries that looked like this:

sqlite> SELECT Path FROM TypedBaseItems WHERE Path LIKE '%/jellyfin/root/default/%';
/var/lib/jellyfin/root/default/Collections
/var/lib/jellyfin/root/default/Movies
/var/lib/jellyfin/root/default/Music
/var/lib/jellyfin/root/default/Shows
/var/lib/jellyfin/root/default/YouTube

I suspect due to having the data directory path configured wrong when initially setting up the libraries.

Manually updating these DB entries to the correct paths corrected the issue (i.e. UPDATE TypedBaseItems SET Path='/srv/jellyfin/root/default/Collections' WHERE Path='/var/lib/jellyfin/root/default/Collections; et al.). I no longer get the "null name" error and library settings save correctly.

At this point in the release cycle, I think this is probably an esoteric enough issue to leave as-is for now. We should definitely improve the error handling portion, but the actual bug we'll have to evaluate after release to see if it's majorly affecting people and fix it if so.

Ran into this as well using the latest unstables (10.9.0, build version 2024041505) after upgrading my instance from 10.8.13 (and previous versions).

The issue was that the Path entries in the TypedBaseItems table of the library.db for each library did not match the actual filesystem paths.

My data is in /srv/jellyfin, with a symlink from /var/lib/jellyfin to /srv/jellyfin, which seemed to be enough in 10.8.z. But this resulted in TypedBaseItems entries that looked like this:

sqlite> SELECT Path FROM TypedBaseItems WHERE Path LIKE '%/jellyfin/root/default/%';
/var/lib/jellyfin/root/default/Collections
/var/lib/jellyfin/root/default/Movies
/var/lib/jellyfin/root/default/Music
/var/lib/jellyfin/root/default/Shows
/var/lib/jellyfin/root/default/YouTube

I suspect due to having the data directory path configured wrong when initially setting up the libraries.

Manually updating these DB entries to the correct paths corrected the issue (i.e. UPDATE TypedBaseItems SET Path='/srv/jellyfin/root/default/Collections' WHERE Path='/var/lib/jellyfin/root/default/Collections; et al.). I no longer get the "null name" error and library settings save correctly.

This is super duper weird. I just looked at the code and the returned library info is indeed derived from the stored library path, and will be incomplete if the path does not match. The problem is, such matching mechanism is very, very old and is actually emby code. I have no idea why this ever worked in 10.8. My guessing is that this could be a migration issue that the path is updated wrong, but it is only guessing.

Agreed there, not sure how it worked fine before. I think we can leave the fix pending for 10.9.1 and see if we really need it based on real-world reports after 10.9.0 drops.