gnome-shell (3.24.2) crashed with segfault

Bug #1730554 reported by Po-Hsu Lin
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This happens when I was navigating through my Google calendar, and the desktop freezes.
My music was still playing in the background, it's just the desktop stop responding.

A few seconds later, it looks like gnome-shell itself has restarted.

Error message in dmesg:
[37530.709259] show_signal_msg: 9 callbacks suppressed
[37530.709264] gnome-shell[2068]: segfault at 604c3f ip 00007fdf96a0560a sp 00007ffebbbef8d0 error 4 in libgobject-2.0.so.0.5200.0[7fdf969d1000+51000]

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-shell 3.24.2-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Nov 7 11:17:42 2017
DisplayManager: gdm3
EcryptfsInUse: Yes
GsettingsChanges:
 b'org.gnome.shell' b'enabled-extensions' b"['<email address hidden>', '<email address hidden>', 'suspend-button@laserb', '<email address hidden>', '<email address hidden>']"
 b'org.gnome.shell' b'command-history' b"['r']"
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'evolution.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'skypeforlinux.desktop', 'google-chrome.desktop', 'org.gnome.Terminal.desktop', 'hexchat.desktop']"
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2017-07-12 (117 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Please look in /var/crash for crash files. If found, do not attach them here but upload them with:

  ubuntu-bug /PATH/TO/FILE.crash

And let us know the ID of the newly created bug.

If you can please also provide more output from 'journalctl'.

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Currently I got blocked by bug 1730639 to upload my crash file.

Tried to modify the locale in the crash file from lzh_TW to zh_TW (and en_US), the tool didn't crash, but it just ask me if I want to send the crash report.
After clicking on Continue, it didn't open a launchpad page for me. I think it's not uploaded successfully.

The title is expected to be "gnome-shell crashed with sigsegv in g_type_check_instance_cast()"

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Please find the attachment for the journalctl output.

I think the system tries to upload the error report, but failed due to the locale issue.

Revision history for this message
Dmitriy Geels (dmig) wrote :

ubuntu-bug complains that there is not enough free memory to analyze crash dump. I'm attaching the dump itself.

Revision history for this message
Dmitriy Geels (dmig) wrote :

In my case error messages look like

Nov 18 07:50:34 kernel: do_general_protection: 14 callbacks suppressed
Nov 18 07:50:34 kernel: traps: gnome-shell[1430] general protection ip:7f3f663c2e0d sp:7ffe9fed66d0 error:0 in libgobject-2.0.so.0.5400.1[7f3f6638

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.]

Changed in gnome-shell (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Marcelo Bello (marcelo-bello) wrote :

Why are these bugs expiring? Guys, this is really annoying, I have an unreliable desktop as a consequence of this bug. I lose the state of my desktop every 2-3 days when I am used of keeping the same Desktop state for multiple months.

Please, keep this open, it is important.

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

A bug can only stay open if it has useful information to help someone fix it, and this one does not (yet).

Crash files should not be attached to bugs because we generally can't debug them without extra retracing. Please only send crash files using the 'ubuntu-bug' command.

Bugs are often overloaded with many different people commenting on them. For a crash bug this is a problem, because it's highly likely each person is actually experiencing a different crash with the same apparent symptoms. So everyone please only report crashes using:

  ubuntu-bug /var/crash/YOURFILE.crash

But if you are not running the current development release of Ubuntu then you will need to apply a workaround from bug 994921 before that will work.

Finally, release 17.04 is no longer supported after January 13, 2018. So please be sure to upgrade to a supported version of Ubuntu: https://wiki.ubuntu.com/Releases

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.