unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Don't know how to reproduce
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-22-generic x86_64
NonfreeKernelMo
.tmp.unity.
ApportVersion: 2.0-0ubuntu5
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sat Mar 31 00:20:54 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
MachineType: Micro-Star International Co., Ltd. X370
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_IN:en
LANG=en_IN
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: unity
Title: unity-panel-service crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/14/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1356AMS.10D
dmi.board.
dmi.board.name: MS-1356
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: Ver 1.000
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: X370
dmi.product.
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #969360, 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.