On 10/21/24 11:45 PM, J Leslie Turriff via tde-devels wrote:
I opened Kate to paste some text. It put up a
message about saving existing
files or data (the message is gone now of course) and when I declined to save
it, the desktop shut down, the system shutdown sequence started, and my
machine powered off.
I'm not sure what logs might have pertinent information about this.
This is just a crystal-ball type guess, the end of the last journal for Felix
will be the most helpful -- but...
it almost seems like you triggered a shutdown from the desktop that invoked
(k/tde)shutdown which then triggered the prompt to save unsaved documents
before continuing. When you chose not to save (or even if you had chosen to
save) shutdown resumed at that point and finished shutting down...
The brings up my question, before this happened, did anything funny happen to
the mouse? (e.g. it got bumped, a book or notepad slid on top of it, the cat
jumped up on the table, etc...) I ask because a right-click on the desktop
brings up the kshutdown entry (last one in context menu 'Log out
"leslie"')
which if (a mouse drop, cat, etc..) occurred could make it look like kate
triggered a shutdown when it was actually just a right and left mouse-click
that triggered it.
(I ask because I've had those occur...) The savior has been with "Advanced
Shutdown Options" configured you are presented with the Log Out, Shutdown,
Sleep, etc.. options in the next window which would be telling. And, the fact
that to then trigger the shutdown inadvertently would require a right and
two-left clicks. Still possible, but less likely.
In the journal output from the last boot, go to the end and back-up to where
you get the first indication of logoff/shutdown. Grab probably 10 lines before
the start of shutdown through the end. Basically you just want to go
line-by-line and see if there is anything that stands out that could have
triggered your shutdown. Posting will just get more eyes on the log that may
help pick something out. (though absent something really odd, I don't expect
any smoking-gun)
Since all processes run in virtual-memory now, it's either got to be something
major like a panic and something non-TDE related, or there is an issue in one
of the base builds tdelibs/tdebase, etc.. that triggers a shutdown -- or your
cat has been busy...
--
David C. Rankin, J.D.,P.E.