Package Details: jellium-desktop-git 0.r1025.f224a4b-1

Git Clone URL: https://aur.archlinux.org/jellium-desktop-git.git (read-only, click to copy)
Package Base: jellium-desktop-git
Description: A Jellyfin Desktop Client
Upstream URL: https://github.com/andrewrabert/jellium-desktop
Licenses: GPL-2.0-only
Conflicts: jellium-desktop
Provides: jellium-desktop
Submitter: nvllsvm
Maintainer: nvllsvm
Last Packager: nvllsvm
Votes: 24
Popularity: 2.43
First Submitted: 2026-07-17 22:49 (UTC)
Last Updated: 2026-07-17 22:49 (UTC)

Latest Comments

1 2 3 4 5 Next › Last »

dsingal commented on 2026-09-27 05:36 (UTC)

Startup hangs at CefInitialize because Chrome's Linux first-run EULA dialog is never shown. The fix is https://github.com/andrewrabert/jellium-desktop/pull/714

LeGmask commented on 2026-09-26 10:26 (UTC)

I cannot launch the app anymore:

❯ jellium-desktop
[Main] jellium-desktop 0.1.0-dev+14dc084
[Main] CEF 152.0.6+g708dc14+chromium-152.0.7977.83
[Main] Display backend: wayland
[Main] proxy listening on wayland-2
[Main] app_display: connected -> 0x55c0e60045f0
[Main] scale seeded from the output probe: 1
[MpvProxy] get_toplevel: capturing app root surface
[Main] decorations: compositor set ServerSide
[Main] root window: first configure 1708x1408 (app toplevel is live)
[Main] [FLOW] mpv handle initialized in 3 ms
[Main] CEF layers parented under app root
[MpvProxy] get_xdg_surface: demoting mpv surface server_id=Some(8)
[MpvProxy] spliced mpv under host-root surface
[jfn_linux_util::dmabuf_probe] dmabuf probe: testing on Wayland EGL display
[jfn_linux_util::dmabuf_probe] dmabuf probe using render node: /dev/dri/renderD128
[jfn_linux_util::dmabuf_probe] dmabuf probe: GBM -> EGL -> GL import OK
[jfn_wayland::lifecycle] paint: EGL/GBM dmabuf shared texture
[Main] Platform init ok
[jfn_gpu_paint::context] gpu_paint: device init failed: no usable adapter available
[Main] shell overlay unavailable: shell has no usable GPU adapter

Does anyone have an idea on how to fix this?

Delivator commented on 2026-09-16 08:29 (UTC) (edited on 2026-09-16 08:59 (UTC) by Delivator)

Doesn't build for me anymore (did before). Getting this error now:

error: linker `x86_64-linux-gnu-gcc` not found
  |
  = note: No such file or directory (os error 2)

Seems to be a cachyos thing. Linking the compiler to the expected path fixed the build for me sudo ln -s /bin/x86_64_v4-linux-gnu-gcc /bin/x86_64-linux-gnu-gcc

Another issue I had was that the window would just be blank/show an infinite loading icon. A workaround seems to be to launch it in x11 mode first, accept the chromium eula and then launch normal again. jellium-desktop --platform x11:

https://github.com/andrewrabert/jellium-desktop/issues/671

red-lichtie commented on 2026-08-23 12:18 (UTC)

When trying to click on a link (IMDB) on actor information, there is a crash in kde-open:

