From owner-freebsd-emulation@FreeBSD.ORG Mon Apr 11 08:41:42 2011 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A6ACA106564A for ; Mon, 11 Apr 2011 08:41:42 +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 43FAF8FC08 for ; Mon, 11 Apr 2011 08:41:42 +0000 (UTC) Received: from home.bluelife.at (93.104.210.95) by groupware.itac.at (Axigen) with (AES256-SHA encrypted) ESMTPSA id 08150D; Mon, 11 Apr 2011 10:41:48 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: Mon, 11 Apr 2011 10:41:41 +0200 From: Bernhard Froehlich To: Tobias Oberstein In-Reply-To: <634914A010D0B943A035D226786325D422B7561FFC@EXVMBX020-12.exch020.serverdata.net> References: <634914A010D0B943A035D226786325D422B64120E5@EXVMBX020-12.exch020.serverdata.net> <977389f91bc1fbdb0c9a85db243e210c@bluelife.at> <634914A010D0B943A035D226786325D422B7561FFC@EXVMBX020-12.exch020.serverdata.net> Message-ID: <7a647eab76b73fd68df8153eaaf9104a@bluelife.at> X-Sender: decke@bluelife.at User-Agent: Roundcube Webmail/0.5.1 X-AxigenSpam-Level: 1 X-CTCH-RefID: str=0001.0A0B0204.4DA2BEC5.009F,ss=1,fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown Cc: freebsd-emulation@freebsd.org Subject: Re: AW: VBox 4.0.4 testing : keyboard layout issue X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 08:41:42 -0000 On Sat, 9 Apr 2011 06:10:46 -0700, Tobias Oberstein wrote: > Hello Bernhard, > >> No it should just work but I admit that i haven't tested it for quite a few >> months. Does it work fine in virtualbox 3.2.x ? Probably it's some upstream > > I did not test it with 3.x, because we need 4.x .. > >> bug because they changed quite a lot in that area and it's contributed code. >> > > ok. I see. > > Would you have time / be willing to accept a small sponsorship to fix > the issue - regardless if it's upstream or a port issue? If so, send > me a private mail .. would be cool;) Sorry that won't help here at the moment. It would be better to find out if it is a client issue or a client configuration issue. If you are sure that you can reproduce the problem with different clients we can go on checking if it is a 4.0 regression or FreeBSD specific. It is a bit complicated to create a bugreport without that information and if it is FreeBSD specific we cannot create a bugreport at all so we need to find out first. -- Bernhard Fröhlich http://www.bluelife.at/