| Summary: | Flatpak Discord crashes on launch when launched from Plasma or KRunner when those were themselves launched using `kstart5` | ||
|---|---|---|---|
| Product: | [Plasma] kde-cli-tools | Reporter: | Nate Graham <nate> |
| Component: | general | Assignee: | Aleix Pol <aleixpol> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | kde |
| Priority: | NOR | ||
| Version First Reported In: | master | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
plasma env
krunner env diff of the files working krunner vs broken krunner differences |
||
|
Description
Nate Graham
2022-06-05 21:34:15 UTC
Crashing clients are the fault of the client. We may be doing something different, but it crashing is still on the client. As to why kickoff and krunner behave differently. the only difference could be the env of both processes. Get and compare with cat /proc/`pidof plasmashell`/environ | tr '\0' '\n' cat /proc/`pidof krunner`/environ | tr '\0' '\n' at a time where things are breaking. Created attachment 149493 [details]
plasma env
Created attachment 149494 [details]
krunner env
Created attachment 149498 [details]
diff of the files
Created attachment 149499 [details]
working krunner vs broken krunner differences
I noticed something interesting. When KRunner is working, if I quit it and restart it with `krunner --replace` in a Konsole window, then it's broken from krunner. I'm attaching a dump of the env differences between working krunner and broken krunner.
Can you test with just this change:
< PATH=/home/nate/kde/usr/bin:/home/nate/bin:/home/nate/.local/bin:/home/nate/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
---
> PATH=/home/nate/bin:/home/nate/kde/usr/bin:/home/nate/bin:/home/nate/.local/bin:/home/nate/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
I'm not sure which way round is the right/wrong one
So this is interesting. When I set $PATH to either of those values and run krunner with kstart5, the problem manifests. When I set $PATH to either of those values and run krunner with the `krunner` binary, the problem goes away. Both $PATH values work. So $PATH doesn't seem relevant, and it's something else that kstart5 does or sets. Have you confirmed "kstart5 flatpak-run .... " breaks? I've discovered that it works in plasmashell too, until the moment when I have to start plasmashell again with kstart5 in a terminal. Thereafter, it doesn't work from Plasma either. If I start plasma manually with `plasmashell` it also works! So the difference really seems to be in something that kstart5 is doing. Only when Plasma and KRunner are launched with kstart5 does using them to launch Discord cause it to crash on launch for me. (In reply to David Edmundson from comment #8) > Have you confirmed "kstart5 flatpak-run .... " breaks? Yes that breaks too. This may only be tangentially related, but I'm having a similar problem when running KeePassXC from Flatpak via Keyboard shortcut, which uses KGlobalAccel, which in turn also uses kstart to run the desktop file.
This is in the journal when I type the shortcut:
kwin_wayland_wrapper[10898]: kstart: Unknown options: branch, arch, command, file-forwarding.
All the options kstart complains about are options to the flatpak run commandline:
/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=keepassxc --file-forwarding org.keepassxc.KeePassXC @@ %f @@
This has happened before [1], and the solution was to prefix the commandline with `--`.
I'm on Fedora Kinoite 36, kf5-kglobalaccel 5.96.0.
[1] https://bugs.kde.org/show_bug.cgi?id=433362
Disregard my recent comment, please; that issue is tracked by https://bugs.kde.org/show_bug.cgi?id=456589. The issue has stopped reproducing for me; closing for now. |