[Karmic] gnome-power-manager crashed with SIGSEGV in IA__g_closure_invoke()

[Andrew Cowie]

Binary package hint: gnome-power-manager

Just resumed from suspend when this bug appeared.

AfC

ProblemType: Crash
Architecture: amd64
Date: Sat Oct 10 17:56:30 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-manager
NonfreeKernelModules: nvidia
Package: gnome-power-manager 2.28.0-0ubuntu3
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-12.39-generic
SegvAnalysis:
 Segfault happened at: 0x40c601: mov 0x8(%rax),%r8
 PC (0x0040c601) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? ()
 ?? ()
 IA__g_closure_invoke (closure=<value optimized out>, return_value=<value optimized out>, n_param_values=<value optimized out>, param_values=0x422e00, invocation_hint=0x22544e0) at /build/buildd/glib2.0-2.22.2/gobject/gclosure.c:752
 signal_emit_unlocked_R (node=0x2133550, detail=<value optimized out>, instance=<value optimized out>, emission_return=<value optimized out>, instance_and_params=<value optimized out>) at /build/buildd/glib2.0-2.22.2/gobject/gsignal.c:3246
 IA__g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=0, var_args=0x7fff5dfc80d0) at /build/buildd/glib2.0-2.22.2/gobject/gsignal.c:2992
Title: gnome-power-manager crashed with SIGSEGV in IA__g_closure_invoke()
Uname: Linux 2.6.31-12-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fuse lpadmin netdev plugdev sambashare users video

[Victor Vargas (kamus)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 397766, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.