New Jellyfin Server/Web release: 10.11.1

[0xDEADC0DE]

Same here, too much problems yet with 10.11.x
Glad I had a backup of the 10.10.7 database

You are lucky. 
I read the upgrade notes. Made a backup of my VM and started the upgrade.
Then I realized, I took a VM backup of my Joplin VM, not Jellyfin.  
At least, the upgrade was working and I'm happy with 10.11.

[tomstephens89]

Metadata scanning for libraries is my biggest issue since updating, especially with music but overall the system is just slow at handling metadata now.

Anything to improve library scanning / metadata performance coming?

Can confirm, issues with new content importing/metadata scanning still happening in 10.11.1.

Some items appear in library under their filename, with various other episodes missing, until manual refresh.

I also done a full library delete and recreate after my update to 10.11.0 to rule out any historic 'baggage' causing problems.

I also had an issue where my music library which is split into two folders (both added in the library config) would not read the second folder. Logs showed only the first folder being watched.

[gaming09]

uncalled for, This team tries their best and you should be grateful these ppl dedicate their time. 

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.

[ajohnson]


[07:47:18] [INF] [7] InternalCodeMigration: Migration 20250420110000_ReaddDefaultPluginRepository was successfully applied
[07:47:18] [INF] [7] InternalCodeMigration: Perform migration 20250420120000_MigrateDisplayPreferencesDb
[07:47:19] [FTL] [7] InternalCodeMigration: Error: SQLite Error 1: 'no such table: userdisplaypreferences'.
[07:47:19] [ERR] [7] InternalCodeMigration: Migration 20250420120000_MigrateDisplayPreferencesDb failed
Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: userdisplaypreferences'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements()+MoveNext()
at Microsoft.Data.Sqlite.SqliteCommand.GetStatements()+MoveNext()
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader()
at Emby.Server.Implementations.Data.SqliteExtensions.Query(SqliteConnection sqliteConnection, String commandText)+MoveNext()
at Jellyfin.Server.Migrations.Routines.MigrateDisplayPreferencesDb.Perform()
at Jellyfin.Server.Migrations.Stages.CodeMigration.Perform(IServiceProvider serviceProvider, IStartupLogger logger, CancellationToken cancellationToken)
at Jellyfin.Server.Migrations.JellyfinMigrationService.InternalCodeMigration.PerformAsync(IStartupLogger logger)
at Jellyfin.Server.Migrations.JellyfinMigrationService.MigrateStepAsync(JellyfinMigrationStageTypes stage, IServiceProvider serviceProvider)
[07:47:19] [INF] [7] InternalCodeMigration: Attempt to rollback librarydb.
[07:47:19] [INF] [7] InternalCodeMigration: Attempt to rollback JellyfinDb.
[07:47:22] [FTL] [7] Main: Error while starting server
Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 1: 'no such table: userdisplaypreferences'.
at Microsoft.Data.Sqlite.SqliteException.ThrowExceptionForRC(Int32 rc, sqlite3 db)
at Microsoft.Data.Sqlite.SqliteCommand.PrepareAndEnumerateStatements()+MoveNext()
at Microsoft.Data.Sqlite.SqliteCommand.GetStatements()+MoveNext()
at Microsoft.Data.Sqlite.SqliteDataReader.NextResult()
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader(CommandBehavior behavior)
at Microsoft.Data.Sqlite.SqliteCommand.ExecuteReader()
at Emby.Server.Implementations.Data.SqliteExtensions.Query(SqliteConnection sqliteConnection, String commandText)+MoveNext()
at Jellyfin.Server.Migrations.Routines.MigrateDisplayPreferencesDb.Perform()
at Jellyfin.Server.Migrations.Stages.CodeMigration.Perform(IServiceProvider serviceProvider, IStartupLogger logger, CancellationToken cancellationToken)
at Jellyfin.Server.Migrations.JellyfinMigrationService.InternalCodeMigration.PerformAsync(IStartupLogger logger)
at Jellyfin.Server.Migrations.JellyfinMigrationService.MigrateStepAsync(JellyfinMigrationStageTypes stage, IServiceProvider serviceProvider)
at Jellyfin.Server.Migrations.JellyfinMigrationService.MigrateStepAsync(JellyfinMigrationStageTypes stage, IServiceProvider serviceProvider)
at Jellyfin.Server.Migrations.JellyfinMigrationService.MigrateStepAsync(JellyfinMigrationStageTypes stage, IServiceProvider serviceProvider)
at Jellyfin.Server.Program.StartServer(IServerApplicationPaths appPaths, StartupOptions options, IConfiguration startupConfig)

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

[kaft]

uncalled for, This team tries their best and you should be grateful these ppl dedicate their time. 

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.

No, not really

I appreciate their efforts. 

But they need to understand that Jellyfin is now too big. Its not a pet project.

And no, being FOSS software doesnt mean everything is forgiven or there arent any procedures.

