Bug 404447 - When plasmashell crashes, it doesn't restart, nor is there a crash message about it
Summary: When plasmashell crashes, it doesn't restart, nor is there a crash message ab...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-wayland (show other bugs)
Version: 5.15.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-16 14:51 UTC by Matej Mrenica
Modified: 2019-09-29 13:41 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matej Mrenica 2019-02-16 14:51:56 UTC
KDE Frameworks Version: 5.55
Qt Version: 5.12.1

ADDITIONAL INFORMATION
Can it be because it is supposed to start with kstart5 but that doesn't work (https://bugs.kde.org/show_bug.cgi?id=403965)

What log should I provide?

Also, this bug might also be present on Xorg, but plasmashell doesn't crash there for me.
Comment 1 David Edmundson 2019-02-16 18:38:18 UTC
>Can it be because it is supposed to start with kstart5 but that doesn't work 

It is not.

Relevant log is:
~/.local/share/sddm/wayland-session.log


Please also start plasmashell from krunner (alt + space) and see if there's a crash icon.
Comment 2 Matej Mrenica 2019-02-17 08:07:43 UTC
So plasmashell crashed just now, so I openned krunner and found out I have disabled this option for starting anything from krunner. So I proceded to krunner settings where I enabled something like 'command line'. After applying settings krunner crashed. No warning or anything just Alt+Space stoped working, so I had to start krunner manually in konsole. Then I started plasmashell from krunner and after plasmashell started, there weren't any messages about any crashes (neither the krunner crash).

My wayland-session.log: https://pastebin.com/B4whvrx3
Comment 3 Matej Mrenica 2019-05-16 19:32:13 UTC
Today plasmashell crashed and there was a notification about that so this might be fixed.
Comment 4 David Edmundson 2019-09-29 13:41:15 UTC
\o/

Please reopen if it comes back