Summary: | app-emulation/virtualbox-4.1.18-r1 - VM crash then connecting via vnc (libvncserver) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Wadlax <wadlax> |
Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | patrick, swapon |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Wadlax
2012-08-17 11:10:17 UTC
Hmm... virtualbox-4.1.18-r1 is already using the patch from that arch linux bug report (see bug #425698 for reference). If that patch really is not fixing the issue I suppose I gotta remove virtualbox-4.1.18-r1 from the tree and wait for the release of virtualbox-4.2.0 before we can use libvncserver-0.9.9 again. I have no ipv6 support net-libs/libvncserver (24bpp jpeg threads zlib -gcrypt -gnutls -ipv6 -test) virtualbox-4.1.18-ipv6_vnc.patch contains : """"" +#ifdef LIBVNCSERVER_IPv6 + if (mVncPort) { + vncServer->port = mVncPort; + vncServer->ipv6port = mVncPort; + } +#else if (mVncPort) vncServer->port = mVncPort; +#endif + """"" So - i think this patch does absolutely nothing in the case you use only ip4 . It may be better to alter virtualbox-4.1.18-r1 (r2) to depend on <net-libs/libvncserver-0.9.9 Anyways , now i'm using stable virtualbox-4.1.18 and stable libvncserver-0.9.8.2-r2 +*virtualbox-4.1.20 (21 Aug 2012) + + 21 Aug 2012; Lars Wendler <polynomial-c@gentoo.org> virtualbox-4.1.12.ebuild, + -virtualbox-4.1.16.ebuild, virtualbox-4.1.18.ebuild, + -virtualbox-4.1.18-r1.ebuild, -files/virtualbox-4.1.18-ipv6_vnc.patch, + +virtualbox-4.1.20.ebuild: + Version bump. Removed old. Pin libvncserver down to versions lower than 0.9.9 + to prevent crashes in virtualbox (bug #431728). + |