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

Bug #637017 reported by suedpol
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gnome-power-manager

I`m running Ubuntu Maverick Beta 64bit on a Compal based Notebook. From time to time, i am testing gnome-shell. When I start gnome-shell or switch from default Desktop, this error occured.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.91-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Mon Sep 13 13:29:32 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100803.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-20-generic root=UUID=65a53c23-2717-4914-91da-55314008338e ro quiet splash
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANG=de_DE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffc6cf5b5c0 <g_str_hash>: movsbl (%rdi),%eax
 PC (0x7ffc6cf5b5c0) ok
 source "(%rdi)" (0x00000001) 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
 g_hash_table_lookup () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: gnome-power-manager crashed with SIGSEGV in g_str_hash()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 04/24/2008
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.06A
dmi.board.asset.tag: N/A
dmi.board.version: 1.06A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: COMPAL
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.06A:bd04/24/2008:svn:pn:pvr1.06A:rvn:rn:rvr1.06A:cvnCOMPAL:ct10:cvrN/A:
dmi.product.version: 1.06A

Revision history for this message
suedpol (j-granz) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_str_hash (v=0x1) at /build/buildd/glib2.0-2.25.15/glib/gstring.c:133
 g_hash_table_lookup (hash_table=0x11e5de0, key=0x1)
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-power-manager (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libavahi-common3: installed version 0.6.27-2ubuntu2, latest version: 0.6.27-2ubuntu3
libgdk-pixbuf2.0-0: installed version 2.21.6-2ubuntu5, latest version: 2.21.7-1ubuntu3
libavahi-glib1: installed version 0.6.27-2ubuntu2, latest version: 0.6.27-2ubuntu3
initramfs-tools: installed version 0.98.1ubuntu1, latest version: 0.98.1ubuntu2
libavahi-common-data: installed version 0.6.27-2ubuntu2, latest version: 0.6.27-2ubuntu3
libavahi-client3: installed version 0.6.27-2ubuntu2, latest version: 0.6.27-2ubuntu3
initramfs-tools-bin: installed version 0.98.1ubuntu1, latest version: 0.98.1ubuntu2

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
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.