I'm having trouble with mozilla-firefox (not binary). Very often, wehn starting up, firefox will not open any windows but the process seems to run in circles or maybe racing with itself (see strace). A debug build yielded many messages upon startup but remains incoclusive (see stratup log). I've set rather conservative CFLAGS. The problem turned up when I migrated from my Athlon XP setup to AMD64. I've taken the homedirectory from the old machine in verbatim, so I first suspected something in .mozilla setting FF up, so I move it away. First startups (i.e. if the frist run wizard is run) seem to always work, but even if I don't touch any prefs, subsequent startups have the hang problem. I half suspect ntpl (or rather, not having nptlonly in USE) being the culprit, but I need dvdrip which in turn needs a non-nptlonly glibc to work :-/ I'm at a complete loss as to what I can do to diagnose more, much less fix it. Any advice will be appreciated - but I'd rather not move mozilla-firefox-bin. emerge info: Portage 2.0.53_rc7 (default-linux/amd64/2005.1, gcc-3.4.4, glibc-2.3.5-r3, 2.6.14.2 x86_64) ================================================================= System uname: 2.6.14.2 x86_64 AMD Athlon(tm) 64 Processor 3700+ Gentoo Base System version 1.12.0_pre10 distcc 2.18.3 x86_64-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] dev-lang/python: 2.3.5, 2.4.2 sys-apps/sandbox: 1.2.13 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.20-r1 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -pipe " CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -pipe " DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ http://gentoo.mirror.solnet.ch http://pandemonium.tiscali.de/pub/gentoo/" LANG="en_US" LC_ALL="en_US" MAKEOPTS="-j1" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.de.gentoo.org/gentoo-portage" USE="amd64 X a52 aalib alsa apache2 audiofile avi bash-completion berkdb bitmap-fonts bmp bzip2 calendar cdparanoia cdr crypt cups curl dio dts dvb dvd dvdr dvdread emboss encode esd ethereal exif expat fam ffmpeg fftw firefox flac foomaticdb fortran ftp gif glut gphoto2 gpm gstreamer gtk gtk2 idn imagemagick imlib imlib2 jack jpeg kdeenablefinal ladcca lcms libcaca libwww lua lzw lzw-tiff mad matroska mikmod mmap mng motif moznocompose moznoirc moznomail mozsvg mp3 mpeg mysqli ncurses nls nptl offensive ogg opengl pam pcre pdflib perl png python quicktime readline recode scanner sdl sharedmem sockets sox spell ssl svg szip tcltk tcpd tetex theora tiff truetype truetype-fonts type1-fonts udev unicode usb userlocales v4l v4l2 vcd vim vim-pager vlm vorbis wmf xine xml2 xmms xosd xpm xv xvid zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS, LINGUAS
Created attachment 73602 [details] Debug messages from debug build of mozilla-firefox
Created attachment 73605 [details] Strace of a failing startup. Flags for strace are -Ff -o log
I just tried and installed the mozilla-firefox-bin package which is 32 bits. It seems to have the same problem (behaviour is the smae, strace looks the same). But maybe its error messages are more helpful: $ firefox-bin No running windows found (firefox-bin:7826): Gdk-WARNING **: gdk_property_get(): length value has wrapped in calculation (did you pass G_MAXLONG?) Fontconfig error: "conf.d", line 1: no element found I have *no* idea what Fontconfig is complaining about or if it has anything to do with my problem.
As far as I can tell, the problem is gone with mozilla-1.5. As far as I am concerned, this means: fixed. I'm changing the resolution to "fixed" accordingly. Maybe "usptream" would be better?
