[Unit]
…
ConditionVirtualization=oracle

Comes handy to ensure it is never started in a non virtualbox guest.

bjolie@embla:~> systemd-analyze
Startup finished in 6407ms (kernel) + 11734ms (userspace) = 18142ms

And no - there is not any ssd disks here, just plain old sata disk in software raid.

There’s no need for me being in the GNOME Team btw, the GNOME apps are simply the reference implementation both for Bluetooth and for Networkmanager (that’s the things I’m mostly involved with). For suspend / power management, there is (phew!) no desktop code involved in the paths I am interested in, so I don’t care.

And of course if I get the first bugreport “Bluetooth works in KDE and not in GNOME” then I will instantly reassign this to the GNOME team - it’s just that I have never seen it happen but I have seen it the other way round too many times.

But that’s way beyond what I wanted to tell. Take the discussion to the mailing list, nobody is going to read it here anyway.

Unfortunately I will not be able to answer because I am censored on that list.

I take it you have no problem dealing with Gnome bugs, despite the fact that KDE has done a better job with bluetooth bugs during the 12.1 cycle than Gnome has. I have no problem having DE maintainers dealing with DE-related bugs. But if you are only going to deal with Gnome-specific bugs, maybe you should be on the gnome team rather than claiming, wrongly, to be working for the whole distro.

And I will of course continue contributing, I will just be spending no thought on KDE bugs. It is simple: If I get a bug assigned, and there is no reproduction without involving KDE, it is going to the KDE maintainers. It’s that easy.

The response to my feature request has clearly shown that the people that are voting on features (where I am pretty sure that this is a different group of persons than the ones actually fixing the problems) does not want a working desktop. Well, let them have their wish But I won’t care if something is broken for them.

I have to say in a point I agree with the moderator, we all know where those discussions take people to (and of course I’m one of the regular trolls), and eventually one of this days I’ll become the next Kemter.

On a personal stance and even if we had our disagreements in the past, I think you should consider your decision and continue contributing… I used to play Federated handball (even had 1 modest intervention on the national team) and my old coach used to say: “Só faz falta quem cá está!” (Only those who are present will become ‘missed’).

Don’t turn your back on us dude, we want you to continue contributing and helping openSUSE! You love it, we love you (even KDE haters like me)!

I hope to see you reconsidering and returning to us, and honestly, you will be missed if you decide not to participate anymore.

We might be in opposite factions when it comes to Desktop preferences, but we’re brothers in arms when it comes to make openSUSE a better experience, and if that isn’t strong enough as a cause, what would be ?

From a friend (at least from my side),
Nelson Marques

And it isn’t that KDE is really the default desktop.

It’s only that the radio button is preselected…
And that is only for new installations…
And those will not be hit by the migration problem the thread started with…

So where where will the change of the preselcted radio button help here?