From owner-freebsd-questions@FreeBSD.ORG Fri Feb 5 03:53:35 2010 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 2BF67106566C for ; Fri, 5 Feb 2010 03:53:35 +0000 (UTC) (envelope-from chuckr@telenix.org) Received: from mail6.sea5.speakeasy.net (mail6.sea5.speakeasy.net [69.17.117.8]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1EA8FC18 for ; Fri, 5 Feb 2010 03:53:35 +0000 (UTC) Received: (qmail 18522 invoked from network); 5 Feb 2010 03:53:34 -0000 Received: from april.chuckr.org (HELO april.telenix.org) (chuckr@[66.92.151.30]) (envelope-sender ) by mail6.sea5.speakeasy.net (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 5 Feb 2010 03:53:34 -0000 Message-ID: <4B6B96A1.2070107@telenix.org> Date: Thu, 04 Feb 2010 22:55:13 -0500 From: Chuck Robey User-Agent: Thunderbird 2.0.0.19 (X11/20090121) MIME-Version: 1.0 To: FreeBSD Questions Mailing List Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: X11/freebsd problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Feb 2010 03:53:35 -0000 I have this problem with my built-under-freebsd-current Xorg, it gives me this following sort of error everytime it starts up: (pts/2):{14}% Xlib: extension "Generic Event Extension" missing on display ":0.0". Xlib: extension "Generic Event Extension" missing on display ":0.0". Usually, that 2nd line shows up 6 to 12 times, I trimmed the repetitions for brevity. Anyone got any idea what this sort of error is? If it isn't a fairly common sort of error, I think I'll hunt to see if maybe there's an Xorg mailing list I could use. I think that the error originated during the period when I was writing a X11 graphical tablet driver, but it never (until now) seemed to actually get it the way. The version of X I was using is completely gone now, and when I found out that the cut-rate graphical tablet itself was too defective to give me a good basis for the driver, well, the driver is history now too (except for all the stuff I learned, very useful!) Thanks. This all came up as I've been searching for a sound player with a good GUI, and that's what triggered the error this time (the audacious port).