mutter crashed with SIGSEGV

Bug #656414 reported by Matt Zimmerman
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)

Bug Description

Binary package hint: mutter

This happened when switching from my netbook's internal display to an external monitor

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: mutter 2.31.5-0ubuntu9
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
CrashCounter: 1
Date: Thu Oct 7 17:16:29 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/mutter
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Alpha i386 (20100315)
ProcCmdline: mutter
 PATH=(custom, user)
 Segfault happened at: 0x41f391d: mov (%eax),%eax
 PC (0x041f391d) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mutter
 ?? () from /usr/lib/dri/
 ?? () from /usr/lib/dri/
 ?? () from /usr/lib/dri/
 ?? () from /usr/lib/dri/
 ?? () from /usr/lib/dri/
Title: mutter crashed with SIGSEGV
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Matt Zimmerman (mdz) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

 i915_emit_state (intel=0x945d998) at i915_vtbl.c:311
 intelRenderStart (ctx=0x945d998) at intel_tris.c:1088
 run_render (ctx=0x945d998, stage=0x94b5188)
 _tnl_run_pipeline (ctx=0x945d998) at tnl/t_pipeline.c:153
 intelRunPipeline (ctx=0x945d998) at intel_tris.c:1075

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mutter (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Matt Zimmerman (mdz)
visibility: private → public
Revision history for this message
dino99 (9d9) wrote :

maverick is well dead since a while

Changed in mutter (Ubuntu):
status: New → Invalid
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.