KRunner - QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 8 destroyed

As we all know for some reason from Plasma 6.0 forward KRunner likes to stop working. Normally one just launches Konsole and enters krunner once or twice to get it running again. I just attempted that and I get the below. Any Ideas on what’s going on?

  krunner                                                                                        ✔  11:48:44 AM
QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 6 destroyed
QThreadStorage: Thread 0x613719c95030 exited after QThreadStorage 3 destroyed
~  krunner                                                                                        ✔  11:48:49 AM
QThreadStorage: Thread 0x6303ee2b6030 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x6303ee2b6030 exited after QThreadStorage 6 destroyed
QThreadStorage: Thread 0x6303ee2b6030 exited after QThreadStorage 3 destroyed
1 Like

Hi - just adding the link to the bug report that you filed on this one so folks can reference that as well: 499477 – KRunner does not appear QThreadStorage: Thread 0x5b49ea50b030 exited after QThreadStorage 8 destroyed

For what it’s worth, I can’t reproduce on my system - I wonder if it’s somehow related to a weird interaction with kernel 6.13? (I’m on 6.12.11)

1 Like

I honestly couldn’t say. I was going to rollback with Snapper, but because of a couple of days of replacing some programs with ones that seem better suited to me for the task they perform the snapshot I’d have to rollback to is from the 24th of last month. All the others are from yesterday. I was just in the CachyOS forums and there was a thread there about problems with kernel 6.13, but nothing to backup the posters claims. I called them out and told them to provide proof.

This is a bug in Qt 6.8.2: Loading....

It’s fixed in the upcoming Qt 6.8.3, and we’ve advised distros to backport the fix to their Qt 6.8.2 packages.

1 Like

Thanks for the info and update much appreciated. I think I can live with it til the 6.3 release.

EDIT:

QT 6.3? Doy mean a newer version than 6.8.2 FOR Plasma 6.3?

Oops, I mis-wrote the versions. I’ve corrected them in the above message.

1 Like

I think I lied, cause it’s hard to wait since there is nothing out there even remotely as good as Krunner.

I forgot to ask is this the reason for Krunner crashing after so many uses? If not is there a fix in the works?

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
 ~ 