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 happened.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity-services 5.8.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-21-generic i686
NonfreeKernelMo
.proc.driver.
Fast Writes: Supported
SBA: Supported
AGP Rates: 8x 4x
Registers: 0xff000e1b:
.proc.driver.
Status: Enabled
Driver: AGPGART
AGP Rate: 8x
Fast Writes: Disabled
SBA: Enabled
.proc.driver.
.proc.driver.
ApportVersion: 2.0-0ubuntu2
Architecture: i386
CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
Date: Sun Apr 1 20:06:48 2012
DistUpgraded: 2012-02-19 14:44:30,889 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Dell Computer Corporation Precision WorkStation 360
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-02-19 (42 days ago)
UserGroups:
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 09/27/2004
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A08
dmi.board.name: 0H1639
dmi.board.vendor: Dell Computer Corp.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComp
dmi.product.name: Precision WorkStation 360
dmi.sys.vendor: Dell Computer Corporation
version.compiz: compiz 1:0.9.7.2-0ubuntu4
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.