SUMMARY You can't make new KWin scripts or adjust existing ones through the system settings STEPS TO REPRODUCE 1. Open system settings 2. Go to windows 3. Click on KWin scripts (or desktop effects, but that will be in a separate BR) OBSERVED RESULT qrc:/kcm/kcm_kwin_scripts/main.qml:26 Type NewStuff.Action unavailable qrc:/qt/qml/org/kde/newstuff/Action.qml:190 Type NewStuff.Dialog unavailable qrc:/qt/qml/org/kde/newstuff/Dialog.qml:110 Type NewStuff.DialogContent unavailable qrc:/qt/qml/org/kde/newstuff/DialogContent.qml:63 Type Kirigami.ContextDrawer unavailable file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/kirigami/ContextDrawer.qml:140 Non-existent attached object EXPECTED RESULT The ability to access KWin Scripts SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.20.0 Qt Version: 6.9.2 Kernel Version: 6.14.0-33-generic (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900HX Memory: 32 GiB of RAM (31.1 GiB usable) Graphics Processor 1: NVIDIA GeForce RTX 4080 Laptop GPU Graphics Processor 2: Intel® Graphics ADDITIONAL INFORMATION A similar error is in the "desktop effects menu", but I will make another bug for that in the respective category
Can't repro on fedora, might be neon bug Operating System: Fedora Linux 42 KDE Plasma Version: 6.5.80 KDE Frameworks Version: 6.19.0 Qt Version: 6.9.2 Kernel Version: 6.16.11-200.fc42.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 16 GiB of RAM (15.5 GiB usable) Graphics Processor: AMD Radeon RX 6600
It's a weird Kirigami or Qt issue that's been dogging us for years. Nobody has been able to figure it out yet. :(
*** Bug 510695 has been marked as a duplicate of this bug. ***
(In reply to Nate Graham from comment #2) > It's a weird Kirigami or Qt issue that's been dogging us for years. Nobody > has been able to figure it out yet. :( I see. Also, do you think this could be moved to major or is high good enough? Plus, if it's a known issue, I'm changing the status to confirmed