Sorry for not replying here earlier, but my system broke on Thursday (hardware-wise) and then I was away over the weekend.
I don’t think it makes sense to still answer all questions, but a few things:
This is definitely fixed in Plasma 5.2 beta, already available in KDE:Frameworks5. It was available in my repo as well, but I now have 5.2 final already which you cannot install at the moment because of too strict dependencies. This should be resolved on Tuesday when 5.2 is released, sorry.
You got a conflict with KDE 4, that means you installed the wrong package. I created two Tumbleweed packages with the fix, one to replace the standard Tumbleweed package (which conflicts with KDE4), and one that replaces my package. You apparently tried to install the former, when you should have installed the latter.
My repo for Tumbleweed (which you are using apparently) still contains the “buggy” 5.1.2, and I cannot update to 5.2 there as the necessary KF5 packages are not in Tumbleweed yet. This will take some days, maybe even weeks (until Plasma 5.2 is in Tumbleweed itself).
In the meantime, you have to add this repo with a higher priority (lower priority number), as already written: http://download.opensuse.org/repositories/home:/wolfi323:/branches:/home:/wolfi323:/branches:/openSUSE:/Factory/snapshot/
“zypper dup” should then sort out everything.
And yes, as has been mentioned, another workaround is to remove/comment out the following in startkde:
# At this point all environment variables are set, let's send it to the DBus session server to update the activation environment
/opt/kf5/lib64/libexec/ksyncdbusenv
if test $? -ne 0; then
# Startup error
echo 'startkde: Could not sync environment to dbus.' 1>&2
test -n "$ksplash_pid" && kill "$ksplash_pid" 2>/dev/null
xmessage -geometry 500x100 "Could not sync environment to dbus."
exit 1
fi
But if you use my packages, /usr/bin/startkde is still the KDE4 version, that’s why you didn’t find those lines. In this case modify /opt/kf5/bin/startkde instead.
Well, such things happen. It wasn’t the newest model any more…
If I’m lucky, only the power supply is damaged, but the mainboard could have been broken too.
The important thing: no data loss!
At the moment I’m busy copying the data over to the new system, which takes time.
So basically it just means that now at the moment I’m not as responsive as before, and don’t have too much time to help others with their problems.
I am also grateful and moderately excited for the news that 5.2 will be released on Tuesday (it’s already Monday afternoon here in NZ).
Yes, but as you are using my Tumbleweed repo, you still have to wait a bit longer.
KDE Frameworks 5.6 and Plasma5 have been submitted to Tumbleweed already, but the packages need to go through review and testing first.
In your case, with your repos, I’d recommend to add that repo I mentioned in my last post (remove any others you might have added before my reply), and run “zypper dup”.
Or, as you don’t seem to be dependent on Plasma5 anyway, just wait…
I cannot tell how long it will take for Tumbleweed though.
If you do want the “bleeding edge” packages, change my repo’s URL to “openSUSE_Factory” (instead of “openSUSE_Tumbleweed”), and add KDE:Frameworks5 too. Then you’ll have Plasma 5.2 (final) some time tomorrow.
If you do want the “bleeding edge” packages, change my repo’s URL to “openSUSE_Factory” (instead of “openSUSE_Tumbleweed”), and add KDE:Frameworks5 too. Then you’ll have Plasma 5.2 (final) some time tomorrow.
Just a heads-up:
Plasma 5.2.0 (final) is now available in the normal Tumbleweed repo (and in my repo for openSUSE_Tumbleweed), so the issue should be fixed in general.
People who added one of my bugfix repos should remove it again now, I have already deleted them.
