From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21972 invoked by alias); 26 Feb 2009 20:32:00 -0000 Received: (qmail 21963 invoked by uid 22791); 26 Feb 2009 20:31:59 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,SUBJECT_FUZZY_TION X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 26 Feb 2009 20:31:49 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n1QKVliG005575 for ; Thu, 26 Feb 2009 15:31:47 -0500 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n1QKVmjX028454 for ; Thu, 26 Feb 2009 15:31:48 -0500 Received: from localhost.localdomain (vpn-14-57.rdu.redhat.com [10.11.14.57]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n1QKVlNp026288 for ; Thu, 26 Feb 2009 15:31:47 -0500 Date: Thu, 26 Feb 2009 20:32:00 -0000 From: Kevin Buettner To: insight@sourceware.org Subject: Re: RFA: Fix "no event type or button # or keysym" error when starting insight Message-ID: <20090226133145.412f82a3@redhat.com> In-Reply-To: <49A6EBDA.8040405@redhat.com> References: <20090226113346.1e3864ca@redhat.com> <49A6EBDA.8040405@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact insight-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: insight-owner@sourceware.org X-SW-Source: 2009-q1/txt/msg00012.txt.bz2 On Thu, 26 Feb 2009 11:22:02 -0800 Keith Seitz wrote: > > This problem has been fixed in the upstream sources. I've appended, > > below, a patch adapted to the current sourceware Tk sources. I've > > located an upstream ChangeLog entry by the original patch author for > > changes to two of the changed files, but not the third. The change > > to tkUnixEvent.c is not critical; I can leave it out if so desired. > > > > Okay? > > Yeah, that's fine: I don't even use the supplied versions of > Tcl/Tk/Itcl/Itk any more: I use the system installed versions to build > insight. Thanks for the quick reply. I've committed this patch. Would you have any objection if I were to update sourceware's Tcl/Tk/Itcl/Itk to the latest upstream release? Kevin