Arch Linux User Repository

jellyfin-desktop crashes perhaps 9/10 times for some users with no fix or workaround available, so I've decided to maintain the last known-working package of jellyfin-media-player (with gpu-acceleration re-enabled), as an option until jellyfin-desktop is fixed.

As of 2026/1/13 there is no fix in sight (upstream is probably busy fixing other things).

There will be no updates due to the nature of the direction of upstream, please keep that in mind. It will be removed (or ownership yielded) when jellyfin-desktop reaches a mature state of functionality.

@ada_1815, Unable to reproduce your issue. Working for me and several others of varying Arch/Arch-based installations.

Unfortunately, as of today it is broken. It shows a black screen and the following is spamming in console:

[49984:50055:0419/184224.364392:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_CONTEXT
[49984:50055:0419/184224.364409:ERROR:gpu_channel_manager.cc(753)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[49984:50055:0419/184224.364413:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[49984:50055:0419/184224.364419:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub

@zjeffer, The hash may have changed because the pathing changed (it's part of the first root directory in the tar.gz.) If I can validate the files inside with the current release then I'll consider the new hash.

Edit: They validated (only the root of the directory changed, thus the hash change). Adjusted PKGBUILD and .SRCINFO. Not bumping version as nothing's changed about the end release.

@zjeffer, The hash not matching is cause enough for me to disregard that source. This is a package maintained as a legacy option purely because the modern client has too many issues. That maintenance is to strictly provide the 1.12.0 package itself before jellyfin-desktop tweaks, but with the hardware-acceleration unbricked, nothing else. I'll be finding any host reasonably trustworthy that holds the old package file matching the exact SHA256 sum. The hash I used at the time was not wrong, so I'll be sticking to it.

@OdinVex Yeah I'm really confused that the hash changed after they moved the repo to jellyfin-archive/jellyfin-desktop-qt, I don't understand why that would happen. Although like @457r0, the hash was already wrong for a while.

To get that hash I simply manually downloaded https://github.com/jellyfin-archive/jellyfin-desktop-qt/archive/refs/tags/v1.12.0.tar.gz and then ran sha256sum on it.

What do you mean with 'checksum-valid responsible host'? Will you download the tar.gz from somewhere other than github?

@zjeffer, I won't be making those changes, especially since the hash is different. I'll find a checksum-valid responsible host for the tar.gz and only change the URI.

To fix the package install, make these changes:

diff --git a/PKGBUILD b/PKGBUILD
index b184089..2263cd9 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -7,28 +7,28 @@ pkgrel=6
 pkgdesc='Jellyfin Desktop Client - Legacy'
 arch=('i686' 'x86_64')
 license=('GPL')
-url='https://github.com/jellyfin/jellyfin-desktop'
+url='https://github.com/jellyfin-archive/jellyfin-desktop-qt'
 conflicts=('jellyfin-desktop')
 depends=('mpv' 'libcec' 'sdl2' 'p8-platform' 'protobuf' 'qt5-webengine' 'qt5-x11extras' 'qt5-quickcontrols')
 makedepends=('cmake' 'git' 'python')
-source=("https://github.com/jellyfin/jellyfin-desktop/archive/refs/tags/v${pkgver}.tar.gz"
+source=("https://github.com/jellyfin-archive/jellyfin-desktop-qt/archive/refs/tags/v${pkgver}.tar.gz"
         "disable-update-check.patch"
         "fix-cmake-4.patch"
         "fix-gpu-acceleration.patch")
-sha256sums=('036d841f6440806fd9f45cccf40223e5dd904ae09d508b29ef1b0583bd3d277e'
+sha256sums=('0bdc7a55289391cdc8329c7a9fead54a57a5c241345f651135443a8c0b592439'
             '2aef728dfdef17f089186d1a2b604837678fa896b4c299dd710b6f37d290aba0'
             '7ff8a15d9e9a7bc9a75bc9f0ee730408827827f6f6d564686ac9f9ca26525342'
             '837cee6d50d143a5f1d959741c26904d3ebd82053027c07bd725c0b871e1af2f')

 prepare() {
-    cd "${srcdir}/jellyfin-desktop-${pkgver}"
+    cd "${srcdir}/jellyfin-desktop-qt-${pkgver}"
     for patch_file in ../*.patch; do
         patch -Np1 < "${patch_file}"
     done
 }

 build() {
-    cd "${srcdir}/jellyfin-desktop-${pkgver}"
+    cd "${srcdir}/jellyfin-desktop-qt-${pkgver}"
     rm -rf build
     mkdir build
     cmake \
@@ -43,6 +43,6 @@ build() {
 }

 package() {
-    cd "${srcdir}/jellyfin-desktop-${pkgver}"
+    cd "${srcdir}/jellyfin-desktop-qt-${pkgver}"
     DESTDIR="${pkgdir}" cmake --install build
 }

Not sure whats going on here, but I get:

==> Validating source files with sha256sums...
    v1.12.0.tar.gz ... FAILED
    disable-update-check.patch ... Passed
    fix-cmake-4.patch ... Passed
    fix-gpu-acceleration.patch ... Passed
==> ERROR: One or more files did not pass the validity check!
error: failed to download sources for 'jellyfin-media-player-1.12.0-6': 

@maxlefou, Nvidia, I'm guessing? They always disabled hardware-acceleration by embedding --disable-gpu before. You can add --disable-gpu to start parameters. I don't cater to Nvidia.

Edit: Not saying that's the issue, just a guess. Merely maintaining this pre-JD version without the crippling disablement of hardware-acceleration for Intel/AMD users.

To me it's the contrary. Since this update, jellyfin media player shows a black window while jellyfin-desktop works like a charm...