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

Bug #447664 reported by Mike Basinger
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: gnome-power-manager

gnome-power-manager crashes when unpluging from AC power.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Oct 9 17:59:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-manager
NonfreeKernelModules: nvidia wl
Package: gnome-power-manager 2.28.0-0ubuntu3
ProcCmdline: gnome-power-manager
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.42-generic
SegvAnalysis:
 Segfault happened at: 0x8052de3: mov 0x8(%eax),%eax
 PC (0x08052de3) ok
 source "0x8(%eax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
 ?? ()
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
Uname: Linux 2.6.31-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Mike Basinger (mike.basinger) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:gpm_disks_set_spindown_timeout (disks=0x80f6290, timeout=60)
gpm_manager_client_changed_cb (client=0x8118480,
g_cclosure_marshal_VOID__VOID ()
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0

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

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 431023, 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.

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.