https://bugs.kde.org/show_bug.cgi?id=499483
--- Comment #18 from balooii <balo...@proton.me> --- > Interesting, Flatseal shows that the Flatpak default has all of these settings Yeah, that's why I suggested to remove some to enforce it using either one or the other. I'm not sure how the selection process goes and which takes precedence if both options are available. > However, if I disable `socket=wayland`, the Flatpak does launch. I then also > verified that the now launched Flatpak is reported as a X11 window and not > Wayland. Cool, then we have confirmed its a wayland thing! > Then I went back and tried launching the AppImage, which does launch (very > quickly, I guess Flatpaks are indeed a bit slower), and checked to confirm if > it's not running on Wayland, but... it was reported as a Wayland window and > not X11. > In both cases, how I checked was using this command in KDE Plasma, while the > app is running: Could you check this within the app? | Help | About Kdenlive | Components Just to confirm if this has anything to do with flatpak or if the crash happens on both appimage/flatpak using wayland/nvidia/kwin/plasma. On my system this method gives me different reports for the four scenarios so seems to be reliable way to detect what is actually used: KDE Flatpak runtime (Wayland) KDE Flatpak runtime (Xcb) Arch Linux (Wayland) Arch Linux (Xcb) Tested cases: force wayland, flatpak flatseal: remove socket=x11 socket=fallback-x11 permissions, keep socket=wayland -> flatpak run force x11/xwayland, flatpak flatseal: remove socket=wayland, keep socket=x11 socket=fallback-x11 -> flatpak run force wayland, appimage QT_QPA_PLATFORM=wayland ./kdenlive-25.04.0-x86_64.AppImage force x11/xwayland, appimage QT_QPA_PLATFORM=xcb ./kdenlive-25.04.0-x86_64.AppImage Thanks! -- You are receiving this mail because: You are watching all bug changes.
