Bug 500198

Summary:	krunner stops working after a while
Product:	[Plasma] krunner	Reporter:	Konstantin <jon9097>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	alexander.lohnau, natalie_clarius, nate, nicolas.fella
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Konstantin 2025-02-16 16:28:25 UTC

krunner stops working after a while. I press Alt+F2 and nothing happens. If I forcibly terminate the krunner process, it opens when I press Alt+F2 or if I type krunner in the terminal.

But it only opens once. Then you have to kill the process again to open it.


>QThreadStorage: Thread 0x605016dfb030 exited after QThreadStorage 8 destroyed
>QThreadStorage: Thread 0x605016dfb030 exited after QThreadStorage 6 destroyed
>QThreadStorage: Thread 0x605016dfb030 exited after QThreadStorage 3 destroyed

User@Alex ~> krunner // Here I launch the krunner
>Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) // krunner open
>qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x609b40cd2a10 // It shows up when I close the krunner window and press Alt+F2 again.
>qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x609b40cd2a10
>qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x609b40cd2a10

Comment 1 Konstantin 2025-02-16 16:30:03 UTC

This problem has been happening for many years

Operating System: Arch Linux 
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
Processors: 32 × Intel® Core™ i9-14900KF
Memory: 62.6 ГиБ of RAM
Graphics Processor: NVIDIA GeForce RTX 4080
Manufacturer: ASUS

Comment 2 Antonio Rojas 2025-02-16 17:12:11 UTC


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

Comment 3 Nate Graham 2025-02-18 15:30:10 UTC


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