On Tue, 31 Oct 2017 16:26:02 +0000, susejunky wrote:
> hendersj;2843544 Wrote:
>> On Tue, 31 Oct 2017 11:36:01 +0000, susejunky wrote:
>> > When i try to install virtualbox 5.1.30 on a laptop running openSUSE
>> > 42.3 with Kernel 4.13.10-2.g951f578-default Yast always gives the
>> > message
>> Where are you obtaining VirtualBox from?
>> Jim Henderson openSUSE Forums Administrator Forum Use Terms &
>> Conditions at http://tinyurl.com/openSUSE-T-C
> I try to install the package virtualbox 5.1.30 from this repository:
Try using the one in the Virtualization repository instead. I’ve been
using that one for years (though not on 42.3 - still running 42.2 here)
and never had a problem with it.
virtualbox has a kernel package (virtualbox-guest-kmp-default-5.1.30_kx.y.z) and my understanding is, that i have to use a version of virtualbox which provides this package in the same version as the kernel in use (i.e. virtualbox-guest-kmp-default-5.1.30_k4.13.10_2.g951f578-3.2.x86_64.rpm).
On Tue, 31 Oct 2017 21:26:02 +0000, susejunky wrote:
> virtualbox has a kernel package
> (virtualbox-guest-kmp-default-5.1.30_kx.y.z) and my understanding is,
> that i have to use a version of virtualbox which provides this package
> in the same version as the kernel in use (i.e.
> So am i wrong?
You are not wrong, but the package you need is in the Virtualization
repository, and is packaged to work with the version of Virtualbox that’s
Are you running the stock Leap kernel with Leap? If so, that should work.
If you’re not running the stock Leap kernel, why aren’t you? You should
not mix Tumbleweed kernels with the Leap distribution - that
configuration is not tested and may lead to weird problems (such as the
problem you’re experiencing).
Use a Virtualbox packaged by openSUSE when you are running a default (I’m not talking about Default) kernel, because that’s what each packaged Virtualbox is targeted at.
If you’re going to use an unusual kernel,
Then you’ll have to know that plenty of things (not just a packaged Virtualbox) will work on that machine with that kernel. And, that’s not unusual but to be expected… It just means you need to decide which things you are willing to bend a little on when you run an unusual kernel.
Aside from building your own dependencies,
You might have more success simply downloading and building Virtualbox from the Oracle website… That version won’t be built against any specific kernel and the install will dynamically build your kernel modules when you install (instead of an openSUSE which packages pre-built modules). And then, if the install fails, it’s usually something the VBox community will need to fix, not an openSUSE issue (but you can post here first to be certain).
As for your original question, a missing libcrypto.so.xx is a common problem. I’m not in front of a machine where I can check, but you should run the usual tries
zypper se --provides *missing_file *
That approach worked fine with openSUSE 42.2 but fails with openSUSE 42.3.
Ah, i see. Something definitely worth trying …
As i mentioned in my first post searching with Yast which package will provide libcrypto.so.1.0.0 yields that it is provided by package libopenssl1_0_0 Version 1.0.2j-10.1 which is already installed on my system (and there definitely is a file /usr/lib64/libcrypto.so.1.0.0). A Google-search with the YaST error message did not render any useful hints so i came here to ask.