gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion failed: (window->display->focus_window != window)"]

Bug #1726026 reported by Eduard
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
GNOME Shell
Confirmed
Critical
gnome-shell (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Happened randomly in my Virtual Machine on Parallels Desktop

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: prl_fs_freeze prl_fs prl_eth prl_tg
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 22 17:37:17 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', '<email address hidden>', 'axemenu@wheezy']"
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'rhythmbox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'shotwell.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop', 'org.gnome.Terminal.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-10-19 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 meta_window_unmanage () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Eduard (eduard-comanici) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_assertion_message (domain=domain@entry=0x7f8d6fff7233 <error: Cannot access memory at address 0x7f8d6fff7233>, file=file@entry=0x7f8d70001112 <error: Cannot access memory at address 0x7f8d70001112>, line=line@entry=1478, func=func@entry=0x7f8d70003330 <error: Cannot access memory at address 0x7f8d70003330>, message=message@entry=0x558d7f503fd0 "assertion failed: (window->display->focus_window != window)") at ../../../../glib/gtestutils.c:2436
 g_assertion_message_expr (domain=0x7f8d6fff7233 <error: Cannot access memory at address 0x7f8d6fff7233>, file=0x7f8d70001112 <error: Cannot access memory at address 0x7f8d70001112>, line=1478, func=0x7f8d70003330 <error: Cannot access memory at address 0x7f8d70003330>, expr=<optimized out>) at ../../../../glib/gtestutils.c:2459
 ?? ()
 ?? ()

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
information type: Private → Public
summary: - gnome-shell crashed with SIGABRT in g_assertion_message()
+ gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion
+ failed: (window->display->focus_window != window)"]
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
Changed in gnome-shell:
importance: Unknown → Critical
status: Unknown → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Looks like this crash is several years old so it's had a few variations. Now tracking in bug 1422253.

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.