gnome-power-manager crashes on resume from suspend

[PeterPall]

Binary package hint: gnome-power-manager

Since about a week ago the gnome-power-manager has stopped displaying its regular "battery discharging" icon when my netbook is not connected to its power supply (I have configured gnome-power-manager to only display an icon when the battery is charging or discharging) but a pair of scissors that - as far as I know means that the said image isn't available.

I have also configured gnome-power-manager to suspend my system when running from battery and the netbook is closed, which normally works like magic.
Since gnome-power-manager no more displays the right icon suspending still works for the first time as does suspending the system by pressing the "suspend" key. But on resume the gnome-power-manager crashes, closing the netbook no more suspends it and pressing the suspend key results in the active program outputting a message like <SF86Sleep> is undefined.

starting gnome-power-manager by hand will make power management work until the next suspend (even if it will still not use the right icon) and results in loads of warnings that always repeat themselves.

{{{
(gnome-power-manager:3923): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-power-manager:3923): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed

(gnome-power-manager:3923): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(gnome-power-manager:3923): Gtk-CRITICAL **: IA__gtk_image_get_storage_type: assertion `GTK_IS_IMAGE (image)' failed

(gnome-power-manager:3923): GLib-GObject-WARNING **: invalid (NULL) pointer instance

(gnome-power-manager:3923): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
}}}
Upon resume gnome-power-manager dies then with the following message:
{{{
(gnome-power-manager:3923): libupower-glib-DEBUG: DBUS timed out, but recovering

Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 276 error_code 5 request_code 149 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...
}}}

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-14.20-generic 2.6.35
Uname: Linux 2.6.35-14-generic i686
Architecture: i386
Date: Sun Aug 8 19:31:54 2010
EcryptfsInUse: Yes
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GnomeSessionSuspendInhibited: Unknown
MachineType: Acer AOA110
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-14-generic root=UUID=d48138a0-331b-4037-abfb-68721f8a85bd ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
dmi.bios.date: 10/06/2008
dmi.bios.vendor: Acer
dmi.bios.version: v0.3309
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 1
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrv0.3309:bd10/06/2008:svnAcer:pnAOA110:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
dmi.product.name: AOA110
dmi.product.version: 1
dmi.sys.vendor: Acer

[PeterPall (peterpall)]

The last update of gnome-power-manager seems to have resolved this problem.
Thanks!

[PeterPall (peterpall)]

Changed the status of the bug again: The last update did fix the icon, but not the crash. The message still reads:

Gdk-ERROR **: The program 'gnome-power-manager' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
  (Details: serial 329 error_code 5 request_code 150 minor_code 15)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
aborting...