Mozilla crashes when trying to load java applet. Reproducible: Always Steps to Reproduce: 1. visit any site with java (example: http://www.alphalink.com.au/~dpd/telnet.html) Actual Results: mozilla crashed Expected Results: page to load Portage 2.0.49-r13 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r6, 2.6.0-test7-bk2) ================================================================= System uname: 2.6.0-test7-bk2 i686 Intel(R) Xeon(TM) CPU 2.80GHz Gentoo Base System version 1.4.3.11 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share/config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-march=pentium4 -O3 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="sandbox ccache autoaddcvs fixpackages" GENTOO_MIRRORS="http://gentoo.oregonstate.edu/ ftp://mirror.iawnet.sandia.gov/pub/gentoo ftp://ftp.gtlib.cc.gatech.edu/pub/gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo " MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 apm avi crypt encode foomaticdb gif libg++ mad mikmod mpeg nls pdflib quicktime xml2 xmms xv zlib gtkhtml gdbm berkdb slang readline arts tetex nas bonobo svga ggi tcltk java guile sdl gpm tcpd pam libwww perl python imlib oggvorbis gtk motif mozilla gphoto2 cdr X kde qt gtk2 -gnome sse sse2 aalib -esd mbox alsa dvd dvb v4l truetype ssl ncurses jpeg dga opengl tiff png -doc ldap xml -lirc oss cups spell snmp xinerama mmx nptl" [ I] dev-java/blackdown-jdk-1.4.1 (1.4.1) [ ~I] net-www/mozilla-1.5 (0) Plugin: lrwxrwxrwx 1 root root 66 Feb 24 2003 /usr/lib/mozilla/plugins/javaplugin_oji.so -> /opt/blackdown-jdk-1.4.1/jre/plugin/i386/mozilla/javaplugin_oji.so -rwxr-xr-x 1 root root 249270 Oct 19 13:49 /opt/blackdown-jdk-1.4.1/jre/plugin/i386/mozilla/javaplugin_oji.so.
Created attachment 19486 [details] end of strace showing crash
Created attachment 19499 [details] unexpected exception in native code outside VM It appears to be a problem with fonts. I've got a similar problem with alsamixergui http://bugs.gentoo.org/show_bug.cgi?id=31206 where XFT had to be removed for the new XFree-base. Could this be another problem from the removal of XFT?
This is caused by glibc being compiled with <a href="http://www.mail-archive.com/java-linux%40java.blackdown.org/msg15377.html">nptl support, which is known to break this version of blackdown</a>. Your choices are: As per the link, do LD_ASSUME_KERNEL="2.4.1" to run mozilla; Do `USE="-nptl" emerge -B glibc`, then untar it in /usr/local/pthreads, and then do `LD_PRELOAD="/usr/local/pthreads/lib/libpthread.so" mozilla` Use the sun-jdk (1.4.2) which correctly supports nptl; Rebuild glibc without nptl.
Well, I tried to recompile glibc without nptl support and it still crashes. Noticed the lib in jdk that is having the problem...libfontmanager.so.
I still have this problem with java+mozilla. Even did a full emerge -C mozilla blackdown-jdk without any luck. Also tried the jre. I had another gentoo system I built this last week and it didn't have the same issue. However it was using 2.4.22 kernel and older Xfree86 with seperate XFT. Maybe someone could test if they have any problems on same setup. Mozilla 1.5 blackdown-jdk 1.4.1 Xfree 4.3.0-r3 gcc version 3.3.2 20031022 (Gentoo Linux 3.3.2-r2, propolice) glibc-2.3.2-r8 (without nptl)
I found the source of the problem after lots of testing. As it turns out there were some fonts installed by KDEs font manager (true type fonts) into /usr/X11R6/lib/X11/fonts/Type1. When it installed the fonts they were installed as perm 600. Instead of giving the error message about permission deined, it would cause libfontmanager.so to crash with sig 11. It would be good to ensure the KDE group knows about this as well as maybe putting some basic error checking in blackdown-jdk.
