Bug 499974

Summary:	krunner stays open as a background process after first run and wont relaunch
Product:	[Plasma] krunner	Reporter:	spengreb <spengreb>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	alexander.lohnau, cwo.kde, natalie_clarius, nate, nicolas.fella
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description spengreb 2025-02-13 10:37:41 UTC

When running krunner since the latest KDE after running krunner once it will forever stay as a background process in the system. This prevents krunner from running again until you kill the background process.

STEPS TO REPRODUCE
1. Open krunner and close it
2. Open process list - krunner is still there
3. Try relaunch krunner

OBSERVED RESULT
Krunner opens and closes the first time correctly. It wont open again until forceably killed.

EXPECTED RESULT
Krunner opens and when closed it fully ends its own process so it can launch again in the future

SOFTWARE/OS VERSIONS

(available in the Info Center app, or by running `kinfo` in a terminal window)
Operating System: EndeavourOS
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
Kernel Version: 6.13.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Graphics Processor: NVIDIA GeForce RTX 2070

ADDITIONAL INFORMATION
Stack trace after running krunner for the first time:

```
$ krunner
kf.svg: The theme "Aritim-Dark-Rounded-Blur" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "Aritim-Dark-Rounded-Blur" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "Aritim-Dark-Rounded-Blur" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.plasma.core: The theme "Aritim-Dark-Rounded-Blur" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
kf.svg: The theme "Aritim-Dark-Rounded-Blur" uses the legacy metadata.desktop. Consider contacting the author and asking them update it to use the newer JSON format.
qt.svg: <input>:387:362: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:388:110: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:389:110: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:389:353: Could not add child element to parent element because the types are incorrect.
qt.svg: <input>:390:109: Could not add child element to parent element because the types are incorrect.
```

stack trace of krunner after the 2nd run

```
$ krunner
QThreadStorage: Thread 0x58de61460030 exited after QThreadStorage 8 destroyed
QThreadStorage: Thread 0x58de61460030 exited after QThreadStorage 6 destroyed
QThreadStorage: Thread 0x58de61460030 exited after QThreadStorage 3 destroyed
```

Comment 1 Nicolas Fella 2025-02-13 10:40:39 UTC

> When running krunner since the latest KDE after running krunner once it will forever stay as a background process in the system. This prevents krunner from running again until you kill the background process.

That in itself is the expected behavior. Any subsequent invokation of krunner will use the existing process

Comment 2 spengreb 2025-02-13 10:43:01 UTC

Thanks for the quick reply!!

I see. I incorrectly assumed that because i was pkilling krunner and then it worked again that krunner should not be running in the background. 

At any rate, it still wont relaunch itself after the first run and I'm not clear at all as to why :)

Comment 3 spengreb 2025-02-13 10:46:37 UTC

I just noticed that this bug is a duplicate of bug #499889

Comment 4 cwo 2025-02-14 12:40:15 UTC

Thanks for reporting! They're both duplicates of bug 499722, marking as such.

AIUI the devs are still investigating how exactly the issue occurs; it seems to be a nvidia-specific issue.

*** This bug has been marked as a duplicate of bug 499722 ***

Comment 5 Nate Graham 2025-02-18 15:30:05 UTC


*** This bug has been marked as a duplicate of bug 480800 ***