unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Release details:
$ lsb_release -rd
Description: Ubuntu precise (development branch)
Release: 12.04
unity:
Installed: 5.8.0-0ubuntu2
Candidate: 5.8.0-0ubuntu2
Version table:
*** 5.8.0-0ubuntu2 0
500 http://
100 /var/lib/
On first reboot after update today, got this automatically generated bug report. System took a little bit long to boot up.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-21-generic i686
.tmp.unity.
ApportVersion: 2.0-0ubuntu1
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sat Mar 31 09:15:26 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
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 admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/30/2007
dmi.bios.vendor: Intel Corp.
dmi.bios.version: GC11020M.
dmi.board.
dmi.board.name: D102GGC2
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD42789-201
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCor
version.compiz: compiz 1:0.9.7.2-0ubuntu4
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 #969413, 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.