ports/186804: www/virtualbox-ose with VNC enabled crashes if Remote Display is turned on after the VM starts
Derek Schrock
dereks at lifeofadishwasher.com
Sun Feb 16 01:10:00 UTC 2014
>Number: 186804
>Category: ports
>Synopsis: www/virtualbox-ose with VNC enabled crashes if Remote Display is turned on after the VM starts
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Feb 16 01:10:00 UTC 2014
>Closed-Date:
>Last-Modified:
>Originator: Derek Schrock
>Release: 10.0-RELEASE
>Organization:
>Environment:
FreeBSD ircbsd 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root at snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
>Description:
If you enable Remote Display after a VM starts and connect via VNC to host:port (default port 5900) the running VM will crash.
>How-To-Repeat:
1) Install www/virtualbox-ose with VNC support.
2) Create a new VM with out Remote Display enabled
3) Make sure Remote Dispaly is disabled
(within the VM settings: Display, Remote Display tab, uncheck Enable Server)
3) Start the VM without Remote Display enabled
4) Turn on Remote Display (see above - check Enable Server)
5) Connect to the VirtualBox host via the port VNC is running on
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list