flameshot crashed with SIGSEGV in <signal handler called>()

[Jean-Baptiste Lallement]

I had this crash after a reboot of the machine

ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: flameshot 0.6.0-9
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 4.19.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 22 08:23:27 2019
ExecutablePath: /usr/bin/flameshot
InstallationDate: Installed on 2014-07-15 (1710 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
ProcCmdline: flameshot
SegvAnalysis:
 Segfault happened at: 0x5654582f2a00: (bad)
 PC (0x5654582f2a00) in non-executable VMA region: 0x56545826c000-0x56545952f000 rw-p [heap]
 Stack memory exhausted (SP below stack segment)
SegvReason: executing writable VMA [heap]
Signal: 11
SourcePackage: flameshot
StacktraceTop:
 ?? ()
 ?? ()
 <signal handler called>
 __GI___poll (fds=0x7f238873fcb8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
Title: flameshot crashed with SIGSEGV in <signal handler called>()
UpgradeStatus: Upgraded to disco on 2018-03-24 (362 days ago)
UserGroups: adm cdrom dip docker kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo
separator:

[Apport retracing service (apport)]

StacktraceTop:
 ?? ()
 SingleApplicationPrivate::terminate (signum=1) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qcoreapplication.h:116
 <signal handler called>
 __GI___poll (fds=fds@entry=0x7f238873fcb8, nfds=nfds@entry=1, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
 poll (__timeout=-1, __nfds=1, __fds=0x7f238873fcb8) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46

[Launchpad Janitor (janitor)]

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

[Nicholas Guriev (mymedia)]

Could you please retest the package of version 0.6.0+git20191001-2 from current release, Ubuntu 20.04? It is unclear for me how to reproduce the issue. I have checked the application in fresh Ubuntu environment, and it worked fine with no crashes.