Macbook Pro 5,4 battery/powermanagement problems

**unixninja92** · May 2nd, 2010

I am having several problems with what i believe to be gnome-power-management. Power management will randomly say that either i do, or don't have a battery. This means that the icon in the notification area does not appear, and I can not access the settings for on battery power. also, when i tell Ubuntu to suspend, it just goes to the screensaver and nothing happens. conky is still able to read the battery just fine, its power management thats having problems.

**paulinchen** · May 2nd, 2010

Same for me with a macbook pro 5.5. Randomly showing the battery when I'm coming from osx.

**benzolchemie** · May 3rd, 2010

Hey there,

I'm running Lucid on a MBP 5,5 with rEFIt and I am having the exact same issue. I only experience the problem when I start up my Mac WITHOUT the power cord attached - when running on AC, the machine behaves correctly. Yet, the gconf-editor shows the correct power management specs even when the different tabs in the power management settings are missing.

Greetings,

Dennis

**paulinchen** · May 5th, 2010

Its definitely a problem with the gnome-power-manager, cause even in the powercontrol of docky and cairo-dock you can see the battery.
Funny as well that, when I plug-off the ac-power the brightness gets lowered, as I set it up, when running on battery.

I found this in the log-file of "gnome-power-manager --verbose 2>&1" .Maybe it's useless cause I'm not that expert, but who knows ...

Code:

(gnome-power-manager:5841): devkit-power-gobject-WARNING **: Error invoking GetAll() to get properties: Message did not receive a reply (timeout by message bus)

**unixninja92** · May 5th, 2010

Originally Posted by paulinchen

Funny as well that, when I plug-off the ac-power the brightness gets lowered, as I set it up, when running on battery.

I have that problem too. Every now and then it works right, but most of the time it dims way too much, and there does not appear to be away to change it. I tried messing with the pommed config file, and that worked for a little bit, but its messing up again now.