[Ignition Fortress] Segmentation fault when closing application

[slim71]

I first noticed this when running IGN trough ROS, but the same is happening launching it on its own.
Precise output for ign gazebo --version:

Ignition Gazebo, version 6.11.0
Copyright (C) 2018 Open Source Robotics Foundation.
Released under the Apache 2.0 License.

I have installed Ignition through humble-full-desktop. I'm not doing much, just launching ign gazebo tugbot_depot.sdf (downloaded from here.
This goes fairly smooth until I click the X to close and confirm my decision, which closes IGN but returns the segfault. Here's the complete output in the terminal:

libEGL warning: egl: failed to create dri2 screen
libEGL warning: egl: failed to create dri2 screen
Stack trace (most recent call last):
#30   Object "[0xffffffffffffffff]", at 0xffffffffffffffff, in 
#29   Object "ign gazebo gui", at 0x561671c3b1c4, in _start
#28   Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2aa9229e3f, in __libc_start_main
#27   Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2aa9229d8f, in 
#26   Object "ign gazebo gui", at 0x561671c3b17e, in 
#25   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa96a8e19, in ruby_run_node
#24   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa96a5317, in 
#23   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa983a30c, in rb_vm_exec
#22   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa9834c96, in 
#21   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa9831fc5, in 
#20   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa982fc34, in 
#19   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa977ba1e, in 
#18   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa96a69ac, in rb_protect
#17   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa983ec61, in rb_yield
#16   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa983a30c, in rb_vm_exec
#15   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa9834c96, in 
#14   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa9831fc5, in 
#13   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa982fc34, in 
#12   Object "/usr/lib/x86_64-linux-gnu/ruby/3.0.0/fiddle.so", at 0x7f2aa947544b, in 
#11   Object "/lib/x86_64-linux-gnu/libruby-3.0.so.3.0", at 0x7f2aa97fd088, in rb_nogvl
#10   Object "/usr/lib/x86_64-linux-gnu/ruby/3.0.0/fiddle.so", at 0x7f2aa9474d6b, in 
#9    Object "/lib/x86_64-linux-gnu/libffi.so.8", at 0x7f2aa9979492, in 
#8    Object "/lib/x86_64-linux-gnu/libffi.so.8", at 0x7f2aa997ce2d, in 
#7    Object "/usr/lib/x86_64-linux-gnu/libignition-gazebo6-ign.so.6.11.0", at 0x7f2aa43bc86c, in runGui
#6    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f2aa40889db, in ignition::gazebo::v6::gui::runGui(int&, char**, char const*, char const*, int, char const*)
#5    Object "/lib/x86_64-linux-gnu/libignition-gui6.so.6", at 0x7f2aa3d5a16c, in ignition::gui::Application::~Application()
#4    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f2aa2eef923, in QObject::~QObject()
#3    Object "/lib/x86_64-linux-gnu/libQt5Core.so.5", at 0x7f2aa2ee4a6d, in QObjectPrivate::deleteChildren()
#2    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f2aa4090e1c, in ignition::gazebo::v6::GuiRunner::~GuiRunner()
#1    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f2aa4090e01, in ignition::gazebo::v6::GuiRunner::~GuiRunner()
#0    Object "/lib/x86_64-linux-gnu/libignition-gazebo6-gui.so.6", at 0x7f2aa409f63b, in void ignition::utils::detail::DefaultDelete<ignition::gazebo::v6::GuiRunner::Implementation>(ignition::gazebo::v6::GuiRunner::Implementation*)
Segmentation fault (Address not mapped to object [0x7f2a4de44f18])

Is there anything I'm missing? This is not a big problem, since it's only on closure (at least for now), but still...

[toitimtoe]

I got the same issue as you, after installing Fortress with Humble, using instructions from the doc.
There's also the annoying libEGL warning, which I assume is a problem from the NVIDIA driver...