From owner-freebsd-x11@FreeBSD.ORG Sun Feb 9 10:26:21 2014 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C8A3570; Sun, 9 Feb 2014 10:26:21 +0000 (UTC) Received: from ravenloft.kiev.ua (ravenloft.kiev.ua [94.244.131.95]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C73A8181A; Sun, 9 Feb 2014 10:26:17 +0000 (UTC) Date: Sun, 9 Feb 2014 12:26:15 +0200 From: Alex Kozlov To: Robert Millan Subject: Re: [PATCH] do not feed keyboard device path in X devd backend Message-ID: <20140209102615.GA11713@ravenloft.kiev.ua> References: <52EFA9A9.2040901@freebsd.org> <52F61969.2060503@freebsd.org> <20140208135404.GA75736@ravenloft.kiev.ua> <52F63866.80505@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <52F63866.80505@freebsd.org> Cc: freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 10:26:21 -0000 On Sat, Feb 08, 2014 at 02:00:06PM +0000, Robert Millan wrote: > > Hi Alex, > > On 08/02/2014 13:54, Alex Kozlov wrote: > >> Here's a patch that implements the same behaviour with devd. I've verified > >> that attaching/detaching a second keyboard no longer causes this ill effect. > > Can you please check if devd patch from xorg-dev work for you? > > http://trillian.chruetertee.ch/ports/browser/trunk/x11-servers/xorg-server/files/extra-devd > > My patches are precisely against this file (devd.c). The pristine code doesn't work, but > with the collection of fixes I just sent everything is working fine here (been using that > for one week or so). Can you please provide Xorg.x.log before and after applying this patch? -- Alex