X-Debbugs-CC: allan grossman <wizard10...@gmail.com> On Wed, Jul 21, 2021 at 02:20:37PM -0500, allan wrote: > this doesn't look real helpful - looks like I may need to install some > source code but not sure which code other than flameshot -
No, it shows exactly what I was looking for: > (gdb) backtrace 5 > #0 QAction::setText (this=0x0, text=...) > at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:116 The this pointer is null, i.e. m_appUpdates is still uninitialized when the call to setText() happens. That is something the upstream devs can't easily argue away. But the question is: Why is it null/uninitialized? Either because Openbox lacks a feature Qt needs for making system trays (and flameshot doesn't properly check for that failing), or because your Internet connection is too fast leading to the wrong race condition outcome. Was flameshot working normally with Openbox in the past? You could also try if lowering your connection speed (latency, throughput) resolves the issue. Maybe going to a coffee shop or some other place with slow Internet is the easiest way. Otherwise you'll have to fiddle with netem[0,1] or the firewall and find ways to throttle speed that way (I can't help you with that). Also: I saw that AppImages[2] are provided, but apparently not for version 0.10.0[3]. It would have been valuable to know if the error occurs with that, too. Maybe you can try the Snap image (I have no experience with using that). If running that via shell is for some reason not possible segfaults should show up in the output of dmesg. Regards. 0: https://stackoverflow.com/questions/24729545/how-to-tc-filter-with-netem 1: https://wiki.linuxfoundation.org/networking/netem 2: https://flameshot.org/guide/installation/installation-linux/#appimage 3: https://github.com/flameshot-org/flameshot/releases/tag/v0.10.0
