gnome-shell crashed with SIGSEGV in _cogl_pipeline_set_parent()

Bug #955090 reported by Martin-Éric Racine
62
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
High
Unassigned

Bug Description

As of today, gnome-shell no longer launches correctly in Precise. The menu bar fails to appear and the window manager crashes. Rebooting did not fix the issue.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-shell 3.2.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
Date: Wed Mar 14 16:15:14 2012
ExecutablePath: /usr/bin/gnome-shell
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=fi:en
 PATH=(custom, user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xb5330a85: mov 0x14(%eax),%eax
 PC (0xb5330a85) ok
 source "0x14(%eax)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.9
 ?? () from /usr/lib/i386-linux-gnu/libcogl.so.9
 cogl_pipeline_new () from /usr/lib/i386-linux-gnu/libcogl.so.9
 ?? () from /usr/lib/i386-linux-gnu/libcogl-pango.so.0
 ?? () from /usr/lib/i386-linux-gnu/libcogl-pango.so.0
Title: gnome-shell crashed with SIGSEGV in cogl_pipeline_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin messagebus netdev plugdev rtkit scanner src sudo tape video

Revision history for this message
Martin-Éric Racine (q-funk) wrote :
Changed in gnome-shell (Ubuntu):
importance: Undecided → High
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _cogl_pipeline_set_parent (pipeline=0x96ff1a8, parent=<optimized out>, take_strong_reference=1) at ./cogl-pipeline.c:300
 _cogl_pipeline_copy (src=0x8efa860, is_weak=0) at ./cogl-pipeline.c:391
 cogl_pipeline_new (context=0x8ef9550) at ./cogl-pipeline.c:429
 get_base_texture_rgba_pipeline (cache=<optimized out>) at cogl-pango-pipeline-cache.c:112
 _cogl_pango_pipeline_cache_get (cache=0x8f34a98, texture=0x994e768) at cogl-pango-pipeline-cache.c:200

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
summary: - gnome-shell crashed with SIGSEGV in cogl_pipeline_new()
+ gnome-shell crashed with SIGSEGV in _cogl_pipeline_set_parent()
tags: removed: need-i386-retrace
Jeremy Bícha (jbicha)
visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
Revision history for this message
shinyblue (shinyblue) wrote :

from syslog

kernel: [ 467.098264] gnome-shell[4981]: segfault at 11 ip 00007f6596a02623 sp 00007fff2efbf0c8 error 4 in libcogl.so.9.0.0[7f65969e3000+83000]

Revision history for this message
Jeremy Bícha (jbicha) wrote :

This is fixed in gnome-shell 3.3.90-0ubuntu1 which you should be getting in your updates shortly. Next time I need to remember to add a breaks to the control file so it's more obvious that upgrading could break gnome-shell.

Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Alex Rybicki (alex-rybicki) wrote :

I currently have gnome-shell 3.3.90-0ubuntu1installed from the update recently, and am now unable to render gnome-shell as described in post 1. I am unable to determine if this is the package which causes gnome-shell to fail to load, however the symptoms are as described, and have appeared for me within the last update period.

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.