compiz crashed with SIGSEGV in GridScreen::handleEvent()

[Nithin Balakrishnan]

Hi,
I am very new to ubuntu/linux/unix , I am using a DELL Latitude 505 , Pentium M processor.

I am not getting the launch bar as welll

Thanks for the help in advance

REgards
Nithin

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: compiz-core 1:0.9.9~daily13.03.08-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic i686
ApportVersion: 2.9.1-0ubuntu1
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
CurrentDmesg:
 [ 37.426048] NetworkManager[869]: segfault at 4 ip 080cca26 sp bfc5d570 error 4 in NetworkManager[8048000+101000]
 [ 42.854991] init: network-manager main process (869) killed by SEGV signal
 [ 42.855042] init: network-manager main process ended, respawning
Date: Sat Mar 16 20:59:32 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Intel Corporation 82852/855GM Integrated Graphics Device [8086:3582] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Dell Latitude D505 [1028:0163]
   Subsystem: Dell Latitude D505 [1028:0163]
InstallationDate: Installed on 2013-03-16 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130315)
MachineType: Dell Inc. Latitude D505
MarkForUpload: True
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-12-generic root=UUID=A6A26F7DA26F50BB loop=/hostname/disks/root.disk ro rootflags=sync quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0xb4a39bef <_ZN10GridScreen11handleEventEP7_XEvent+2447>: mov 0x28(%eax),%edx
 PC (0xb4a39bef) ok
 source "0x28(%eax)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 GridScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libgrid.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20130125
 RegexScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libregex.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20130125
 SnapScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libsnap.so
Title: compiz crashed with SIGSEGV in GridScreen::handleEvent()
UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code -11:
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 11/03/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0H2049
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/03/2006:svnDellInc.:pnLatitudeD505:pvr:rvnDellInc.:rn0H2049:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D505
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.03.08-0ubuntu1
version.libdrm2: libdrm2 2.4.42-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu2b1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1b1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.4-0ubuntu1b1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu3b1

[Apport retracing service (apport)]

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 #1054049, 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.