Hi,
I’ve searched and found virtualbox issues on here but not what I am experiencing.
Using Yast, I searched virtualbox and installed it but when I click on the application I see the window open in the Panel and after a few seconds it disappears… no error, nothing.
Can someone help me even understand what is happening here?
Thanks,
BSF
What package(s) exactly did you install?
Try to run “VirtualBox” in a terminal window to get some error messages.
Ah, I was trying “virtualbox”… thanks! Ok so it does load from the terminal but it does come with a couple of warnings:
/usr/bin/VirtualBox: line 5: /usr/lib/virtualbox/VBoxUSB_DevRules: No such file or directory
Qt WARNING: libpng warning: iCCP: known incorrect sRGB profile
The contents of the file /usr/bin/Virtualbox show:
#!/bin/bash
export QT_NO_KDE_INTEGRATION=1
/usr/bin/id -nG | grep -v -e "root" -e "vboxusers" >/dev/null && /usr/lib/virtualbox/VBoxPermissionMessage && exit
if ! -f /etc/udev/rules.d/60-vboxdrv.rules ]; then
/usr/lib/virtualbox/VBoxUSB_DevRules && sudo touch /etc/udev/rules.d/60-vboxdrv.rules
fi
LD_LIBRARY_PATH="/usr/lib/virtualbox${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}" /usr/lib/virtualbox/VirtualBox $@
I can confirm that the file or directory doesn’t exist. Not sure what the second warning means. A quick google tells me it has been patched but not sure how to apply this (if I need to).
Please post:
zypper se -si virtualbox vbox
uname -a
S | Name | Type | Version | Arch | Repository
--+------------------------------+---------+-----------------------+--------+--------------------------
i | virtualbox | package | 5.0.10-10.1 | x86_64 | openSUSE-Leap-42.1-Update
i | virtualbox-guest-kmp-default | package | 5.0.10_k4.1.12_1-10.1 | x86_64 | openSUSE-Leap-42.1-Update
i | virtualbox-guest-tools | package | 5.0.10-10.1 | x86_64 | openSUSE-Leap-42.1-Update
i | virtualbox-guest-x11 | package | 5.0.10-10.1 | x86_64 | openSUSE-Leap-42.1-Update
i | virtualbox-host-kmp-default | package | 5.0.10_k4.1.12_1-10.1 | x86_64 | openSUSE-Leap-42.1-Update
i | virtualbox-qt | package | 5.0.10-10.1 | x86_64 | openSUSE-Leap-42.1-Update
and
Linux Aaron-Suse 4.1.15-8-default #1 SMP PREEMPT Wed Jan 20 16:41:00 UTC 2016 (0e3b3ab) x86_64 x86_64 x86_64 GNU/Linux
Ah, don’t know how relevant those errors were/are but seems it wasn’t loading because I wasn’t a member of the vboxusers group. Added myself and logged out/in and it seems to be loading now.
Yes, you have to be member of vboxusers to be able to run it.
But the /usr/bin/VirtualBox script should actually show a warning dialog otherwise.
It seems this is part of the problem:
/usr/bin/VirtualBox: line 5: /usr/lib/virtualbox/VBoxUSB_DevRules: No such file or directory
It’s caused by this “code” that has been added recently to warn users that they have to modify some udev rules to get USB support (a lot of users “complained” that openSUSE’s packages do not support USB at all; they do, but it’s disabled by default because of security concerns)
if ! -f /etc/udev/rules.d/60-vboxdrv.rules ]; then
/usr/lib/virtualbox/VBoxUSB_DevRules && sudo touch /etc/udev/rules.d/60-vboxdrv.rules
fi
Apparently /usr/lib/virtualbox/VBoxUSB_DevRules (which is supposed to show the warning dialog) is missing in the package.
Should be reported as bug. And I have no idea how that “sudo touch” is supposed to work at all anyway.
To fix it, just run “sudo touch /etc/udev/rules.d/60-vboxdrv.rules” or copy over /usr/lib/udev/rules.d/60-vboxdrv.rules to /etc/udev/rules.d/.
Virtualbox has been a problem for me since 12.1. It never works just installing it from software manager.
For Leap (and every opensuse release back to 12.1) i had to install make, gcc, gcc-c++, kernel-source, kernel-syms
then i had to modprobe vboxdrv, vboxnetadp, and vboxnetflt
don’t forget to modify your startup scripts by adding the modules above to a new script in /etc/modules-load.d/ or you’ll need to load those three modules after every reboot for virtualbox to work.
then the package from opensuse works for me. This happens every time with every edition i’ve ever installed.
setup ubuntu for a friend, it worked immediately after installation.
guess i’m a little frustrated.
It works great here since even longer. And I always used the openSUSE packages, never had any problem…
For Leap (and every opensuse release back to 12.1) i had to install make, gcc, gcc-c++, kernel-source, kernel-syms
then i had to modprobe vboxdrv, vboxnetadp, and vboxnetflt
don’t forget to modify your startup scripts by adding the modules above to a new script in /etc/modules-load.d/ or you’ll need to load those three modules after every reboot for virtualbox to work.
None of this is necessary.
If the vboxdrv.service is enabled (it is by default), it will load the kernel modules on boot.
make, gcc, gcc-c++, kernel-source, kernel-syms are only needed to compile the kernel modules. But openSUSE’s packages come with them pre-compiled, that’s only needed if you install VirtualBox from virtualbox.org.
So you either confuse things here, or you maybe installed both versions (openSUSE’s and Oracle’s), which will give you problems sooner or later.