gnome-shell crashed with SIGSEGV in meta_screen_free()

Bug #1556661 reported by silberfan
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/828caaef21d44111907f5b36e8bc4ea6ffd551b2

---

System send error Message for any programs who was chrashed.and start error messenger.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.4-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
Uname: Linux 4.4.0-12-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
Date: Sun Mar 13 15:46:40 2016
DisplayManager:

ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 13'"
 b'org.gnome.desktop.interface' b'font-name' b"'Cantarell 11'"
 b'org.gnome.desktop.interface' b'clock-show-date' b'false'
 b'org.gnome.desktop.interface' b'document-font-name' b"'Sans 11'"
InstallationDate: Installed on 2016-03-13 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160312)
ProcCmdline: gnome-shell
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb1ad5fac47 <meta_screen_free+7>: mov 0x18(%rdi),%rbp
 PC (0x7fb1ad5fac47) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 meta_screen_free () from /usr/lib/libmutter.so.0
 meta_display_close () from /usr/lib/libmutter.so.0
 meta_display_open () from /usr/lib/libmutter.so.0
 meta_run () from /usr/lib/libmutter.so.0
 main ()
Title: gnome-shell crashed with SIGSEGV in meta_screen_free()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
silberfan (nugget-0) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007fb1ad5fac47 in meta_screen_free () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 #1 0x00007fb1ad5eca05 in meta_display_close () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 #2 0x00007fb1ad5edd22 in meta_display_open () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 #3 0x00007fb1ad5f66cc in meta_run () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 #4 0x0000000000402197 in main ()
StacktraceTop:
 meta_screen_free () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 meta_display_close () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 meta_display_open () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 meta_run () from /tmp/apport_sandbox_3BjdJT/usr/lib/libmutter.so.0
 main ()

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 gnome-shell (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix released (no crashes reported after 17.04)

Changed in gnome-shell (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.