From owner-freebsd-questions@FreeBSD.ORG Fri Dec 11 03:49:32 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5DC3106566C for ; Fri, 11 Dec 2009 03:49:32 +0000 (UTC) (envelope-from mpd@jesters-court.net) Received: from jcnetns.yclan.net (216-164-162-123.pa.subnet.cable.rcn.com [216.164.162.123]) by mx1.freebsd.org (Postfix) with ESMTP id 7B1498FC12 for ; Fri, 11 Dec 2009 03:49:32 +0000 (UTC) Received: from localhost (c-24-5-80-38.hsd1.ca.comcast.net [24.5.80.38]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mpd@jcnetns.yclan.net) by jcnetns.yclan.net (Postfix) with ESMTPSA id 8241825A3D; Thu, 10 Dec 2009 22:49:30 -0500 (EST) Date: Thu, 10 Dec 2009 19:46:29 -0800 From: mpd To: Glen Barber Message-ID: <20091211034629.GA71275@jesters-court.net> References: <20091211025508.GA4357@jesters-court.net> <4ad871310912101919j6876f01cp3bd24629ca089fc5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ad871310912101919j6876f01cp3bd24629ca089fc5@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) Cc: questions@freebsd.org, mpd Subject: Re: upgraded to 8, no mouse is broken 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, 11 Dec 2009 03:49:32 -0000 On Thu, Dec 10, 2009 at 10:19:43PM -0500, Glen Barber wrote: > On Thu, Dec 10, 2009 at 9:55 PM, mpd wrote: > > I just updated my system from 7.2 to 8.0 STABLE. What do I need to do to > > make my mouse work in X again? This system has an unbroken chain of > > fbsd since 2.2.6, but I'm about to drop it due to this. This is > > horrible. > > > > Since you have given no information on what the symptoms are, nor on > what you have tried, I'll take a long-shot here: > > Have a look ate the 20090124/20090123 entries of /usr/ports/UPDATING > Option "AllowEmptyInput" "off" was the fix. Thanks! > > > -- > Glen Barber --