On Tue, 2018-11-06 at 19:35 +0800, Ed Greshko wrote: > On 11/6/18 7:24 PM, 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. > > So, you can move the mouse? > > > 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. > > And where are you typing these commands? Doing a Crtl-Alt-F2? I sued Shift-Tab to get to an open Konsole. Note that everything except Plasma still works, my other windows are running etc. I even sent that report from Evolution before logging out. > > '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. > > Back in the F26 or F27 days I was having some issues. Forgot the circumstances but back > then I was > advised that doing > > kquitapp plasmashell > > plasmashell & Yes, I remembered too late that I even have a script for that (BTW it's now kquitapp5). However: It just happened again, this time when I came back from my lunch break. At least that eliminates by backup system from suspicion. This time I just logged out using Ctrl-Alt-Del, then logged in again. Plasma started up but was still frozen (except the clock widget now showed the updated time). I tried the same thing again, with no difference. Doing it a third time would indicate insanity, so this time I switched to another console (Shift-Alt-Fn), logged in as root and tried a 'telinit 3'. The DE disappeared, I ran 'telinit 5' and the DE didn't come back. However I now had a GUI cursor on my root console window, so presumably Xorg was running even though some component of KDE was not. I rebooted. poc _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
