search

Flupp / sticky-window-snapping

A KWin script which lets snapped window edges stick together when one window is resized.
https://store.kde.org/p/1112552/
121 stars 12 forks source link

Configuration file not in "expected location" #18

Open rafaelhlima opened 2 years ago

rafaelhlima commented 2 years ago

Hi! I installed the Sticky Window Snapping extension and ran the commands bellow so that the configuration dialog would appear in System Settings.

mkdir --parents ~/.local/share/kservices5/
ln --relative --symbolic ~/.local/share/kwin/scripts/sticky-window-snapping/metadata.desktop ~/.local/share/kservices5/kwin-script-sticky-window-snapping.desktop

After restarting System Settings the "Configure" button does appear, but when I click it I get the following error message: "Plugin does not provide configuration file in expected location". Sticky_edges

The plugin itself is working, but I cannot change any settings.

I installed version 1.0.1 of the plugin. Below is my system info:

Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.0 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-28-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660/PCIe/SSE2

Flupp commented 2 years ago

I can reproduce the problem. It is also currently discussed in the KDE bug tracker.

I do not know yet what is the preferred solution. In the meantime, you can try branch metadata.json (c890dcac5df9e5a5fb153ae01b20ae8411fa474d). (I’ll remove the branch as soon as the problem is solved.)

nclarius commented 2 years ago

Does this work for you? When I just add the json file while keeping the desktop one I'm getting the same error. When I empty the contents of the metadata.desktop or delete the file altogether, the script will not show up in the list of KWin scripts at all, even when I link the metadata.json instead. Did I miss a step?

Flupp commented 2 years ago

The above mentioned branch works for me. A simple kpackagetool5 --install package in the root of the repo does the trick. (No symlink hackery necessary in contrast to the old metadata.desktop approach.) Maybe double check that no files from previous installations are left.

nclarius commented 2 years ago

Thanks, that did the trick. Though https://bugs.kde.org/show_bug.cgi?id=444378#c6 is my preferred solution now.

nclarius commented 2 years ago

I have no second system to test my scripts on, so if I may ask, re. your comment in the bug report:

Did I understand it correctly that

So it can only ever work with one of the versions?

rafaelhlima commented 2 years ago

Hi! Weirdly enough the bug disappeared after frameworks got updated to 5.91. Can this be related?

I have just clicked the Configure button and the settings dialog appeared.

alex1701c commented 2 years ago

https://invent.kde.org/frameworks/kcmutils/-/commit/60ac2bf394c9cd8a142698332ffdbee55a61e705 That should have fixed it.

The issue was, that because of the symlinking the compatibility code path in kcmutils was used and there this one key was missing.