-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin does not provide configuration file in expected location #23
Comments
@ryu-ketsueki you can try to follow the steps in this video if you want: https://youtu.be/Tn47ubqb6FE |
That is not my problem at all. This video does not cover this specific problem. There, the configuration dialog appears after doing the symlink but here with me, it gives the error on the title of this issue. It is probably expecting a dedicated configuration file instead of looking up on kwinrc. It could be because Plasma updated the way the scripts work so this means this script needs to be updated to use that new format of having a dedicated configuration file |
Oh...Would you please share your Firefox CSS with me?! I'd love to see if it works for me or not. |
I found out where the configuration for Force Blur is stored and added manually with Kate. It is working. But the problem remains the same. The configuration dialog doesn't work. |
Just for visibility, the config for Force Blur is in
Assuming you need to add another program, add to the |
I have got the same problem. The piece of text you mentioned doesn't show up in the kwinrc. |
The script was already working on my machine before an update returned this error. I'd try adding those lines to the kwinrc and running
Otherwise, not really aware of any fix for this. The last commit in this project was nearly two years ago, so I'm not sure if this will be fixed. |
I'll just use a WM :) |
I reported a bug directly to KDE some time ago and I got an answer. It would seem that with Kwin's migration to jsons for metadata, the .desktops got not only deprecated but also unsupported. Force Blur must move from using .desktop for metadata to json. https://develop.kde.org/docs/extend/plasma/widget/setup/#metadatajson |
Hey, thanks for the heads up. I was kinda puzzled, as I could not reproduce at all, but I now get the same issue after updating KDE last night. This is a critical issue, so I'll look into it. |
It sounds like the source of the error message is here: https://invent.kde.org/plasma/kwin/-/blob/77ec43d5e15a8b8ad8e1824ebf49d7d3cbf015c5/src/scripting/genericscriptedconfig.cpp#L83 So KCM checks for two file: |
Alright, I could run KWin script module independently using
So, yeah, this script has Anyway, I'll upload the fix soon. |
KCM complained when trying to open up the script config panel: Plugin does not provide configuration file in expected location This was due to a behavior change in KWin when loading KCM modules for plugins. We need to designate the related KCM module manually, using `X-KDE-ConfigModule` field in metadata Note that we're using `genericscripted` module, which generates config dialog using `config.xml` and `config.ui`.
0.6 fixed configuration panel, but blur doesn't work. |
Yup you're right... The fix was fine, but an error was introduced while clearing up the metadata.desktop... Releasing again. |
Unfortunately I still see "Plugin does not provide configuration file in expected location" even after some reinstalls of the script via the github code or directly via "Kwin Scripts" -> "Get New Scripts". |
I switched to i3 now but I if you want me to, I could test if the plugin will work.
|
Any help is appreciated! :) |
@leon-erd I uploaded two different versions, because KWin 5.24.0 broke the compatibility (though it seems like they fixed it back in 5.24.1). If you're using 5.23, then please download v0.5. The other one (v0.6.1) is currently broken for KWin<5.24.0. |
Thanks a lot! It does work now with the v0.5! :) |
The title above is an error given whenever I try to open the configuration dialog. It happens with Force Blur only. I was going to use it to blur Firefox as I got a CSS theme that has a transparent background
The text was updated successfully, but these errors were encountered: