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

Bug #408456 reported by roman y. bogdanov
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

after apt-get upgrade, and installed new kernel. but not reboot.

ProblemType: Crash
ACAdapter: Not Present
Architecture: i386
Battery: Not Present
CPUScaling: Not Present
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gnome-power-manager
HalComputerInfo:
 Error: command ['lshal', '-u', '/org/freedesktop/Hal/devices/computer'] failed with exit code 1: Could not initialise connection to hald.
 Normally this means the HAL daemon (hald) is not running or not ready.
LaptopPanel: Not Present
Package: gnome-power-manager 2.24.2-2ubuntu8
ProcCmdLine: root=UUID=16b91f4a-1b8d-423a-a5b7-be17d4804be1 ro crashkernel=384M-2G:64M@16M,2G-:128M@16M
ProcCmdline: gnome-power-manager
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature'
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__BOOLEAN ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__BOOLEAN()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
roman y. bogdanov (brjppru) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Possible regression detected

This crash has the same stack trace characteristics as bug #148175. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.

tags: added: regression-retracer
tags: removed: need-i386-retrace
Revision history for this message
Scott Howard (showard314) wrote :

Thanks for your report and helping make Ubuntu better. After rebooting, has this crash reappeared? It appears that HAL crashed after the upgrade, which caused GPM to crash.

(From dmesg):

hal segfaulted first:
[362742.276805] hald[2737]: segfault at b7a16008 ip b7d3e078 sp bfb89ecc error 4 in libc-2.9.so[b7cc7000+15c000]
[366251.920944] gnome-power-man[3670]: segfault at 8 ip 0806de43 sp bf88c4b0 error 4 in gnome-power-manager[8048000+50000]

Changed in gnome-power-manager (Ubuntu):
status: New → Incomplete
visibility: private → public
Revision history for this message
roman y. bogdanov (brjppru) wrote :

after reboot, all ok

Revision history for this message
Scott Howard (showard314) wrote :

Thanks for following up. It appears that the install modified a file HAL needed to continue to run, and a reboot was necessary. Closing since Ubuntu now uses devicekit-power instead of HAL, and a reboot was necessary to properly boot with the new kernel.

Changed in gnome-power-manager (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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