499477 2025-02-03 20:09:57 +0000 KRunner does not appear QThreadStorage: Thread 0x5b49ea50b030 exited after QThreadStorage 8 destroyed 2025-02-18 02:45:48 +0000 1 1 4 Plasma krunner general 6.2.5 Other Linux RESOLVED DUPLICATE 480800 https://bugreports.qt.io/browse/QTBUG-133206 NOR crash --- 1 cummingcowgirl plasma-bugs-null alexander.lohnau cnharrison dashmeshsingh98 kdedev malikth32 natalie_clarius nate scolipede2 0 oldest_to_newest 2394723 0 cummingcowgirl 2025-02-03 20:09:57 +0000 I run KRunner once or twice and as expected it stops working. I launch Konsole to launch krunner from it and I get the below. Did a logoff to see if that would fix the issues but no luck. QThreadStorage: Thread 0x5b49ea50b030 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x5b49ea50b030 exited after QThreadStorage 6 destroyed QThreadStorage: Thread 0x5b49ea50b030 exited after QThreadStorage 3 destroyed 2394734 1 kdedev 2025-02-03 20:46:32 +0000 Thanks for reporting this bug. I'm not able to reproduce it with git-master or Plasma 6.2.5. To investigate and try to reproduce, we need some more information. Please provide the following, from the bug template: SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: Thanks. 2394770 2 cummingcowgirl 2025-02-03 22:40:53 +0000 Operating System: Garuda Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.1-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7700X 8-Core Processor Memory: 61.8 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3060/PCIe/SSE2 2394796 3 cnharrison 2025-02-04 02:54:53 +0000 same issue Operating System: CachyOS Linux KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.0-3-cachyos (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 31.1 GiB of RAM Graphics Processor: Quadro T1000/PCIe/SSE2 2395327 4 scolipede2 2025-02-06 08:11:40 +0000 Same issue, seems to have started since moving to kernel 6.13 Operating System: EndeavourOS KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.13.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 7900X 12-Core Processor Memory: 61.9 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3090/PCIe/SSE2 2395477 5 kdedev 2025-02-06 20:06:59 +0000 Confirmed, since multiple people are experiencing this. They are all on kernel 6.13. 2395669 6 cummingcowgirl 2025-02-07 13:21:22 +0000 Seems like it started with Krunner and went from there. My impression is that 6.13 seems to not like one or more items in QT 6.8.2. Both comments about 65.13 and the latest QT seem to be at the center of the issue. 2395893 7 malikth32 2025-02-08 02:43:55 +0000 I initially had this issue on kernel 6.13.1, but it did **not** stop occurring after downgrading to 6.12.10. Operating System: EndeavourOS KDE Plasma Version: 6.2.5 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.10-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 3 3100 4-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 This is especially infuriating as I have it bound to my super key. I'd like to be able to open apps :( 2395982 8 cummingcowgirl 2025-02-08 11:25:13 +0000 Right now I have uLauncher so all I have to do is CTL + Shift. The only bad this is it only only search apps and the internet. I've searched for a decent temporary replacement, but I could only find uLauncher.l 2396011 9 nate 2025-02-08 15:05:02 +0000 This is a bug in Qt 6.8.2: https://bugreports.qt.io/browse/QTBUG-133206 It's fixed in Qt's git master, and we've advised distros to backport the fix. 2398863 10 cummingcowgirl 2025-02-17 11:01:28 +0000 And on Framework 6.11 the issue is still there. Just now: ~~~ ~  krunner  ✔  02:57:59 AM QThreadStorage: Thread 0x567776bbe030 exited after QThreadStorage 8 destroyed QThreadStorage: Thread 0x567776bbe030 exited after QThreadStorage 4 destroyed QThreadStorage: Thread 0x567776bbe030 exited after QThreadStorage 3 destroyed ~  ~~~ 2399211 11 nate 2025-02-18 02:44:26 +0000 Please see https://community.kde.org/Get_Involved/Issue_Reporting#Understand_what_the_resolution_statuses_mean 2399212 12 nate 2025-02-18 02:45:48 +0000 As for the actual issue, rather than just the error message, since you're all using NVIDIA GPUs, it's most likely https://bugs.kde.org/show_bug.cgi?id=480800, which is also an upstream issue. *** This bug has been marked as a duplicate of bug 480800 ***