mutter crashed with SIGSEGV in ctk_render_custom_quad_asm() - I received this when I ran the mouse over the left hand icon bar. This is the netbook image. After choosing to try ubuntu netbook.... there is a failure of some sort before I got to the desktop. Too fast to read.
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mutter (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: mutter
- I received this when I ran the mouse over the left hand icon bar. This is the netbook image. After choosing to try ubuntu netbook.... there is a failure of some sort before I got to the desktop. Too fast to read, one line at the top of a black screen.
I tested this on 2 dell D600 laptops with the same results.
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: mutter 2.31.5-0ubuntu9
ProcVersionSign
Uname: Linux 2.6.35-22-generic i686
Architecture: i386
Date: Sat Apr 9 14:49:24 2011
ExecutablePath: /usr/bin/mutter
LiveMediaBuild: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: mutter
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x41a111c <ctk_render_
PC (0x041a111c) ok
source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mutter
StacktraceTop:
ctk_render_
ctk_render_
?? () from /usr/lib/
?? () from /usr/lib/
g_cclosure_
Title: mutter crashed with SIGSEGV in ctk_render_
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Luke Up (x-launchpad-lukeup-com) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #688733, 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.