gnome-shell crashed with SIGSEGV in meta_window_new()

Bug #1304884 reported by René
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GNOME Shell
New
Critical
gnome-shell (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I tried to start gnome shell via "gnome-shell --replace" after login to Gnome (Metacity)

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: gnome-shell 3.10.4-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Apr 9 10:05:08 2014
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell.calendar' b'show-weekdate' b'true'
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
 b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1'
 b'org.gnome.desktop.interface' b'cursor-blink' b'false'
 b'org.gnome.desktop.interface' b'clock-show-date' b'true'
InstallationDate: Installed on 2013-04-16 (357 days ago)
InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214)
ProcCmdline: gnome-shell --replace
SegvAnalysis:
 Segfault happened at: 0x7f85d884df41 <meta_window_new+2545>: mov (%rax),%edx
 PC (0x7f85d884df41) ok
 source "(%rax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_window_new () from /usr/lib/libmutter.so.0
 meta_screen_manage_all_windows () from /usr/lib/libmutter.so.0
 meta_display_open () from /usr/lib/libmutter.so.0
 meta_run () from /usr/lib/libmutter.so.0
 ?? ()
Title: gnome-shell crashed with SIGSEGV in meta_window_new()
UpgradeStatus: Upgraded to trusty on 2014-04-07 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
René (pirateking) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 meta_window_new (display=0x1c68800, xwindow=39845898, must_be_viewable=must_be_viewable@entry=1, effect=effect@entry=META_COMP_EFFECT_NONE) at core/window.c:1358
 meta_screen_manage_all_windows (screen=0x7f85c000d540) at core/screen.c:901
 meta_display_open () at core/display.c:934
 meta_run () at core/main.c:553
 main (argc=1, argv=0x7fff7ddd1c38) at main.c:439

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in gnome-shell:
importance: Unknown → Critical
status: Unknown → New
Revision history for this message
René (pirateking) wrote :

Hi, do you need more information?

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

Thank you for reporting this bug to Ubuntu.
Ubuntu GNOME 14.04 (trusty) reached end-of-life on April 28, 2017

https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes/UbuntuGNOME#Support
https://lists.ubuntu.com/archives/ubuntu-gnome/2017-March/004211.html

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in gnome-shell (Ubuntu):
status: Incomplete → Won't Fix
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.