gnome-power-manager crashed with SIGSEGV in g_timeout_dispatch()

[Spooky]

Binary package hint: gnome-power-manager

 Ubuntu 9.04 - de Jaunty Jackalope

gnome-power-manager:
  Geïnstalleerd: 2.24.2-2ubuntu7
  Kandidaat: 2.24.2-2ubuntu7
  Versietabel:
 *** 2.24.2-2ubuntu7 0
        500 http://nl.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

Package crashes when battery was almost empty

ProblemType: Crash
ACAdapter: Present
Architecture: amd64
Battery: Present
CPUScaling: Present
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-power-manager
LaptopPanel: Present
Package: gnome-power-manager 2.24.2-2ubuntu7
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=nl_NL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
 g_timeout_dispatch (source=0x2517450,
Title: gnome-power-manager crashed with SIGSEGV in g_timeout_dispatch()
Uname: Linux 2.6.28-11-server x86_64
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

[Apport retracing service (apport)]

StacktraceTop:_dbus_connection_lock (connection=0x0) at dbus-connection.c:355
_dbus_pending_call_get_connection_and_lock (
reply_handler_timeout (data=0x0)
timeout_handler_dispatch (
g_timeout_dispatch (source=0x2517450,

[Scott Howard (showard314)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.

[Boniek (boniek12p)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!