mutter crashed with SIGSEGV in ctk_render_target_new()

Bug #651198 reported by luk1don
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mutter (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mutter

Apport

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: mutter 2.31.5-0ubuntu8
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Wed Sep 29 16:47:09 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/mutter
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Beta i386 (20100902.1)
ProcCmdline: mutter
ProcEnviron:
 LANG=pl_PL.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: mutter
StacktraceTop:
 ?? ()
 ctk_render_target_new () from /usr/lib/libclutk-0.3.so.0
 ?? () from /usr/lib/libclutk-0.3.so.0
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: mutter crashed with SIGSEGV in ctk_render_target_new()
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

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

StacktraceTop:
 ?? ()
 ctk_effect_context_init (self=0x8fbf8a0)
 g_type_create_instance () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/libgobject-2.0.so.0

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
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.