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.