From owner-freebsd-questions@FreeBSD.ORG Mon Oct 29 22:15:16 2007 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CF4916A46C for ; Mon, 29 Oct 2007 22:15:16 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.176]) by mx1.freebsd.org (Postfix) with ESMTP id 0AB7713C4C8 for ; Mon, 29 Oct 2007 22:15:15 +0000 (UTC) (envelope-from josh.carroll@gmail.com) Received: by py-out-1112.google.com with SMTP id u77so3280846pyb for ; Mon, 29 Oct 2007 15:15:02 -0700 (PDT) Received: by 10.35.87.10 with SMTP id p10mr6885745pyl.1193626676537; Sun, 28 Oct 2007 19:57:56 -0700 (PDT) Received: by 10.35.110.17 with HTTP; Sun, 28 Oct 2007 19:57:56 -0700 (PDT) Message-ID: <8cb6106e0710281957j51feec28ue23360c496a7adbc@mail.gmail.com> Date: Sun, 28 Oct 2007 22:57:56 -0400 From: "Josh Carroll" To: "Hakan K" In-Reply-To: <8cb6106e0710281950s37b50753kf5a08c1760f8d2f9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <4718A0EE.6030804@chello.nl> <8cb6106e0710281855g151fd811nc4f06a6566850e03@mail.gmail.com> <105fa37b0710281937j4004538cid69963ea83277ac@mail.gmail.com> <8cb6106e0710281950s37b50753kf5a08c1760f8d2f9@mail.gmail.com> Cc: freebsd-questions@freebsd.org, David van Kuijk Subject: Re: Problem with VNC on AMD64 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: josh.carroll@gmail.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Oct 2007 22:15:16 -0000 > vnc-4.1.2_2 from ports. I wonder if this is related to it compiling > against ancient XFree86 source? The tightvnc port has the same problem, actually. Same message in the vnc log, but also another: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 102 (X_ChangeKeyboardControl) Value in failed request: 0x3c Serial number of failed request: 6 Current serial number in output stream: 8 Xlib: sequence lost (0x10000 > 0x8) in reply type 0x0! X Error of failed request: 0 Major opcode of failed request: 0 () Serial number of failed request: 0 Current serial number in output stream: 8 Would it matter that the window manager itself is linked against/compiled against X.org, while these VNC ports use old XFree86? I wouldn't think so, unless Xlib is different enough. Perhaps this should be posted to freebsd-x11 instead? Josh