Date: Sun, 28 Oct 2007 22:57:56 -0400 From: "Josh Carroll" <josh.carroll@gmail.com> To: "Hakan K" <dominor@gmail.com> Cc: freebsd-questions@freebsd.org, David van Kuijk <dj.vankuijk@chello.nl> Subject: Re: Problem with VNC on AMD64 Message-ID: <8cb6106e0710281957j51feec28ue23360c496a7adbc@mail.gmail.com> In-Reply-To: <8cb6106e0710281950s37b50753kf5a08c1760f8d2f9@mail.gmail.com> References: <4718A0EE.6030804@chello.nl> <8cb6106e0710281855g151fd811nc4f06a6566850e03@mail.gmail.com> <105fa37b0710281937j4004538cid69963ea83277ac@mail.gmail.com> <8cb6106e0710281950s37b50753kf5a08c1760f8d2f9@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8cb6106e0710281957j51feec28ue23360c496a7adbc>