gnome-power-manager crashed with SIGSEGV in fclose()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
one more
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-power-manager 2.32.0-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Fri Mar 25 23:33:04 2011
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: Sony Corporation VGN-Z11VRN_B
ProcCmdline: gnome-power-manager
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f988721b0e4 <fclose+4>: mov (%rdi),%ecx
PC (0x7f988721b0e4) 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: Upgraded to natty on 2011-03-25 (1 days ago)
UserGroups:
dmi.bios.date: 07/17/2009
dmi.bios.vendor: INSYDE
dmi.bios.version: R2169M3
dmi.board.
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: VGN-Z11VRN_B
dmi.product.
dmi.sys.vendor: Sony Corporation
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.