Package Base Details: virtualbox-bin

Git Clone URL: (read-only, click to copy)
Keywords: machine oracle virtualization vm
Submitter: Rainmaker
Maintainer: dbermond
Last Packager: dbermond
Votes: 58
Popularity: 1.30
First Submitted: 2015-08-18 09:16
Last Updated: 2021-04-30 10:55

Latest Comments

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

Kr1ss commented on 2018-10-12 13:08

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

@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

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?


GeneArch commented on 2018-07-24 13:00

Sorry, this happens with the development snapshots:

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:

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?



drankinatty commented on 2018-07-07 07:13

Only change from 5.2.12 to 5.2.14 are:



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:



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)