You can check the status here (on the right side):
Well, AFAIUI 12.2 still has a higher priority on the build service because the packages have been downloaded more often. But that will change over time…
That would be a bug then…
I haven’t tried it myself yet, as I am on 12.3.
But I’m already desperately waiting for a few of those bugfixes…
Maybe that is a “diplomatic hint” to finally use activities, but to be honest I still do not see any big advantage in using them. If you can tell me one… In the moment AFAIK the two are simply two ways to do the very same thing.
I don’t really use activities myself.
But they are not a replacement for virtual desktops, they are a complement. The main difference is that you can associate files, programs and plasmoids with activities and they then only show in these activities so you can quickly switch between them. (Well, I guess there’s a better explanation somewhere at kde.org… ;))
On the fact of default setting: the default settings are the first thing that I change to adapt to my own preferences. But maybe other users have no preferences but accept always default…but why we do still all these possibilities of personalisation, given that logic we should cement it all like gnome did…
I didn’t want to imply that users shouldn’t change the defaults. I also like to have a lot of configuration options to play with. That’s why we use KDE I guess.
What I wanted to say is, I think most users will have more than 1 desktop (although that’s KDE’s default), so they won’t have the desktop changer disappear. (unless there is a bug, of course lol!)
is it better to report KDE bugs generally to KDE instead to bugzilla.novell? What is better (more efficient for the project)?
General KDE bugs should be reported at bugs.kde.org, bugs caused by openSUSE customizations should be reported at bugzilla.novell.com. If you’re not sure, just pick one. They will tell you if you’re on the wrong one…
At the end I found out that the only way to do this is: just make sure you change it via Yast - edit sysconfig.
It behaves like that since years… This is a deliberate change by openSUSE.
There’s also a bug report about that: