compiz crashed with SIGSEGV in i915UpdateTextureState()

[iGadget]

I was just trying to open the File menu in Nautilus when I noticed it wasn't working. Then all of the sudden the entire desktop was garbled (allthough the mouse pointer still looked and responded fine). After a few seconds, the desktop returned but different sections started blinking into a repeating pattern. All I could do from there was do CTRL+Alt+F1 and try a sudo gdm-restart. This didn't work either (just a black screen), so I did a reboot from the console. After that I was kindly requested to report this bug.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.38-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 6 21:43:20 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x6483e96: mov 0x20c(%eax),%eax
 PC (0x06483e96) ok
 source "0x20c(%eax)" (0x0000020c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /usr/lib/dri/i915_dri.so
 i915UpdateTextureState () from /usr/lib/dri/i915_dri.so
 ?? () from /usr/lib/dri/i915_dri.so
 _tnl_draw_prims () from /usr/lib/dri/libdricore.so
 _tnl_vbo_draw_prims () from /usr/lib/dri/libdricore.so
Title: compiz crashed with SIGSEGV in i915UpdateTextureState()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[iGadget (igadget)]

FYI - together with this crashreport, I got another request to file a bug - see bug 752125 for details: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/752125

[Apport retracing service (apport)]

StacktraceTop:
 i915_update_tex_unit (intel=0x92ae120, unit=<value optimized out>, ss3=32) at i915_texstate.c:161
 i915UpdateTextureState (intel=0x92ae120) at i915_texstate.c:392
 intelRunPipeline (ctx=0x92ae120) at intel_tris.c:1063
 _tnl_draw_prims (ctx=0x92ae120, arrays=0x92f1670, prim=0xbf9c20b8, nr_prims=1, ib=0x0, min_index=0, max_index=3) at tnl/t_draw.c:518
 _tnl_vbo_draw_prims (ctx=0x92ae120, arrays=0x92f1670, prim=0xbf9c20b8, nr_prims=1, ib=0x0, index_bounds_valid=1 '\001', min_index=0, max_index=3) at tnl/t_draw.c:424

[Omer Akram (om26er)]

the stacktrace seems to have some sensitive data it seems.

[iGadget (igadget)]

Okay... that's bad. Since it's a freshly installed system, I can only guess of what that sensitive data could be. My password? Ubuntu One token?
What's a proper action to take now, remove the system from Ubuntu One? Change my password? Or am I missing something?

[Sebastien Bacher (seb128)]

where do you see sensitive datas there?

[iGadget (igadget)]

Sebastien, wouldn't it be wise to wait for Omer's reply before changing the visibility to public? Or are you certain there's no sensitive data in the stacktrace?

[Sebastien Bacher (seb128)]

I'm pretty sure there is no private data since unity doesn't deal with datas but we can keep it as private still

[Omer Akram (om26er)]

my bad, those different variable names in the trace looked like names :-P but as Seb said unity doesn't deal with that kind of data.