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.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.6 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
J Leslie Turriff composed on 2024-10-21 23:45 (UTC-0500):
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.
sudo journalctl -b -1 -e
would be the place to start looking for clues, the tail end of the journal for your previous boot - that is, if you're not using one of those non-systemd distros.
On Tuesday 22 October 2024 00:06:37 Felix Miata via tde-devels wrote:
J Leslie Turriff composed on 2024-10-21 23:45 (UTC-0500):
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.
sudo journalctl -b -1 -e
would be the place to start looking for clues, the tail end of the journal for your previous boot - that is, if you're not using one of those non-systemd distros.
Hmm. This is what I get:
| @23:45:11 root@pinto | wd=~ | ● journalctl -b -1 -e | Specifying boot ID or boot offset has no effect, no persistent journal was found. | rc=0
So something isn't working right here.
Leslie
On 10/22/24 5:07 AM, J Leslie Turriff via tde-devels wrote:
no persistent journal was found.
Not a problem, that just means your install isn't configured to preserve a persistent journal. It isn't being saved on reboot.
Generally, the journal config file was /etc/systemd/journald.conf, but openSUSE likes to put individual pieces of the config in /etc/systemd/journald.conf.d/
You can make the journal persistent and limit its size on disk to 1/2G (probably close to a year of boots depending on how chatty you make it)
You can do that with:
$ cat /etc/systemd/journald.conf.d/10-persistent-size.conf Storage=persistent SystemMaxUse=512M
(or set the SystemMaxUse to whatever you want, 50M is plenty for a couple of boots to be saved, maybe a couple of months...)
On 10/22/24 5:47 AM, David C. Rankin via tde-devels wrote:
You can do that with:
$ cat /etc/systemd/journald.conf.d/10-persistent-size.conf Storage=persistent SystemMaxUse=512M
(or set the SystemMaxUse to whatever you want, 50M is plenty for a couple of boots to be saved, maybe a couple of months...)
Don't forget to restart journald or reboot after the changes (Not sure which is needed)
J Leslie Turriff composed on 2024-10-22 05:07 (UTC-0500):
Felix Miata wrote:
sudo journalctl -b -1 -e
would be the place to start looking for clues, the tail end of the journal for your previous boot - that is, if you're not using one of those non-systemd distros.
Hmm. This is what I get:
| @23:45:11 root@pinto | wd=~ | ● journalctl -b -1 -e | Specifying boot ID or boot offset has no effect, no persistent journal was found. | rc=0
So something isn't working right here.
David gave you an interpretation of the official method to configure persistent journal. I have found that if /var/log/journal/ exists, a persistent journal is enabled, unless /etc/systemd/journal* disables it.
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...
On Tuesday 22 October 2024 04:23:12 David C. Rankin via tde-devels wrote:
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.
Well, now that you mention it, yes, my mouse stopped working because the battery dropped below its usable threshold; so what you suggest is undoubtedly what happened. I have added Solaar to my Autostart manager list in the Control Center (it wasn't persisting across Login|out) so that I can watch the mouse battery, so theoretically I will be able to take preemptive action the next time.
(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.
I see in Session Manager => General an option, Use alternative shutdown dialog layout, but the Help for Session Manager doesn't explain what that provides?
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...
Thank you for sharing this.
Leslie -- Platform: Linux Distribution: openSUSE Leap 15.5 - x86_64 Desktop Environment: Trinity Qt: 3.5.0 TDE: R14.1.2 tde-config: 1.0
-
David C. Rankin -
Felix Miata -
J Leslie Turriff