Summary: | gnome-extra/gnome-power-manager-2.20.0-r1: when battery level is low does nothing. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Andrea Brandi <starise> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
The output of "gnome-power-bugreport.sh".
Battery info by g-p-m lshal of my battery |
Description
Andrea Brandi
2007-12-21 19:49:45 UTC
Created attachment 139055 [details]
The output of "gnome-power-bugreport.sh".
This works fine for me, for the record. I'm not sure how to go about debugging this. power management and suspend is a bit of a black art on Linux. I guess we'll start with the obvious: does g-p-m correctly show your battery status? How do you suspend? If you click on g-p-m, and select suspend, does it suspend? If you switch the critical power option to shutdown, does it work? > I guess we'll start with the obvious: does g-p-m correctly show your battery > status? Yes, it shows me correctly my battery status. > How do you suspend? with g-p-m icon! In a terminal the command "hibernate-ram --force" work! > If you click on g-p-m, and select suspend, does it suspend? Right! It's all ok! But at wake up, it show me an error like "operation is not completed successful". But, however, all (software and drivers) works great! > If you switch the critical power option to shutdown, does it work? Now I tried this and: No! Nothing happens, the battery goes down and PC turns off. :( I tried also to set the normal battery plugin for gnome-panel to show me a message when the battery is critical (5%). So.. this show me the message correctly Created attachment 139226 [details]
Battery info by g-p-m
Created attachment 139512 [details]
lshal of my battery
for the record, this is happening to me as well with latest hal and g-p-m 2.22 and I believe it started with the sysfs power interface. Are you using the /proc or the /sys interface in your kernel settings ? Please get back to us and also read bug #203306 to see if you are having a similar issue. |