Hi, I needed to downgrade dkms from 3.0.2-1 to 3.0.1-1, see the aur-general Archives. Regards, Ralf
Search Criteria
Package Details: virtualbox-bin 6.1.34-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/virtualbox-bin.git (read-only, click to copy) |
---|---|
Package Base: | virtualbox-bin |
Description: | Powerful x86 virtualization for enterprise as well as home use (Oracle branded non-OSE) |
Upstream URL: | https://www.virtualbox.org/ |
Keywords: | machine oracle virtualization vm |
Licenses: | GPL2 |
Conflicts: | virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch |
Provides: | virtualbox, virtualbox-host-dkms, VIRTUALBOX-HOST-MODULES |
Replaces: | virtualbox-sun, virtualbox_bin |
Submitter: | Rainmaker |
Maintainer: | dbermond |
Last Packager: | dbermond |
Votes: | 57 |
Popularity: | 0.000416 |
First Submitted: | 2015-08-18 09:16 (UTC) |
Last Updated: | 2022-04-21 01:32 (UTC) |
Dependencies (15)
- device-mapper (device-mapper-git, device-mapper-noudev)
- dkms
- fontconfig (fontconfig-srb, fontconfig-minimal-git, fontconfig-ubuntu, fontconfig-git)
- hicolor-icon-theme (hicolor-icon-theme-git)
- libgl (glshim-git, libhybris-ext-libgl-git, libhybris-libgl-git, mesa-libgl-noglvnd, nvidia-340xx-utils, libglvnd-git, swiftshader-git, amdgpu-pro-libgl-cfe, amdgpu-pro-libgl, libglvnd)
- libidl2
- libxcursor (libxcursor-git)
- libxinerama (libxinerama-randr-git)
- libxmu
- python (python38, python36, python37, python39, python3.7, nogil-python, python311)
- sdl (sdl-openglhq, sdl-nokbgrab, sdl-openglhq-nokbgrab, sdl-git, sdl2_compat12-git, sdl12-compat-git, sdl12-compat)
- python (python38, python36, python37, python39, python3.7, nogil-python, python311) (make)
- virtualbox-bin-guest-iso (optional) – for guest additions CD image
- virtualbox-bin-sdk (optional) – for the software developer kit
- virtualbox-ext-oracle (virtualbox-ext-oracle-dev) (optional) – for Oracle extensions pack
Required by (31)
- albert (requires virtualbox) (make)
- albert (requires virtualbox) (optional)
- albert-bin (requires virtualbox) (optional)
- albert-git (requires virtualbox) (make)
- albert-git (requires virtualbox) (optional)
- albert-switch-application (requires virtualbox) (make)
- albert-switch-application (requires virtualbox) (optional)
- cernvm-webapi (requires virtualbox)
- darch-conf (requires virtualbox)
- fdroidserver (requires virtualbox) (optional)
- fdroidserver-git (requires virtualbox) (optional)
- genymotion (requires virtualbox)
- genymotion-beta (requires virtualbox)
- minikube-bin-aliyun (requires virtualbox) (optional)
- minikube-git (requires virtualbox) (optional)
- minishift (requires virtualbox) (optional)
- minishift-bin (requires virtualbox) (optional)
- python-malboxes-git (requires virtualbox)
- sailfishos-sdk-bin (requires virtualbox)
- vdfuse (requires virtualbox)
Sources (12)
- 013-Makefile.patch
- 60-vboxdrv.rules
- dkms.conf
- http://download.virtualbox.org/virtualbox/6.1.34/VirtualBox-6.1.34-150636-Linux_amd64.run
- https://download.virtualbox.org/virtualbox/6.1.34/VirtualBoxSDK-6.1.34-150636.zip
- LICENSE.sdk
- VBoxAuth-r94273.h
- VBoxAuthPAM-r94273.c
- VBoxAuthSimple-r94273.cpp
- vboxreload
- vboxweb.service
- virtualbox.sysusers
Latest Comments
Ralf_Mardorf commented on 2021-11-25 08:53 (UTC)
drankinatty commented on 2021-11-14 02:05 (UTC)
With Linux 5.15, for Linux Guests, vboxadd-setup.log will show:
error: no such file or directory # include <drm/drm_irq.h>
Since most of the features are native in the kernel, this build failure installing guest additions seems to only effect the initial modesetting for the terminal. X, Shared-Folders, and the rest continues to work fine on the guest. Notified Oracle via the Virtualbox list and we will see what they say. Current Oracle TestBuilds (revs: 148164 and 148140-ext pack) do not address the issue.
So at least for virtualbox-bin, the 5.15 update doesn't cause any significant issues (thankfully!)
Kr1ss commented on 2021-10-21 19:03 (UTC)
drankinatty commented on 2021-10-21 19:00 (UTC)
6.1.28 is out -- just update the version number, build no, etc.. and sums and it is good to go.
nursoda commented on 2021-09-11 13:43 (UTC)
Current virtualbox-bin package dated 2021-07-29 and showing version 6.1.26 r145957 also works fine on current kernel 5.14.2-arch1-2 for me.
drankinatty commented on 2021-09-11 07:13 (UTC)
Linux kernel 5.14 is supported by VirtualBox test builds 6.1.27r146191 and newer.
dbermond commented on 2021-07-21 02:51 (UTC)
@drankinatty Thanks for appreciating the package. Working fine for me too.
drankinatty commented on 2021-07-21 01:55 (UTC)
Kudos on the fast update -- all working well.
dbermond commented on 2021-05-06 00:32 (UTC)
@drankinatty There is no virtualbox-bin directory on the AUR sources.
drankinatty commented on 2021-05-05 21:37 (UTC)
Was inclusion of the ./virtualbox-bin directory in the source package intentional?
drankinatty commented on 2021-02-26 00:08 (UTC)
Well, the commit of "Add patch for linux 5.11" should do it. You were one step ahead. I just built from the teestbuild which incorporates the patch. (I am quite pleasantly surprised you already had it covered) Now if we can just get Oracle to fix the guest issue with 5.10+, we will be is great shape.
dbermond commented on 2021-02-25 17:18 (UTC)
@drankinatty I have no problems building the virtualbox kernel modules with latest 5.11.1 kernel. Works fine for me.
drankinatty commented on 2021-02-25 17:14 (UTC) (edited on 2021-02-25 17:34 (UTC) by drankinatty)
Fun continues. vboxnetflt fails to build with 5.11. Bug: https://www.virtualbox.org/ticket/20198 The testbuilds https://www.virtualbox.org/wiki/Testbuilds as of revision 142917 allows 5.11 vboxnetflt module to build on Arch. However, Arch host/Arch Guest, Guest will fail to boot with Kernel Panic for kernels after 5.9. Bug is months old and still unresolved https://www.virtualbox.org/ticket/20055
joolsrulez commented on 2021-01-25 16:43 (UTC)
6.1.18-1 bug can't select ISO file in KIO Open dialog is gone
drankinatty commented on 2021-01-22 06:05 (UTC) (edited on 2021-01-22 07:36 (UTC) by drankinatty)
Any luck with 6.1.18 that came out on 1/12/21? Note, I built from 6.1.18 and the Archlinux Host is fine. However, attempting to update the Archlinux guest to 5.10 succeeds in installing the Linux_Guest_Additions, but on reboot a Kernel Panic occurs. This has been an continual issue with Linux 5.10 guests. (make a snapshot before you try) Reverting the guest to Linux 5.9.14 and all is good.
joolsrulez commented on 2021-01-10 14:08 (UTC)
Virtualbox 6.1.16 : Storage Section under VM configuration : Can't select ISO file in KIO Open dialog [Was OK before release of 6.1.14]
dbermond commented on 2020-11-22 00:20 (UTC)
@ElijahLynn This package is not the virtualbox extension pack. You can find the extension pack here. The package description already states what differentiates it from the repository one: "Oracle branded non-OSE".
ElijahLynn commented on 2020-11-19 03:31 (UTC)
Appreciate that @Kr1ss. I read that a bit and see it is basically the "VirtualBox Extension Pack" which according to https://www.nakivo.com/blog/how-to-install-virtualbox-extension-pack/, says:
- Support for USB 2.0 and USB 3.0 devices
- Host webcam pass-through
- VirtualBox Remote Desktop Protocol (VRDP)
- Disk image encryption with AES algorithm
- Intel PXE Boot ROM
Would be good if somehow this package could put that in a description of sorts to distinguish the two because as an outsider, I had no idea.
Kr1ss commented on 2020-11-18 23:09 (UTC) (edited on 2020-11-18 23:10 (UTC) by Kr1ss)
@ElijahLynn basically the package in [community] provides you the fully free and open source edition, while this one here is the Oracle branded one, containing some proprietary extensions. (See §1 in the licensing FAQ)
ElijahLynn commented on 2020-11-18 22:58 (UTC)
What is the difference between virtualbox-bin AUR and https://www.archlinux.org/packages/community/x86_64/virtualbox/?
drankinatty commented on 2020-10-21 07:48 (UTC)
Yes, thank you, after discussing on the vbox-users list, it was the binary.iso that contains the files that needed patching and there isn't any way for you to do that. Sorry for the noise -- also 6.1.16 is out and works fine with Linux 5.9.1 -- all you need to do is update the build no., drop the patch, set release to 1 and regen the checksums. (I hate kernel version updates....)
dbermond commented on 2020-10-19 03:22 (UTC)
@drankinatty I have an impression that you did not read my previous comment. I'll repeat it one more time: there is no guest additions source to patch here because this is a -bin (pre-compiled) package. There is only dkms sources to patch on this package. And there is nothing being patched on '/tmp' here.
drankinatty commented on 2020-10-19 02:37 (UTC) (edited on 2020-10-19 02:37 (UTC) by drankinatty)
If you are just repackaging what is built in virtualbox-bin-guest-iso-6.1.14-3-any.pkg.tar.zst that is provided as part of this package, then it's Oracle's issue. The problem is -- while you patch /tmp/vbox.0/r0drv/linux/the-linux-kernel.h to build this package -- the src files installed from virtualbox-bin-guest-iso-6.1.14-3-any.pkg.tar.zst to the guest when you install the guest-additions are not patched. So is there away to patch the same files you patch to build the host modules (with the same patch) so they are packaged in the virtualbox-bin-guest-iso-6.1.14-3 built by this package so that guest-additions build?
dbermond commented on 2020-10-18 13:31 (UTC)
@drankinatty What are you talking about? This is a -bin package and the guest additions are not built from sources. There is no guest additions source to patch here and the package does not install a directory named '/opt/VBoxGuestAdditions-6.1.14/'.
drankinatty commented on 2020-10-18 10:26 (UTC)
Linux 5.9-1 guest-additions build fails so it looks like applying the same patch is needed by the guest-additions package. Error from vboxadd-setup.log
In file included from /tmp/vbox.0/VBoxGuest-linux.c:36:
/tmp/vbox.0/r0drv/linux/the-linux-kernel.h:141:11: fatal error: linux/smp_lock.h: No such file or directory
141 | # include <linux/smp_lock.h>
| ^~~~~~~~~~~~~~~~~~
compilation terminated.
The 021-kernel-5.9.patch looks like it should have addressed this, maybe this can be adapted to the guest-additions package produced during the build?
The crux is this, the src file installed on the host in /usr/src/vboxhost-6.1.14_non_OSE/ are patched for 5.9.1, the files that get installed on the guest to /opt/VBoxGuestAdditions-6.1.14/src/vboxgues-6.1.14/ are not (they are still dated Sept. 4, 2020). So guest additions fail to build on Arch guests.
dbermond commented on 2020-09-05 14:52 (UTC)
@Kr1ss Thanks for pointing this. Fixed.
firewalker commented on 2020-08-17 09:02 (UTC)
Unfortunately in my case the versions that works causes kernel panics.
firewalker commented on 2020-08-17 08:37 (UTC)
dbermond commented on 2020-08-14 13:06 (UTC)
@nursoda At the time of this writing, VirtualBox 6.1.13 is not yet released by upstream. Not even the repository package is updated to 6.1.13.
nursoda commented on 2020-08-14 13:01 (UTC)
For the time being, could you please update to 6.1.13 – virtualbox-ext-oracle is updated already and breaks virtualbox-bin due to 12 vs 13 version mismatch. I know that I can downgrade that but … I try to stay up-to-date on all packages ;) Anyway: Does 6.1.13 solve the Kernel 5.8 issue?
dbermond commented on 2020-08-12 20:25 (UTC)
Upgrading linux to 5.8 will break virtualbox-bin 6.1.12.
I've prepared a patch for linux 5.8 (based on the repository package) but apparently it modifies the modules version, since it causes a 'module version mismatch' error when running a virtual machine.
So a patch for the dkms sources will not be sufficient. We need an update from upstream supporting linux 5.8. Based on the release history, it should not take too much long.
Ralf_Mardorf commented on 2020-07-17 03:59 (UTC)
Update: VirtualBox Ticket #19719
Ralf_Mardorf commented on 2020-07-17 03:08 (UTC)
Hi, after installing 6.1.12-1 + extension pack a Windows 10 guest can be used with the new guest additions, but a Windows 7 guest doesn't boot anymore, after installing the guest additions. Starting Windows 7 in safe mode works, but doesn't find a solution. I restored Windows 7 from a snapshot and tried again. The Windows 7 guest failed to boot again after installing the guest additions. Does anybody experience the same issue?
dbermond commented on 2020-04-21 23:26 (UTC)
@joerg-krause AUR helpers are not supported. Please use makepkg.
No malicious code on this PKGBUILD, it's just extracting the main source file.
joerg-krause commented on 2020-04-16 06:30 (UTC)
The Aura package manager fails to build this package to avoid potentially malicious code:
sudo aura -Ax virtualbox-bin
aura >>= Determining dependencies...
aura >>= WARNING: The PKGBUILD of `virtualbox-bin` contains blacklisted bash expressions.
sh "VirtualBox-${pkgver}-${_build}-Linux_amd64.run" --target "${pkgname}-${pkgver}" --nox11 --noexec
aura >>= `sh` can be used to execute arbitrary code not tracked by this PKGBUILD.
aura >>= Do you wish to quit the build process? [Y/n]
aura >>= Cancelled further processing to avoid potentially malicious bash code.
Ralf_Mardorf commented on 2020-04-06 11:12 (UTC) (edited on 2020-04-06 11:12 (UTC) by Ralf_Mardorf)
Romario74, see the "Update" added to my original comment. I noticed that the extension pack needed to be reinstalled already before you replied. However, there's still an issue displayed for one guest's settings, even while the guest seems to be usable. After doing some further testing virtualbox-bin 6.1.4-2 seems not to work when booted to the real-time patched kernel 5.6.2, it seems to work when booted to the real-time patched kernel 4.19.106. "Seems", since I only made short tests and those failed when booted to the kernel 5.6.2, but worked when booted to the kernel 4.19.106. Now I'll try to backup two tablets with the Windows 7 and with the Windows 10 guest, while booted into 5.6.2-arch1-2 with "threadirqs". Until now the Windows 7 guest works. If I don't report anything else within the next hours, it continued to work without failure and the Windows 10 guest worked, too.
Romario74 commented on 2020-04-05 20:37 (UTC)
You have to reinstall the extension pack. This is what gives you USB support for your VMs. No need to restore from backup. And thanks for the virtualbox update, works fine with kernel 5.6.
Ralf_Mardorf commented on 2020-04-05 18:18 (UTC) (edited on 2020-04-05 20:17 (UTC) by Ralf_Mardorf)
A self-build real-time patched kernel 5.6.2-rt1 as well as 5.6.2-arch1-2 from Testing, with virtualbox-bin 6.1.4-2, trying to start a Windows 10 or Windows 7 guest fails with "Implementation of the USB 2.0 controller not found!" The same happens for a self-build real-time patched 4.19.106-rt46. After downgrading to virtualbox-bin 6.1.4-1, the self-build real-time patched kernel 4.19.106-rt46, that could be used before the upgrade to virtualbox-bin 6.1.4-2, still results in the same error. Even while I'm loading and unloading the modules on demand, I restarted the machine to no avail. FWIW all modules were build. The vbox and vbox-prev files do only contain different timestamps, anything else doesn't differ. The snapshots were not touched at all. Since it worked a few hours before I upgraded virtualbox-bin, nothing else was upgraded, I'll restore the guests from backups or what ever else might be broken.
Update: There was no need to restore from a backup, I just needed to reinstall the extension pack, so perhaps it even works with kernel 5.6. I can't test it now. Both Windows guests can be used again, but an invalid setting for the Windows 7 guest is detected, it's just not mentioned what setting.
dbermond commented on 2020-04-05 16:46 (UTC)
@Romario74 I've added a patch for linux 5.6.
Romario74 commented on 2020-03-31 14:41 (UTC)
dkms modules do not build with kernel 5.6
Ralf_Mardorf commented on 2019-07-28 16:29 (UTC)
It isn't solved. I've run out of ideas.
Ralf_Mardorf commented on 2019-07-28 14:14 (UTC) (edited on 2019-07-28 14:14 (UTC) by Ralf_Mardorf)
Ralf_Mardorf commented on 2019-07-27 17:50 (UTC) (edited on 2019-07-27 17:51 (UTC) by Ralf_Mardorf)
Hi, a Windows 7 guest quite suddenly can't access a shared folder anymore. If I open the shared folder, I get a BlueScreen and Windows 7 immediately crashes and restarts, see aur-general. In the meantime I tested 3 different kernels and restored Windows 7 from a snapshot, as well as Windows 7 and ~/.VirtualBox/ from a backup. Windows doesn't provide useful information, but the VirtualBox logs mention "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE", which seems to lead to a vboxdrv.rules issue. However, even after getting rid of the "Failed to open "/dev/vboxdrvu", errno=13, rc=VERR_VM_DRIVER_NOT_ACCESSIBLE" message, by using vboxdrv.rules from the community package, the Windows guest still crashes, see aur-general.
shillshocked commented on 2019-06-06 23:01 (UTC)
No sound or internet with Virtualbox 6 (at least with ALSA and NAT AFAIK)
peschu commented on 2019-04-19 17:02 (UTC)
@dbermond Muchas Gracias! Already building it :-)
dbermond commented on 2019-04-19 15:21 (UTC)
@peschu package updated.
peschu commented on 2019-04-18 22:15 (UTC)
will there be an update to 6.0.6? my extensions already upgraded to 6.0.6 :-/
shillshocked commented on 2019-04-08 07:17 (UTC)
Latest Virtualbox doesn't play ALSA audio with Windows 8.1 Guest. This seems like a regression, downgrading to 5.0.40 seems to be the only solution.
drankinatty commented on 2019-01-16 01:42 (UTC) (edited on 2019-01-16 01:43 (UTC) by drankinatty)
Note: 6.0.0 VirtualBox (the console) would coredump when accessed via ssh -X and Win7 guests run --headless and accessed via rdesktop were unusable. Oracle released 5.2.24 today and building and downgrading resolved all problems. (5.2 branch will be supported through 2020) Also released today was 6.0.2 (I have not tried it yet). This problem was worked on the vbox-users mailing list, but no bug filed as of yet.
Ralf_Mardorf commented on 2018-12-31 15:08 (UTC) (edited on 2018-12-31 15:09 (UTC) by Ralf_Mardorf)
Your decision makes sense, but it breaks my workflow. Fortunately I even don't need to use NoExtract of pacman.conf, since /usr/local/bin is head of PATH.
$ ls -hAl /usr/bin/virtualbox*
lrwxrwxrwx 1 root root 31 Dec 31 15:46 /usr/bin/virtualbox -> ../../opt/VirtualBox/VirtualBox
lrwxrwxrwx 1 root root 33 Dec 31 15:46 /usr/bin/virtualboxvm -> ../../opt/VirtualBox/VirtualBoxVM
$ echo $PATH | cut -d: -f1
/usr/local/bin
$ ls -hAl /usr/local/bin/virtualbox
lrwxrwxrwx 1 root root 28 Dec 30 05:15 /usr/local/bin/virtualbox -> /opt/VirtualBox/VirtualBoxVM
Guten Rutsch!
Ralf
dbermond commented on 2018-12-31 11:40 (UTC)
@Ralf_Mardorf I accidentally removed a line that broke this. Now fixed.
Ralf_Mardorf commented on 2018-12-30 03:58 (UTC) (edited on 2018-12-30 04:18 (UTC) by Ralf_Mardorf)
Hi,
neither a soft link, nor the PATH variable provide to run the new command, providing the old options such as "--startvm", without using the complete path to the command.
It was like this
$ pacman -Q virtualbox-bin
virtualbox-bin 5.2.22-1
$ pacman -Ql | grep /bin/virtualbox
virtualbox-bin /usr/bin/virtualbox
$ ls -hl /usr/bin/virtualbox
lrwxrwxrwx 1 root root 26 Nov 11 18:25 /usr/bin/virtualbox -> /opt/VirtualBox/VirtualBox
$ /usr/bin/virtualbox --help | grep -e --startvm
--startvm <vmname|UUID> start a VM by specifying its UUID or name
and changed to
$ pacman -Q virtualbox-bin
virtualbox-bin 6.0.0-1
$ ls -hl /usr/bin/virtualbox
ls: cannot access '/usr/bin/virtualbox': No such file or directory
$ /usr/bin/VirtualBox --help | grep startvm
If you are looking for --startvm and related options, you need to use VirtualBoxVM.
$ pacman -Ql virtualbox-bin | grep VirtualBoxVM -m1
virtualbox-bin /opt/VirtualBox/VirtualBoxVM
$ grep Exec /opt/VirtualBox/virtualbox.desktop -m1
Exec=VirtualBox %U
$ grep Exec /usr/share/applications/virtualbox.desktop -m1
Exec=VirtualBox %U
Since the desktop files were always using VirtualBox and people writing scripts usually avoid CamelCase, it makes sense to add a new link /usr/bin/virtualbox against /opt/VirtualBox/VirtualBoxVM. Too funny, my several years old script already separated VirtualBox from virtualbox. Don't ask me why I added the %U to the script, looks like a copy and paste error from a desktop file :D.
$ ls -hAl /usr/local/bin/vbox
-rwxr-xr-x 1 root root 157 Jul 17 2014 /usr/local/bin/vbox
$ grep case -A3 /usr/local/bin/vbox
case $* in
"") VirtualBox %U ;;
*) virtualbox --startvm "$*" ;;
esac
However, even if you don't want to add a /usr/bin/virtualbox link, at least add a link /usr/bin/VirtualBoxVM against /opt/VirtualBox/VirtualBoxVM, as it is done for VirtualBox:
$ pacman -Ql virtualbox-bin | grep /usr/bin/VirtualBox
virtualbox-bin /usr/bin/VirtualBox
$ ls -hAl /usr/bin/VirtualBox
lrwxrwxrwx 1 root root 31 Dec 30 01:34 /usr/bin/VirtualBox -> ../../opt/VirtualBox/VirtualBox
Guten Rutsch!
Ralf
Ralf_Mardorf commented on 2018-11-12 19:27 (UTC)
While I agree that if an AUR helper should fail, the user has to try to build it without a helper, before adding a comment, we shouldn't spread myths regarding yaourt. A lot of users are satisfied by yaourt, there are not many use cases when yaourt could fail. Actually, I build 5.2.22-1 using yaourt 1.9-1 without any issue at all. IIUC the OP was able to build and install virtualbox. If the OP wants to learn what was going wrong regarding the permissions, I recommend to repeat everything and post the used commands and their complete output to an Arch forum, assuming googling shouldn't already enlighten the OP.
Kr1ss commented on 2018-11-12 13:52 (UTC)
I'd recommend not to use yaourt in the first place. It's proven to be unsafe, is deprecated and no longer actively maintained.
If u really must use an AUR helper, I'd suggest taking a look at the Arch Wiki page before choosing one.
Even better would probably be to simply use Arch's default tooling, i.e. makepkg
, or but maybe that's more of a personal preference.
dschaefer79 commented on 2018-11-12 08:18 (UTC)
I have installed virtualbox-bin 5.22 but at the end of install. I have this error /usr/lib/yaourt/aur.sh: line 211: cd: /root: Permission denied
Can anyone help me ?
Thanks,
Kr1ss commented on 2018-10-31 00:19 (UTC) (edited on 2018-10-31 00:20 (UTC) by Kr1ss)
Yep, SDK is now included in the package.
drankinatty commented on 2018-10-31 00:13 (UTC)
Yikes, whatever changes were made to accommodate the SDK or in the 5.2.20 release has ballooned the package size by 31.74 MiB. Is that expected? I haven't seen that big of a jump in vbox package size in years.
dbermond commented on 2018-10-12 20:17 (UTC)
@Kr1ss Thank you for reporting this. Fixed.
Kr1ss commented on 2018-10-12 13:08 (UTC) (edited on 2018-10-12 23:48 (UTC) by Kr1ss)
There seems to be a conflict w/ the virtualbox-sdk
package from community
@dbermond (b/c of usr/lib/python3.7/site-packages/vboxapi*
).
Would u pls consider adding that to the PKGBUILD ?
Thx a lot for the package, btw !
EDIT : Thank you for fixing this so quickly !
dbermond commented on 2018-07-24 23:59 (UTC)
@GeneArch Please do not report problems when using a modified PKGBUILD.
I don't know if this will be a problem in future upstream stable releases.
GeneArch commented on 2018-07-24 13:11 (UTC)
with the older 5.2.16 everything works fine.
So its the development snapshots this is happening with. Do you know if this will be a problem when those migrate to released builds?
thanks
GeneArch commented on 2018-07-24 13:00 (UTC)
Sorry, this happens with the development snapshots:
https://www.virtualbox.org/wiki/Testbuilds
pkgver=5.2.97 _build=123594
which i built by obvious tweaks to your PKGBUILD.
I need to go back and test 5.2.16.
dbermond commented on 2018-07-24 03:27 (UTC)
@GeneArch I cannot reproduce your issue. VirtualBox is loading fine for me and everything is working as expected. Tested with Plasma and LXQt.
You said Plasma 5.11.1 but I think that you mean Qt 5.11.1, because Plasma is currently at 5.13.3.
Here is a link to a possibly related problem: https://www.virtualbox.org/pipermail/vbox-dev/2018-July/015046.html.
Please share your solution if you find something.
GeneArch commented on 2018-07-24 01:56 (UTC) (edited on 2018-07-24 02:04 (UTC) by GeneArch)
Running on plasma 5.11.1 i get problems with this package running setuid. Error on attempting to run Virtualbox gives:
Qt FATAL: FATAL: The application binary appears to be running setuid, this is a security hole. Aborted
Removing the setuid - app now starts but then complains it needs to be setuid root.
Thoughts on how to fix?
Thanks
gene
drankinatty commented on 2018-07-07 07:13 (UTC) (edited on 2018-07-07 07:14 (UTC) by drankinatty)
Only change from 5.2.12 to 5.2.14 are:
pkgver=5.2.14
_build=123301
sha256sums=('2ea513dadaab9b32df6c18827ebfe98524e297d2b44678ce1518a3486d8b3e73'
'0aebe22abab402ea6b6573af637a99d8056a904920a52d84fb97729219219c23'
'69417a9e8855cab8e4878886abe138f559fd17ae487d4cd19c8a24974a8bbec2'
'656905de981ffa24f6f921c920538854a235225053f44baedacc07b46ca0cf56'
'12dbba3b59991f2b68cddeeeda20236aeff63e11b7e2d1b08d9d6a82225f6651'
'cc1c0500ab07bc13563d99037f776bf64bdc90bb521e31e2e0b04e42ea5bb36a'
'e9df0fff15184d0a90abe17707bdbe1931582433bbc14ded4fb3b0252653c801'
'5112f0e1ba3bd0bd92ef2edb2d21024e265abb02841aa29aa05410526adc273f')
gary9872 commented on 2018-06-02 17:22 (UTC)
I don't have much use for this. If anyone needs help adopting this, let me know
drankinatty commented on 2017-12-27 11:01 (UTC) (edited on 2017-12-27 11:02 (UTC) by drankinatty)
The only changes to PKGBUILD between 5.2.2 and 5.2.4 are:
pkgver=5.2.4
_build=119785
md5sums=('70973209cc9bc0e82e40a34362061f96'
'2d04c2e2d8c71558c910a51ec773731a'
'fe60f9510502bea67383d9198ae8c13c'
'c159d683ba1947290fc2ad2c64194150'
'3ac185709bfe688bb753c46e170d0546'
'31144fa409c0d7c6b464d44b2140b521'
'05175249e1206c491b2b36670e8db9ec'
'c32a61f3a1611e184098cc9b0d6765bb')
All diff/patch hunks succeed, but several will be off by 1 - 8 bytes of context. So for future updates, I suspect new diffs will need to be taken. For now, the changes above have 5.2.4 happily installed and running with the extension-pack just as they always have.
drankinatty commented on 2017-12-06 15:05 (UTC)
If it helps, the update PKGBUILD update required for 5.2.2 is simply:
pkgver=5.2.2 _build=119230
Works fine -- even loads the modules after install (unlike 5.2.0 -- but still messes with the setvideomodehint for current vms) Smoother than 5.2.0. It's a keeper. (not to mention the forced move to 5.2.X due to the 4.14 kernel update)
Ralf_Mardorf commented on 2017-12-05 06:02 (UTC)
Linux 4.14.3-1 is provided by "Core". Trying to build the modules still results in the same errors. "Linux hosts: fixed kernel module compilation and start failures with Linux kernel 4.14 (bug #17267)" - https://www.virtualbox.org/wiki/Changelog
Pinned Comments