Gnome-power-manager won't recognize I am on a laptop

[Nick Barcet]

Binary package hint: gnome-power-manager

gnome-power-manager won't recognize I have a laptop by default meaning that:
 - it won't show the battery state when running on battery
 - it won't display the "On battery power" tab in the preferences
until some power event occurs such as:
 - plug or unplug power
 - I do a "sudo service laptop-mode status"
But a 'cat /proc/acpi/battery/BAT1/state' or 'info' always shows the same info before and after gnome-power-manager displays the problem.

Laptop is an acer aspire-one AO751h. This behaviour does not occur on other HW I have.

ProblemType: Bug
Architecture: i386
Date: Fri Oct 30 11:40:09 2009
DistroRelease: Ubuntu 9.10
Package: gnome-power-manager 2.28.1-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48+ureadahead2-generic
SourcePackage: gnome-power-manager
Tags: ubuntu-unr
Uname: Linux 2.6.31-14-generic i686
XsessionErrors:
 (gnome-settings-daemon:2060): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2060): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2083): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2099): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-panel:2079): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window

[Neoprenanzug (raketenforscher)]

Confirming for Koala on Acer Extenza 7630EZ, no UNR

[Esqui (esquiskwerl)]

Not sure if it's related, but does the same for me on Dell Mini 10v running Lucid Alpha 2 (UNR).

However, it does not switch to showing battery if I unplug/replug power.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GNOME Power Manager is available on Maverick and we are wondering if this bug is still an issue for you with that version? Could you please test and comment back? Thanks in advance.

[Nick Barcet (nijaba)]

This bug seems indeed fixed in 10.10