New Jellyfin Server/Web release: 10.11.1

[kaft]

You really should've taken more time and testing on these releases.

Its a major release with breaking changes, and you are not a small, selfhosted app anymore.

This project is free, we get a top notch alternative to paid projects like Plex (an even better alternative tbh), and the devs don't earn anything besides donations. Besides, this particular release included a major database change and it was posted all over the place that bugs were obviously expected with first releases. You can't expect a major change to not have bugs, specially when released to the general public with countless different setups. Being a big project now doesn't make them owe us anything. THis is a community project, if there are bugs, you should report them to help troubleshooting, telling the devs they should test their releases more before releases will only drag the project down (bugs reported by general users are key to the project's success). Like the previous post said, that was uncalled for.

Take it whatever you like..


My point still stands.. 
The project is now too big for these situations..

1-2 more botched updates and you will remember me.

[Graeme]

But they need to understand...

No, they really don't! They don't need to do anything. The developers working on this are volunteers. Giving their time, skills and experience freely. Equally, they are free to walk away the moment the work is no longer rewarding for them. They are not your employees. They have not sold you a product. They have given you a product freely and for free, and which you are free to use or not as you wish.

If you'd like to be able to demand certain features be added or bugs be fixed, then hire a developer to work on the project and pay them. You will then have some claim to tell that developer, and ONLY that developer what to do.

If you don't think that's fair then it's you that should walk away. Otherwise be part of the team. Make good bug reports, create issues on the github for things that need attention. Provide help here to users less experienced than you, in a friendly and collaborative manner. In short be part of the solution rather than part of the problem.

[Topomov]

You really should've taken more time and testing on these releases.

Its a major release with breaking changes, and you are not a small, selfhosted app anymore.

This project is free, we get a top notch alternative to paid projects like Plex (an even better alternative tbh), and the devs don't earn anything besides donations. Besides, this particular release included a major database change and it was posted all over the place that bugs were obviously expected with first releases. You can't expect a major change to not have bugs, specially when released to the general public with countless different setups. Being a big project now doesn't make them owe us anything. THis is a community project, if there are bugs, you should report them to help troubleshooting, telling the devs they should test their releases more before releases will only drag the project down (bugs reported by general users are key to the project's success). Like the previous post said, that was uncalled for.

Take it whatever you like..


My point still stands.. 
The project is now too big for these situations..

1-2 more botched updates and you will remember me.

Why don't you fork Jellyfin and show us how it's done if you don't like the way this project is being handled?

[raulo1985]

You really should've taken more time and testing on these releases.

Its a major release with breaking changes, and you are not a small, selfhosted app anymore.

This project is free, we get a top notch alternative to paid projects like Plex (an even better alternative tbh), and the devs don't earn anything besides donations. Besides, this particular release included a major database change and it was posted all over the place that bugs were obviously expected with first releases. You can't expect a major change to not have bugs, specially when released to the general public with countless different setups. Being a big project now doesn't make them owe us anything. THis is a community project, if there are bugs, you should report them to help troubleshooting, telling the devs they should test their releases more before releases will only drag the project down (bugs reported by general users are key to the project's success). Like the previous post said, that was uncalled for.

Take it whatever you like..


My point still stands.. 
The project is now too big for these situations..

1-2 more botched updates and you will remember me.

No, I will not remember you, because I have my backups as advised by the team countless times, and I willingly want to try and test a new release that is advertised everywhere is going to include a major db change (which anyone understands will initially have bugs). If you don't want to experience issues, stay on 10.10.7, nobody is forcing you to upgrade, and most of us prefer new releases to test new features even if they are not that polished.

And what's that about the project being big? If your project is an echo hello world! obviously you wont have bugs, JF on the other hand is a very complex piece of software. If you expect a free project, with devs working on their spare time, to be bug free on every release, even after major changes, then probably this is not the place for you. Support here is a lot better than what one could ask, literally for free.

Anyway, it's better to get back on topic, these last releases deserve threads that contribute to troubleshooting instead of just complaining (which, as you surely understand, doesn't solve any bug and doesn't help at all).

Take care.

[raulo1985]

After some issues, I managed to make my library work as expected (not a huge library, though). I would have recreated it from scratch to avoid migration issues, but I have many clients already set up and I don't have access to many of them (relatives that live far from where I am), so I needed to keep the db so they can still auto login. Idk if it will help anyone else, but this is what I did (involves some clean server installations, some libraries recreations and some library scanning):

General info / prerrequisites:

- I'm using Linux Mint 22.2 and I've always installed JF using apt or .deb packages (no Docker).
- I had a full 10.10.7 backup stored and secured.

Steps:

- Did a clean Linux Mint install (probably this step can be skipped)
- Purged my previous JF server if not installing the SO from scratch (sudo apt purge jellyfin jellyfin-server jellyfin-web jellyfin-ffmpeg7)
- Installed JF 10.10.7 using the .deb packages for Ubuntu 24.04.
- Restore the full backup (and keep it safe, in case anything goes wrong).
- Deleted all the "other" libraries, and also the music library (just kept the movies and collections libraries)
- Scanned those remaining libraries (movies and collections) to ensure the db is ok before migration.
- Made another backup before migration, just in case.
- In my case, installed libjemalloc2 and libicu70 dependencies before migration (libjemalloc2 can be installed using apt, for libicu70 I downloaded the .deb package for Jammy since Noble comes with libicu74). Both dependencies were not installed while trying to upgrade JF, the key was to install them before migration.
- Migrated using sudo apt install jellyfin
- Waited for migration to finish (looking at the new UI)
- Enter the dashboard using Firefox and check every setting is correctly set.
- Full scan the libraries again (movies and collections)
- Recreated the "other" and music libraries from scratch (and then scan / replace all their metadata).
- Took a new backup, which is the one I'll use in case something happens (and kept the 10.10.7 backup just in case I want to roll back). I guess you can use this backup to reinstall everything if you want to use another SO or Docker (the previous steps just allowed me to accomplish a succesful migration).
- That's it, JF works as well as 10.10.7, at least in my case. Collections are preserved, and I haven't experienced performance issues while using the UI or during playback.

My logic was to try to migrate the least of the db and recreate most of it from scratch to avoid possible migration issues. I kept the movies and collections libraries because I ran into all sorts of issues when migrating the database after deleting all the libraries (including movies and collections), specially whith collections. Keeping only the movies and collections libraries during migration and after a full rescan is what did the trick for me. After that, I recreated my other libraries, scanned them, and all is good now (took some hours for the scans to be completed, though).

Just my two cents.

[RostigerSpieler]

So performance has improved with this update, unlike the previous version.

However, there is still a bug in the search function. The search function cannot handle the following letters: Ä, Ü and Ö. As in the films Hexenjäger (Witch Hunter) or Hänsel und Gretel (Hansel and Gretel).

[ajohnson]


...
[07:47:19] [ERR] [7] InternalCodeMigration: Migration 20250420120000_MigrateDisplayPreferencesDb failed
Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: userdisplaypreferences'.
...

I too am getting the no such table userdisplaypreferences error with a crash loop.

I realized this was due to OOM. I restored from backup and increased resources (I gave it 6Gi with a limit of 8Gi) and the migration finished this time successfully