gnome-shell crashed with SIGSEGV in g_dbus_connection_signal_unsubscribe()

Bug #1703300 reported by Marko Stanković
66
This bug affects 11 people
Affects Status Importance Assigned to Milestone
gnome-shell (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

https://errors.ubuntu.com/problem/2258b834217f97f59fe38634745b76a577b781d1

---

Automatically generated crash report after I switched to gdm3 and gnome-shell.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
Uname: Linux 4.10.0-26-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sun Jul 9 19:35:05 2017
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2015-05-21 (781 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150517)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7fd359c8a2e2 <g_dbus_connection_signal_unsubscribe+34>: cmp (%rdx),%rax
 PC (0x7fd359c8a2e2) ok
 source "(%rdx)" (0x00001e01) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 g_dbus_connection_signal_unsubscribe () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_object_unref () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 () at /usr/lib/libgjs.so.0
 () at /usr/lib/libgjs.so.0
Title: gnome-shell crashed with SIGSEGV in g_dbus_connection_signal_unsubscribe()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Marko Stanković (sm4rk0) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_dbus_connection_signal_unsubscribe (connection=0x558ae0de7330, subscription_id=249) at ../../../../gio/gdbusconnection.c:3637
 g_dbus_proxy_finalize (object=0x558ae1499f70) at ../../../../gio/gdbusproxy.c:220
 g_object_unref (_object=0x558ae1499f70) at ../../../../gobject/gobject.c:3314
 release_native_object (priv=priv@entry=0x558ae0edd550) at gi/object.cpp:1259
 object_instance_finalize (fop=<optimized out>, obj=<optimized out>) at gi/object.cpp:1663

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
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
Revision history for this message
Daniel van Vugt (vanvugt) wrote :
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

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

Zero crash reports in 18.10 onward.

tags: removed: artful
Changed in gnome-shell (Ubuntu):
status: Confirmed → Fix Released
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.