SUMMARY STEPS TO REPRODUCE 1. Click the volume icon on the taskbar (or the network icon) 2. Observe that the volume widget does not open, the icon becomes underlined like it is selected, but no widget 3. If you did not observe #2, leave your computer running overnight and try again in the morning? It's a bit random and usually fixes when I restart. OBSERVED RESULT Volume widget does not open, the icon becomes underlined like it is selected, but no widget EXPECTED RESULT Volume widget opens SOFTWARE/OS VERSIONS Windows: No macOS: No (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.4.5 KDE Frameworks Version: 6.18.0 Qt Version: 6.9.2 Kernel Version: 6.16.7-arch1-1 (64 bit) Graphics Platform: Wayland ADDITIONAL INFORMATION This wasn't happening until a recent system update probably within the last couple weeks, and now it happens about once a day or every other day. Running `journalctl --user -f` showed no additional logs while it was happening and clicking the taskbar icons. Restarting plasmashell fixes it, e.g. `killall plasmashell; kstart plasmashell`
Apparently I missed the summary section and I can't edit the post. Here's a summary: Clicking systemtray icons such as volume or network randomly stop opening their respective widgets, instead just showing the outline and the dropdown error changes like normal, but no widget. Once it happens, widgets stop opening until a reboot or plasmashell is restarted.
Do you have an NVIDIA GPU?
Created attachment 184987 [details] attachment-2940034-0.html Yes Nvidia 3080 - Driver: 580.82.09 On Tue, Sep 16, 2025, at 5:03 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=509557 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > Status|REPORTED |NEEDSINFO > > --- Comment #2 from Nate Graham <nate@kde.org> --- > Do you have an NVIDIA GPU? > > -- > You are receiving this mail because: > You reported the bug. Paul Hansen mail@paul.rs https://github.com/paul-hansen
Thanks. Looks like the same issue as Bug 480800, or a recurrence of it. That issue had to be fixed in Qt. There may be another change in Qt required if this issue is coming back. :/ Or it could be a regression in the NVIDIA driver itself. Either way, it's an issue somewhere upstream, not in Plasma itself. *** This bug has been marked as a duplicate of bug 480800 ***
I'm having the same problem on my Fedora Asahi installation (M1 Macbook Air 2020), and noticed that the widgets stop displaying if I: 1. Open the widget (such as the System tray, Sensor, Calendar and Kickoff) 2. Click on another opened window (in my case, I've tested this with Firefox, Dolphin and System settings) 3. Try to open said widget, but then it doesn't come up The bug can be avoided if I click the widget button to "manually" close it. Sometimes, even the Hover Task to Preview action stops working. This occurs when I hover over active tasks and then move the pointer to applications that have some kind of interactive highlighting of UI elements, like Firefox hyperlinks or Dolphin displayed files, all of this quickly enough to do it before the Preview closes.
frankgrimy thanks for the tip, that is exactly what is happening for me too and I can consistently replicate it now that I know it's caused by simply clicking outside of the widget to close it. Nate Graham, is there a plan to fix this? It seems odd that you closed it as a duplicate of a bug that was supposedly fixed in an older version than what I reported. If it is the same shouldn't it be reopened? Is there an issue I can follow where it was reported upstream or something? (attempting to change the status to reported if it lets me, seems like we need some eyes on this.)
Yeah, since you have Qt 6.9 or later, then either Bug 480800 isn't fixed, or this is a different issue.
I guess this is happening because Vulkan rendering might be enabled on your system. Check kcmshell6 kcm_qtquicksettings so the Rendering backend is set to Automatic or OpenGL, and the Render loop should be set to Automatic too. Also uncheck GL Core Profile. Then log out and log in again, or reboot.
Ah! That was it, I had a gpu driver crash or something awhile back and it was giving me a warning about being in software rendering mode and clicking it opened that prompt so I selected vulkan instead of auto to try to force it to switch back, didn't realize vulkan was problematic and forgot about it. For anyone coming here looking for a workaround, you can search the app launcher for "Plasma renderer" to open that prompt again and switch back to auto. Thanks all!