After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 505243 - Laptop does not hibernate when power is critically low
Laptop does not hibernate when power is critically low
Status: RESOLVED NOTABUG
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.20.x
Other All
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-12-23 15:59 UTC by Julian Sikorski
Modified: 2008-02-17 09:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Attachments
Power chart (78.71 KB, image/png)
2007-12-23 16:02 UTC, Julian Sikorski
Details
Discharge profile (35.32 KB, image/png)
2007-12-23 23:28 UTC, Julian Sikorski
Details
Discharge accuracy (36.85 KB, image/png)
2007-12-23 23:28 UTC, Julian Sikorski
Details
gnome-power-bugreport.sh output (2.77 KB, text/plain)
2007-12-24 13:38 UTC, Julian Sikorski
Details

Description Julian Sikorski 2007-12-23 15:59:29 UTC
Please describe the problem:
This bug was originally reported at Red Hat bugzilla #351551. Basically, the issue is that although g-p-m does display a warning about power being critically low, it does not put the laptop in ACPI S4 mode.

Steps to reproduce:
1. Get a Toshiba Satellite A100-847 laptop
2. Plug out the AC cord
3. Wait until battery runs out of power


Actual results:
Laptop goes off

Expected results:
Laptop hibernates

Does this happen every time?
Yes

Other information:
Comment 1 Julian Sikorski 2007-12-23 16:02:18 UTC
Created attachment 101507 [details]
Power chart

Take a look at the end. There is a false lid closed event, and also the power goes up without reason.
FWIW, g-p-m 2.18 from Fedora 7 was working perfectly OK.
Comment 2 Richard Hughes 2007-12-23 20:52:23 UTC
It looks like your battery is pretty screwed - could you please attach the discharge accuracy and data graph screenshot and we can see if this is indeed the case. Thanks.
Comment 3 Julian Sikorski 2007-12-23 23:28:32 UTC
Created attachment 101523 [details]
Discharge profile
Comment 4 Julian Sikorski 2007-12-23 23:28:53 UTC
Created attachment 101524 [details]
Discharge accuracy
Comment 5 Julian Sikorski 2007-12-23 23:32:38 UTC
I'm not sure what do you mean by a screwed battery, but I think this is unlikely. This laptop is only 11 months old. What is more, when g-p-m says that the battery is almost empty, it is almost empty. The time estimate for fully loaded battery seems a bit off, though (95 mins), as under windows (never really measured linux) you can certainly pull more than that.
Comment 6 Richard Hughes 2007-12-24 09:09:57 UTC
Hmm. You are correct, the battery is fine. Could you please run gnome-power-bugreport.sh and attach the output here. Thanks.
Comment 7 Julian Sikorski 2007-12-24 13:38:03 UTC
Created attachment 101542 [details]
gnome-power-bugreport.sh output

Here you go.
Comment 8 Julian Sikorski 2008-01-27 10:33:32 UTC
Hmm, can I provide some more info?
Comment 9 Julian Sikorski 2008-02-17 09:58:17 UTC
Hibernation has started to work again. That's strange. Maybe that was a kernel bug and one of the kernel updates has fixed it? Or maybe g-p-m eventually learned when to hibernate? If that's the case, the required time is was far too long. Anyway, the problem seems to be gone now (without any g-p-m updates), so I'm closing the bug.