[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #9 from Nate Graham --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #8 from David Edmundson --- Have you confirmed "kstart5 flatpak-run " breaks? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #7 from Nate Graham --- 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #6 from David Edmundson --- 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 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #5 from Nate Graham --- Created attachment 149499 --> https://bugs.kde.org/attachment.cgi?id=149499=edit 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. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #4 from Nate Graham --- Created attachment 149498 --> https://bugs.kde.org/attachment.cgi?id=149498=edit diff of the files -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #3 from Nate Graham --- Created attachment 149494 --> https://bugs.kde.org/attachment.cgi?id=149494=edit krunner env -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 --- Comment #2 from Nate Graham --- Created attachment 149493 --> https://bugs.kde.org/attachment.cgi?id=149493=edit plasma env -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 454907] Flatpak Discord crashes on launch when launched from Kickoff or Task Manager, but not KRunner or `flatpak run`
https://bugs.kde.org/show_bug.cgi?id=454907 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Edmundson --- 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. -- You are receiving this mail because: You are watching all bug changes.
