gnome-shell crashed with SIGSEGV in std::_Rb_tree::equal_range from std::_Rb_tree::erase

[Rasmus Eneman]

I just started the computer and opened Firefox from the Dash.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.24.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sun Jun 25 19:41:46 2017
DisplayManager: lightdm
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2017-06-03 (22 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170602)
ProcCmdline: /usr/bin/gnome-shell
SegvAnalysis:
 Segfault happened at: 0x7fb97759b4d9 <_ZNSt8_Rb_treeIP12_ConnectDataS1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE5eraseERKS1_+57>: cmp 0x20(%rdi),%rax
 PC (0x7fb97759b4d9) ok
 source "0x20(%rdi)" (0x0002011f) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 std::_Rb_tree<_ConnectData*, _ConnectData*, std::_Identity<_ConnectData*>, std::less<_ConnectData*>, std::allocator<_ConnectData*> >::erase(_ConnectData* const&) () at /usr/lib/libgjs.so.0
 () at /usr/lib/libgjs.so.0
 g_main_context_dispatch () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in std::_Rb_tree<_ConnectData*, _ConnectData*, std::_Identity<_ConnectData*>, std::less<_ConnectData*>, std::allocator<_ConnectData*> >::erase()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip input lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 std::_Rb_tree<_ConnectData*, _ConnectData*, std::_Identity<_ConnectData*>, std::less<_ConnectData*>, std::allocator<_ConnectData*> >::equal_range (__k=@0x7ffe9938a320: 0x558585aa0920, this=0x55858793b998) at /usr/include/c++/6/bits/stl_tree.h:1722
 std::_Rb_tree<_ConnectData*, _ConnectData*, std::_Identity<_ConnectData*>, std::less<_ConnectData*>, std::allocator<_ConnectData*> >::erase (this=0x55858793b998, __x=@0x7ffe9938a320: 0x558585aa0920) at /usr/include/c++/6/bits/stl_tree.h:2298
 std::set<_ConnectData*, std::less<_ConnectData*>, std::allocator<_ConnectData*> >::erase (__x=@0x7ffe9938a320: 0x558585aa0920, this=<optimized out>) at /usr/include/c++/6/bits/stl_set.h:602
 signal_connection_invalidate_idle (user_data=<optimized out>) at gi/object.cpp:1585
 g_main_dispatch (context=0x5585853d19d0) at ../../../../glib/gmain.c:3234

[Launchpad Janitor (janitor)]

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

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.

[Launchpad Janitor (janitor)]

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