From owner-freebsd-x11@FreeBSD.ORG Wed Sep 1 13:32:58 2010 Return-Path: Delivered-To: x11@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B7E5710656B3 for ; Wed, 1 Sep 2010 13:32:58 +0000 (UTC) (envelope-from web@umich.edu) Received: from iamlegend.mr.itd.umich.edu (iamlegend.mr.itd.umich.edu [141.211.14.68]) by mx1.freebsd.org (Postfix) with ESMTP id 6351B8FC18 for ; Wed, 1 Sep 2010 13:32:58 +0000 (UTC) Received: FROM tombraider.mr.itd.umich.edu (smtp.mail.umich.edu [141.211.12.86]) By iamlegend.mr.itd.umich.edu ID 4C7E4EDE.9EB45.13673 ; 1 Sep 2010 09:02:22 EDT Received: FROM itcom245.staff.itd.umich.edu (itcom245.staff.itd.umich.edu [141.213.135.249]) By tombraider.mr.itd.umich.edu ID 4C7E4EDD.BAB8.1003 ; Authuser web; 1 Sep 2010 09:02:21 EDT Date: Wed, 1 Sep 2010 08:57:46 -0400 From: William Bulley To: steve@FreeBSD.org Message-ID: <20100901125746.GB74409@itcom245.staff.itd.umich.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: x11@FreeBSD.org Subject: Re: serious (for me) Xorg 7.5 mouse/kbd problem in 8.1-STABLE X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Sep 2010 13:32:58 -0000 This is a follow-up to my message to you from earlier in the week... ----- Forwarded message from Peter Hutterer ----- To: William Bulley From: Peter Hutterer Date: Wed, 1 Sep 2010 08:02:36 +1000 Subject: Re: mwm bug in xorg 7.5 xserver (from June) On Tue, Aug 31, 2010 at 08:11:03AM -0400, William Bulley wrote: > According to Peter Hutterer on Mon, 08/30/10 at 17:56: > > > > I'm pretty sure this is one of the bugs fixed by > > http://cgit.freedesktop.org/xorg/xserver/commit/?id=1884db430a5680e37e94726dff46686e2218d525 > > I can't tell you how much I appreciate your answer. It gives me some > positive hope that I can get back to my window manager of choice (mwm). > > Forgive me for asking, but what exactly am I to do with this information? oh, right. so this patch was on master. I don't think it's been cherry-picked to one of the stable branches (1.7.x in your case). Since it's (potentially) fixed upstream, the best approach is to notify your X maintainers and let them know about this fix. They'll then likely backport it and add it to the ports system. However, it's likely worth your time (and theirs) to download the patch from above and try to manually apply it to your local install. If it really fixes the problem - great. If not, then we need to figure out what is still broken. The patch above is in the 1.9 version of the server, so if you have that one available (or you can test it otherwise, e.g. by cloning from git) that should show if the bug is fixed too. as for server versions: the current versions out in the wild are 1.7.7, 1.8.2 and 1.9.0 (just came out two weeks ago). hth Cheers, Peter > Except for the C code patch(es) at the end of the above page, I have > very little understanding of the bulk of that reference. I am now > running the following ports on FreeBSD 8.1-STABLE: > > xorg-7.5 > xorg-drivers-7.5 > xorg-libraries-7.5 > xorg-server-1.7.5,1 > xf86-input-keyboard-1.4.0 > xf86-input-mouse-1.5.0 > > among others. Am I supposed to patch the xorg-server source using the > above mentioned patches, or should I download a more recent xorg-server? > > I note that in your HTML calendar of Xorg important dates, that a few > weeks ago saw the release of xorg-server 1.7.9 (IIRC). It is likely > that this "fix" or "patch" is in that server, based on the timestamp > of the above URL, but, while I am not adverse to replacing my 1.7.5 > vintage xorg-server with the newer 1.7.9 version, I fear that there > may be other compile time, link time, and/or run time interactions. > > I am used to building my entire system (kernel, libraries, and ports > or applications) from source, but I rarely patch individual objects, > instead leaving that up to the port maintainers who are infinitely > more familiar with the port in question. Your advice is greatly > appreciated in guiding my next actions. Thank you again! ----- End forwarded message ----- Regards, web... -- William Bulley Email: web@umich.edu 72 characters width template ----------------------------------------->|