QThreadStorage warning in the log

Help
1

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
2

@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.

3

It is a regression in Qt 6.8.2, reported and fixed in 6.8.3 with requests to backport the fix to ditros:
https://bugreports.qt.io/browse/QTBUG-133206
https://bugreports.qt.io/browse/QTBUG-133500
https://bugs.kde.org/show_bug.cgi?id=499537

2 Likes
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.

5

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

6