[kde] [Bug 500195] New: When consulting app version via CLI, thread destroyed output appears

EpicTux123 bugzilla_noreply at kde.org
Sun Feb 16 15:42:00 GMT 2025


https://bugs.kde.org/show_bug.cgi?id=500195

            Bug ID: 500195
           Summary: When consulting app version via CLI, thread destroyed
                    output appears
    Classification: I don't know
           Product: kde
           Version: unspecified
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: EpicTux123 at proton.me
  Target Milestone: ---

$ 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

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list