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
On startup
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-power-manager 2.32.0-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Fri Apr 8 02:57:00 2011
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcCmdline: gnome-power-manager
ProcEnviron:
LANGUAGE=pt_PT:en
LANG=pt_PT.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f6897 <fclose+23>: cmpb $0x0,0x46(%esi)
PC (0x007f6897) ok
source "$0x0" ok
destination "0x46(%esi)" (0x00000046) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-power-manager
StacktraceTop:
fclose () from /lib/i386-
?? ()
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: 08/17/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.49
dmi.board.
dmi.board.name: 30FD
dmi.board.vendor: Compal
dmi.board.version: 01.99
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.