Just now Arch decided to shut down gracefully without me touching anything at all. I read a bit about scheduled shutdowns and while shutdown --show said nothing was scheduled, running busctl get-property org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager ScheduledShutdown gave me a UNIX timestamp that does correspond to a specific time in the future. Could this be related?
#system powers off without consent
145 messages · Page 1 of 1 (latest)
I also ran sudo busctl call org.freedesktop.login1 /org/freedesktop/login1 org.freedesktop.login1.Manager CancelScheduledShutdown and got a false output which by the documentation means no shutdown was scheduled
But its still very weird how it decided to just turn off because yes
had this problem as well, i thought my laptop battery was giving out so I never really touched this issue, well enough it disappeared without me needing to do anything. it just fixed itself. how frequently does it happen to you?
Its kinda random
Are you using kde plasma?
Run this journalctl -u systemd-logind to check who/what created the scheduled shutdown
yes
there is absolutely nothing apart from a message "The system will power off now!"
it doesnt even give a reason for the shutdown or i cant find on
Before it?
nothing relevant
only when i logged out and logged in back again
but nothing about a shutdown
You can check what happened in the last boot journalctl -b -1 -e
yes i did that already
and there was nothing relevant
nothing that would suddenly cause a shutdown
Or just search for shutdown journalctl | grep -i 'shutdown'
right before the shutdown i was taking a screenshot
cant see anything relevant
Also try journalctl | grep -i 'poweroff'
also nothing
idk ig ill see if it happens again bc like lol
it was so random
not even a shutdown for a crash it was a graceful shutdown but it was unasked of
You are not running any cron jobs?
It could be hardware related.
idk ive been running this installation for 2 years now
i used to run it as like a secondary system tho i only recently nuked windows and adopted it fully
Okay, you are running a DE or a WM?
im using a laptop
so faulty power cable seems impossible
@past kite Did you try switching KDE Plasma to something else just to make sure that is the same issue across.
not yet
might be the next thing i try bc its happened twice already
im gonna try using the lts kernel first
Okay, you need to time it and note what you were doing when it turned off.
it happens with literally any action
im trying my usual X11 WM instead of KDE now
bc lts did the thing too
it happens without me even touching anything sometimes (just watching a video)
Yeah, I didn’t think that would be kernel related.
Did it happen whit WM?
not for now but its been only 39min
so far its powered off between 15min to 5h
5h is the maximum it stood
Yeah, okay.
i dont see why plasma would power off suddenly anyways either
could it be bc im using plasma-meta
Not sure about that, but we have to eliminate suspicions starting with the DE.
The plasma-meta does not have anything.
If it is a hardware issue, it could be something like overheating.
cant be i checked temps already
I mean plasma-desktop is the one that has all the other packages not plasma-meta.
and i think overheating would show in journal
Yeah, maybe.
man what a troublesome issue
i sure hope so too
To eliminate this being a hardware issue, you could run some stress tests just to check the temps and make sure it’s not turning off.
i had my cpu running at 95 and it was fine
Yeah, I'm not say it's the CPU it could be something else.
I mean, the chipset could turn the CPU off.
i mean i ran high end games and it was fine it happened a long while after that
so i doubt its that
in any case maybe the battery but i find that a bit weird
I don't think it the battery.
then its gotta be the DE
either that or my installation is faulty
if its not the DE ig ill just reinstall
You are using the default kernel, and switched to the lts one, right?
I mean not the zen one.
Yeah, that is one less thing to worry about(kernel).
It can't be.
could it be bc im using a secondary NTFS drive (without windows on it)
i have a feeling its gonna be the DE
Yeah, it could be. Time will tell.
if it goes past 4-5h without issue ill prob determine its the DE
You sad this installation was very long.
yea it went through a lot
Yeah, right.
I mean how log have you bean using this installation of arch?
2 years
approximately
i initially had it on an external SSD and a few days ago i cloned it to an encrypted LUKS container on another drive to use it as a main OS
i basically rsync'd the root directory to the new drive
That is a very long time, and at what time this issue stated happening?
Oh, okay.
after I cloned it and installed plasma
i never had this issue back when i was using it as an external ssd
ive had it running for over 20h back then
Yeah, that could be the cause of the issue — something somewhere got corrupted.
@tardy bone it has to be kde plasma
i used qtile for over 2h switched to plasma and in 5min it powered off
and i get a wall message to and that has to be sent by plasma bc by default i dont have it
i uninstalled plasma and i have switched to cinnamon for the time being
What the msg say?
"The system will power off now"
thats all the info i got
im starting to think its an nvidia + wayland issue
bc cinnamon works fine
(its x11)
and since plasma only has wayland now thats prob the reason
Okay, yeah that would show on systemd logs.
Could be, one way to check is to run plasma with X11.
Last time i checked there was an option to use X?
not with plasma 6 apparently
No sure about that, at this moment.
Oh, okay, that is weird.
yea
problem is that x11 now causes my games to stutter
man i hate nvidia
nevermind the problem persists in x11
i guess ill have to reinstall
Yeah, that is the right thing to do.
F u n
After you install Arch and KDE plasma don't do a lot of configuration just to see if it happens again.
Fair point
Keep the defaults as much as you can.
Problem is i dont have much time so ill prob go back to windows for the time being
Yeah.
i think the problem is solved now @tardy bone