Upgrade to KDE 5

[cmcgrath5035]

@wolfi323

Try to run this to update all of them:

sudo zypper dup --from 10 --from 11 --from 12

This should sort it out. Priorities only have effect when installing new packages or when using “zypper dup”. For normal updates there’s the so-called “vendor-stickiness”, i.e. packages are not switched to other repos (“vendors”) automatically, even if there’s a higher version.

Making sure that libKF5Crash5 comes from the KDE:Frameworks5 repo should help as well, but there might be other problems.

It works. Of course it does, says wolfi.

Thanks

So when you runPackage switcher in YAST2 GUI, more than once, I assume the last (most recent)switch is the stickiest?
So I could have run package switcher on repo 11, then repo 12, then repo 10 and achieved same result?

BTW, I don’t think Virtual Box application has updated recently, but for sure I had to recompile the kernel interfaces as part of kernel upgrade 13.1 to 13.2.
Perhaps that broke clipboard sharing?

[wolfi323]

@cmcgrath5035

It works. Of course it does, says wolfi.

rotfl!

So when you runPackage switcher in YAST2 GUI, more than once, I assume the last (most recent)switch is the stickiest?
So I could have run package switcher on repo 11, then repo 12, then repo 10 and achieved same result?

Yes. Such a switch only takes that one particular repo into account. So the priorities don’t matter there either.

You could switch 3 times as you suggest, but the problem is that the switch to repo 11 will uninstall KDE4. I’m not sure whether the switch to repo 10 will then automatically unremove the KDE4 packages. I think it does though, because the conflict no longer applies then.

BTW, I don’t think Virtual Box application has updated recently, but for sure I had to recompile the kernel interfaces as part of kernel upgrade 13.1 to 13.2.
Perhaps that broke clipboard sharing?

You mean on the host?
I don’t think that matters. If the host kernel module doesn’t work, you wouldn’t even be able to start the VM.
And a recompile on a newer kernel shouldn’t break anything.

Maybe you need to run “VBoxService” in the guest for clipboard sharing to work? I’m not sure at the moment.
AFAIK Oracle’s guest additions include an init script that start it automatically during boot already.

[cmcgrath5035]

@wolfi323

rotfl!
You mean on the host?
I don’t think that matters. If the host kernel module doesn’t work, you wouldn’t even be able to start the VM.
And a recompile on a newer kernel shouldn’t break anything.

Maybe you need to run “VBoxService” in the guest for clipboard sharing to work? I’m not sure at the moment.
AFAIK Oracle’s guest additions include an init script that start it automatically during boot already.

Yes, host end recompile to new (13.2) kernel

I dunno, I (re)installed Guest Additions from the built-in CD image (on the VM) and clipboard started working again.

Looking at my host oS 13.2, I see 4 Vbox Services running: autostart, baloonctl, drv and web-service.

From the oS 13.2 Client VM end (running Plasma5!!) I see Vbox services running: add, add-service and add-x11.

I don’t run oS in VMs all that much, will watch more closely if/when I build another one.