From owner-freebsd-gnome Sat Jan 25 17:18:40 2003 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 0910237B401 for ; Sat, 25 Jan 2003 17:18:37 -0800 (PST) Received: from sv02.webonaut.com (kirk.webonaut.com [212.41.243.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id D30AF43EB2 for ; Sat, 25 Jan 2003 17:18:35 -0800 (PST) (envelope-from klammer@webonaut.com) Received: from [212.41.243.28] (sisko.webonaut.com [212.41.243.28]) by sv02.webonaut.com (Postfix) with ESMTP id 5C44C766C6; Sun, 26 Jan 2003 02:18:28 +0100 (CET) Subject: Re: YAMM - Yet Another Mozilla Mail ;-) From: Franz Klammer To: Joe Marcus Clarke Cc: Maxime Romano , FreeBSD GNOME Users In-Reply-To: <1043537898.328.34.camel@gyros> References: <1043476825.12343.17.camel@shumai.marcuscom.com> <1043492669.589.24.camel@ds9.webonaut.com> <1043532291.328.17.camel@gyros> <1043537768.35287.7.camel@ds9.webonaut.com> <1043537898.328.34.camel@gyros> Content-Type: text/plain Organization: Message-Id: <1043544064.94883.5.camel@ds9.webonaut.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.1 Date: 26 Jan 2003 02:21:04 +0100 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-gnome@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Am So, 2003-01-26 um 00.38 schrieb Joe Marcus Clarke: > On Sat, 2003-01-25 at 18:36, Franz Klammer wrote: > > Am Sa, 2003-01-25 um 23.04 schrieb Joe Marcus Clarke: > > > On Sat, 2003-01-25 at 06:04, Franz Klammer wrote: > > > > Am Sa, 2003-01-25 um 07.40 schrieb Joe Marcus Clarke: > > > > > On Sat, 2003-01-25 at 01:27, Maxime Romano wrote: > > > > > > >From: Joe Marcus Clarke > > > > > > >On Fri, 2003-01-24 at 20:01, Franz Klammer wrote: > > > > > > > > Am Sa, 2003-01-25 um 01.29 schrieb Joe Marcus Clarke: > > > > > > > > > On Fri, 2003-01-24 at 19:25, Franz Klammer wrote: > > > > > > > > > > Am Sa, 2003-01-25 um 01.05 schrieb Joe Marcus Clarke: > > > > > > > > > > > On Fri, 2003-01-24 at 19:00, Franz Klammer wrote: > > > > > > > > > > > > Am Sa, 2003-01-25 um 00.09 schrieb Joe Marcus Clarke: > > > > > > > > > > > > > On Fri, 2003-01-24 at 17:41, Maxime Romano wrote: > > > > > > > > > > > > > > >From: Joe Marcus Clarke > > > > > > > > > > > > > > >To: Franz Klammer > > > > > > > > > > > > > > >CC: FreeBSD GNOME Users > > > > > > > > > > > > > > >Subject: Re: YAMM - Yet Another Mozilla Mail ;-) > > > > > > > > > > > > > > >Date: 24 Jan 2003 14:18:27 -0500 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >On Thu, 2003-01-23 at 13:07, Franz Klammer wrote: > > > > > > > > > > > > > > > > hello! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > just for info. > > > > > > > > > > > > > > > > maybe it helps a little to track down the problem. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > to try it out, yesterday i've installed mozilla-1.3a > > > > > > > > > > > > > > > > with xft and gtk2 support. > > > > > > > > > > > > > > > > (on -current with -march=pentiumpro and -O2 ;o)) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > everything works well if i'm don't think about that i > > > > > > >have > > > > > > > > > > > > > > > > to run it with root-rights: sudo mozilla. > > > > > > > > > > > > > > > > (the same i've written yesterday regarding > > > > > > >1.2.1/gtk/xft) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >Okay, I've reproduced the crash with Galeon 1.3.1 and > > > > > > >Mozilla with > > > > > > > > > > > > > > >GTK2. The problem is an expat conflict. expat is being > > > > > > >linked from > > > > > > > > > > > > > > >fontconfig instead of the static version that is included > > > > > > >with Mozilla. > > > > > > > > > > > > > > >This would be okay, except that Galeon is doing something > > > > > > >bad. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Definately. I'm seeing this problem too, and am currently > > > > > > >recompiling > > > > > > > > > > > > > > mozilla-gtk2. But, considering what you just said, it isn't > > > > > > >going to change > > > > > > > > > > > > > > much. Any idea how to fix this? > > > > > > > > > > > > > > > > > > > > > > > > > > I'm testing a possible fix now. Try removing --enable-reorder > > > > > > >from > > > > > > > > > > > > > mozilla-devel's Makefile, and see if that helps. My machine > > > > > > >won't be > > > > > > > > > > > > > done recompiling for a while. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > i've found the reason but i don't know why: mozilla didn't start > > > > > > > > > > > > with some gtk2-themes. e.g. with my favorite theme "fishing the > > > > > > >sky" > > > > > > > > > > > > i have to start it with sudo. if i change the theme to e.g. > > > > > > >gtk-default > > > > > > > > > > > > i can start mozilla as normal user. > > > > > > > > > > > > > > > > > > > > > > Try going through the theme files, and see if there are > > > > > > >restrictive > > > > > > > > > > > permissions. I haven't tried a non-default GNOME theme myself to > > > > > > >see if > > > > > > > > > > > it works. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > didn't help. just to be sure I've done a > > > > > > > > > > chmod -R 777 ~/.themes - the problem persist. > > > > > > > > > > > > > > > > > > What about font permissions? Have you tried themes other than the > > > > > > >"bad" > > > > > > > > > one and default? What exactly happens when you run it as a normal > > > > > > >user? > > > > > > > > > > > > > > > > > > Joe > > > > > > > > > > > > > > > > > > > > > > > > > THEMES: > > > > > > > > ============== > > > > > > > > gnububble: no > > > > > > > > > > > > > > > > Redmond95: ok, but: > > > > > > > > (:91532): Gtk-WARNING **: > > > > > > > > /usr/X11R6/lib/gtk-2.0/2.2.0/engines/libredmond95.so: > > > > > > > > Undefined symbol "gtk_widget_get_direction" > > > > > > > > > > > > > > > > > > > > > > > > Metal: ok, but: > > > > > > > > (:98114): Gtk-WARNING **: > > > > > > > > /usr/X11R6/lib/gtk-2.0/2.2.0/engines/libmetal.so: > > > > > > > > Undefined symbol "gtk_toggle_button_get_type" > > > > > > Okay, here are my findings. I get the same errors you do, but they > > > appear to be harmless. All apps work as expected including Mozilla. As > > > for the other themes, they work just fine for me as well (including with > > > Mozilla). I think you got bit by the old GTK directory problem, Franz. > > > It is not sufficient for you to just bump the shared lib version when it > > > comes to GTK themes. You also have to go through the the Makefile, and > > > replace occurrences of the 2.0.0 directory with 2.2.0 (there are quite a > > > few of these in Bluecurve, for example). > > > > > > After doing that, the theme works great, and Mozilla comes right up with > > > the Bluecurve look and feel. (Note, other non-ported themes may have > > > some other, deeper editing that needs to be done). > > > > i did a search of all occurrences of 2.0.0 (gtk-only) and i found the > > there was no port i've installed*). it's interesting (strange?) but > > bluecurve/mozilla didn't work for me. also sudo didn't help me with > > this theme. > > > > my currently installed mozilla (1.3a,GTK2.2,Xft) isn't compiled with -g > > but if i start with gdb (bluecurve +/-sudo) the first two lines of > > the backtrace are these: > > > > #0 0x00000000 in ?? () > > #1 0x292d10ba in XML_ParserCreate_MM () from > > /usr/local/lib/libexpat.so.4 > > > > > > maybe i need also first your galeon/mozilla-patch? > > you have written something about libexpat. > > Yep. You're hitting the symbol conflict that my patch fixes. I didn't > do any theme testing until after relinking with -Bsymbolic. Give it a > shot. Hopefully, it will fix all your theme/Mozilla problems. > ok. mozilla works for me now. it seems that only themes with an (own) engine will be used. bluecurve and the standard gtk-engines are ok. if i select the other themes mozilla comes up with gtk-default. thanks! franz > Joe -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-gnome" in the body of the message