From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Nov 13 15:30:23 2005 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 93A8416A41F for ; Sun, 13 Nov 2005 15:30:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38FC543D46 for ; Sun, 13 Nov 2005 15:30:23 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.3/8.13.3) with ESMTP id jADFUMxl093890 for ; Sun, 13 Nov 2005 15:30:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.3/8.13.1/Submit) id jADFUME9093889; Sun, 13 Nov 2005 15:30:22 GMT (envelope-from gnats) Date: Sun, 13 Nov 2005 15:30:22 GMT Message-Id: <200511131530.jADFUME9093889@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: User1001 Cc: Subject: Re: ports/86318: graphics/xfig 3.2.4_1 takes over cpu after clicking editing-type button X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: User1001 List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Nov 2005 15:30:23 -0000 The following reply was made to PR ports/86318; it has been noted by GNATS. From: User1001 To: Michael Nottebrock , bug-followup@freebsd.org Cc: Subject: Re: ports/86318: graphics/xfig 3.2.4_1 takes over cpu after clicking editing-type button Date: Sun, 13 Nov 2005 09:26:58 -0600 No change - xfig 3.2.4_3 locks up as soon as I select anything from the left (Editing) panel, and CPU utilization "reaches for the sky". Xfig 3.2.5_alpha5 works like a charm, is about 2 years newer than 3.2.4, and has bug fixes and enhancements over 3.2.4. I vote for upgrading xfig port to 3.2.5_alpha5. Michael Nottebrock wrote: > It still might be the fix for the issue - at least I cannot reproduce your > problem. > > Could you please try xfig-3.2.4_3 and see if it works for you?