compiz crashed with SIGSEGV in nux::GpuRenderStates::SubmitChangeStates()

Bug #700560 reported by Rogério Theodoro de Brito
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Nux
New
Undecided
Unassigned
Unity
New
Undecided
Unassigned
nux (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: compiz

Hi.

I just had some 10 minutes to spare and decided to try the latest natty ISO and, just upon starting the desktop, I received a message that compiz died. This crash is 100% reproducible with this image and I can provide any further details. For the time being, I will only send what apport gathered, since life is annoying without a window manager.

Regards,

Rogério Brito.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.2.1+glibmainloop3-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.37-12.26-generic 2.6.37
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/allscreens/options/active_plugins'
CrashCounter: 1
Date: Sun Jan 9 04:46:17 2011
Disassembly: => 0x0: Não é possível acessar a memória no endereço 0x0
ExecutablePath: /usr/bin/compiz
LiveMediaBuild: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110108)
PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G Integrated Graphics Controller [8086:2572] (rev 02) (prog-if 00 [VGA controller])
ProcCmdline: /usr/bin/compiz
ProcEnviron:
 LANGUAGE=pt_BR.UTF-8:pt:en_GB:en
 LANG=pt_BR.UTF-8
 LC_MESSAGES=pt_BR.utf8
 SHELL=/bin/bash
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- locale=pt_BR console-setup/layoutcode?=br console-setup/modelcode?=abnt2
RelatedPackageVersions:
 xserver-xorg 1:7.5+6ubuntu6
 libgl1-mesa-glx 7.9+repack-1ubuntu3
 libdrm2 2.4.22-2ubuntu1
 xserver-xorg-video-intel 2:2.13.901-2ubuntu2
 xserver-xorg-video-ati 1:6.13.2-1ubuntu2
SegvAnalysis:
 Segfault happened at: 0x0: Não é possível acessar a memória no endereço 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
 source "0x0" (0x00000000) not located in a known VMA region (needed readable region)!
SegvReason:
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 ?? ()
 nux::GpuRenderStates::SubmitChangeStates() () from /usr/lib/libnux-graphics-0.9.so.0
 nux::WindowThread::RenderInterfaceFromForeignCmd() () from /usr/lib/libnux-0.9.so.0
 UnityScreen::paintDisplay(CompRegion const&) () from /usr/lib/compiz/libunityshell.so
 UnityScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in nux::GpuRenderStates::SubmitChangeStates()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] Arquivo ou diretório não encontrado: '/etc/X11/xorg.conf'
XsessionErrors: (nautilus:3151): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed
dmi.bios.date: 08/31/2006
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: 8I865GME-775
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd08/31/2006:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn8I865GME-775:rvr:cvn:ct3:cvr:
glxinfo: Error: [Errno 2] Arquivo ou diretório não encontrado
system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-12-generic

Revision history for this message
Rogério Theodoro de Brito (rbrito) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 nux::WindowThread::RenderInterfaceFromForeignCmd (
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
tags: added: compiz-0.9
visibility: private → public
affects: compiz (Ubuntu) → nux (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.