Since the 6.3.0 update I’m getting a stack of theme/icon pack pending updates under Discover, but I can’t update them. Every time I try the resulting error returned is:
I am guessing like in the KDE Store, many of the submissions need to be updated by their developer to be compatible and comply with KDE upgrades. Themes are one of the sections that are notorious for leaving out the appearance of icons, etc.
So unless approved by the current Plasma release, it’s better to stay on default.
Have you tried creating a new user and starting from a system default? Perhaps comparing config files would help you narrow down the culprit on your previously installed incompatible themes/icons.
Honestly? I shouldn’t have to create a new user to resolve a problem with Discover. That would really impact my workflow.
Something has changed in relation to theming under 6.3.0 and it’s manifesting as a problem under Discover. The installed themes were specifically made for KDE 6, this system has only ever run KDE 6 - It’s not like they could have carried over from an upgrade from 5.27.
You might have misunderstood. It’s just a method to determine the difference between what changed or added. I wasn’t suggesting an abandonment of your main user account.
Just as an example, a new user would not have the themes you installed on your main account installing one at a time to see which work can give you an idea which is working and which is not. You can then remove the incompatible themes and icons.
I haven’t actually looked into just where KDE stores themes, icon packs, and widgets by default. If such items are installed to the root partition, than no matter what user account was used, they’d quite possibly still appear under Discover.
as was said themes are 3rd party offerings that are often broken since plasma 5 to plasma 6 transition and they are notorious for not fully deleting themselves when uninstalled.
from my notes
## THEMES AND COLORS ##
#a global theme can add items to these settings, but may not remove them all upon uninstall
- Appearance > Global Theme
- Appearance > Plasma Style
- Appearance > Colors
- Appearance > Windows Decorations
- Appearance > Icons
- Appearance > Cursors
- Appearance > Splash Screen
- Startup and Shutdown > SDDM
#need to manually check each settings page, select the red trash can(s) and hit apply
Not really, I had about 5 themes installed that I’d tried over time but never used, as stated all themes were made specifically for Plasma 6.
This wasn’t just themes; it was icon packs, widgets, as well as a desktop effect - All downloaded via the respective ‘get new…’ buttons under KDE Neon 6 directly.
Perhaps KDE devs should have thought of that before making sweeping changes to Plasma theming? Especially when said themes, icon packs and widgets were downloaded from within Plasma 6 itself using the ‘Get New…’ button.
Should we not use the ‘Get New…’ button?
However, to hammer a point home, the issue is a result of an update applied only days ago - And oddly enough no one here can seem to outline just what changed that resulted in the issue experienced?
you should read the disclaimer warning that pops up when you use the “get new” button… you are essentially leaving KDE.
sticking with the builtin theme options like breeze is far safer.
these sorts of breakages can happen when major changes are made to the code, but they don’t happen that often… KDE has been around a long time and it’s only just now on ver 6.
Changes are to be expected as KDE evolves and progresses. Lotsa those found on KDE Store now work on version 6.2.5, and some still don’t with false indication that they might work with Plasma 6.
Plasma 6.3 is so recent it’s still sizzling. The third-party (themes, icons, scripts, etc.) are aware and those hard at work might get their stuff working sooner than later.
Then those that do not work will remain on the store and users will try them and -tada- they dont work.
It shouldn’t be KDE following the needs of the addons. Maybe it is better not to use ‘Get New…’ but hey, KDE developers made it available and functional so…
the point revisions to plasma 6 should not be affecting addons that are truly plasma 6 compliant.
the issue is how can a lowly user such as me know if a 3rd party addon is actually plasma 6 compliant or just saying they are with some minor tweak so that it doesn’t immediately produce an error message or crash.
the only tools i have are the reviews in the store and time.
the reviews over time will sort these out, but it will take ppl like you and me trying them on our devices, adding reviews to the store page, and giving feedback to the 3rd party developers so they know what to fix (assuming they are even still engaged).
The bigger question is what changed regarding theaming under KDE Neon with Plasma 6.3.0 that caused the issue under Discover to begin with? As it wasn’t a problem prior to an update that was released just after 6.3.0.
For some reason, the original question seems to be getting ignored. All I’m seeing are scarecrow arguments regarding a feature (Get New…) present under KDE Plasma.
i run it like 10 times thans work oke Download of “Deepin BigSur Dark Plasma 6” failed, error: Error transferring after 10 times works but you have to do somtining els first then go back take a other schot then works