systemd-coredump[706453]: [🡕] Process 706450 (kde-open) of user 1000 dumped core.

                                               Stack trace of thread 706450:
                                               #0  0x00007f0bb88b7a0c n/a (libQt6WaylandClient.so.6 + 0xd7a0c)
                                               #1  0x00007f0bb8c43db6 n/a (libffi.so.8 + 0x8db6)
                                               #2  0x00007f0bb8c3fa6d n/a (libffi.so.8 + 0x4a6d)
                                               #3  0x00007f0bb8c42e32 ffi_call (libffi.so.8 + 0x7e32)
                                               #4  0x00007f0bb87d47cd n/a (libwayland-client.so.0 + 0x47cd)
                                               #5  0x00007f0bb87d56b9 n/a (libwayland-client.so.0 + 0x56b9)
                                               #6  0x00007f0bb87d5aeb wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x5aeb)
                                               #7  0x00007f0bb87d9670 wl_display_dispatch_queue_timeout (libwayland-client.so.0 + 0x9670)
                                               #8  0x00007f0bb87d9740 wl_display_dispatch_queue (libwayland-client.so.0 + 0x9740)
                                               #9  0x00007f0bb87d982c wl_display_roundtrip_queue (libwayland-client.so.0 + 0x982c)
                                               #10 0x00007f0bb8862e9a n/a (libQt6WaylandClient.so.6 + 0x82e9a)
                                               #11 0x00007f0bb88fd18a n/a (libqwayland.so + 0x218a)
                                               #12 0x00007f0bbddacbac _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt6Gui.so.6 + 0x1ac>
                                               #13 0x00007f0bbddae228 _ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt6Gui.so.6 + 0x1ae228)
                                               #14 0x00007f0bbd589175 _ZN23QCoreApplicationPrivate4initEv (libQt6Core.so.6 + 0x189175)
                                               #15 0x00007f0bbddae32b _ZN22QGuiApplicationPrivate4initEv (libQt6Gui.so.6 + 0x1ae32b)
                                               #16 0x00007f0bbe6fe876 _ZN19QApplicationPrivate4initEv (libQt6Widgets.so.6 + 0xfe876)
                                               #17 0x00005582fb0b6192 n/a (kde-open + 0x5192)
                                               #18 0x00007f0bbcc27781 n/a (libc.so.6 + 0x27781)
                                               #19 0x00007f0bbcc278b9 __libc_start_main (libc.so.6 + 0x278b9)
                                               #20 0x00005582fb0b7235 n/a (kde-open + 0x6235)

                                               Stack trace of thread 706451:
                                               #0  0x00007f0bbcca0952 n/a (libc.so.6 + 0xa0952)
                                               #1  0x00007f0bbcd11a57 ppoll (libc.so.6 + 0x111a57)
                                               #2  0x00007f0bbc7c6f59 n/a (libglib-2.0.so.0 + 0x63f59)
                                               #3  0x00007f0bbc7c7055 g_main_context_iteration (libglib-2.0.so.0 + 0x64055)
                                               #4  0x00007f0bbd89d0b2 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFla>
                                               #5  0x00007f0bbd591983 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x19198>
                                               #6  0x00007f0bbd6b9342 _ZN7QThread4execEv (libQt6Core.so.6 + 0x2b9342)
                                               #7  0x00007f0bbd36c7d1 n/a (libQt6DBus.so.6 + 0x397d1)
                                               #8  0x00007f0bbd7784fb n/a (libQt6Core.so.6 + 0x3784fb)
                                               #9  0x00007f0bbcc980a2 n/a (libc.so.6 + 0x980a2)
                                               #10 0x00007f0bbcd2080c n/a (libc.so.6 + 0x12080c)
                                               ELF object binary architecture: AMD x86-64

Version Info:

$ pacman -Qi jellium-desktop-git 
Name            : jellium-desktop-git
Version         : 0.r1137.28f2cf1-1

$ pacman -Qi plasma-desktop 
Name            : plasma-desktop
Version         : 6.7.4-1

dramm commented on 2026-08-13 23:29 (UTC)

@nvllsvm Thank you for the clarification.

nvllsvm commented on 2026-08-13 18:32 (UTC)

@dramm Jellium Desktop was intended to become Jellyfin Desktop v3.0 before I moved it out of the Jellyfin organization and renamed to JellIUM Desktop.

I'm not in contact with the Jellyfin organization but it appears they are trying to resurrect the legacy Qt-based Jellyfin Desktop v2.0 code base. I'm not affiliated with that effort at all.

dramm commented on 2026-08-13 16:52 (UTC) (edited on 2026-08-13 16:54 (UTC) by dramm)

@nvllsvm Could you link to where they stated that jellyfin-desktop is no longer an official Jellyfin project? I understand the last release was a good while ago, but their website still lists jellyfin-desktop as their official client (https://jellyfin.org/downloads/clients). Edit: Also, as of this moment, the last commit was 11 hours ago.

zapotah commented on 2026-08-04 20:52 (UTC)

hopefully @nvllsvm puts a conflict dep on this and jellium packages sooner rather than later considering how few know that the player project has been spun off...

Obradinn commented on 2026-08-02 06:32 (UTC)

Hi there, just wondering, why is jellium-desktop-git more popular than jellium-desktop-bin ?

MagicAndWires commented on 2026-07-22 00:01 (UTC)

Might be worth adding jellyfin-desktop-git to the provides and conflicts lists for backwards compatibility/continuity reasons.

Was quite confused to find the entire package was missing and it took quite a while to figure out it was simply renamed.