Created attachment 181616 [details] The warning SUMMARY The following warning comes up in two scenarios where it shouldn't: "This Global Theme does not provide any applicable settings. Please contact the maintainer of this Global Theme as it might be broken. STEPS TO REPRODUCE Scenario 1: 1. Apply Breeze or Breeze Dark on the Quick Settings page 2. Go to Colors & Themes > Global Theme 3. Click on the theme you applied in step 1. Scenario 2. 1. Apply a Global Theme on the Colors & Themes > Global Theme page 2. Change any theme component e.g. Colors, Cursors, Icons etc. 3. Go back to Colors & Themes > Global Theme 4. Click on the theme you applied in step 1. OBSERVED RESULT The dialog that comes up isn't the usual dialog, but one where there's a false warning about the theme being broken. EXPECTED RESULT The usual dialog comes up. SOFTWARE/OS VERSIONS System Settings: 6.3.90 KDE Frameworks: 6.15.0 Qt: Using 6.9.0 and built against 6.9.0 KDE neon Unstable Edition (Wayland) Build ABI: x86_64-little_endian-lp64 Kernel: linux 6.11.0-26-generic
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5507
I don't think the merge request (based in the merge request description) should fix this behaviour. In Scenario 1, the Quick Settings global theme doesn't contain the "Desktop and window layout", only the visuals. So the user may want to apply the same theme again to also use the "Desktop and window layout" provided by it. In Scenario 2, one of the currently selected theme components is not the same as the one provided by the currently selected Global Theme. So the user may want to reapply the Global Theme to go back to the theme components provided by it.
I can see that, but the concept of re-applying what's already applied — and indicated visually as such in the UI — strikes me as unintuitive and odd, which is why I went for the approach I did in that merge request.
So this merge request will basically not allow do user to encounter this bug? I guess that's a solution :) Also, how do you find out so quickly when bugs are duplicates of others? Sometimes I do a search and also pay attention to the auto-suggested similar bugs and still miss that my issue had already been reported.
8 years of triaging KDE bugs on and off (and 5 of doing it pretty intensively), so I have a mental map of what I've seen before. If I can't recall it exactly, then if I've seen it before, it's in my browser history, so I can usually find it by searching for some relevant keywords.
i somehow can't reproduce the error dialog, if i change for instance just the colors and then re-apply the global theme i already have and will correctly reset the colors to default, with no error dialog appearing
*** Bug 479921 has been marked as a duplicate of this bug. ***
*** Bug 502738 has been marked as a duplicate of this bug. ***
>i somehow can't reproduce the error dialog, if i change for instance just the colors and then re-apply the global theme i already have and will correctly reset the colors to default, with no error dialog appearing I can. If I click on my active lnf theme first I get the warning If I click on a random lnf theme, get a prompt - and then select the original, I do not get a warning.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5524
Git commit 8c74fe5206f1e1a7e3bc13622923b2a0da9c9593 by Nate Graham, on behalf of David Edmundson. Committed on 28/05/2025 at 14:36. Pushed by ngraham into branch 'master'. kcms/lookandfeel: Initialise member variables We have various member variables reflecting the support of the currently selected lnf theme. This updates if selection changes, but not on startup. The user-facing impact of this is applying the initially selected lnf gives a warning about this lnf not supporting layouts or contents. M +5 -2 kcms/lookandfeel/kcm.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/8c74fe5206f1e1a7e3bc13622923b2a0da9c9593
Git commit 0c487ef393624e4760474bf946b03390b920f775 by David Edmundson, on behalf of Nate Graham. Committed on 29/05/2025 at 10:19. Pushed by davidedmundson into branch 'Plasma/6.4'. kcms/lookandfeel: Initialise member variables We have various member variables reflecting the support of the currently selected lnf theme. This updates if selection changes, but not on startup. The user-facing impact of this is applying the initially selected lnf gives a warning about this lnf not supporting layouts or contents. (cherry picked from commit 8c74fe5206f1e1a7e3bc13622923b2a0da9c9593) f8b27a97 kcms/lookandfeel: Initialise initial member variables Co-authored-by: David Edmundson <kde@davidedmundson.co.uk> M +5 -2 kcms/lookandfeel/kcm.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/0c487ef393624e4760474bf946b03390b920f775