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.

fwiw, propably redundant to mention this, but people should not install this. The current upstream project is jellium-desktop and the package is jellium-desktop-git thats built from the project repo for the foreseeable future.

@atriix, See the pinned comment.

Requires libvpx1.15 for libvpx.so.11

jellyfinmediaplayer: error while loading shared libraries: libvpx.so.11: cannot open shared object file: No such file or directory

@DrumSlayer, this is a legacy package, it won't receive any updates because there are no updates upstream, it's the last update there ever was and it's here purely for those it may still work for (such as myself and a few others I pretty much created this for).

Edit: It's probably unhelpful to mention I just did a clean compile of it and it works. Looks like a driver issue for you.

I do have the same exact issue as @ada_1815 jellyfinmediaplayer opens up a little black window , and console is spamming

[54313:54377:0427/171528.461667:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_CONTEXT
[54313:54377:0427/171528.461675:ERROR:gpu_channel_manager.cc(753)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[54313:54377:0427/171528.461680:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[54313:54377:0427/171528.476743:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub

GPU is RTX 3070 with proprietary nvidia driver if it can helps

It seems related to issue #842 on jellyfin-qt (legacy) https://github.com/jellyfin-archive/jellyfin-desktop-qt/issues/842

Thing is that the new jellyfin is absolutely broken on every PC i own, windows or linux, and i don't think the issue will be fixed on legacy jellyfin ;(

@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?