I would like to report the bug but I do not know in which component. Practically every KDE application leaves a similar message in the log
QThreadStorage: Thread 0x61e8d47d67a0 exited after QThreadStorage 9 destroyed
here are a few examples
04.02.2025 18:23:06:941
kdeconnectd
QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 8 destroyed
04.02.2025 18:23:06:941
kdeconnectd
QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 7 destroyed
04.02.2025 18:23:06:941
kdeconnectd
QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 6 destroyed
04.02.2025 18:23:06:941
kdeconnectd
QThreadStorage: Thread 0x5c4e47a16b50 exited after QThreadStorage 2 destroyed
04.02.2025 18:24:48:959
dolphin
QThreadStorage: Thread 0x62067d9841d0 exited after QThreadStorage 9 destroyed
04.02.2025 18:25:34:595
konsole
QThreadStorage: Thread 0x5dbefabaf6a0 exited after QThreadStorage 9 destroyed
04.02.2025 18:25:57:326
kcalc
QThreadStorage: Thread 0x5a5fe0125d40 exited after QThreadStorage 8 destroyed
04.02.2025 18:28:52:878
spectacle
QThreadStorage: Thread 0x61e8d47d67a0 exited after QThreadStorage 9 destroyed
04.02.2025 18:31:31:729
kioworker
QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 8 destroyed
04.02.2025 18:31:31:730
kioworker
QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 7 destroyed
04.02.2025 18:31:31:730
kioworker
QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 6 destroyed
04.02.2025 18:31:31:730
kioworker
QThreadStorage: Thread 0x61010e5c4600 exited after QThreadStorage 1 destroyed
04.02.2025 18:31:33:082
dolphin
QThreadStorage: Thread 0x58cec8b001d0 exited after QThreadStorage 9 destroyed
04.02.2025 18:31:57:204
dragon
QThreadStorage: Thread 0x5c9b59aa6870 exited after QThreadStorage 8 destroyed
04.02.2025 18:36:31:696
kdenlive
QThreadStorage: Thread 0x5fdba02f4510 exited after QThreadStorage 9 destroyed
However, QT but not KDE apps do not. Among those that do not:
Octopi (pacman QT interface on Arch)
Krita
but also Systemsettings e Ksyslog which are KDE anyway
Any idea?
However, there do not seem to be any malfunctions.
Moreover, if I launch them from the terminal, many more appear in the terminal itself, this is dolphin:
QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 7 destroyed
QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 6 destroyed
QThreadStorage: Thread 0x60d8ff457600 exited after QThreadStorage 1 destroyed
QThreadStorage: Thread 0x6487b7bf11d0 exited after QThreadStorage 9 destroyed
@Guido_I :
There’s also the following KDE Discuss thread – <KRunner - QThreadStorage >
And, there’s also a related Bug Report: <KRunner does not appear QThreadStorage >
Looking at the Bug Report, it seems to be a Plasma 6 issue but, on this Plasma 5 system I’m seeing the following systemd user Journal entries –
Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6cd94c70 exited after QThreadStorage 15 destroyed
Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6cd94c70 exited after QThreadStorage 12 destroyed
Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6ce3f3f0 exited after QThreadStorage 15 destroyed
Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d6ce3f3f0 exited after QThreadStorage 12 destroyed
Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d70f18220 exited after QThreadStorage 15 destroyed
Feb 05 16:10:15 digikam[5072]: QThreadStorage: Thread 0x555d70f18220 exited after QThreadStorage 12 destroyed
Operating System: openSUSE Leap 15.6
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.4.0-150600.23.33-default (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 29.3 GiB of RAM
Graphics Processor: AMD Radeon Vega 11 Graphics
Manufacturer: ASUS
On this Qt5 system, only digiKam is throwing these messages.
meven
February 6, 2025, 4:44pm
3
2 Likes
meven
February 6, 2025, 4:50pm
4
We have bugs.kde.org for this.
If you don’t know the component pick a default one, if it concerns the session plasma-desktop, graphics kwin, file-management dolphin… And the bug should get triaged eventually.
Although discuss can be an antichamber, in any case looking searching at recent bugs in bugs.kde.org is a good idea to see if something is already reported.
I know where the bugs are reported, but I wasn’t sure which component to use. Anyway, it seems to be a problem with Qt 6.8.2
This problem persists in QT 6.8.3. Is there any other way to fix it?
Every time I activate krunner, it also outputs the following message:
qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d40b20de750
qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x5d40b20de750
I have seen it for the first time, now:
$ spectacle --help
(......)
QThreadStorage: entry 9 destroyed before end of thread 0x5f2f182a6c50
QThreadStorage: entry 5 destroyed before end of thread 0x5f2f182a6c50
QThreadStorage: entry 4 destroyed before end of thread 0x5f2f182a6c50
My system:
$ kinfo
Operating System: Arch Linux
KDE Plasma Version: 6.3.5
KDE Frameworks Version: 6.14.0
Qt Version: 6.9.0
Kernel Version: 6.12.30-1-lts (64-bit)
Graphics Platform: X11
Processors: 6 × Intel® Core™ i5-9400 CPU @ 2.90GHz
Memory: 15.5 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
Related thread with Qt 6.9.0:
Regards
1 Like