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
Logged into guest session, logged out. Stuck at black screen/blinking line for 2 minutes.
Hit power button for reboot- skipped login screen, right to my desktop [with 2 files showing-NO panels anywhere].
Apport window pops up.
I switched to other blank workspaces.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-power-manager 2.32.0-2ubuntu2
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Wed Mar 30 15:31:07 2011
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110329.1)
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Dell Inc. Inspiron 1546
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7f56a046c0e4 <fclose+4>: mov (%rdi),%ecx
PC (0x7f56a046c0e4) 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: 02/01/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0V2X0M
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1546
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.