compiz crashed with SIGSEGV in intel_region_data()

[Jamison Lofthouse]

I think this is related to the crashes with update manager but I was using banshee at the time it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: libnux-0.9-0 0.9.44-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
CrashCounter: 1
Date: Sun Apr 17 12:09:03 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x104d5c6: rep movsl %ds:(%esi),%es:(%edi)
 PC (0x0104d5c6) ok
 source "%ds:(%esi)" (0x0a67387b) ok
 destination "%es:(%edi)" (0x0000007b) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /lib/i386-linux-gnu/libc.so.6
 ?? ()
 intel_region_data () from /usr/lib/dri/i915_dri.so
 intel_miptree_image_data () from /usr/lib/dri/i915_dri.so
 intel_finalize_mipmap_tree () from /usr/lib/dri/i915_dri.so
Title: compiz crashed with SIGSEGV in intel_region_data()
UpgradeStatus: Upgraded to natty on 2011-04-17 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __memcpy_ia32 () at ../sysdeps/i386/i686/multiarch/../memcpy.S:75
 ?? ()
 intel_region_data (intel=0x97a2b80, dst=0xa531520, dst_offset=0, dstx=0, dsty=0, src=0xa673800, src_pitch=67, srcx=0, srcy=0, width=67, height=24) at intel_regions.c:370
 intel_miptree_image_data (intel=0x97a2b80, dst=0xa69e470, face=0, level=0, src=<value optimized out>, src_row_pitch=67, src_image_pitch=1608) at intel_mipmap_tree.c:407
 copy_image_data_to_tree (intel=0x97a2b80, unit=0) at intel_tex_validate.c:103

[Timo Aaltonen (tjaalton)]

What's the status of this bug? Marked as invalid for other components without an explanation.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.