Created attachment 149169 [details] Screen recording showing the behavior SUMMARY 3rd party window decorations settings not opening STEPS TO REPRODUCE 1. Install a third party window decoration (e.g. Sierra Breeze or Lightly) 2. Try to click on the pencil icon to configure it OBSERVED RESULT Settings do not open, no console output EXPECTED RESULT Settings should open SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.24.90 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.4 ADDITIONAL INFORMATION It only happens with 3rd party decorations that provide a custom configuration screen. I think it's only the ones written in C++.
Cannot reproduce. The config window for the Lightly theme opens just fine for me on git master. Maybe it got fixed already? Alexander, does this ring any bells?
I can not reproduce too. From looking at the code, we always go through `KDecoration2::Preview::PreviewBridge::configure`. Here we create a KCM from the KPluginFactory we load as a plugin. Breeze has it's own plugin with the id "org.kde.breeze", other plugins use the org.kde.kwin.aurorae factory which dynamically loads their QML config assets. Maybe the plugin loading fails or the plugin does not exist. Please run `qtpaths --plugin-dir ` and add "org.kde.kdecoration2" to the returned path. The run an "ls" in the full path. Hopefully a kwin5_aurorae.so plugin shows up :) Please also check the logs, by running "kcmshell5 kcm_kwindecoration" in the terminal.
ls `qtpaths --plugin-dir`/org.kde.kdecoration2 Result: breezedecoration.so hellodecoration.so kwin5_aurorae.so lightlydecoration.so sierrabreeze.so kcmshell5 kcm_kwindecoration Opens the KCM in a seperate window and it still doesn't work. Output: ``` kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86): This returns 1 when using Qt HiDPI scaling. file:///usr/lib/qt/qml/org/kde/kirigami.2/PlaceholderMessage.qml:235:5: QML Heading: Binding loop detected for property "verticalAlignment" kf.coreaddons: KPluginFactory could not load the plugin "/usr/lib/qt/plugins/org.kde.kdecoration2/sierrabreeze.so" kf.coreaddons: KPluginFactory could not load the plugin "/usr/lib/qt/plugins/org.kde.kdecoration2/breezedecoration.so" kf.coreaddons: KPluginFactory could not load the plugin "/usr/lib/qt/plugins/org.kde.kdecoration2/hellodecoration.so" kf.coreaddons: KPluginFactory could not load the plugin "/usr/lib/qt/plugins/org.kde.kdecoration2/lightlydecoration.so" Module 'org.kde.kwin.decoration' does not contain a module identifier directive - it cannot be protected from external registrations. ```
From where/how have you installed those window decorations? >kf.coreaddons: KPluginFactory could not load the plugin "/usr/lib/qt/plugins/org.kde.kdecoration2/breezedecoration.so" This really makes me wonder, because it is a first party plugin. Do you have it up to date or at the same version as KWin?
I installed them all from the AUR. I just tried to recompile them (I'm not sure if I did before) but that didn't help. Breeze is at version 5.24.90-1 from the kde-unstable repo.
What is the version of KWin you use?
pacman -Qi kwin ``` Name : kwin Version : 5.24.90-2 Description : An easy to use, but flexible, composited Window Manager Architecture : x86_64 URL : https://kde.org/plasma-desktop/ Licenses : LGPL Groups : plasma Provides : None Depends On : kscreenlocker xcb-util-cursor plasma-framework kcmutils breeze pipewire-session-manager libqaccessibilityclient lcms2 libxcvt Optional Deps : maliit-keyboard: virtual keyboard for kwin-wayland Required By : hello-kde-git kwin-effects-sliding-notifications kwin-effects-yet-another-magic-lamp kwin-scripts-forceblur plasma-workspace sierrabreeze-kwin-decoration-git Optional For : None Conflicts With : None Replaces : kwayland-server Installed Size : 24.47 MiB Packager : Antonio Rojas <arojas@archlinux.org> Build Date : Thu 19 May 2022 08:33:44 PM CEST Install Date : Thu 19 May 2022 10:24:37 PM CEST Install Reason : Explicitly installed Install Script : Yes Validated By : Signature ```
>From where/how have you installed those window decorations?(In reply to Alexander Lohnau from comment #4) > From where/how have you installed those window decorations? Please provide this info and the version of these decorations you have installed. That might help reproducing the issue.
pacman -Qi lightly-git ``` Name : lightly-git Version : r2172.121a61e5-1 Description : A modern style for qt applications Architecture : x86_64 URL : https://github.com/Luwx/Lightly Licenses : GPL2 Groups : None Provides : lightly-qt Depends On : frameworkintegration kdecoration breeze-icons kwayland hicolor-icon-theme Optional Deps : None Required By : None Optional For : None Conflicts With : lightly-qt Replaces : None Installed Size : 1078.06 KiB Packager : Unknown Packager Build Date : Wed 25 May 2022 06:19:26 PM CEST Install Date : Wed 25 May 2022 06:19:32 PM CEST Install Reason : Explicitly installed Install Script : No Validated By : None ``` pacman -Qi sierrabreeze-kwin-decoration-git ``` Name : sierrabreeze-kwin-decoration-git Version : r70.c2776ee-1 Description : OSX-like window decoration for KDE Plasma written in C++ (git version) Architecture : x86_64 URL : https://github.com/kay0u/SierraBreeze Licenses : GPL2 Groups : None Provides : None Depends On : kwin Optional Deps : breezemite-yakuake-git: Matching theme for Yakuake Required By : None Optional For : None Conflicts With : None Replaces : None Installed Size : 302.38 KiB Packager : Unknown Packager Build Date : Thu 19 May 2022 10:34:50 PM CEST Install Date : Thu 19 May 2022 10:34:56 PM CEST Install Reason : Explicitly installed Install Script : No Validated By : None ```
I'm gonna try to reproduce this in a clean Arch or Neon VM and provide the steps I used
Thanks for the additional info. I think it might be due to plugin loading API which got deprecated a while ago in KWin and has been removed now.
I have created Pull Requests in the two affected repositories, though there was no response from the maintainers yet.
Thank you for your efforts! I have applied the patch for the `lightly-git` AUR package. For the SierraBreeze one, I asked the maintainer of the AUR package if they could apply it too.
Those two PRs have been merged.