gnome-power-manager crashed with SIGABRT in __kernel_vsyscall()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-power-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-power-manager
This was an natty livecd; I had logged off to see if that would fix an X strangeness, this happened
upon logging in again. I had selected the old-style with no effects mode, if that matters. The
previous login was in safe mode.
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: Sun May 1 11:33:12 2011
ExecutablePath: /usr/bin/
GnomeSessionIdl
GnomeSessionInh
GnomeSessionSus
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdline: gnome-power-manager
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/false
PATH=(custom, no user)
ProcKernelCmdLine: file=/cdrom/
Signal: 6
SourcePackage: gnome-power-manager
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/i386-
abort () from /lib/i386-
g_assertion_
g_assertion_
Title: gnome-power-manager crashed with SIGABRT in __kernel_vsyscall()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 02/25/2004
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1002.002
dmi.board.name: P4P800-E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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 #740878, 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.