Jellyfin flatpak closes immediately on launch

[Fenir8]

Logs:
https://pastebin.com/qZr8a0zE

Describe the bug
Jellyfin media player closes/crashes immediately on launch. I am using the flatpak version. I did not have this problem before today. A few others seemed to have the same issue today in the troubleshooting channel with the flatpak?

To Reproduce
Steps to reproduce the behavior:

1. Launch Jellyfin

Expected behavior
Jellyfin should launch

Desktop (please complete the following information):

• OS: Bazzite (Linux)
• Installation Method Flatpak

Additional context
Have tried reinstalling, clearing data, etc, behavior persists.

[Fenir8]

further troubleshooting that hopefully helps:
Oct 01 18:16:32 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: QSocketNotifier: Can only be used with threads started with QThread
Oct 01 18:16:32 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: qt.qpa.qgnomeplatform: Could not find color scheme ""
Oct 01 18:16:32 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: libpng warning: iCCP: known incorrect sRGB profile
Oct 01 18:16:32 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: Listening to socket: "/tmp/jmp_pmpUniqueApplication_alluren.sock"
Oct 01 18:16:32 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: Signal handlers installed successfully.
Oct 01 18:16:32 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: Logging to /home/alluren/.var/app/com.github.iwalton3.jellyfin-media-player/data/jellyfinmediaplayer/logs/jellyfinmediaplayer.log
Oct 01 18:16:33 rainbow-egg io.github.kolunmi.Bazaar.desktop[54162]: [2:52:1001/181633.173873:ERROR:address_tracker_linux.cc(214)] Could not bind NETLINK socket: Address already in use (98)
Oct 01 18:16:33 rainbow-egg systemd-coredump[54223]: [🡕] Process 54162 (jellyfinmediapl) of user 1000 dumped core.

                                                 Stack trace of thread 2:
                                                 #0  0x0000000000000000 n/a (n/a + 0x0)
                                                 #1  0x00007fbb9c2f9203 n/a (/usr/share/runtime/lib/plugins/QAdwaitaDecorations/wayland-decoration-client/libqadwaitadecorations.so + 0x14203)
                                                 #2  0x00007fbbdd51c066 n/a (/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.17 + 0x31c066)
                                                 #3  0x00007fbbdf37adae n/a (/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.15.17 + 0x17adae)
                                                 ELF object binary architecture: AMD x86-64

[sharpenedblade]

I can reproduce on fedora 42 and the latest flatpack on gnome.

Backtrace:

#0  0x00007f05780585e5 in QAdwaitaDecorations::forceRepaint (this=this@entry=0x556ca8123a60) at /run/build/qadwaitadecorations/src/qadwaitadecorations.cpp:753
#1  0x00007f057805920f in QAdwaitaDecorations::handleMouse (this=0x556ca8123a60, inputDevice=0x556ca7922460, local=..., global=<optimized out>, b=..., mods=...) at /run/build/qadwaitadecorations/src/qadwaitadecorations.cpp:693
#2  0x00007f05aff37b1b in QtWaylandClient::QWaylandWindow::handleMouseEventWithDecoration(QtWaylandClient::QWaylandInputDevice*, QtWaylandClient::QWaylandPointerEvent const&) () at /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#3  0x00007f05aff37ef1 in QtWaylandClient::QWaylandWindow::handleMouse(QtWaylandClient::QWaylandInputDevice*, QtWaylandClient::QWaylandPointerEvent const&) () at /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#4  0x00007f05aff28023 in QtWaylandClient::QWaylandInputDevice::Pointer::flushFrameEvent() () at /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#5  0x00007f05b4722056 in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.8
#6  0x00007f05b4720db1 in ffi_call_int () at /usr/lib/x86_64-linux-gnu/libffi.so.8
#7  0x00007f05b472162e in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.8
#8  0x00007f05c58a80ee in wl_closure_invoke.constprop () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#9  0x00007f05c58a8959 in dispatch_event () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#10 0x00007f05c58a8d53 in wl_display_dispatch_queue_pending () at /usr/lib/x86_64-linux-gnu/libwayland-client.so.0
#11 0x00007f05aff2ce72 in QtWaylandClient::QWaylandDisplay::flushRequests() () at /usr/lib/x86_64-linux-gnu/libQt5WaylandClient.so.5
#12 0x00007f05c471c066 in QObject::event(QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#13 0x00007f05c657adae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f05c46ef1a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f05c46f24c9 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f05c474add3 in ??? () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f05b5d133d6 in g_main_dispatch.lto_priv () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f05b5d74047 in g_main_context_iterate_unlocked.isra () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f05b5d12863 in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f05c474a479 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f05c46edbc2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f05c46f61fe in QCoreApplication::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x0000556ca75897b5 in ??? ()
#24 0x00007f05c3e2b3c8 in __libc_start_call_main () at /usr/lib/x86_64-linux-gnu/libc.so.6
#25 0x00007f05c3e2b48b in __libc_start_main () at /usr/lib/x86_64-linux-gnu/libc.so.6
#26 0x0000556ca758aaf5 in ??? ()

[sharpenedblade]

Disabling wayland with flatseal makes it work again. I think this is a qt bug.