For the past several weeks (sorry for not reporting it earlier), plasma fails to auto-restart when kwin_wayland crashes. KRunner does, so I have been using krunner to launch Plasma manually, which works. But it seems like plasmashell should come up automatically.
It seems I encountered the same bug yesterday when I was testing Firefox behavior on Wayland. I didn't pay attention to other details, and I only remember I plugged out and in a Type-C converter (which contains a HDMI port, an RJ45 port and some USB ports)
Also happens when I manually restart kwin_wayland.
plasmashell can be automatically restarted after `kwin_wayland --replace` on 5.23.4.
I ran `kwin_wayland --replace` and plasmashell was successfully restarted on git master (5.24.80).
I can still reproduce the issue with current git master.
Is this with or without systemd startup?
With.
Works here, we need some logs from "journalctl --user -b" after reproducing
Created attachment 145719 [details] journalctl log
Attached the requested log.
>app-plasmashell- That makes no sense. It means it's being autostarted from either the user manually or there exists a /etc/xdg/autostart/org.kde.plasmashell.desktop that's super outdated and doesn't have the line X-systemd-skip=true All points to a local setup issue. systemctl --user show plasma-plasmashell.service.
Created attachment 145916 [details] `systemctl --user show plasma-plasmashell.service` output There is /etc/xdg/autostart/org.kde.plasmashell.desktop, but it has X-systemd-skip=true in it. I am attaching the output of `systemctl --user show plasma-plasmashell.service`. All the paths in it seem to point to my built-from-source stuff.
I encountered the same problem. Manually restarting kwin_wayland can restart plasmashell though ,but after kwin_wayland crashes and automatically restarts, plasmashell won't be there.
Update: Running `kwin_wayland --replace` can't restart plasmashell now
Update: when the bug happens, I can't logout/restart/shutdown from Kickoff.
(In reply to Fushan Wen from comment #15) > Update: when the bug happens, I can't logout/restart/shutdown from Kickoff. Sounds like Bug 448517.
Fushan do you also have a self compiled KDE alongside distro packages?
Edit: Jan 21 09:11:50 Liberator systemd[1255]: app-plasmashell-b2281e652ea9446591db0bff66da1800.scope: Consumed 2min 30.774s CPU time. This being a scope means it wasn't handled by the xdg-autostart. There's only one explanation. The user typed "plasmashell --replace" into krunner at which point the session isn't managing it.
can reproduce this bug on neon unstable. 1. reproduce kwin_wayland crash reported as bug 446318 result: I see a black screen with mouse pointer and Plasma is not automatically restarted. Plasma manually restarted with 'plasmashell --replace' is unusable. Right-click on desktop, logout/reboot/shutdown via kickoff do not work.
(In reply to David Edmundson from comment #17) > Fushan do you also have a self compiled KDE alongside distro packages? I usually install and update packages from the unstable-kde repo from openSUSE, and only manually compile packages when I need it.
I guess systemd refuses to restart plasmashell after a limit. I can still see plasmashell is restarted for the first time it crashes.
(In reply to David Edmundson from comment #18) > Edit: > Jan 21 09:11:50 Liberator systemd[1255]: > app-plasmashell-b2281e652ea9446591db0bff66da1800.scope: Consumed 2min > 30.774s CPU time. > > This being a scope means it wasn't handled by the xdg-autostart. > > There's only one explanation. The user typed "plasmashell --replace" into > krunner at which point the session isn't managing it. I restart plasmashell with `kstart5 -- plasmashell --replace` so that it gets managed in a cgroup. When I restart plasmashell like this, and then restart kwin with `kstart5 -- kwin_wayland --replace`, plasmashell doesn't get automatically started like I would expect. This can't possibly be an unsupported thing to do. If it is, there is a design flaw in the way our auto-restarting infrastructure works that we need to fix.
(In reply to Patrick Silva from comment #19) > can reproduce this bug on neon unstable. > > 1. reproduce kwin_wayland crash reported as bug 446318 > > result: I see a black screen with mouse pointer and Plasma is not > automatically restarted. > Plasma manually restarted with 'plasmashell --replace' is unusable. > Right-click on desktop, logout/reboot/shutdown via kickoff do not work. problem with logout, reboot and shutdown reported as bug 449948
*** Bug 453639 has been marked as a duplicate of this bug. ***
>can reproduce this bug on neon unstable. Patrick can you confirm if this happens after a clean boot and a kwin restart or if you had also manually explicitly replaced plasmashell before the kwin restart?
Tested on neon unstable right now: 1. boot 2. login to Wayland 3. ran 'kwin_wayland --replace' with krunner Result: black screen with mouse pointer
I can reproduce that too.
Interesting, I've just tried it on Lenovo P1 gen2 (Intel GPU) on Fedora 36 and it replaced it perfectly. Also I've recently noticed that on my desktop with AMD GPU it also recovered and restarted after a GPU driver reset.
> Patrick can you confirm if this happens after a clean boot and a kwin restart or if you had also manually explicitly replaced plasmashell before the kwin restart? I can on KDE Neon, note that kde neon doesnt use systemd boot because of to old systemd without xdg autostart generator support
After some investigation today, we found that ultimately this was caused by me using systemd boot but not restarting plasmashell using the systemd boot tools. I was doing: kquitapp5 plasmashell && kstart5 plasmashell instead of: systemctl restart --user plasma-plasmashell.service Ultimately I was doing that to work around https://bugs.kde.org/show_bug.cgi?id=439159, but the systemctl command doesn't seem to cause it either, which is nice. Switching to `systemctl restart --user plasma-plasmashell.service` fixes the issue entirely with systemd boot. This is still valid for the non-systemd case though; re-titling to be about that.