gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion failed: (wd >= 0)"]

Bug #1713034 reported by ubername
42
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GLib
New
Unknown
gnome-shell (Ubuntu)
Fix Released
Medium
Marco Trevisan (Treviño)

Bug Description

https://errors.ubuntu.com/problem/3554ed6882d41ea6b6fe921fbc9450c857b89eaa
https://errors.ubuntu.com/problem/7d4e9fc521926903d3f796d9d01b38c242396745
https://errors.ubuntu.com/problem/1f19262e2fd594a3cf2d89af52d8a58b42aa2c56

Upstream bug https://gitlab.gnome.org/GNOME/glib/issues/1370

---

ProblemType: CrashDistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.3-0ubuntu4
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Aug 25 12:05:50 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2014-08-13 (1107 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140810)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bashSignal: 6SourcePackage: gnome-shell
StacktraceTop:
 g_assertion_message () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-shell crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

Revision history for this message
ubername (ubername) wrote :
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 : StacktraceTop.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: (wd >= 0)"]
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion failed: (wd >= 0)"]

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-shell (Ubuntu):
status: New → Confirmed
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
summary: - gnome-shell crashed with SIGABRT in g_assertion_message() ["assertion
+ gnome-shell crashed with SIGABRT in _ip_get_path_for_wd() ["assertion
failed: (wd >= 0)"]
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

Anyone getting this bug could please attach the report from
  jouralctl /usr/bin/gnome-shell

Changed in gnome-shell (Ubuntu):
status: Confirmed → Triaged
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in glib:
importance: Unknown → Medium
status: Unknown → Confirmed
description: updated
Changed in glib:
status: Confirmed → Incomplete
Changed in glib:
status: Incomplete → Expired
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Fix Released, apparently. Zero reports of this crash after 17.10.

Changed in gnome-shell (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :
description: updated
Changed in glib:
importance: Medium → Undecided
status: Expired → New
Changed in gnome-shell (Ubuntu):
status: Fix Released → Confirmed
status: Confirmed → Triaged
tags: added: bionic eoan
removed: artful
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Looks like most of the crashes stopped happening in previous series. And the most recent one stopped happening after 3.36.0. So probably fixed?

Changed in glib:
importance: Undecided → Unknown
status: New → Unknown
Changed in gnome-shell (Ubuntu):
status: Triaged → Fix Released
tags: removed: eoan
Changed in glib:
status: Unknown → New
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.