Bug 512192

Summary: Plasma Widgets and Other Things Stop Responding on Wayland
Product: [Plasma] plasmashell Reporter: lra1982
Component: Application Launcher (Kickoff) widgetAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: normal CC: grispoil, kdedev, mikel5764, nate, noahadvs
Priority: NOR Keywords: wayland-only
Version First Reported In: 6.5.2   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: The bug in action
Log file from running journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt
More footage of this bug

Description lra1982 2025-11-16 14:38:07 UTC
Created attachment 186843 [details]
The bug in action

SUMMARY
At seemingly random times, the widgets in my taskbar will stop responding. This includes network menu, sound menu, bluetooth menu, systray, **application launcher**, etc. I have not identified any patterns or triggers for this other than just using the desktop. I am reporting specifically application launcher because when it crashes, there is no way for me to open anything new.

STEPS TO REPRODUCE
1. Use some programs like Chrome, Steam, Discord, and maybe a fullscreen game
2. Open application launcher
3. It doesn't open

OBSERVED RESULT
The application launcher refuses to open and just shows a blue rectangle at the top of the icon.

EXPECTED RESULT
The application launcher opens and you can see a menu with all your programs.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.17.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i7-10700F CPU @ 2.90GHz
Memory: 16 GiB of RAM (15.4 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 2070 SUPER

ADDITIONAL INFORMATION
I am sure that my drivers (nvidia-open) are up to date. I have not observed this bug on X11. I have seen this bug for months now ever since I tried the Wayland release. Attached is a video of the bug in action. I know it's a slightly old video, but it showcases the same problem that I experience today.
Comment 1 lra1982 2025-11-16 14:41:09 UTC
I forgot to include this in the original report. I have to mention that the only way that I know how to fix this issue is by signing out of plasma and signing back in. Quite the finicky solution.
Comment 2 grispoil 2025-11-17 16:00:14 UTC
I got the exact same issue since updating to Plasma 6.5. Restarting Plasma in terminal temporarily fixes the issue, but it's annoying. I've also noticed using journalctl in terminal that the error : " Need a window and a context ToolTipDialog(0x56059387a770, visibility=QWindow::Hidden, flags=QFlags<Qt::WindowType>(FramelessWindowHint|WindowStaysOnTopHint|WindowDoesNotAcceptFocus), transientParent=0x560593a10e80, geometry=437,944 296x232) " shows up after a while each time I click on the non-working icons.
Comment 3 lra1982 2025-11-18 00:27:40 UTC
I am glad to see that I have reported this to the right place then. Since you're also experiencing it, it is likely not an issue from my specific configuration.
Comment 4 TraceyC 2025-11-19 18:51:03 UTC
Thanks for the bug report, and the recording. I'm changing this from "crash" to "normal, since that doesn't look like a crash. I see the animation happen when you click the application launcher, and that it doesn't appear.

Can you check kwin's logs when the bug happens? You'll need to start a terminal before the freeze, and then type this into it when the bug is happening: 

  journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt

Then, attach ~/log.txt to this report. Thanks.
Comment 5 lra1982 2025-11-19 20:05:18 UTC
Created attachment 186963 [details]
Log file from running journalctl --boot --user-unit plasma-kwin_wayland > ~/log.txt

Thanks for recognizing the issue. Attached is a log from the command you told me to run. This was taken after the bug started affecting me.
Comment 6 TraceyC 2025-11-20 00:54:30 UTC
Thanks for the logs. The kwin developers will need to take a look.
Comment 7 grispoil 2025-11-20 13:55:47 UTC
I'd like to add this error message, in Kwin journal, it seems to regard the same issue : 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible Nov 19 22:13:55 eukaryot kwin_wayland[2535]: Invalid framebuffer status: "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT" Nov 19 22:13:55 eukaryot kwin_wayland[2535]: Failed to create framebuffer: Invalid argument Nov 19 22:13:55 eukaryot kwin_wayland[2535]: Failed to create framebuffer: Invalid argument Nov 19 22:15:10 eukaryot plasmashell[3000]: need a window and a context ToolTipDialog(0x565157397450, visibility=QWindow::Hidden, flags=QFlags<Qt::WindowType>
Comment 8 lra1982 2025-11-30 14:31:30 UTC
Created attachment 187266 [details]
More footage of this bug
Comment 9 lra1982 2025-11-30 14:35:10 UTC
I added a bit more footage of this happening. Now it looks like there is somewhat of a pattern to this happening. I didn't even have to run a game this time for it to do this; it seems to have something to do with windows being opened after being minimized. If you need another log file from me, I will surely give you one if you give me the command to run. Thanks for the support.
Comment 10 Nate Graham 2025-12-08 17:11:36 UTC
Unfortunately this is an NVIDIA GPU driver issue.

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