https://bugs.kde.org/show_bug.cgi?id=479010
Bug ID: 479010
Summary: Inconsistent Flatpak launch behavior across
Application Launcher, Krunner and Overview that often
leads to the application crashing
Classification: I don't know
Product: kde
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: unblended_icing...@simplelogin.com
Target Milestone: ---
SUMMARY
Sometimes KDE became bugged and one of the launch method (Application Launcher,
Krunner and Overview) produces different launch behavior than the others,
usually resulting in the newly started Flatpak application to crash.
This bug is completely random, but it usually occurs after the desktop
environment is up for at least a day. Logging out and re-logging in fixes the
issue temporarily, until KDE becomes bugged and starts happening again.
Nothing useful splits out in `journalctl` when it happens, it seems almost the
same when launching normally.
The issue have been seen on these Flatpak applications:
- Kodi https://flathub.org/apps/tv.kodi.Kodi - immediately crashes and core
dumps when launched by Overview
- TLP UI https://flathub.org/apps/com.github.d4nj1.tlpui - won't open when
launched by Application Launcher
- XnView MP https://flathub.org/apps/com.xnview.XnViewMP - opens, but crashes
after a few seconds of usage when launched by Application Launcher
Krunner seems to always work (There might be other applications that breaks
when launched by Krunner though).
STEPS TO REPRODUCE
1. Open one of the applications listed above
2. Watch it crashes (or doesn't launch at all)
OBSERVED RESULT
It crashes or doesn't launch.
EXPECTED RESULT
It should launch.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.111.0
Qt Version: 5.15.11
Wayland session
Fedora 39
This also occurs on openSUSE Tumbleweed before. It doesn't occur on Kubuntu
22.04 LTS (with KDE Plasma 5.24)
ADDITIONAL INFORMATION
The application launching logic should be moved into a standalone desktop file
launcher daemon and communicated over DBus ("start this desktop file") to
completely eliminate this type of inconsistencies. It isn't a good idea to
construct your own launch arguments repeatedly in different components when the
logic could be shared and moved into one standalone component.
--
You are receiving this mail because:
You are watching all bug changes.
