gnome-power-manager crashes when starting a guest session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
gnome-power-manager crashes when starting a guest session.
Yet I don't get any further problems. For example, if I press the power button, I do get the shutdown/
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
CrashCounter: 1
Date: Thu Apr 14 18:01:13 2011
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
MachineType: Dell Inc. Latitude E5500
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: gnome-power-manager
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x53a897 <fclose+23>: cmpb $0x0,0x46(%esi)
PC (0x0053a897) 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: Upgraded to natty on 2011-04-03 (11 days ago)
UserGroups:
dmi.bios.date: 04/15/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0DW634
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E5500
dmi.sys.vendor: Dell Inc.
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.