compiz crashed with SIGSEGV in TfpTexture::bindTexImage()

Bug #1047205 reported by kylea
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Opened LIbreOffice Text - Screen froze and then compiz crashed and restarted

Linux kylea-1210 3.5.0-13-generic #14-Ubuntu SMP Wed Aug 29 16:48:44 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Description: Ubuntu quantal (development branch)
Release: 12.10

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.4.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3
Uname: Linux 3.5.0-13-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
Date: Fri Sep 7 17:30:27 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb7b59a8696: movdqu -0x10(%rsi),%xmm0
 PC (0x7fb7b59a8696) ok
 source "-0x10(%rsi)" (0x249a6c50) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 TfpTexture::bindTexImage(unsigned long const&) () from /usr/lib/compiz/libopengl.so
 TfpTexture::enable(GLTexture::Filter) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in TfpTexture::bindTexImage()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
kylea (kylea) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /tmp/tmpbF1TVS/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (10.5 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

metacity-common version 1:2.34.5-0ubuntu1 required, but 1:2.34.8-0ubuntu2 is available
libquvi-scripts version 0.4.7-1 required, but 0.4.8-2 is available
outdated debug symbol package for libcdparanoia0: package version 3.10.2+debian-11 dbgsym version 3.10.2+debian-10ubuntu1
mountall version 2.38 required, but 2.40 is available
libedata-book-1.2-15 version 3.5.90-0ubuntu1 required, but 3.5.91-0ubuntu1 is available
libudisks2-0 version 1.99.0-2 required, but 1.99.0-3 is available
outdated debug symbol package for libudisks2-0: package version 1.99.0-3 dbgsym version 1.99.0-2
tzdata version 2012e-0ubuntu1 required, but 2012e-0ubuntu2 is available
libglib2.0-bin version 2.33.10-0ubuntu3 required, but 2.33.12-3 is available
outdated debug symbol package for libglib2.0-bin: package version 2.33.12-3 dbgsym version 2.33.10-0ubuntu3
libgail-3-0 version 3.5.12-0ubuntu3 required, but 3.5.16-0ubuntu1 is available
outdated debug symbol package for libjack-jackd2-0: package version 1.9.8~dfsg.4+20120529git007cdc37-2ubuntu1 dbgsym version 1.9.8~dfsg.1-1ubuntu1
yelp-xsl version 3.5.90-0ubuntu2 required, but 3.5.91-0ubuntu1 is available
apt version 0.9.7.5ubuntu1 required, but 0.9.7.5ubuntu2 is available
gir1.2-freedesktop version 1.33.9-1 required, but 1.33.10-1 is available
libgtk-3-0 version 3.5.12-0ubuntu3 required, but 3.5.16-0ubuntu1 is available
python-problem-report version 2.5.1-0ubuntu4 required, but 2.5.1-0ubuntu7 is available
python-gi version 3.3.90-1 required, but 3.3.91-1 is available
libyelp0 version 3.5.90-0ubuntu1 required, but 3.5.91-0ubuntu1 is available
libgoa-1.0-common version 3.5.90-0ubuntu1 required, but 3.5.91-0ubuntu1 is available
apport version 2.5.1-0ubuntu4 required, but 2.5.1-0ubuntu7 is available
gvfs-common version 1.13.7-0ubuntu5 required, but 1.13.7-0ubuntu6 is available
libapt-pkg4.12 version 0.9.7.5ubuntu1 required, but 0.9.7.5ubuntu2 is available
libgl1-mesa-glx version 9.0~git20120821.c1114c61-0ubuntu2 required, but 9.0~git20120903.e1673d20-0ubuntu1 is available
gsettings-desktop-schemas version 3.5.90-0ubuntu2 required, but 3.5.91-0ubuntu1 is available
gir1.2-goa-1.0 version 3.5.90-0ubuntu1 required, but 3.5.91-0ubuntu1 is available
libgtk2.0-common version 2.24.11-0ubuntu1 required, but 2.24.12-0ubuntu1 is available
libcamel-1.2-40 version 3.5.90-0ubuntu1 required, but 3.5.91-0ubuntu1 is available
outdated debug symbol package for kbd: package version 1.15.3-9ubuntu1 dbgsym version 1.15.2-3ubuntu4
libebackend-1.2-5 version 3.5.90-0ubuntu1 required, but 3.5.91-0ubuntu1 is available
libdrm-nouveau2 version 2.4.38-0ubuntu2 required, but 2.4.39-0ubuntu1 is available
outdated debug symbol package for libcap-ng0: package version 0.6.6-2ubuntu1 dbgsym version 0.6.6-1ubuntu1
libgtk-3-common version 3.5.12-0ubuntu3 required, but 3.5.16-0ubuntu1 is available
python-zeitgeist version 0.9.0.1-1 required, but 0.9.5-0ubuntu1 is available
libglib2.0-0 vers...

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 927168, so it 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. Feel free to continue to report any other bugs you may find.

tags: removed: need-amd64-retrace
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.