Bug 500195

Summary:	When consulting app version via CLI, thread destroyed output appears
Product:	[I don't know] kde	Reporter:	EpicTux123 <EpicTux123>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED UPSTREAM
Severity:	normal	CC:	jfischer_5809, nate, nepnep, p.r.worrall
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
URL:	https://bugreports.qt.io/browse/QTBUG-133206
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description EpicTux123 2025-02-16 15:42:00 UTC

$ dolphin --version
dolphin 24.12.2
QThreadStorage: Thread 0x559ef8cbfb90 exited after QThreadStorage 9 destroyed
QThreadStorage: Thread 0x559ef8cbfb90 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x559ef8cbfb90 exited after QThreadStorage 7 destroyed
QThreadStorage: Thread 0x559ef8cbfb90 exited after QThreadStorage 3 destroyed

$ plasma-discover --version
discover 6.3.0
QThreadStorage: Thread 0x56315d6ee4f0 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x56315d6ee4f0 exited after QThreadStorage 7 destroyed
QThreadStorage: Thread 0x56315d6ee4f0 exited after QThreadStorage 6 destroyed
QThreadStorage: Thread 0x56315d6ee4f0 exited after QThreadStorage 1 destroyed

$ spectacle --version
spectacle 24.12.2
QThreadStorage: Thread 0x55bc01829fa0 exited after QThreadStorage 9 destroyed
QThreadStorage: Thread 0x55bc01829fa0 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x55bc01829fa0 exited after QThreadStorage 7 destroyed
QThreadStorage: Thread 0x55bc01829fa0 exited after QThreadStorage 4 destroyed



Before, it was only stating the version without the additional thread-related output.


Operating System: Fedora Linux 41
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.11.4-301.fc41.x86_64 (64-bit)
Graphics Platform: Wayland

Comment 1 Paul Worrall 2025-02-17 08:23:28 UTC

Confirmed

Operating System: Arch Linux 
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.11.0
Qt Version: 6.9.0
Graphics Platform: Wayland

Comment 2 Nate Graham 2025-02-18 22:34:06 UTC

This is harmless and comes from Qt. Nothing we can do about it in KDE, I'm afraid.

Comment 3 EpicTux123 2025-02-18 22:52:34 UTC

Nate, do you know of any bugs filled upstream regarding this problem?

Comment 4 Antonio Rojas 2025-02-19 08:11:10 UTC

*** Bug 500376 has been marked as a duplicate of this bug. ***

Comment 5 Antonio Rojas 2025-02-19 08:11:21 UTC

*** Bug 500375 has been marked as a duplicate of this bug. ***

Comment 6 Nate Graham 2025-02-19 20:49:16 UTC

https://bugreports.qt.io/browse/QTBUG-133206

Already fixed in Qt 6.8.3 as far as I can see.

Comment 7 Antonio Rojas 2025-04-27 06:52:53 UTC

*** Bug 503416 has been marked as a duplicate of this bug. ***