I can't start mozilla navigator when set as startup preference, it simply fails. Even when called from gnome-terminal no error to stderr is reported. I have to call "mozilla --mail" in gnome-terminal to start Mozilla Mail and even when I select Navigator in the Window Menu, nothing happens. The only way I could open the Navigator is by selecting a link in the mail window, for instance, the Thunderbird Mail link when you start Mozilla Mail. After that, the navigator works perfectly. I can open tabs, new windows etc. Reproducible: Always Steps to Reproduce: 1. Start mozilla with Navigator selected at startup option. Actual Results: Nothing happens Expected Results: Mozilla Navigator should open. It is mozilla 1.4 with antialiasing. Computer is a Athlon XP 1600+. Kernel is 2.4.20-gentoo-r5. /etc/make.conf options: CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=athlon-xp -O3 -pipe -march=athlon -fomit-frame-pointer -fprefetch-loop-arrays -ffast-math -fforce-addr -falign-functions=4 -fstrict-aliasing -maccumulate-outgoing-args"
I have this same problem. I found that if you start mozilla as: mozilla <blah> Where <blah> is anything, it will start. It seems to need a command line parameter, or it fails to start. I have many other problems with this mozilla build too, like random crashes in mail, (takes the whole of mozilla down), and preferences not being saved. Athlon 1GHz CPU. Portage 2.0.48-r5 (default-x86-1.4, gcc-3.2.3, glibc-2.3.2-r1) ================================================================= System uname: 2.4.20-win4lin-r1 i686 AMD Athlon(tm) processor GENTOO_MIRRORS="http://www.ibiblio.org/gentoo http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/ http://ftp.gentoo.skynet.be/pub/gentoo/" 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/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 oss 3dnow apm avi crypt cups encode foomaticdb gif jpeg gnome libg++ libwww mad mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml alsa gdbm berkdb slang readline arts aalib nas bonobo svga ggi tcltk java guile mysql X sdl gpm tcpd pam ssl perl python esd imlib oggvorbis gtk qt motif opengl mozilla ldap cdr clamav dga doc dvd ethereal fbcon flash gb gd gphoto2 gtk2 imap ipv6 kerberos lcms libgda maildir mozcalendar moznoirc mozp3p mozsvg oav odbc pic samba sasl scanner slp snmp socks5 sse tiff usb wmf xface xml -kde" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-march=athlon -O2 -fomit-frame-pointer -pipe" CXXFLAGS="-march=athlon -O2 -fomit-frame-pointer -pipe" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j3" AUTOCLEAN="yes" SYNC="rsync://192.168.0.254/gentoo-portage" FEATURES="ccache sandbox distcc userpriv usersandbox"
is this still an issue since 1.5 is stable now ?
Yes. The bug is still present in mozilla 1.5 (mozilla 1.5-r1)
Is this still an issue with 1.6-r1? If so, would you mind testing mozilla-1.7_beta-r1 which uses a different launcher? You will probably need to emerge --sync to get the latest bits. Thanks.
no response from poster
