Bug 503421

Summary: "QThreadStorage N destroyed" diagnostics when spawning a konsole process via a shell prompt
Product: [Applications] konsole Reporter: Jim Fischer <jfischer_5809>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED FIXED    
Severity: normal CC: christoph
Priority: NOR    
Version First Reported In: 25.04.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Jim Fischer 2025-04-27 08:40:17 UTC
SUMMARY
When I spawn a konsole process via a command shell prompt, I'm seeing one or more Qt diagnostic messages that say,

QThreadStorage: Thread 0x562be97adbc0 exited after QThreadStorage 9 destroyed


STEPS TO REPRODUCE
1. Open any command shell application, e.g., xterm, konsole
2. At the command shell prompt, spawn a konsole process, e.g.,
        $ konsole --version

OBSERVED RESULT
== Desktop session: X11 ==
$ konsole --version
konsole 25.04.0
QThreadStorage: Thread 0x55f7754c7bc0 exited after QThreadStorage 9 destroyed
QThreadStorage: Thread 0x55f7754c7bc0 exited after QThreadStorage 5 destroyed
QThreadStorage: Thread 0x55f7754c7bc0 exited after QThreadStorage 4 destroyed


== Desktop Session: Plasma (Wayland) ==
$ konsole --version
VMware: No 3D enabled (0, Success).
libEGL warning: egl: failed to create dri2 screen
VMware: No 3D enabled (0, Success).
libEGL warning: egl: failed to create dri2 screen
konsole 25.04.0
QThreadStorage: Thread 0x555752824bc0 exited after QThreadStorage 9 destroyed
QThreadStorage: Thread 0x555752824bc0 exited after QThreadStorage 5 destroyed
QThreadStorage: Thread 0x555752824bc0 exited after QThreadStorage 4 destroyed


EXPECTED RESULT
$ konsole --version
konsole 25.04.0


SOFTWARE/OS VERSIONS
$ kinfo
Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.14.3-200.fc41.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × 13th Gen Intel® Core™ i7-13700
Memory: 5.7 GiB of RAM
Graphics Processor: llvmpipe

ADDITIONAL INFORMATION
Comment 1 Christoph Cullmann 2025-04-27 19:00:19 UTC
That should be a Qt issue and will be gone with e.g. 6.9.