Bug 513732

Summary: Configuration windows from plasmoids do not render / appear blank
Product: [Plasma] plasmashell Reporter: Javier Jaramillo <javierjaramillogarcia>
Component: generalAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: kde, nate
Priority: NOR    
Version First Reported In: 6.5.4   
Target Milestone: 1.0   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Example of configuration window not rendering
Example of configuration window not rendering (2)
Non-rendering configuration window of plasmoid when Breeze is used

Description Javier Jaramillo 2025-12-23 09:25:08 UTC
Created attachment 187896 [details]
Example of configuration window not rendering

SUMMARY

When trying to open the configuration window for any plasmoid (either the ones that are part of KDE or community-based), the window opens but does not render - it appears blank or totally transparent.

STEPS TO REPRODUCE
1. Right click on any plasmoid
2.  Click "Configure XYZ" (Any plasmoid like Digital Clock / Panel Colorizer / Apdatifier etc"

OBSERVED RESULT
The configuration window open, but does not render - it appears blank or transparent 

EXPECTED RESULT
The configuration window opens and renders.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: KDE running over Wayland on ArchLinux
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1

ADDITIONAL INFORMATION
Comment 1 Javier Jaramillo 2025-12-23 09:25:53 UTC
Created attachment 187897 [details]
Example of configuration window not rendering (2)
Comment 2 Nate Graham 2025-12-23 20:17:14 UTC
That's weird.

Can you reproduce the issue in a new clean user account on the same computer, with no visual or functional customizations applied, and when opening the config window of one of the default widgets?
Comment 3 Javier Jaramillo 2025-12-23 20:37:00 UTC
Hello Nate,
I just tried with a fresh user - the config windows of the default widgets are working fine. So it seems the issue is related to some of the customizations that I have in my user - I will try to troubleshoot which one. I do not recall changing anything on my system lately, but maybe some of the themes have updated and I didn't notice (or I don't remember).
Comment 4 Javier Jaramillo 2025-12-23 20:46:13 UTC
I have tried to change one by one Colors, Application Style, Plasma Style, Windows Decorations and Icons to the standard themes (Breeze and Oxygen) - no luck. I have also used the Global Theme option to force changing everything to Breeze, and same result - I attach screenshot of the non-rendering window on Breeze.
Comment 5 Javier Jaramillo 2025-12-23 20:47:37 UTC
Created attachment 187917 [details]
Non-rendering configuration window of plasmoid when Breeze is used
Comment 6 Javier Jaramillo 2025-12-25 10:21:05 UTC
Merry Christmas to the KDE team!
I have investigated a bit more on this Xmas Eve morning using journalctl. Everytime I open a plasmoid configuration window I got the following string of error messages from plasmashell

***

plasmashell[1146]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/configuration/AppletConfiguration.qml:348:5: Type Kirigami.ApplicationItem unavailable 
                                                          Kirigami.ApplicationItem { 
                                                          ^
plasmashell[1146]: file:///usr/lib/qt6/qml/org/kde/kirigami/ApplicationItem.qml:78:1: Type Kirigami.AbstractApplicationItem unavailable 
                                                      Kirigami.AbstractApplicationItem { 
                                                      ^
plasmashell[1146]: file:///usr/lib/qt6/qml/org/kde/kirigami/AbstractApplicationItem.qml:131:5: Type OverlayDrawer unavailable 
                                                          property OverlayDrawer globalDrawer 
                                                          ^
plasmashell[1146]: file:///usr/lib/qt6/qml/org/kde/kirigami/OverlayDrawer.qml:14:1: Type KT.OverlayDrawer unavailable 
                                                      KT.OverlayDrawer { 
                                                      ^
plasmashell[1146]: qrc:/qt/qml/org/kde/kirigami/templates/OverlayDrawer.qml:232:36: Type KTP.DrawerHandle unavailable 
                                                          readonly property Item handle: KTP.DrawerHandle { 
                                                                                         ^
plasmashell[1146]: qrc:/qt/qml/org/kde/kirigami/templates/private/DrawerHandle.qml:68:17: ".onActiveValueChanged" is not available due to component versioning. 
                                                                      onActiveValueChanged: (delta) => { 
                                                                      ^
plasmashell[1146]: QQmlComponent: Component is not ready

***

I have tried to reinstall the 'kirigami' component from my distro repositories (Current version 6.21.0-2), but to no avail
Comment 7 Nate Graham 2025-12-30 17:29:23 UTC
That means it's probably not a theming issue, but rather a technical issue. If you've turned on the Vulkan renderer or messed with the render loop settings, those could potentially cause it.

Since it seems like this has been caused by a configuration issue, I'm closing bug report for now.

If you figure out which specific setting or change is causing the problem, please do let us know so we can ascertain whether this is a bug in any of our code or not. Thanks a lot!
Comment 8 Javier Jaramillo 2025-12-31 08:47:14 UTC
I did investigate a bit more yesterday and I have not been able to identify the specific change or setting that was causing the issue. 
However, I have been able to fix it by deleting my ~/.config/plasma-org.kde.plasma.desktop-appletsrc and ~/.config/plasmashellrc files. I got the default plasma desktop look after deleting both files, and all configuration windows were rendering correctly with my current theme / window decoration etc. I then edited my plasma desktop with the widgets that I was using before, and now everything works well (so the widgets were not the cause of the issue).

Thank you for all your help and I wish the KDE Team a happy new year!