SUMMARY Plasmashell repeatedly crashes under Wayland when playing media in Chromium (Flatpak) on Nobara Linux (Fedora-based, Plasma 6, Qt6). After several crashes, plasmashell fails to restart. STEPS TO REPRODUCE - Start KDE Plasma 6 session with Wayland on Nobara Linux (Fedora-based). - Launch Chromium (Flatpak, latest version). - Play a YouTube video or other media content. OBSERVED RESULT Plasmashell crashes and restarts several times, then fails to start. Relevant log entries: Logs: "plasmashell[3821]: segfault at 10 ip 00007f137f4a0382 sp 00007ffc4bd5ec00 error 4 in libQt6QuickTemplates2.so.6.9.2systemd-coredump[6538]: Process 3821 (plasmashell) of user 1000 terminated abnormally with signal 11/SEGV, processing...systemd[3489]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGVsystemd[3489]: plasma-plasmashell.service: Failed with result 'core-dump'.qrc:/qt/qml/plasma/applet/org/kde/plasma/mediacontroller/main.qml:70:28: QML CompactRepresentation (parent or ancestor of Image): Cannot open: file:///tmp/.org.chromium.Chromium.TdtQ9naudit[7097]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 subj=flatpak pid=7097 comm="chrome" exe="/app/chromium/chrome" sig=11 res=1audit[7181]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 subj=flatpak pid=7181 comm="chrome" exe="/app/chromium/chrome" sig=11 res=1audit[7195]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=4 subj=flatpak pid=7195 comm="chrome" exe="/app/chromium/chrome" sig=11 res=1" EXPECTED RESULT Plasmashell remains stable and does not crash when playing media in Chromium (Flatpak) under Wayland. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Nobara Linux (Fedora-based) KDE Plasma Version: 6.4.4 KDE Frameworks Version: 6.17.0 Qt Version: 6.9.2 Chromium: Flatpak (latest from Flathub) Wayland session ADDITIONAL INFORMATION - The issue does not occur under X11. - Disabling hardware acceleration in Chromium reduces crash frequency but does not fully resolve the issue. - All packages and Flatpak runtimes are up to date.
*** This bug has been marked as a duplicate of bug 510317 ***