unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Something crashed, but no clue what happened. Everything looks OK.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
NonfreeKernelMo
.proc.driver.
.proc.driver.
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sun Apr 1 15:06:31 2012
DistUpgraded: 2012-03-24 05:31:16,036 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Gateway FX530XM
ProcCmdline: /usr/lib/
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 6
SourcePackage: unity
Title: unity-panel-service crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-03-24 (10 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 01/09/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LA97510J.
dmi.board.
dmi.board.name: OEMD975XBGG1
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD59331-206
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.chassis.
dmi.modalias: dmi:bvnIntelCor
dmi.product.name: FX530XM
dmi.product.
dmi.sys.vendor: Gateway
version.compiz: compiz 1:0.9.7.2-0ubuntu4
version.ia32-libs: ia32-libs 20090808ubuntu35
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.