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

[Eliah Kagan]

Binary package hint: gnome-power-manager

Shortly after logging into a Lubuntu Desktop session on a Lubuntu Oneiric i386 system, gnome-power-manager 3.0.2-0ubuntu1 crashed with signal 5 (SIGTRAP) in g_object_newv(). This looks a bit like bug 788801 (see the stack trace in that bug's duplicate bug 797162), so perhaps this is also due to the package (gnome-power-manager in this case, rather than indicator-datetime-preferences) not yet being ported to gtk3.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gnome-power-manager 3.0.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
Uname: Linux 2.6.39-3-generic i686
Architecture: i386
CrashCounter: 1
CurrentDmesg: [ 172.890085] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
Date: Tue Jun 14 21:29:12 2011
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: Unknown
GnomeSessionInhibitors: Failed to acquire
GnomeSessionSuspendInhibited: Unknown
InstallationMedia: Lubuntu 11.04 "Natty Narwhal" - i386 (20101203)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.39-3-generic root=UUID=0de7388d-7c47-4992-b4a0-66d8b40bdb07 ro quiet splash vt.handoff=7
Signal: 5
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
 g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: gnome-power-manager crashed with signal 5 in g_object_newv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/31/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/31/2009:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.

[Jean-Baptiste Lallement (jibel)]

Thanks for your report. Could you please install libglib2.0-0-dbg and provide a full trace ?
You can use apport-retrace (https://wiki.ubuntu.com/Apport#Tools) on the crash file which will install the required dbg packages.
Thanks in advance.

[Eliah Kagan (degeneracypressure)]

With libglib2.0-0-dbg installed, I attempted to retrace with "sudo apport-retrace -g" followed by the .crash file. This is all I got for the trace:

Program terminated with signal 5, Trace/breakpoint trap.
#0 0x004d03f9 in g_return_if_fail_warning (
    log_domain=0x83de401 "\344=\b\360\263v\a schema 'org.gnome.settings-daemon.plugins.power' is not installP", pretty_function=0x0, expression=0x0)
    at /build/buildd/glib2.0-2.29.8/./glib/gmessages.c:582
582 /build/buildd/glib2.0-2.29.8/./glib/gmessages.c: No such file or directory.
 in /build/buildd/glib2.0-2.29.8/./glib/gmessages.c
(gdb) bt
#0 0x004d03f9 in g_return_if_fail_warning (
    log_domain=0x83de401 "\344=\b\360\263v\a schema 'org.gnome.settings-daemon.plugins.power' is not installP", pretty_function=0x0, expression=0x0)
    at /build/buildd/glib2.0-2.29.8/./glib/gmessages.c:582
#1 0x00000005 in ?? ()
#2 0x083de401 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

I invoked ubuntu-bug with the .crash file and examined the stack trace to make sure I wasn't making a mistake, and confirmed that this is the crash file from this bug, even though the not very successful retrace looks quite different. (I did not resubmit the report.) A full session transcript (with a few control characters from interactive prompts removed for easy reading) is attached.

Do you have any recommendations for another way to get a good trace? (The crash has not recurred yet. Or, if it has, Apport has not been triggered, perhaps because of the constant crashing of nm-applet every second or so on the same machine, due to bug 797498. I'll update shortly to get the fix for that.)

[Eliah Kagan (degeneracypressure)]

I updated to fix the unrelated nm-applet crash which was interfering with Apport, and moved the original crash report out of the /var/crash directory, and this crash (which was apparently happening every time I logged on) triggered Apport. I've re-reported it as bug 797712, which has a complete stack trace and an almost complete thread stack trace. Since that contains the requested information and no one else has indicated they are affected by this bug yet, I'm marking this as a duplicate of that report.

[Eliah Kagan (degeneracypressure)]

In case anyone is wondering, the reason this bug is a duplicate of bug 607999 is because this bug was re-reported as bug 797712, and bug 797712 has just been found to be a duplicate of bug 607999. In the (unlikely) event that anyone thinks this isn't really a duplicate of bug 607999, they should post in/about bug 797712 instead of this bug.