Application gets terminated every time, a few seconds after startup, on Fedora Linux 40 KDE Spin

[torokati44]

Regardless of whether I start rs.ruffle.Ruffle from the command line, or from the graphical Discover client, it gets terminated with exit code 137 (signal 9, SIGKILL) after about 5-6 seconds.

Running flatpak permission-set background background rs.ruffle.Ruffle works around the problem, and lets the application function normally afterwards.

This also got reported as:

• https://github.com/flatpak/flatpak/issues/5427
• https://github.com/flathub/com.logseq.Logseq/issues/128

I have xdg-desktop-portal 1.18.4 and xdg-desktop-portal-kde 6.1.3 installed (6.1.4 just came out a few days ago, hasn't landed yet in the distro package archives).

[torokati44]

Pinging @nicolasfella and @Pointedstick, as assumed KDE project contacts, pardon me.

[Pointedstick]

Sounds like the app might be missing the appropriate background permissions in its manifest?

[torokati44]

It doesn't make sense for it to have that permission - it's not something the app wants to do (it has no tray icon or anything, it's always supposed to have its main window visible). Also, this problem doesn't occur on other distros/DEs.

[torokati44]

Actually, on a different PC with the same Fedora 40 KDE setup, I can't reproduce... :face_with_spiral_eyes: Something might be cursed on the affected system. What mechanism is involved in detecting whether an app runs in the background or not? :thinking:

[Doomsdayrs]

I see no harm in adding the permission

[Doomsdayrs]

But this issue should not be closed if the permission is added, just to keep record there is an issue (the background permission is not needed)

[Doomsdayrs]

A possible explanation is the application is performing a task before the UI is rendered, considering it background and thus causing a termination.