New Jellyfin Server/Web release: 10.11.8

[solosuono]

I'm also having problems with collections. I just refreshed, and the collections page is blank. If I wait a minute, they appear, but if I open it again, they disappear. There must be a bug.

[Alessandro Rossi]

I have upgraded from 10.11.6 to x.7 and then x.8 but I just noticed that after the update I cannot play anymore several movies in mkv not starting due to HLS (HTTP Live Streaming) error, so apparently related to the fMP4?
Hardware acceleration is off, and restoring the 10.11.6 from clonezilla backup, it works ok. I may try to upgrade again to see if it was something broken due to the migration. Also I may consider to install Jellyfin as docker instead of standalone app, to avoid that it's upgraded automatically when I update Ubuntu.

PS: tested with docker and everything with last version 10.11.8 is fine so I have removed the apt version.

[Kandy]

I'm also having problems with collections. I just refreshed, and the collections page is blank. If I wait a minute, they appear, but if I open it again, they disappear. There must be a bug.

It's a known and documented issue. It'll be fixed in 12.0.

[PlsFixWebOS]

Is there any chance we will get a patch fixing DV playback on WebOS soon? Profile 8.1 is completely broken since 10.11.x and it was/is working fine with version 10.10.x
I really don't want to keep running software with serious security issues just to get basic functionality that got broken with the new version

[abpjf]

At this point I'd rather subject myself to the barely-functional iteration (x.7) that's at least allowing me to play content rather than faff around with more piecemeal "fixes" and introduce god-knows-what-else eldritch abominations lurking in the code.

And Devs should just STOP with the whole "upgrade/update is Required" directives going forward - or even contemplating new code bases that would require such ever again. If a bullet-proof release can't be guaranteed, then don't release anything at all.

While I can appreciate the whole "let's get off a security-compromised version" - let's also be a bit realistic about our own perceived threat surfaces.

I'm sure I don't speak for everyone here, but ffs it's a media server. Given that I run mine on segregated machine(s) to begin with, I could care less what erstwhile bad actor(s) can/would do to/with the host server or the NAS it's connected to. Have at it. Whatchoo gonna do, delete all the Movies? Steal the login credentials? Whoopdeedo! Knock yourself out.

[CRHISTOPHER2222 DIAZ]

Why does Jellyfin consume so much CPU to load the home screen?

[linuxgaming]

At this point I'd rather subject myself to the barely-functional iteration (x.7) that's at least allowing me to play content rather than faff around with more piecemeal "fixes" and introduce god-knows-what-else eldritch abominations lurking in the code.

And Devs should just STOP with the whole "upgrade/update is Required" directives going forward - or even contemplating new code bases that would require such ever again. If a bullet-proof release can't be guaranteed, then don't release anything at all.

While I can appreciate the whole "let's get off a security-compromised version" - let's also be a bit realistic about our own perceived threat surfaces.

I'm sure I don't speak for everyone here, but ffs it's a media server. Given that I run mine on segregated machine(s) to begin with, I could care less what erstwhile bad actor(s) can/would do to/with the host server or the NAS it's connected to. Have at it. Whatchoo gonna do, delete all the Movies? Steal the login credentials? Whoopdeedo! Knock yourself out.

This people... take heed to some common sense.

[metropical]

all good here. 2018 i7 Mac mini. Media on external MacPro3,1.

[trooper]

Upgraded from v10.10.7 to v10.11.8 a couple of weeks ago, the process was smooth. This new release solved the few known issues I had with my setup, and I couldn't find any problem following the operation.

[PJ R.]

At this point I'd rather subject myself to the barely-functional iteration (x.7) that's at least allowing me to play content rather than faff around with more piecemeal "fixes" and introduce god-knows-what-else eldritch abominations lurking in the code.

And Devs should just STOP with the whole "upgrade/update is Required" directives going forward - or even contemplating new code bases that would require such ever again. If a bullet-proof release can't be guaranteed, then don't release anything at all.

While I can appreciate the whole "let's get off a security-compromised version" - let's also be a bit realistic about our own perceived threat surfaces.

I'm sure I don't speak for everyone here, but ffs it's a media server. Given that I run mine on segregated machine(s) to begin with, I could care less what erstwhile bad actor(s) can/would do to/with the host server or the NAS it's connected to. Have at it. Whatchoo gonna do, delete all the Movies? Steal the login credentials? Whoopdeedo! Knock yourself out.

Your attitude stinks.  There is no such thing as bullet-proof software.  You definitely don't speak for everyone.  Security is a very real priority for others so you can rant all you want about not caring re:security.  I did not notice any issues with 10.10.7 or 10.10.8.  These "zero-day issues" you describe do not affect everyone.