unity-panel-service crashed with SIGABRT in raise()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The problem is appearing after update from Oneiric Ocelot to Precise Pangoline
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-0ubuntu2
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: None
CrashCounter: 1
Date: Sat Mar 31 17:33:00 2012
DistUpgraded: 2012-03-31 17:11:41,661 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: MSI MS-7032
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-31 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 07/26/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080011
dmi.board.
dmi.board.name: MS-7032
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7032
dmi.product.
dmi.sys.vendor: MSI
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.