New Jellyfin Server/Web release: 10.9.6

New Jellyfin Server/Web release: 10.9.6 - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Announcements (https://forum.jellyfin.org/f-announcements)
+--- Forum: Project Announcements (https://forum.jellyfin.org/f-project-announcements)
+--- Thread: New Jellyfin Server/Web release: 10.9.6 (/t-new-jellyfin-server-web-release-10-9-6)

Pages: 1 2 3 4

RE: New Jellyfin Server/Web release: 10.9.6 - Moutaineer1024 - 2024-06-07

Hi Joshua, I really appreciate the work that you and all the other members of the team do on this project.

This:

(2024-06-06, 07:26 PM)joshuaboniface Wrote: For our Docker users, we now have additional tags you can use to more granularly pull the images! This applies both to Docker Hub and GHCR. Going forward, we'll be publishing tags like so:

latest, always tracks whatever the latest release is, including through major and minor version bumps
X (e.g. 10), tracks the latest in 10.y.z (which is our "major" version for the forseeable future) NEW
X.Y (e.g. 10.9), tracks the latest in 10.9.z minor, good for those who don't want to jump right to 10.10 later on but want the bugfix releases automatically NEW
X.Y.Z (e.g. 10.9.6), tracks the specific point release
X.Y.Z.YYYYMMDD-HHMMSS (e.g. 10.9.6.20240606-184155), tracks the specific packaging build, which in future might change for long-running stable releases to update dependencies and such, while still tracking the same Jellyfin code revision (i.e. vX.Y.Z tag)

Just broke my (and no doubt others) update script.
If I could offer some commentary, please consider putting the keyword in the tag name.
So you wouldn't just have X, you'd have X-MAJOR, or even just MAJOR.
Anyone tracking MAJOR likely doesn't care about it being X, only that it's always going to have the latest MAJOR in it.

If _I_ was doing the naming, I'd do this:
latest
major
minor
point
nightly-YYYYMMDD-HHMMSS
X.Y.Z

Everybody wins, and it's obvious what each one is.

RE: New Jellyfin Server/Web release: 10.9.6 - ZmgwsYzhM2nV - 2024-06-07

OK, I'm not sure when this problem started, but I guess it's with one of the last versions of Jellyfin. I use NFO files for my metadata, I mean I don't use scrapers, I make the files by hand. But now I noticed that if I make a change to the NFO file, it doesn't get picked up when I do a library scan. So for example, I have the following NFO file for a show's episode:

Code:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<episodedetails>

  <plot>whatever plot</plot>

  <lockdata>true</lockdata>

  <dateadded>2021-03-04 08:44:00</dateadded>

  <title>whatever title</title>

  <year>1992</year>

  <imdbid>whatever imdbid</imdbid>

  <showtitle>whatever showtitle</showtitle>

  <episode>1</episode>

  <season>1</season>

  <aired>1992-11-12</aired>

</episodedetails>

(This is with placeholders now just to show the structure...)

Any ideas? Bug with the latest version(s)?

RE: New Jellyfin Server/Web release: 10.9.6 - KodiUser1138 - 2024-06-08

Gave 10.9.6 a try installing. Hoped it would work well. Frank, did it work?

[Image: giphy.gif?cid=6c09b952nz2scr47nsoa7eh5jc...y.gif&ct=g]

[Image: giphy.gif?cid=6c09b952nz2scr47nsoa7eh5jc...y.gif&ct=g]

Was able to revert back to the working 10.9.3

RE: New Jellyfin Server/Web release: 10.9.6 - fredhags - 2024-06-08

Seems to me that 10.9.3 is the version to run for the moment.
But I can see that people are doing a good job hammering out the bugs.

RE: New Jellyfin Server/Web release: 10.9.6 - pavichokche - 2024-06-08

I think the devs are doing amazing work! On Windows I haven't had any issues yet! I only skipped 19.5 because it seemed problematic, but otherwise at least 10.9.2, 10.9.3, 10.9.4 and 10.9.6 have been good!

RE: New Jellyfin Server/Web release: 10.9.6 - sq1sz - 2024-06-10

After creating the media library, when you modify the name, an additional media library will appear, similar to an extra copy. In order to delete the extra media library, it does not appear in the media library management section, only showing up on the homepage and in the media navigation sidebar.

RE: New Jellyfin Server/Web release: 10.9.6 - RogerT - 2024-06-11

10.9.6 fixed my issues with problems from 10.9.5. Libraries appear to be updating and everything seems fine.
Working on Ubuntu Server 22.0.04, regular install. Great work guys.

RE: New Jellyfin Server/Web release: 10.9.6 - ZmgwsYzhM2nV - 2024-06-11

10.9.6 seems to completely ignore reading nfo files... when I add a new episode to a show, the info in the corresponding nfo file is not picked up. (I use handcrafted nfo files and don't use scrapers.)

Edit: for movies it still seems to work. My workflow or hosting didn't change, and if I recall correctly 10.9.3 was still fine in this respect, so something along the way prevents 10.9.6 from reading tv show nfo files...

Edit2: But then again, edits in a movie's nfo file also don't get picked up. Sigh...

RE: New Jellyfin Server/Web release: 10.9.6 - Iskelderon - 2024-06-11

For me, an old "friend" seems to be back.
These echoes of no longer existing paths happened when an item was moved and the references in collections or libraries weren't updated correctly.
This problem on Windows systems was fixed with 10.9.0, but somehow it's back and even the task to address this doesn't pick them up.

Code:
[2024-06-11 07:00:48.780 +02:00] [WRN] [38] MediaBrowser.Controller.Entities.BaseItem: Unable to find linked item at path "G:\Video_other\J\New Initial D the Movie - Legend 1 - Awakening (2014) [tmdbid-271709]\New Initial D the Movie - Legend 1 - Awakening - - In 2014, a new legend starts running.mkv"

[2024-06-11 07:00:49.782 +02:00] [WRN] [38] MediaBrowser.Controller.Entities.BaseItem: Unable to find linked item at path "E:\Video\Avatar The Last Airbender\Avatar - The Last Airbender (2005) [tmdbid-246] [imdbid-tt0417299]\S01\Avatar - The Last Airbender - S01E08 - Avatar Roku Winter Solstice (2).mkv"

RE: New Jellyfin Server/Web release: 10.9.6 - fromage9747 - 2024-06-11

Any chance this business of a movie getting removed from Continue watching going to get fixed? Really getting on my nerves. Tried setting it to only use a single thread to work around the database locked issue, but the issue remains. Running 10.9.6