unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i don't know what is happend.. after last update i restarted my pc and there was an alert with a question if i want to report this bug. Also my wireless mouse is not working.. only touchpad..
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-21-generic i686
NonfreeKernelMo
.tmp.unity.
ApportVersion: 2.0-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Mon Apr 2 08:49:33 2012
DistUpgraded: 2012-03-12 08:10:37,854 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: LENOVO 4151/200
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-12 (20 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare
dmi.bios.date: 03/26/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 0CCN52WW(V1.18)
dmi.board.name: JIWA1
dmi.board.vendor: LENOVO
dmi.board.version: REFERENCE
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 4151/200
dmi.product.
dmi.sys.vendor: LENOVO
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 #971216, 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.