Do you maybe still have any old digikam-plugin-* packages installed?
Those plugins are integrated into the image editor now AFAIK, so there shouldn’t be a need to install any plugins.
I don’t see anything in the build log that would indicate that those options are not being compiled in.
Maybe try to run “kbuildsycoca5 --noincremental”, may be caused by an outdated cache.
Guess I see the same thing as the OP. Packages are from KDE_Extra repo for TW. I’ll switch to the stock TW packages ( means digikam -> digikam5 ) and see if the issue persists
No, version 5.2.0 is named digikam in Tumbleweed too, not digikam5 (that’s the name I use in my repo to be able to install it side-by-side with the KDE4 version).
There should not really be a difference between KDE:Extra and the stock Tumbleweed package though, as KDE:Extra is the devel project, the package from there is submitted as-is to Tumbleweed.
Running “kbuildsycoca5 --noincremental” in my case has not resulted in the missing (sub)menu entries for ‘Colour’, ‘Enhance’, ‘Decorate’, and ‘Effects’ appearing.
What I have discovered however is a new user does not exhibit this problem.
I wonder could it perhaps be caused by the ‘Migration Assistant’ that I chose to run at first startup of V5*
Also, I’m a little confused as to where and which configuration files V5* actually uses…
Hm, that directory is completely empty here anyway.
AFAIK, this would only contain customizations to the GUI (like rearranging toolbars and so on), so you could probably just delete it.
But yes, maybe some KDE4 file has been copied over that the KF5 version doesn’t like.
Ah yes. I never changed those settings here though.
(Actually I’m not really using digikam at all)
There were lots of ‘kipiplugin_*.rc’ files which I guess were all from the KDE4 version. They now seem to reside in ‘~/.local/share/kxmlgui5/digikam/’
Yes, seems so.
The migrator just copies everything from ~/.kde4/share/apps/digikam/ to ~/.local/share/digikam/ though.
May be worth a bug report.
According to the name this seems to contain the “window/GUI settings” for the image editor, yes.
Apparently the GUI has changed too much in the KF5 version, so the KDE4 file causes problem or something like that.
May be also worth a bug report, in that case it would probably be better to just skip migrating that file to prevent such problems.