On Tue, 2018-11-20 at 13:44 -0500, Neal Becker wrote:
Patrick O'Callaghan wrote:
> F29 updated.
> For the last couple of days I've turned on my monitor in the morning to
> find Plasma unresponsive, i.e. clicking on the bottom panel does
> nothing, neither does right-clicking on the background.
> The machine is left on at night (not suspended or hibernating, just the
> monitor turned off), and today the clock widget shows a frozen time of
> 4:55am. Nothing is running overnight except the DE and my backup
> software (rsnapshot) which does run at around that time though it has
> been doing that for years without issue and according to the logs
> completed on time as usual.
> 'killall -s SIGSEGV plasmashell' (which in the past would kick it into
> restarting) is ineffective. Maybe the magic incantation has changed,
> but as none of this stuff is documented in man pages I don't know.
> '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.
Since F29 I have seen plasma freezing every day. Nothing to do with NFS, I
don't use it.
That's useful to know. I've turned off my NFS mounts completely to see
what happens but my own reason for suspecting it was the 'D'-state
WCHAN value plasmashell gets into. If it's not NFS then it's almost
certainly some other kernel bug. This is a situation that should never
arise even with a badly-behaved program, but so far I haven't found
anything else which triggers it.
I find I have to reboot the machine to clear it, which again is typical
of this kind of bug.