Ubuntu
gnome-power-manager package

gnome-power-manager crashed with signal 5 in dbus_g_connection_register_g_object()

Bug #523041 reported by smoosh
160
This bug affects 34 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Fix Released
Critical
Martin Pitt
Ubuntu lucid-alpha-3
Lucid
Fix Released
Critical
Martin Pitt
Ubuntu lucid-alpha-3

Bug Description

Binary package hint: gnome-power-manager

Crashed right after startup

ProblemType: Crash
Architecture: i386
Date: Wed Feb 17 07:12:20 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-power-manager
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100213)
Package: gnome-power-manager 2.29.2-0ubuntu5
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
Signal: 5
SourcePackage: gnome-power-manager
StacktraceTop:
 dbus_g_connection_register_g_object ()
 ?? () from /usr/lib/libappindicator.so.0
 app_indicator_set_menu () from /usr/lib/libappindicator.so.0
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: gnome-power-manager crashed with signal 5 in dbus_g_connection_register_g_object()
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:4177): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:4177): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (bluetooth-applet:4241): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed
 (polkit-gnome-authentication-agent-1:4259): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
smoosh (lolomcdoo) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 dbus_g_connection_register_g_object (connection=0x8438d0c,
 check_connect (self=0x840e000)
 app_indicator_set_menu (self=0x840e000, menu=0x845caf0)
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-power-manager (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Martin Pitt (pitti) wrote :

I get this as well. This started to happen with the new indicator patch from yesterday (see bug 497870).

Changed in gnome-power-manager (Ubuntu):
status: New → Confirmed
assignee: nobody → Jan Arne Petersen (jpetersen)
importance: Medium → High
visibility: private → public
Revision history for this message
Martin Pitt (pitti) wrote :

This breaks g-p-m completely, milestoning for alpha-3. Jan, Ken, can you please have a look at this?

Changed in gnome-power-manager (Ubuntu Lucid):
milestone: none → lucid-alpha-3
status: Confirmed → Triaged
Revision history for this message
Martin Pitt (pitti) wrote :

If I start g-p-m manually, it works, but I get a nice message

(gnome-power-manager:1852): GLib-GObject-WARNING **: IA__g_object_new_valist: object class `GsdOsdNotification' has no property named `Z\x8b\u000c$\x89\u0004$\x8bD$\u0004\xc2\u000c'

which looks like corrupt memory. It doesn't seem directly related to this crash, though, but is also a sign of addressing invalid/corrupted memory.

Revision history for this message
Martin Pitt (pitti) wrote :

This patch should be written more robustly. It initializes icon->priv->app_indicator = app_indicator_new() without ever checking for success, or NULL, and all the new code which accesses this does not do anything like g_assert() or g_return_if_fail() if the indicator is NULL. It should just fall back to the current upstream behaviour (showing its own tray icon) if initializing the indicator fails.

Revision history for this message
Martin Pitt (pitti) wrote :

Backing out patch for now.

affects: gnome-power-manager (Ubuntu Lucid) → udev (Ubuntu Lucid)
Changed in udev (Ubuntu Lucid):
assignee: Jan Arne Petersen (jpetersen) → Martin Pitt (pitti)
importance: High → Medium
affects: udev (Ubuntu Lucid) → gnome-power-manager (Ubuntu Lucid)
Changed in gnome-power-manager (Ubuntu Lucid):
importance: Medium → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnome-power-manager - 2.29.2-0ubuntu6

---------------
gnome-power-manager (2.29.2-0ubuntu6) lucid; urgency=low

  * debian/rules: Disable appindicator for now. The patch causes g-p-m to
    crash on startup (LP: #523041 ), is very brittle (no
    checks for indicator_new() failure/NULL pointers) and does not fall back
    to upstream behaviour dynamically if indicator initialization fails.
    This reopens LP #497870.
 -- Martin Pitt <email address hidden> Wed, 17 Feb 2010 10:02:05 +0100

Changed in gnome-power-manager (Ubuntu Lucid):
status: Triaged → Fix Released
Revision history for this message
Jan Arne Petersen (jpetersen) wrote :

I get the same crash in every application using the AppIndicator when killing indicator-application-service twice. So it seems a geenral problem and not gnome-power-manager specific.

Revision history for this message
Jan Arne Petersen (jpetersen) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.