Ubuntu GNOME

gnome-shell crashed with SIGABRT in g_assertion_message() after opening the lid with a second monitor plugged in

Bug #1277756 reported by Thomas N on 2014-02-08

This bug report is a duplicate of: Bug #1216362: gnome-shell crashed with SIGABRT in sigorset(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Ubuntu GNOME	New	Undecided	Unassigned

Bug Description

This is not the first time it happend. It has happend when I followed these steps:
1. My laptop is running without any monitor plugged in
2. I close the lid of the laptop
3. I plug my external monitor in with the lid of my laptop closed
4. I open the lid of my laptop
-> the picture only appears on the external monitor, but with a resolution which is much too low
-> the picture freezes
-> when unplugging the monitor and closing/reopening the lid on the laptop, the laptop screen stays blank
-> the laptop fan starts making more noise which means something is working
-> after a little while, gnome gets reset and the picture appears as it should on both monitors

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: gnome-shell 3.10.2.1-0ubuntu1~saucy1 [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 7 19:24:38 2014
DisplayManager: gdm
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
b'org.gnome.desktop.interface' b'buttons-have-icons' b'true'
b'org.gnome.desktop.interface' b'clock-show-date' b'true'
b'org.gnome.desktop.interface' b'clock-show-seconds' b'true'
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.interface' b'menus-have-icons' b'true'
InstallationDate: Installed on 2013-04-28 (285 days ago)
InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424)
MarkForUpload: True
ProcCmdline: /usr/bin/gnome-shell
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
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
?? () from /usr/lib/libmutter.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: Upgraded to saucy on 2013-11-18 (81 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

Thomas N (thnaeff) wrote on 2014-02-08:

CrashDB.txt Edit (263 bytes, text/plain; charset="utf-8")
Dependencies.txt Edit (27.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (302 bytes, text/plain; charset="utf-8")
gdmSessionLog.txt Edit (825 bytes, text/plain; charset="utf-8")
gnomeSessionLog.txt Edit (2.2 MiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu GNOME (ug-bot) wrote on 2014-02-12: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1216362, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.