v1.12.0 - Bugfix Release

[iwalton3]

This version fixes a bunch of bugs and removes the obsolete third party plugin for intro skipping.

Changes:

• Prevent issue where wayland has black screen due to broken gpu accel (Black screen with Wayland (Sway) #165, Black screen in Wayland Fedora 39 #610)
• Prevent SRT text being squished and unreadable ([Bug] Subtitles format bugged when loaded automatically #643)
• Handle server connection timeout. (Cannot connect to any server if cannot connect to previously logged in server #747)
• Remove obsolete skip intro support.
• Update branding
• Fix caching issues to prevent broken web client when the server web version updates
• Auto fill last used server into server box if server connection fails on startup
• Fix SSL certificate verification issues on Linux

About Windows Downloads:

• The desktop installer requires administrator rights.
• You can avoid warnings on files by unblocking the file in the properties dialog.
• You can manually build a release using these instructions.

---

This discussion was created from the release v1.12.0 - Bugfix Release.

[jimmyjoeoneleg]

3 clean windows 10 systems, error 0x0000143 Uninstalled, and reinstalled, same. Uninstalled, re-downloaded older version, back online. Thanks for the missing hour... Not ready for the public release... Only reason I installed was it wanted to update. May want to consider disabling that feature until some knows what they are doing...

[makanimike]

same. 1.12.0. will not launch on my Windows 10 PC. I get a 0x0000142 error though.
Downgraded back to 1.11.1 for the time being.

[iwalton3]

The x64-legacy build which was just added should fix this error. It happened because the version of MPV we upgraded to for the main x64 build doesn't support CPUs without the following instructions:

avx avx2 bmi bmi2 fma lzcnt movbe sse3 sse4 sse4.1 sse4.2 ssse3 xsave sahf mwait crc32 cx16 popcnt f16c

[xxzandy]

Any possibilities to create Windows installer that would detect the CPU. I have multiple Haswell, Broadwell, Skylake, Kabylake -era computers with Jellyfin player.

[simonhowson]

Any possibilities to create Windows installer that would detect the CPU. I have multiple Haswell, Broadwell, Skylake, Kabylake -era computers with Jellyfin player.

I second this suggestion. I tried installing the regular Windows version onto a Microsoft Surface Go tablet with a Pentium Gold 4415Y processor that was introduced in 2017 - a lot later than 2013 - but it did not work.

There should be one Windows installer that installs the correct files based on CPU support. I had to uninstall the regular Windows version then install the Legacy version which was not a great user experience when using this application on the first day.

[laska140493]

Yup, same for me on Windows 11 24h2 PC

[iwalton3]

The x64-legacy build which was just added should fix this error. It happened because the version of MPV we upgraded to for the main x64 build doesn't support CPUs without the following instructions:

avx avx2 bmi bmi2 fma lzcnt movbe sse3 sse4 sse4.1 sse4.2 ssse3 xsave sahf mwait crc32 cx16 popcnt f16c

[kofzhanganguo]

Rec.2025-03-21.08.22.40.mp4

After opening the software, it reports a d3dcompiler_47.dll error. The version used is JellyfinMediaPlayer-1.12.0-windows-x64-legacy. Because the JellyfinMediaPlayer-1.12.0-windows-x64 version cannot run, my CPU model is relatively old and I cannot use the JellyfinMediaPlayer-1.12.0-windows-x64 version. However, after opening the JellyfinMediaPlayer-1.12.0-windows-x64-legacy version, it reports a d3dcompiler_47.dll error. However, after clicking OK on the error, it can be used normally. Every time you open the software, it will report that d3dcompiler_47.dll cannot locate the program input point.

[Solar040]

Any chance of the flatpak version getting an update?

[iwalton3]

Okay the actual issue is flathub sometimes manually holds up application publish jobs indefinitely. You'll note the publish job claims to be successful on that page but if you look closer it says it isn't actually published.

https://buildbot.flathub.org/#/builders/2/builds/88726
https://docs.flathub.org/blog/improved-build-validation

To bypass this in the mean time, install from the test repo using this command:

flatpak install --user https://dl.flathub.org/build-repo/171540/com.github.iwalton3.jellyfin-media-player.flatpakref

Note that the test builds don't get automatic updates and will eventually expire. If this is a long term issue I'll throw a copy of the build in a more stable location.

[ImCannibal]

looks like the test repo is busted too

[iwalton3]

New test build:

flatpak install --user https://dl.flathub.org/build-repo/171540/com.github.iwalton3.jellyfin-media-player.flatpakref

[Solar040]

Ah well thanks. Its finally through onto Flathub now, however attempting to play anything just results in the application quitting for whatever reason.

[gregi4414-a11y]

[johnleejg]

HDR content being played as if unsupported (washed out colors) with the latest update on Apple Silicon

[igotcha]

can not use by macOS 12.7.2

[iwalton3]

The macos 12 runner on GitHub Actions is discontinued so I can only build for 13 and newer.

[igotcha]

Unfortunately, my MacBook Pro is too old to be upgraded to 13.

[quinndiggity]

Unfortunately, my MacBook Pro is too old to be upgraded to 13.

@igotcha , could consider using OpenCore; just in case you were unaware of the project

[thoja21]

@iwalton3 Can we update the release notes to reflect this?

[dzaqwan]

How do I skip intro now? It did work perfectly on previous version

[r1kaj]

Jellyfin started to officially support media segments in v10.10. You have to enable the skip button in your client settings and install the intro-skipper plugin.

[ursmilesopretty]

Hello, I am having issue with the mac client.
My setup is the server is on a linux machine on my home network, my mac client is also on my home network.
I am able to connect on the mac via the web UI, but for the media player client, I can only select my server, the log in would fail and "quick connect" is also unavailable.
Is there some hidden network setting on mac that causing this? or there are some problem with the client itself? Thanks

[Aviatorpaal]

Yay! Now 10-bit HDR/Dolby Vision is displayed correctly when direct streaming to a MacOS Apple Silicon M3 Pro Macbook Pro. All the content was overexposed earlier, even without transcoding to SDR

[TharinduLakshanKumara]

Installed the compiled .deb for Noble Numbat with apt and I have no sounds playing on any of the videos. Videos play fine but with no audio.

[Kavey78]

I'm still able to use with Debian Trixie, but reliability is waning. Playing videos is usually fine, but attempting to change my place in the timeline can start some visual glitches. Also sometimes playing multiple videos in a row (say like a series) sometimes the next video will have severe visual glitches impeding viewing the video. Sometimes audio will cut out. Same can be true of pausing videos, especially for lengthy periods. Restarting the app can help, but can be annoying when at the end of a file that the system thinks is close enough to the end to be considered over and I have to find my place again.

I really like having the desktop client which is compatible with the vast majority of my files so it can stream directly vs. the web client which is pretty compatible but sometimes needs to covert audio or video for one reason or another.

I tried compiling from source to see if that would improve, but using the instructions provided failed. It worked in prior debian releases.

I've tried clearing the software cache and resetting jellyfin-media-player, but the glitches just appear to be part of the current overall environment.

Any chance of getting an official update? Especially with the new server preparing for release?

[sydbat]

LM 22.2

Similar to Kavey78, but somewhat different. I can access and play everything from the server on "remote" machines running JMP or Android clients (phone, laptop, other networked computers, or in Firefox) but have trouble playing just about anything on the computer that runs the Jellyfin server. Sometimes I get lucky and can play music or movies or TV shows. Other times I get the error box saying nothing can play, or I can play a video, but there is no sound. This is frustrating.

Also, will there be a new version of JMP when the next version of the server comes out? This might solve my issues and other peoples too.

[Kavey78]

I did try the flatpak which I normally don't deal with, but in this case it did seem to solve most of my playback issues, but did introduce new issues such as the mouse cursor being tiny. (I run my main system on a 50in TV). I've tried every suggestion I can find for debian xfce flatpak, and nothing seems to change the size of the mouse cursor. However I'm happy to continue using it as long as it resolves my other issues as playback is my main function for this system.

[Kavey78]

Unfortunately this may have introduced an audio popping glitch which I can only guess might be the result of the sandboxing that flatpak does that does not appear in other applications now. For a full picture, this system is a desktop with proxmox with the nvidia graphics card passed through to the main VM which connects to my TV via HDMI for video and audio. It's taken a while to get a configuration that is working as expected. This just throws a new wrench into it.

[CathodeRayTubeAutist]

so i get this error and it spams me with it until l i kill the jellyfin with task manager. im using a x64 windows 8. cpu is core 2 duo. Legacy x64 version of jellyfin is installed.

[Rand0mB0y]

so i get this error and it spams me with it until l i kill the jellyfin with task manager. im using a x64 windows 8. cpu is core 2 duo. Legacy x64 version of jellyfin is installed.

I have the same exact issue, but on a Win 10 i7 8th gen CPU. After researching online, some people suggest that it may be due to obsolete DirectX (and the only way to update the DirectX is via Windows update... my Win version is pretty old, and I want to leave it that way for now)... OR, instead, it could be that JellifinMediaPlayer is using some mixing objects that were built with different platform toolsets (different C++ redistributables),I have quite a few Microsoft Visual C++ versions installed. So maybe the software is not correctly fully using the C++ 2015-2022 redist?

The earlier client version (JMP v1.11.1) is still rock solid, though.

[DaaNMaGeDDoN]

Not sure if this is the right place, but i have reason to believe something is off with the version that is currently in https://repo.jellyfin.org/files/client/jellyfin-media-player/debian/stable/release/ used by extrepo (permalink) compared to this latest release here:

1. install the latest release mentioned here for Debian Trixie (https://github.com/jellyfin/jellyfin-media-player/releases/tag/v1.12.0 , asset: jellyfin-media-player_1.12.0-trixie.deb )
2. adding the jellyfin repo through extrepo.
3. apt update, apt says there is a new version available for jmp, upgrade jmp.
4. noticed different behavior: the ignoreSSLErrors setting is ignored after this. This makes me think the extrepo url holds a different release. jellyfinmediaplayer --version does however show the same version number for both. Also i noted the release here installs more dependencies than the one obtained via extrepo. This can also be seen during step 3, when apt says there are dependencies that are no longer required. Not removing those dependencies after installing the "extrepo upgrade" does not fix my issue, but gives less errors (apart from the SSL error) when starting jmp from the command line. Obviously the SSL error is still present when using the release here, but the client continues to connect, which made me conclude the difference in behavior towards the setting.

The fact that this particular client doesnt accept my server cert is a different issue. I have been successful adding&trusting the (self-signed) ca on several clients without issues. Date&time on client is correct, ca imported in FFesr works as expected, openssl s_client -showcerts -connect mydomain.tld:8920 shows the server cert is verified by the imported ca. I got the feeling it has to do with the localization settings of that specific client, but was unable verify, a fresh Debian Trixie on the same machine with different (EN-us) localization presents the same issue. But, as mentioned, at least this release here does respect the ignoreSSLErrors setting so i can work around that for now. If anybody has an idea, i would love to hear that. I must have missed something here.

Anyhow, thank you for all the great work you all have been doing, the extrepo page said to report issues here first, but i went ahead and created an account anyway to report a different issue with the same yaml, i am awaiting approval for the account. I'll make sure to refer to this post in my future communication with the maintainer, Juri Grabowski.