From owner-freebsd-stable@FreeBSD.ORG Thu Jan 9 14:16:28 2014 Return-Path: Delivered-To: freebsd-stable@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 31CCAA13 for ; Thu, 9 Jan 2014 14:16:28 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B5FFB184C for ; Thu, 9 Jan 2014 14:16:27 +0000 (UTC) Received: from nb981.math (nb981.math.uni-hamburg.de [134.100.222.111]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0Mao5W-1VgyP01Vik-00KaKt; Thu, 09 Jan 2014 15:16:20 +0100 Message-ID: <52CEAD58.2070401@janh.de> Date: Thu, 09 Jan 2014 15:08:24 +0100 From: Jan Henrik Sylvester User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Matthias Gamsjager Subject: Re: 10.0-RC4 -> 10.0-RC5: Xorg stopped using /dev/sysmouse References: <52CEA744.8050105@janh.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:3s54ej3rMl3pfBKgA7PCSYNejtbm6Q00RM+mWGJVDIl 0YozvGyWvmD2KH0NZ6zvGABtcL20UIKPDICw7bVmwbzMMHGNun VWCqkDInGsBW9itokfQ55ckkmYX2h5cjX6nOn/NI9NyvvZYASu DrYUbDjy3davtbZtq+fwKP2voi9rFFE+o+dl64VYYJLBhfemN0 mHQYp9jnspkxO9Yd3+f5HRHpAiX29k6SpmcM88k6gyQFKKqL2h XB8bdVcuScSsazNrdpKNJOsPeXul7IZezgVVf5j+MfzrNHeoDU 6vxl6Xyd5x2o5t3tGG7Ql2QcrXG1J6iOwp0Dl7MZN5R7Jw91w= = Cc: stable-list freebsd X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 14:16:28 -0000 On 01/09/2014 14:48, Matthias Gamsjager wrote: > Killing all moused processes 'fixes' Xorg mouse but proper patch would > be nice Well, rebuilding sysutils/hal does fix this problem properly, which still leaves the questions, if r260406 is the cause and if there is a reasonable way to find affected ports. I guess I was just impatient and the official announcement of 10.0-RC5 will contain this information. Cheers, Jan Henrik