On Wed, 2018-11-07 at 11:18 -0600, Rex Dieter wrote:
Patrick O'Callaghan wrote:
> 'kill <PID>' does kill it, but how do I run it again without logging
> out? Simply running plasmashell from the command line does put up the
> widget panel but it's still frozen, and the command never returns.
You can (re)launch 'plasmashell' via krunner (ALT-F2)
I had another freeze overnight. This time I tried 'kquitapp5
plasmashell' and it did nothing. I also tried killing it with SEGV and
again nothing. A straight kill did manage to kill it.
However re-rerunning with 'plasmashell &' just brought back a frozen
widget panel. It looks like there is something more fundamental going
I've now installed this morning's updates which include a bunch of KDE
stuff (mostly kf5* I think), and rebooted the machine just in case.
I'll report back if the problem recurs.
That said, may be worth trying to get a backtrace out of the
plasmashell process, if you have terminal access, run:
gdb -p <PID>
and issue command:
thread apply all bt
Getting a worthwhile backtrace may require installing -debuginfo packages,
via something like:
dnf debuginfo-install plasma-workspace
(warning, it's a lot, but will give much better results)
I'll do that if and when it happens again.