Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Oct 2010 19:18:33 -0500
From:      Adam Vande More <amvandemore@gmail.com>
To:        Ade Lovett <ade@freebsd.org>
Cc:        FreeBSD Ports <ports@freebsd.org>, Bernhard Froehlich <decke@bluelife.at>, vbox@freebsd.org
Subject:   Re: Virtualbox UI and remote X clients
Message-ID:  <AANLkTinJobKRdVS_VbPdLOkMF38P_63cH9JhEsmt3KB7@mail.gmail.com>
In-Reply-To: <1DBB2A85-B3F8-4F90-9DC1-D4BEEFAFD94E@FreeBSD.org>
References:  <A02E5D3C-FBE1-44F6-9806-E2AFCAC9B221@FreeBSD.org> <1dad91bb50fce77a99073c0f3ece5818@bluelife.at> <1DBB2A85-B3F8-4F90-9DC1-D4BEEFAFD94E@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 22, 2010 at 5:04 PM, Ade Lovett <ade@freebsd.org> wrote:

>
> On Oct 22, 2010, at 16:21 , Bernhard Froehlich wrote:
> > Could you please post that errors?
>
> freebsd% setenv DISPLAY remote:0
> freebsd% VirtualBox
>
> Wait for UI to pop up, click on 'Settings' for any virtual host, VirtualBox
> crashes with:
>
> Qt WARNING: QGLContext::makeCurrent(): Cannot make invalid context current.
> Segmentation fault
>
>
> (remote) in this case has been (so far):
>
> MacOSX 10.6 with Apple's X11.app
> MacOSX 10.6 with XQuartz.app
> Windows XP with cygwin/X
> Windows 7 with cygwin/X
> Xvnc on the FreeBSD box, then using either the Mac or Windows box to fire
> up a vnc client to get to the Xvnc.
>
>
> > It sounds like an upstream bug so it
> > would be good to collect a few details like why it happens on your
> > system bug I cannot reproduce it here with Intel graphics.
>
> Please re-read what I said.  The host machine (running the virtualboxes)
> has NO graphics of any kind.  It's FreeBSD 8.1-STABLE/amd64 hooked up to a
> VT320 terminal as a serial console.  It has X11 libraries and the various
> toolkits (QT etc) installed, but no Xorg server (other than Xvnc), no X11
> drivers (graphics/keyboard/mouse).
>
> 3.2.8 was fine
> 3.2.8_1 broke things
> 3.2.10 (unsurprisingly) hasn't changed
>

I can confirm this issue, I reported it on the emulation mailing list a few
days ago.  Thanks for finding the exact breakage point.
-- 
Adam Vande More



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTinJobKRdVS_VbPdLOkMF38P_63cH9JhEsmt3KB7>