From owner-freebsd-ports@FreeBSD.ORG Fri Oct 22 21:37:03 2010 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B0A761065670 for ; Fri, 22 Oct 2010 21:37:03 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from groupware.itac.at (groupware.itac.at [91.205.172.99]) by mx1.freebsd.org (Postfix) with ESMTP id 4A0FE8FC0C for ; Fri, 22 Oct 2010 21:37:03 +0000 (UTC) Received: from home.bluelife.at (91.205.172.21) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 0168BB; Fri, 22 Oct 2010 23:21:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Fri, 22 Oct 2010 21:21:56 +0000 From: Bernhard Froehlich To: Ade Lovett In-Reply-To: References: Message-ID: <1dad91bb50fce77a99073c0f3ece5818@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.4.2 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0201.4CC20073.017F,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: FreeBSD Ports , vbox@FreeBSD.org Subject: Re: Virtualbox UI and remote X clients X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Oct 2010 21:37:03 -0000 On Fri, 22 Oct 2010 15:02:20 -0500, Ade Lovett wrote: > Folks, > > It would appear that ever since 3.2.8_1 of virtualbox-ose, a number > of additions were made to unconditionally enable some kind of hardware > acceleration in the UI. > > This completely breaks the UI with a variety of QT errors, when > running on a remote X11 displays, so far I've tested X11.app and > XQuartz.app on OSX, cygwin/X on Windows 7/XP, and even an Xvnc server > running on a FreeBSD/amd64 box. Could you please post that errors? 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. Do you probably have nvidia graphics or anything special? Maybe the bug you are hitting was already fixed upstream so could you test the virtualbox-ose-devel port [1] and see if the problem persists? Sure we could make an option for that patch or revert it but that won't fix the underlying problem that it uncovered. So I would really like to get it at least analyzed first and if it cannot get fixed we can always disable it. [1] http://svn.bluelife.at/nightlies/virtualbox-port.tar.gz -- Bernhard Fröhlich http://www.bluelife.at/