Package Details: virtualbox-bin 6.0.14-2

Git Clone URL: https://aur.archlinux.org/virtualbox-bin.git (read-only)
Package Base: virtualbox-bin
Description: Oracle VM VirtualBox Binary Edition (Oracle branded non-OSE version)
Upstream URL: https://www.virtualbox.org/
Keywords: machine oracle virtualization vm
Licenses: GPL2
Conflicts: virtualbox, virtualbox-host-dkms, virtualbox-host-modules-arch, virtualbox-sdk
Provides: VIRTUALBOX-HOST-MODULES, virtualbox=6.0.14, virtualbox-guest-iso, virtualbox-host-dkms, virtualbox-sdk
Replaces: virtualbox-sun, virtualbox_bin
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 51
Popularity: 0.88
First Submitted: 2015-08-18 09:16
Last Updated: 2019-12-03 01:33

Dependencies (14)

Required by (50)

Sources (13)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

GeneArch commented on 2018-07-24 13:11

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

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

@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

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

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

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

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

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

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

gary9872 commented on 2017-11-22 00:06

Ralf

I don't use the testing repos.

If someone does and would like to submit a patch, I'd be happy to add it.