Date: Wed, 24 Oct 2018 18:51:34 +0200 From: Florian Smeets <flo@smeets.xyz> To: Alexander Zagrebin <alex@zagrebin.ru>, freebsd-ports@freebsd.org Cc: Jung-uk Kim <jkim@FreeBSD.org> Subject: Re: [jkim@FreeBSD.org: svn commit: r482272 - in head/emulators: virtualbox-ose virtualbox-ose-additions virtualbox-ose-additions-nox11 virtualbox-ose-kmod virtualbox-ose-nox11 virtualbox-ose/files] Message-ID: <88e3f83a-d247-a0e4-fb9a-bfefef0e72a1@smeets.xyz> In-Reply-To: <20181020232228.40845b45@vm2.home.zagrebin.ru> References: <20181018075031.GA5833@mail.smeets.xyz> <20181020232228.40845b45@vm2.home.zagrebin.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --S4EnJ7dEOi0pmilluQ7aa7GR4pn6OWNup Content-Type: multipart/mixed; boundary="ewFZvd9MQsBo1PKmD4x9il7iDVpD9ETVh"; protected-headers="v1" From: Florian Smeets <flo@smeets.xyz> To: Alexander Zagrebin <alex@zagrebin.ru>, freebsd-ports@freebsd.org Cc: Jung-uk Kim <jkim@FreeBSD.org> Message-ID: <88e3f83a-d247-a0e4-fb9a-bfefef0e72a1@smeets.xyz> Subject: Re: [jkim@FreeBSD.org: svn commit: r482272 - in head/emulators: virtualbox-ose virtualbox-ose-additions virtualbox-ose-additions-nox11 virtualbox-ose-kmod virtualbox-ose-nox11 virtualbox-ose/files] References: <20181018075031.GA5833@mail.smeets.xyz> <20181020232228.40845b45@vm2.home.zagrebin.ru> In-Reply-To: <20181020232228.40845b45@vm2.home.zagrebin.ru> --ewFZvd9MQsBo1PKmD4x9il7iDVpD9ETVh Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 20.10.18 22:22, Alexander Zagrebin wrote: > =D0=92 Thu, 18 Oct 2018 09:50:31 +0200 > Florian Smeets via freebsd-ports <freebsd-ports@freebsd.org> =D0=BF=D0=B8= =D1=88=D0=B5=D1=82: >=20 >> does 5.2.20 break VNC remote console to VBoxHeadless VMs for anyone >> else? I can still connect to the console with VNC but all I get is a >> black screen. Going back to 5.2.18 restores VNC functionality. >=20 > I can confirm that.=20 >=20 > Also I have to notice, that while there is an active VNC connection to > the some machine, the second connection to the same machine crashes > a VirtualBox process (this applies to all versions). >=20 So, I'm not alone, good to know ;) I found out some more. It appears that the only problem is, that we don't "see" anything. I can blindly type stuff via VNC and when I log in via SSH and check the log I see authentication errors that are caused by typing stuff into the black VNC session. Linux seems to be affected to, there is a bug report without a lot of information https://www.virtualbox.org/ticket/18072 Florian --ewFZvd9MQsBo1PKmD4x9il7iDVpD9ETVh-- --S4EnJ7dEOi0pmilluQ7aa7GR4pn6OWNup Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEE7LNouHkIv7aRTXJp71uk3NWp88AFAlvQoxZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEVD QjM2OEI4NzkwOEJGQjY5MTRENzI2OUVGNUJBNERDRDVBOUYzQzAACgkQ71uk3NWp 88AbVhAAuC87deqZ4lnIDDq/a8zb0FfJEnxqOr7JmGfalPWCM6834NDSQjOfp8E2 qCHDuo+EASGkILyAJ8TuPds9MeW85qOAD2Zr8OSFOgVGCE/ktcxxnA+MykyRePdH BTICfjvuM62TTTkLI0Fp1W9KG8h15EkhULZbt5o3l7RASRo3WH7+b+HOCA66MSqC zZXePKWbrN57zvFs4YYUfr9f0lYDZO1qlBdCdOo/hAjyg1u06WvauohuCAu3K218 whmVbZ22y8B9CIXBWJORKk+L2wYH25m6ZyJlXYKV19ffmoOFVGDy11IItsg5pZkF p2bT0CfbmP3bR9IEWBuZnIFX/Z/kwx7p8B6ERhM3jUSfcrgXsu22lVKW6sGNTPkC HC/qra/gEDc9z6h0vFFBARX+Uph128V9MT5MtAD7He5RLDM9R+Acbqv1Mob2e/2T z+IZr8wCIb5Sx2ZX68MjE32/611CfqmuncAjgJ8zW+eU+fUeDPM6RMIiHwvcRUDz bETOISXfEU/XJddtxvHztdSsWHalJGktHhNWPLPUQfH8B6WUXVxcdALs3Bs8scLC zlG7YhTZxu9KTZnEjUBA2+ezE06j4MjyuEj96Phuu+qSXYHGUiJnu2SUpn/e+wZJ qnEwdF3n41+DiMTsVZeXl1B0t8XI1STXGrAXLcFNBbnno2MCoPs= =9fs6 -----END PGP SIGNATURE----- --S4EnJ7dEOi0pmilluQ7aa7GR4pn6OWNup--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?88e3f83a-d247-a0e4-fb9a-bfefef0e72a1>