https://bugs.kde.org/show_bug.cgi?id=492049
--- Comment #3 from [email protected] --- Hi. Sorry for the delay. I will paste the output below. Before, however, I want to note here that this bug may also apply to the application launcher (when searching apps) as it takes a few seconds to load. The launcher however does not give a "not responding" indication, nor does it happen consistently like Discover (it seems like it happens the first time I use it after boot/ a period of time of not using it). It's also maybe important to mention that it worked fine on Fedora 40 (implicitly KDE Plasma 6) before it ended like this. This goes for both Discover and the Application Launcher. Output: ``` [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/bin/plasma-discover'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; [Current thread is 1 (Thread 0x7fc8be1bab00 (LWP 6321))] KCRASH_INFO_MESSAGE: Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = <optimized out>} Cannot QML trace cores :( ``` -- You are receiving this mail because: You are watching all bug changes.
