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

Bug #618891 reported by Rodolfo Augusto Manzoli
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

gnome-power-manager crashed with SIGSEGV

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-power-manager 2.31.6-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-15.21-generic 2.6.35.1
Uname: Linux 2.6.35-15-generic x86_64
Architecture: amd64
Date: Mon Aug 16 17:10:40 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-power-manager
GnomeSessionIdleInhibited: No
GnomeSessionInhibitors: None
GnomeSessionSuspendInhibited: No
InstallationMedia:

MachineType: - N/A
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-15-generic root=UUID=b38ae365-6f72-40e4-9d20-e2372bf0f466 ro vga=792 splash quiet splash
ProcCmdline: gnome-power-manager
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 LANG=pt_BR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f00ab3d207e <find_image_offset+46>: movsbl 0x0(%rbp),%eax
 PC (0x7f00ab3d207e) ok
 source "0x0(%rbp)" (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:
 icon_name_hash (cache=0x1f6a5d0,
 find_image_offset (cache=0x1f6a5d0,
 _gtk_icon_cache_get_icon_flags (cache=0x1f6a5d0,
 theme_dir_get_icon_suffix (dir=0x1d56950,
 theme_lookup_icon (
Title: gnome-power-manager crashed with SIGSEGV in icon_name_hash()
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors: (polkit-gnome-authentication-agent-1:2224): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
dmi.bios.date: 12/31/2007
dmi.bios.vendor: COMPAL
dmi.bios.version: 1.16
dmi.board.name: IFT01
dmi.board.vendor: -
dmi.board.version: IFT00
dmi.chassis.asset.tag: -
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnCOMPAL:bvr1.16:bd12/31/2007:svn-:pnN/A:pvrN/A:rvn-:rnIFT01:rvrIFT00:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: N/A
dmi.product.version: N/A
dmi.sys.vendor: -

Revision history for this message
Rodolfo Augusto Manzoli (rmanzoli88) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () 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
Download full text (5.7 KiB)

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:

libgcc1: installed version 1:4.5.1-1ubuntu2, latest version: 1:4.5.1-5ubuntu1
libavahi-common3: installed version 0.6.25-1ubuntu6, latest version: 0.6.27-2ubuntu1
mountall: installed version 2.15, latest version: 2.17
libbonobo2-common: installed version 2.24.3-1, latest version: 2.31.91-0ubuntu1
libudev0: installed version 151-12, latest version: 161+git20100827-1
libpolkit-gobject-1-0: installed version 0.96-2, latest version: 0.96-2ubuntu1
gnome-power-manager: installed version 2.31.6-0ubuntu1, latest version: 2.31.91-0ubuntu1
policykit-1: installed version 0.96-2, latest version: 0.96-2ubuntu1
python2.6: installed version 2.6.6~rc1-1ubuntu1, latest version: 2.6.6-1ubuntu1
python-minimal: installed version 2.6.5-12ubuntu1, latest version: 2.6.5-13ubuntu1
libcups2: installed version 1.4.4-3, latest version: 1.4.4-3ubuntu1
tzdata: installed version 2010k-0ubuntu1, latest version: 2010l-1
libwnck-common: installed version 1:2.30.3-0ubuntu2, latest version: 1:2.30.3-1ubuntu1
libplymouth2: installed version 0.8.2-2ubuntu3, latest version: 0.8.2-2ubuntu4
libgtk2.0-common: installed version 2.21.5-1ubuntu6, latest version: 2.21.7-1ubuntu1
klibc-utils: installed version 1.5.18-1, latest version: 1.5.20-1
gconf2: installed version 2.31.7-0ubuntu3, latest version: 2.31.91-0ubuntu3
libgdu0: installed version 2.30.1-1, latest version: 2.30.1-2
python: installed version 2.6.5-12ubuntu1, latest version: 2.6.5-13ubuntu1
libdbus-glib-1-2: installed version 0.86-1, latest version: 0.88-2
libpam0g: installed version 1.1.1-3ubuntu3, latest version: 1.1.1-4ubuntu1
libglib2.0-0: installed version 2.25.13-1ubuntu1, latest version: 2.25.15-0ubuntu2
gcc-4.5-base: installed version 4.5.1-1ubuntu2, latest version: 4.5.1-5ubuntu1
libgail18: installed version 2.21.5-1ubuntu6, latest version: 2.21.7-1ubuntu1
libklibc: installed version 1.5.18-1, latest version: 1.5.20-1
cpp-4.4: installed version 4.4.4-8ubuntu2, latest version: 4.4.4-13ubuntu2
libc-bin: installed version 2.12.1-0ubuntu1, latest version: 2.12.1-0ubuntu4
libfreetype6: installed version 2.4.2-1, latest version: 2.4.2-2
libpython2.6: installed version 2.6.6~rc1-1ubuntu1, latest version: 2.6.6-1ubuntu1
libindicator0: installed version 0.3.11-0ubuntu2, latest version: 0.3.12-0ubuntu1
passwd: installed version 1:4.1.4.2-1ubuntu2, latest version: 1:4.1.4.2-1ubuntu3
dpkg: installed version 1.15.8.2ubuntu4, latest version: 1.15.8.4ubuntu3
libgnome2-common: installed version 2.30.0-1ubuntu1, latest version: 2.31.0-0ubuntu2
libparted0debian1: installed version 2.2-7ubuntu1, latest version: 2.3-2ubuntu1
gcc-4.4-base: installed version 4.4.4-8ubuntu2, latest version: 4.4.4-13ubuntu2
libgnome-keyring0: installed version 2.30.1-1ubuntu1, latest version: 2.31.91-0ubuntu1
libdevmapper1.02.1: installed version 2:1.02.39-1ubuntu4, latest version: 2:1.02.39-1ubuntu5
udev: installed version 151-12, latest version: 161+git20100827-1
libdbusmenu-g...

Read more...

tags: removed: need-amd64-retrace
visibility: private → public
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.