Summary: | kwin_wayland crashes in Plasma::AbstractRunner::name() when starting plasmashell from the Overview effect search field | ||
---|---|---|---|
Product: | [Plasma] krunner | Reporter: | Lyubomir <liubomirwm> |
Component: | general | Assignee: | Alexander Lohnau <alexander.lohnau> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | nate, nicolas.fella, plasma-bugs |
Priority: | NOR | ||
Version: | 5.24.5 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Lyubomir
2022-05-13 17:09:41 UTC
No idea why this crashes, the stacktrace looks Qt-internal. I did not experience any crash recently, though I do not use Arch which is the distro that the other bug reporter uses too. Cannot reproduce; no crash here. @Nate is it possible that these crashes on plasmashell startup are related to the following crash: https://bugs.kde.org/show_bug.cgi?id=451939? I think it usually happens when plasmashell and some different apps receive SIGABRT for some reason. So then I have to start plasma from the launcher. Today I started it and got yet another crash, with different stacktrace (AFAIS). I've filed a new bug for that. Is it possible that something else (like Systemd --user instance) is sending this SIGABRT to the apps and the apps themselves are not the cause, thus the stacks appearing different? Or maybe nevermind, cause this is SIGSEGV and not SIGABRT? *** This bug has been marked as a duplicate of bug 448825 *** |