unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Compiz keeps shutting down, and last night it shut-down the whole netbook and I had to log-in again.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-20-generic i686
.tmp.unity.
ApportVersion: 2.0-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
CurrentDmesg: [ 42.588880] init: plymouth-stop pre-start process (1510) terminated with status 1
Date: Sat Mar 31 09:02:13 2012
DistUpgraded: 2012-03-03 22:25:47,219 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Acer AOD257
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-04 (27 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 06/13/2011
dmi.bios.vendor: INSYDE
dmi.bios.version: V1.06
dmi.board.
dmi.board.name: JE06_PT
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.
dmi.modalias: dmi:bvnINSYDE:
dmi.product.name: AOD257
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.
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.