unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Sorry can't give you too much info. Updated to all the lastest patches and new kernel. Prior to this the optirun command would not work under bumblebee on my Nvidia optimus notebook. After a reboot with for the patches I ran the optirun xbmc command and it actually worked but I got this unity panel crash. Tried the same command again and didn't get this crash. XBMC (eden) works fine.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-21-
NonfreeKernelMo
.proc.driver.
.proc.driver.
.tmp.unity.
ApportVersion: 2.0-0ubuntu1
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sat Mar 31 10:50:54 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120325)
MachineType: Acer Aspire 4750
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANGUAGE=en_SG:en
LANG=en_SG.UTF-8
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: 02/18/2011
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V1.19
dmi.board.
dmi.board.name: Aspire 4750
dmi.board.vendor: Acer
dmi.board.version: V1.19
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: Aspire 4750
dmi.product.
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.7.2-0ubuntu4
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
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.