Summary: | app-emulation/virtualbox-bin tries to load libraries from wrong location | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex <barracuda72> |
Component: | Current packages | Assignee: | masterzorag <masterzorag> |
Status: | RESOLVED UPSTREAM | ||
Severity: | trivial | CC: | proxy-maint |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Strace of VBoxManage |
as seen in you attachment (since my 5.1.8 seems works fine) https://github.com/gentoo/gentoo/pull/2695 (In reply to masterzorag from comment #1) > as seen in you attachment (since my 5.1.8 seems works fine) > > https://github.com/gentoo/gentoo/pull/2695 I can confirm that 5.1.8 works fime for me too. Closed, I guess. |
Created attachment 451338 [details] Strace of VBoxManage As of =app-emulation/virtualbox-bin-5.1.6.110634, VirtualBox binaries tries to load XPCOM library from /usr/lib64/virtualbox despite being installed to /opt/VirtualBox. In /etc/vbox/vbox.cfg INSTALL_DIR is set to "INSTALL_DIR=/opt/VirtualBox", but generated file ~/.VirtualBox/xpti.dat contains line "1,AppDir,/usr/lib64/virtualbox". Even if I change that, file got regenerated at each VBox* programs start, and even if I forbid writing to this file the VBox* binaries still trying to load library from /usr/lib64/virtualbox. Strace of "VBoxManage showvminfo" attached. The possible easiest solution to this is to create symlink "/usr/lib64/virtualbox -> /opt/VirtualBox". I think ebuild should do that.