From owner-freebsd-gnome@FreeBSD.ORG Wed Jul 2 11:59:59 2003 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D7CB337B401 for ; Wed, 2 Jul 2003 11:59:59 -0700 (PDT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by mx1.FreeBSD.org (Postfix) with SMTP id A0BE443FBF for ; Wed, 2 Jul 2003 11:59:58 -0700 (PDT) (envelope-from blueeskimo@gmx.net) Received: (qmail 18028 invoked by uid 65534); 2 Jul 2003 18:59:57 -0000 Received: from dsl-cust-145.openweb.ca (EHLO [64.39.186.145]) (64.39.186.145) by mail.gmx.net (mp015) with SMTP; 02 Jul 2003 20:59:57 +0200 From: Adam To: Jeremy Messenger In-Reply-To: References: <1057163177.96047.65.camel@jake> Content-Type: text/plain Message-Id: <1057172396.96047.75.camel@jake> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.0 Date: 02 Jul 2003 14:59:56 -0400 Content-Transfer-Encoding: 7bit cc: gnome@freebsd.org Subject: Re: gedit 2.3.3 crashes on 4.8-STABLE and 5.1-RELEASE X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2003 19:00:00 -0000 On Wed, 2003-07-02 at 14:34, Jeremy Messenger wrote: > No crash, the spell check works perfect here. Yes, I did close, start and > close gedit again. I did removed gedit-plugins by myself and upgrade gedit > to 2.3.3 few days ago. But, I am not sure what you did with gedit by > compile without Gnome libraries, which I just leave everything by default > from Joe. You should show how you compile, what CFLAGS and many more if you > are expecting for the more help. > > BTW: My system is 5.1-CURRENT yesterday. The only compile option I have set is 'NO_OPENSSH=true' in my make.conf. I assume you are already using the GNOME 2.3.3 libs? I'm not, which is why I needed to make the modifications. I'm suspicious that the outdated libs is related to the problem. GNOME 2.3.3 is due out in 5 days, so perhaps my problem will be fixed then. -- Adam