Ubuntu
unity package

compiz crashed with SIGSEGV

Bug #943335 reported by Jean-Baptiste Lallement on 2012-02-29

This bug report is a duplicate of: Bug #927168: compiz crashed with SIGSEGV in memmove() from drisw_update_tex_buffer() from dri_set_tex_buffer2() from drisw_bind_tex_image() from __glXBindTexImageEXT() from TfpTexture::enable() from enableFragmentOperationsAndDrawGeometry(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	unity (Ubuntu)	New	Undecided	Unassigned

Bug Description

Ubuntu Alternate i386 LTSP

Crash on ltsp client start.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: unity 5.4.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.93-0ubuntu2
Architecture: i386
Date: Wed Feb 29 16:25:08 2012
ExecutablePath: /usr/bin/compiz
ExecutableTimestamp: 1330015289
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120228)
ProcCmdline: compiz --replace
ProcCwd: /home/ubuntu
ProcEnviron:
LANGUAGE=en_US.UTF-8
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0xb74e1b53: rep movsl %ds:(%esi),%es:(%edi)
PC (0xb74e1b53) ok
source "%ds:(%esi)" (0xd43c75db) not located in a known VMA region (needed readable region)!
destination "%es:(%edi)" (0xaea0109b) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
?? () from /lib/i386-linux-gnu/libc.so.6
?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
?? () from /usr/lib/i386-linux-gnu/dri/swrast_dri.so
?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
?? () from /usr/lib/i386-linux-gnu/mesa/libGL.so.1
Title: compiz crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Jean-Baptiste Lallement (jibel) wrote on 2012-02-29:

Dependencies.txt Edit (6.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2012-02-29: This bug is a duplicate

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