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

Bug #493212 reported by Nicolas Sassiat
78
This bug affects 35 people
Affects Status Importance Assigned to Milestone
devicekit-power (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-power-manager

?

ProblemType: Crash
Architecture: i386
Date: Sat Dec 5 18:00:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-power-manager
Package: gnome-power-manager 2.28.1-0ubuntu1
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=en_GB.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
 LANGUAGE=en_GB:en
ProcVersionSignature: Ubuntu 2.6.27-14.33-generic
SegvAnalysis:
 Segfault happened at: 0xb7845047 <g_str_hash+7>: movsbl (%edx),%eax
 PC (0xb7845047) ok
 source "(%edx)" (0x00000000) 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_str_hash () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libdevkit-power-gobject.so.1
 g_cclosure_marshal_VOID__STRING ()
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: gnome-power-manager crashed with SIGSEGV in g_str_hash()
Uname: Linux 2.6.27-14-generic i686
UserGroups:

Revision history for this message
Nicolas Sassiat (n-sassiat) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:g_ascii_strtod () from /lib/libglib-2.0.so.0
g_hash_table_get_keys () from /lib/libglib-2.0.so.0
dkp_device_removed_cb (proxy=0x932d008,
g_cclosure_marshal_VOID__STRING ()
marshal_dbus_message_to_g_marshaller (closure=0x93335e8,

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
visibility: private → public
affects: gnome-power-manager (Ubuntu) → devicekit-power (Ubuntu)
Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

I have just reported bug 728867, which I think may be a duplicate of this bug, but I am not sure. Bug 728867 looks like it may have a better stack trace, and I was able to describe what I was doing when it occurred (though of course that description might not actually be causally related to the bug).

Revision history for this message
Tommy_CZ (t-kijas) wrote :

I can confirm it in latest Natty Alpha 3, 64-bit.

Changed in devicekit-power (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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