https://bugs.kde.org/show_bug.cgi?id=444378

--- Comment #9 from Flupp <bugs.kde....@derflupp.e4ward.com> ---
Created attachment 147299
  --> https://bugs.kde.org/attachment.cgi?id=147299&action=edit
metadata-compatibility.fods

I checked several Plasma versions to find out which metadata formats work or
don’t work for each version.

For `metadata.desktop`, I varied usage of `X-KDE-ConfigModule` and
`X-KDE-Library`, and I varied symlinking the desktop file in
`~/.local/share/kservices5/`. For `metadata.json` I just used one variant with
`X-KDE-ConfigModule` and without symlink.

Depending on the Plasma version, I encountered four different outcomes (details
can be found in the attached `metadata-compatibility.fods`):


• Plasma 5.24.2, 5.24.1: all variant work except `metadata.desktop` with
`X-KDE-Library` and without symlink.

• Plasma 5.24.0: same as above except `metadata.desktop` with `X-KDE-Library`
and with symlink results in the reported error message.

• Plasma 5.23.5, 5.23.4: Only `metadata.desktop` with `X-KDE-Library` and with
symlink works. Any version using `X-KDE-ConfigModule` results in the reported
error message.

• Plasma 5.23.2, 5.23.1, 5.22.5, 5.20.5, 5.18.5: All variants using
`X-KDE-Library` and symlink work. For the `metadata.desktop` using only
`X-KDE-ConfigModule` with symlink, clicking the configuration button results in
the error message “The module Sticky Window Snapping is not a valid
configuration module. The diagnosis is: The desktop file
kwin-script-sticky-window-snapping.desktop does not specify a library.”


>From that I infer that, for maximal backwards compatibility, we are stuck with
the variant `metadata.desktop` with `X-KDE-Library` and with symlink for quite
some time when there is no further bugfix release for Plasma 5.23 assuming many
distributions currently using Plasma 5.23 won’t switch to a newer version soon.
That is unfortunate because this variant requires manual intervention by the
user creating the symlink even with the newest Plasma version.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to