[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.

[SP Loomis]

I thought I'd add my tuppence worth here.

I have been using, on and off, Jellyfin for a few years. Previously it was Emby then Plex but those I eventually dropped. You can imagine the reasons for that. My collection serves my children, other family and friends and is normally available 24/7 less the short time for a scripted backup once per week.

My main system currently runs on a properly configured N100 mini PC running under linux with attached 4x20TB drives. It also hosts an ancient but serviceable Subsonic server for audio. If it ain't broke....? My backup server is an i9 mini PC running under Windows 11 Pro with an attached DAS. The systems rsync every few days via a script and Tailscale. The latter is Windows as, at my age, long retired and having been in IT (what used to be called data processing and networking) for forty odd years, I could croak it at any time and none of my family or associates have the slightest knowledge of linux or that black screen thing. Mind you, they're not so hot with Windows either and they wonder why I have used, for years, a MacBook for daily personal use.

Jellyfin has provided me with few problems, in part with regards to the linux box, as it is run bare metal assisted by various Cloudflare bits.That one updated itself overnight when 10.11.1 was released. I didn't even notice the upgrade for more than a day even although it was constantly being used from three countries. No problems, at all, except per library scanning seems a bit problematic and my LG OLED TV pops with 'out of memory' warnings although the cheap bedroom TCL has yet to throw a wobbler. The LG thing matters little as I normally use an Nvidia Shield Pro box which has carried on regardless. No doubt these foibles will be rectified in time. After all, it is version .1.

I thank all of the developers who give their time to the Jellyfin project and the contributors who are willing to share their experiences but there seems to be an annoying number of detractors who fail to consider that this is not a commercial project, some even have the gall to compare with Plex where there is, it fact, little to no comparison. If you want to be spied on, your info harvested, blinded by all sorts of nonsense and, dare I say, pay through the teeth, on you go, Plex is your boy. 

I get the feeling that many have played around with all sorts of containers, even containers within containers and containers within VMs. That being the case, it's a 'workshop' fool around system not one for production and hence more than liable to exhibit problems for literally endless reasons including the clear fact that some commentators obviously have little system knowledge but have elected to go for the most obtuse configurations and wonder why it inevitably goes pop if it ever works at all.

People have to learn so they firstly make mistakes and ask for guidance but it seems that many refuse to read the notes, writeups, articles, etc before delving in. They seem to demand 100% success first time. Where's the fun in that? One learns from failure, seldom from success.

A good example of those last two paragraphs is struggling to use Jellyfin within a container within Proxmox and then screaming that they can't get hardware acceleration to work on their seven(teen?) year old system with 2G RAM (and maybe a 5.25 inch floppy!). Maybe like the one angry user with some esoteric, unaccredited and not recommended version of linux with Jellyfin, in a container within Docker in a VM under Proxmox and more than obviously with little to no knowledge of using the command line, moaning that wireless doesn't work, the CPU burning at 100%, video stuttering and probably black smoke everywhere and blaming it all on Jellyfin. Likewise those who complain that it just won't go on their ten year old Raspberry Pi and wonder why. Not that they have done any reading.

If you want a media system, follow the rule of KISS. It always works ....eventually and on the way, you've picked up a few experiences whereby you can assist others. If you prefer some hybrid monster, well done but that's all of your eggs in one creaking basket.

[zx1970]

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.

Hello All,
I just register to add one comment, here it is : As I understand the principles of release/bugs/solving cycle in the small microcosm of open-source, once you become a largely distributed solution working for millions of users, you have to take care of the publicity and rumors when you release a new version. Your solution is now at a point where it grows because reliable or it fails because bugs making an average user not able to see his/her favorite movie tonight. If it fails, he/she will simply change of solution and never go back.
BR

[Shaun Finnerty]

zx1970 im sorry but i just cant agree. i really dont like this kind of black and white thinking that always comes up in these discussions. i do get that people get frustrated when an update breaks stuff, esp when you just wanna sit down and watch a movie, but we gotta be realistic about it.

every bit of software out there, no matter how big or how much money behind it, has had breaking changes or buggy releases. thats just how software works when its being improved or rebuilt. this isnt unique to this project, even the huge paid ones go through the same thing.

and while yeah its fair to expect some level of stability, its just not realistic to expect a bunch of volantier devs to run things like a massive company with full qa teams and test systems. these devs do this for free in their own time, and the progress depends on the community giving feedback and reporting bugs after a release, not just complaining about them.

there also needs to be some responsability on users too. keep backups, understand theres always some risk when upgrading, if this application is critical for you then you should be testing the upgrade in a vm or another docker container, if you are working on bare metal accept the risk that this might happen to youif something goes wrong. Peeople really need to report it so it helps the project. thats how open source stuff gets better.

so yeah, i get people being annoyed, but this kind of project only keeps growing if people help each other out instead of just pointing fingers.

[RogerT]

Just performed the update on 2 systems, both updated without issues, Be a day or 2 to see if anything pops up, but so far looks great!
Thanks to all the developers for the hard work! It is appreciated.