Hello! My girlfriend’s HP laptop running kubuntu 24.04 has this problem: when it’s turned off (either from the GUI or poweroff
) it discharges overnight, from 100% to 0% in a few days.
I searched the web to look for fixes:
- wake on lan is disabled in the BIOS
- USB ports have no settings in the bios, but there’s nothing connected to them anyway
- the system is actually powered off, not sleeping (at least if
poweroff
actually works) - everything, firmware included, is up to date
She doesn’t remember having this problem from the beginning, but cannot tell when this started occurring
Did any of you ever encounter this problem? I don’t know what else to do, and it’s quite annoying.
Thank you for your time!
does this happen if you force it to shut down by holding the power button for +10sec, or if you remove and reinsert the battery after power off?
forcing a shutdown or removing and installing the battery, will ensure that the laptop is indeed shut down and not just halting during the shutdown process.
if you still have the same issue after this test I would guess your battery is dying, but if not you know that the issue is a software and not a hardware problem…
anyway, best of luck getting it sorted
on most new laptops, you cannot remove the battery that easily, you have to disassemble the back cover ☹️
An alternative would be to boot into the bios and shut down from there
That’s true, but long press on the power button still works, so you can try that instead then? 🙂
I hate this about new laptops…
I miss the old switch on the bottom.
I’ll try it as soon as I can, thanks for the suggestion! I don’t think the battery is dying, because while powered on the battery life is very good
let’s hope it’s a software issue, in general it’s much cheaper to fix software than hardware 🙂
you can also try using the “sudo halt --poweroff” command.
if it ks software related. that command will force an instant shutdown ignoring all normal shutdown run levels (use with caution if you have open files that need to be saved in advance).
if that command succeeds as well after the battery test, you can be sure the problem lies within the shutdown run level scripts, which should help you narrow it down even more.
okay, I think we have some news: if I kill the pc by holding the power button, after a night the battery loses 0%! so I guess the problem is that it’s not shutting down properly. I tried to
sudo halt --poweroff
and it drained the battery as usual. I then triedsudo halt -f
and something strange happened: the screen immediately turned off, but the red LED on the volume key indicating that the volume is muted stayed on, so the pc wasn’t completely off. what could be the problem? and why does this happen only when I force thehalt
? could it be a kernel issue?thanks for the help and for your time!!!
Hi, a bit busy today so I can investigate some more later, but the problem you are describing is in many cases related to the kernel version and has been resolved by up or downgrading the kernel version.
it might be worth looking into, at least it’s a simple task, while I get some more time to investigate or offer more for you to look into.
great that it worked so far, at least now you know where the problem is :)
I’ll try other kernels then, but I don’t know how to check if the system is actually powered off or not without waiting 8 hours and checking the battery drain XD perhaps the
halt
could be the keythanks!! I’ll update the thread if I’ll discover something new
the halt command is like a handbrake for the kernel, so it basically shuts everything down hard and stops, but it does not power off the system without you telling it to, so that is why your LEDs stayed on after you used the other parameter.
you could just try to downgrade/ upgrade the kernel, do s shutdown for a few hours during daytime when the computer is not beeing used, then turn it back on and check the percentage.
you will see the drain if it’s not a full night, but it might not be so drastic.
if it’s completely shut down there should be no loss in percentage, even for a short period of time as there probably is now…
I’ll try to think up another solution, but a bit busy today as I mentioned on the last post
probably related to this kernel bug though:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2059738
downgrading the kernel should fix it as a workaround it would seem.