compiz crashed with SIGSEGV in CompWindow::id()

[raed]

lsb_release -rd
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

after login to ubuntu 13.04 this bug appears every time

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: compiz-core 1:0.9.9~daily13.01.25-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4
Uname: Linux 3.8.0-2-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.8-0ubuntu3
Architecture: i386
CasperVersion: 1.330
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Thu Jan 31 11:04:30 2013
DistUpgraded: Fresh install
DistroCodename: raring
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Giga-byte Technology Device [1458:353b]
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130131)
MachineType: Dell Inc. OptiPlex 790
MarkForUpload: True
ProcCmdline: compiz --sm-disable --fast-filter decor
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --
SegvAnalysis:
 Segfault happened at: 0xb7761f0a <_ZNK10CompWindow2idEv+10>: mov 0x10(%eax),%eax
 PC (0xb7761f0a) ok
 source "0x10(%eax)" (0x00000098) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 CompWindow::id() const () from /usr/lib/libcompiz_core.so.ABI-20121210
 PrivateCompositeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libcomposite.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20121210
 DecorScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libdecor.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20121210
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/11/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0HY9JP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA03:bd04/11/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1
version.libdrm2: libdrm2 2.4.41-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2
xserver.bootTime: Thu Jan 31 11:04:37 2013
xserver.configfile: default
xserver.devices:
 input Power Button KEYBOARD, id 6
 input Power Button KEYBOARD, id 7
 input Dell Dell QuietKey Keyboard KEYBOARD, id 8
 input Logitech USB Optical Mouse MOUSE, id 9
 input Microsoft LifeChat LX-3000 KEYBOARD, id 10
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.13.2-0ubuntu1
xserver.video_driver: nouveau

[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 #976513, 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.