You are not logged in.
I have an older Dell 610 laptop that I upgraded to Lithium. I have noticed that occasionally when playing videos over 20 minutes or so, the laptop shuts down. No noticeable warning, The screen goes black and the power light goes out.
When restarting, it has to recover the journal before booting.
I never had this problem running Hydrogen.
Overheating maybe? The case does feel warm, but no more so then during a normal session.
What diagnostic steps can I take? (And having written that, I immediately think, "have you looked at the logs." And, no, I haven't... First thing to do when I get back to that machine....)
Thanks,
David
Offline
Maybe check what you have for suspend and hibernate? Are these enabled automatically after the screen goes blank? (20 minutes or so).
It seems this shouldn't be an issue as the video player should be known, but you also say it has to recover the journal on boot? Anyway, food for thought.
Last edited by sleekmason (2020-10-07 16:13:48)
Offline
When restarting, it has to recover the journal before booting.
That would point to an unordered shutdown, even a kernel crash. Or overheating.
You might still be able to find something in the journal.
journalctl -b -1
for the previous boot.
Offline
dbickin wrote:When restarting, it has to recover the journal before booting.
That would point to an unordered shutdown, even a kernel crash. Or overheating.
You might still be able to find something in the journal.journalctl -b -1
for the previous boot.
journalctl required sudo, and even then I got back: Specifying boot ID has no effect, no persistent journal was found
With out the -1, it just showed messages from the current boot. Mind you, I ran this after a clean shutdown.
David
Offline
I have an older Dell 610 laptop that I upgraded to Lithium.
I generally don't think this is a good idea, even if it is described here in the forum as feasible. For me the differences are simply too large (!) hydrogen/helium <---> lithium .
As an idea for your problem I have only:
1. you should set up the journal for the normal user.
First we set up the group (everything as root):
addgroup --system systemd-journal
Then we create a folder for the journal, since this does not happen automatically in Debian:
mkdir -p /var/log/journal
the rights:
chown root:systemd-journal /var/log/journal
Now we add the new user to the group:
gpasswd -a $user systemd-journal
For $user the own user must be entered here.
To their error:
2. open a terminal and enter the following command
sudo journalctl -af > /home/$user/BUG.txt
Leave the terminal open and then play with your video to provoke the error.
Maybe you will have a hint in this text file after the restart.
Also look for hints in the ~/.xsession-errors.old
Last edited by unklar (2020-10-08 17:03:20)
Offline
Specifying boot ID has no effect, no persistent journal was found
Just to clarify, unklar gave you instructions how to make the journal persistent, among other things.
Offline
I haven't answered because I haven't gotten it to crash again while playing videos. I have watched very long videos with no issues. The only difference I could see is that when it crashed, the laptop was sitting on a solid surface (A cardboard box), so maybe that meant it couldn't cool itself as well??
Well, it did crash once, but I had left it sitting turned on doing "nothing" and when I went back to it hours later, it had crashed.
~/.xsession-errors.old showed nothing interesting... actually had less errors than on a clean shutdown, but likely because I hadn't done much to accumulate small errors.
I didn't have the journalctl thing running, so nothing from that.
Oh, to clear up one thing, I used the word "upgrade" unwisely. It was an "upgrade" in that the laptop used to run hydrogen and now runs lithium, but it was not a "apt upgrade". I did a clean install to a new partition.
Also, I was unclear on unklar's instructions, does creating the system-journal group allow the persistent log? I took it that he was instructing on how to make it visible to the regular user, but sudo should work for viewing the log, or am I totally misunderstanding the situation? (And why doesn't lithium install the group if it is needed?)
Thanks,
David
Offline
^ That group should exist already, so to make the journal persist across boots just edit /etc/systemd/journald.conf and set
Storage=persistent
(I can't recall if you may need to create /var/log/journal first.)
Running journalctl as root shows all entries from boot onwards, without sudo it just shows your ${USER} results.
Be Excellent to Each Other...
The Bunsenlabs Lithium Desktop » Here
FORUM RULES and posting guidelines «» Help page for forum post formatting
Artwork on DeviantArt «» BunsenLabs on DeviantArt
Offline