gnome-power-manager crashed with SIGSEGV in fclose()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crash occurred while installing traceroute via the software center.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-power-manager 2.32.0-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-10-generic x86_64
Architecture: amd64
Date: Wed Aug 10 14:27:06 2011
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 3249CTO
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f9d2a69f0e4 <fclose+4>: mov (%rdi),%ecx
PC (0x7f9d2a69f0e4) ok
source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
fclose () from /lib/x86_
?? ()
g_type_
?? () from /usr/lib/
g_object_newv () from /usr/lib/
Title: gnome-power-manager crashed with SIGSEGV in fclose()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 06/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET46WW (1.16 )
dmi.board.name: 3249CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 3249CTO
dmi.product.
dmi.sys.vendor: LENOVO
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #736291, so 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. Please continue to report any other bugs you may find.