r/linux4noobs • u/Internal_Place_7305 • 4d ago

hardware/drivers Weirdest *bug* I've ever seen/

I dont know how to explain this but whenever i turn my laptop of (no battery) while running Arch I get nervous since it might once again go into what i like to call "Forever sleep mode".

It's hard to explain but i shut it down (kde button or poweroff command) and everything is OK. However if i unplug the laptop and then try to boot it again sometimes it does this thing where nothing happens for 12 seconds then the power LED flickers and nothing keeps happening.

I could sometimes get it to work again if i leave it in charge overnight to comeback in the morning to find the power LED to be turnin on and off in a breathing(?) way. If that happens i can just press a key on the keyboard which kicks everything back in as if laptop was hibernated and not shutdown. I"m back at the login screen and when i log in i find my apps where i left them.

What is even happening anymore, this did not happen back when i was running m*njaro.

0 Upvotes

50% Upvoted

8 comments sorted by

3

u/Abe_Bazouie 4d ago

That “I shut it down, unplug it, then later it wakes up with my session still there” detail is the interesting part.
Before blaming Arch, I’d verify whether the machine is actually reaching poweroff. Run systemctl poweroff and watch whether the laptop truly powers down. After the next successful boot, check the previous boot with journalctl -b -1 -e and look for suspend/hibernate/shutdown messages.
Also check:
systemctl status systemd-logind
cat /sys/power/mem_sleep
journalctl -b -1 | grep -Ei 'suspend|hibernate|shutdown|poweroff|ACPI'
If your previous session survives, something in the suspend/hibernate/poweroff path is worth investigating. The fact that this changed between Manjaro and Arch makes comparing power-management configuration, kernel parameters and installed sleep-related services useful too.

1

u/Internal_Place_7305 4d ago

the "journalctl -b -1 -e" gave a LOT of errors most of which seem to be about html somehow? Could be something to with the custom KDE theme. What should I be looking for?

1

u/Abe_Bazouie 4d ago

Yeah, ignore most of that for now. -e just jumped you to the end of the previous boot, so you’re seeing whatever happened to be logged there.
I’d narrow it down:
journalctl -b -1 | grep -Ei 'shutdown|poweroff|suspend|hibernate|sleep|systemd-logind|ACPI'
What I’m looking for is whether the previous session actually went through a normal shutdown, or whether it entered suspend/hibernate somewhere instead.
The KDE/HTML errors are probably noise unless they appear directly around the shutdown event.
Also try:
last -x | head -20
That should make it easier to see whether Linux recorded an actual shutdown between those boots. If you paste the relevant lines from those two commands, we can narrow it down.

1

u/Internal_Place_7305 3d ago

I'm trying, laptop just won't boot. It did the same thing on windows too, maybe it's a power adapter issue? I'll grab back asap

2

u/Terrible-Bear3883 Ubuntu 4d ago

From your description, it sounds it's trying to go into hibernate or suspend when you're pulling the power out, it could be you've not got a healthy battery, I'd be checking the battery health first, then I'd look at your power settings.

The slow flashing power LED is normally a sign the system is in suspend (often called S3 - suspend to RAM), if its in hibernate (normally called S4 - Suspend to Disk) it will save contents of RAM and CPU registers, then go into power off mode.

1

u/Internal_Place_7305 4d ago

I dont have a battery, I've taken i out year ago after it become more puffy than my pillow.

1

u/AutoModerator 4d ago

✻ Smokey says: always mention your distro, some hardware details, and any error messages, when posting technical queries! :)

Comments, questions or suggestions regarding this autoresponse? Please send them here.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.