Bug 549772 – g-p-m daemon crashes when battery %age changes

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 549772 - g-p-m daemon crashes when battery %age changes


Summary:	g-p-m daemon crashes when battery %age changes


Status:	RESOLVED DUPLICATE of bug 547766

Product:	gnome-power-manager
Classification:	Deprecated
Component:	gnome-power-manager
Version:	2.23.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Power Manager Maintainer(s)
QA Contact:	GNOME Power Manager Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-08-28 23:42 UTC by Christopher Halse Rogers
Modified:	2008-09-02 04:21 UTC

See Also:
GNOME target:	---
GNOME version:	2.23/2.24

Attachments
gdb session with G_DEBUG set to 'fatal_criticals' (11.57 KB, text/plain) 2008-09-01 23:57 UTC, Christopher Halse Rogers	Details

Description Christopher Halse Rogers 2008-08-28 23:42:25 UTC

Running Ubuntu Intrepid, with GNOME 2.23.90, gnome-power-manager version 2.23.6.

Linking from: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/260597

Gnome power manager crashes very frequently, apparently each time the percentage battery charge changes.  Sometimes, but not always, it'll spit out
"""
** (gnome-power-manager:8551): CRITICAL **: gpm_cell_array_get_cell: assertion `GPM_IS_CELL_ARRAY (cell_array)' failed

** (gnome-power-manager:8551): CRITICAL **: gpm_cell_get_unit: assertion `cell != NULL' failed
"""
just before crashing.

Backtrace follows:
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
(gdb) set pagination 0
(gdb) run --no-daemon
Starting program: /usr/bin/gnome-power-manager --no-daemon
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7fc8f8c0f770 (LWP 22236)]

Program received signal SIGSEGV, Segmentation fault.

+ Trace 205824

Thread 140501143582576 (LWP 22236)

#0 ??
#1 ??
#2 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#3 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#4 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#5 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#6 ??
#7 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#8 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#9 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#10 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#11 ??
#12 marshal_dbus_message_to_g_marshaller
at dbus-gproxy.c line 1665
#13 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#14 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#15 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#16 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#17 dbus_g_proxy_manager_filter
at dbus-gproxy.c line 1718
#18 dbus_connection_dispatch
at dbus-connection.c line 4406
#19 message_queue_dispatch
at dbus-gmain.c line 101
#20 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2073
#21 g_main_context_iterate
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2706
#22 IA__g_main_loop_run
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2929
#23 ??
#24 __libc_start_main
from /lib/libc.so.6
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??

Thread 1 (Thread 0x7fc8f8c0f770 (LWP 22236))

#0 ??
#1 ??
#2 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#3 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#4 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#5 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#6 ??
#7 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#8 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#9 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#10 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#11 ??
#12 marshal_dbus_message_to_g_marshaller
at dbus-gproxy.c line 1665
#13 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#14 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#15 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#16 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#17 dbus_g_proxy_manager_filter
at dbus-gproxy.c line 1718
#18 dbus_connection_dispatch
at dbus-connection.c line 4406
#19 message_queue_dispatch
at dbus-gmain.c line 101
#20 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2073
#21 g_main_context_iterate
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2706
#22 IA__g_main_loop_run
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2929
#23 ??
#24 __libc_start_main
from /lib/libc.so.6
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??

Thread 1 (Thread 0x7fc8f8c0f770 (LWP 22236))

#0 ??
#1 ??
#2 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#3 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#4 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#5 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#6 ??
#7 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#8 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#9 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#10 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#11 ??
#12 marshal_dbus_message_to_g_marshaller
at dbus-gproxy.c line 1665
#13 IA__g_closure_invoke
at /build/buildd/glib2.0-2.17.7/gobject/gclosure.c line 767
#14 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3244
#15 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 2977
#16 IA__g_signal_emit
at /build/buildd/glib2.0-2.17.7/gobject/gsignal.c line 3034
#17 dbus_g_proxy_manager_filter
at dbus-gproxy.c line 1718
#18 dbus_connection_dispatch
at dbus-connection.c line 4406
#19 message_queue_dispatch
at dbus-gmain.c line 101
#20 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2073
#21 g_main_context_iterate
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2706
#22 IA__g_main_loop_run
at /build/buildd/glib2.0-2.17.7/glib/gmain.c line 2929
#23 ??
#24 __libc_start_main
from /lib/libc.so.6
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??

(gdb) cont
Continuing.

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) quit

Comment 1 Tobias Mueller 2008-08-29 08:43:41 UTC

Hm, I can't see any g-p-m function involved in that stacktrace, probably due to missing debug symbols. Could you get us a stacktrace with symbols please?

Also, a stacktrace could be of help, when running g-p-m with the environment variable G_DEBUG set to "fatal_criticals".

TIA

Comment 2 Christopher Halse Rogers 2008-09-01 23:57:11 UTC

Created attachment 117816 [details]
gdb session with G_DEBUG set to 'fatal_criticals'

Ha.  Silly me.  I'd installed all the debug symbols for g-p-m's dependencies, but not for g-p-m itself!

Here's a backtrace with g-p-m debug symbols, and G_DEBUG set to fatal_criticals.

Comment 3 Christopher Halse Rogers 2008-09-02 04:21:54 UTC

This looks to be the same as the (resolved) bug 547766.

*** This bug has been marked as a duplicate of 547766 ***