From owner-freebsd-x11@FreeBSD.ORG Fri Mar 28 13:13:46 2008 Return-Path: Delivered-To: freebsd-x11@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 586C8106566C for ; Fri, 28 Mar 2008 13:13:46 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from QMTA10.emeryville.ca.mail.comcast.net (qmta10.emeryville.ca.mail.comcast.net [76.96.30.17]) by mx1.freebsd.org (Postfix) with ESMTP id 2E7A98FC14 for ; Fri, 28 Mar 2008 13:13:46 +0000 (UTC) (envelope-from cokane@freebsd.org) Received: from OMTA12.emeryville.ca.mail.comcast.net ([76.96.30.44]) by QMTA10.emeryville.ca.mail.comcast.net with comcast id 6aaz1Z00Q0x6nqcAA0DD00; Fri, 28 Mar 2008 13:13:23 +0000 Received: from discordia ([24.60.135.75]) by OMTA12.emeryville.ca.mail.comcast.net with comcast id 6dDj1Z00C1dmTCQ8Y00000; Fri, 28 Mar 2008 13:13:45 +0000 X-Authority-Analysis: v=1.0 c=1 a=uoiM2rKEazUA:10 a=c5sTgUsrrxMA:10 a=ThchSbmp4U_MCrCpgS0A:9 a=oxJtA_IZw0ZOEj0FfaoA:7 a=aloB4Qoy_SP0mIgBUErMgWDSyEYA:4 a=vNGxQsTWjH8A:10 Received: by discordia (Postfix, from userid 103) id 9344D1636F8; Fri, 28 Mar 2008 09:13:43 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.1.8-gr1 (2007-02-13) on discordia X-Spam-Level: X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.1.8-gr1 Received: from [172.31.1.6] (unknown [172.31.1.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by discordia (Postfix) with ESMTP id CE94C1636F8; Fri, 28 Mar 2008 09:13:36 -0400 (EDT) Message-ID: <47ECEE13.8080306@FreeBSD.org> Date: Fri, 28 Mar 2008 09:09:39 -0400 From: Coleman Kane Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.12 (X11/20080312) MIME-Version: 1.0 To: Matthew Seaman References: <47EBF0C7.6010901@infracaninophile.co.uk> <47EBF1B0.7000905@FreeBSD.org> <47EC979A.2030906@infracaninophile.co.uk> In-Reply-To: <47EC979A.2030906@infracaninophile.co.uk> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-x11@freebsd.org Subject: Re: (OT) X pausing until mouse move (collecting commonalities) X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: cokane@FreeBSD.org List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2008 13:13:46 -0000 Matthew Seaman wrote: > Coleman Kane wrote: >> Matthew Seaman wrote: > >>> Bingo. Everything is nice and fast again and I don't have to wiggle >>> the >>> mouse to enter text. Unfortunately Thunderbird seems to have lost >>> contact >>> with Enigmail[*] as a result of these changes and I'm sure there are >>> a few other >>> things that aren't working quite right (but then I'm the old-school >>> type >>> that regards a mouse as a tool used to select which xterm gets the >>> keyboard >>> focus.) > >> Thunderbird seems to not work with enigmail for me since the upgrade >> to TB 2.0.0.12. The engimail people seem intent on blaming everyone >> else for not using "official copies" of ThunderBird, but I cannot >> seem to get it to work even if I follow their special directions for >> building the software from within mail/thunderbird/work after a new >> TB build/install (without running make clean). Their whole argument >> about this being "my fault" for using an "unofficial version" of TB >> smells to me, but I suppose I could always go and fix the problem >> myself. I don't even know what the actual error is that causes this >> to occur. > > Yeah. The interaction between Thunderbird and Enigmail seems a bit > flakey > at best. I've seen it go out, then a few days later when I've got > some time > to investigate, updating ports and recompiling everything (portupgrade > -fR enigmail\*) > to ensure a good baseline --- well, that seems to bring it back. I've > certainly got enigmail working with 2.0.0.12 at the moment on one > machine, > and it was working fine on the other with that combo too. > > Cheers, > > Matthew > amd64 or i386? I've got an amd64 system, and from what I've heard the problem happens more often under amd64. -- Coleman Kane