Bug 71055 – mozilla-firefox-1.0_pre-r2 compiled with xprint is very unstable

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Ramon de Ruiter 2004-11-13 06:32:43 UTC]

Since i emerged Firefox with xprint support, the browser is very unstable. On some sites the browser just closes, on others it hangs and needs to be killed manually with 'kill -9 pidof mozilla-firefox'.
When i re-emerged Firefox without xprint support, it works just fine like it always did.

Reproducible: Always
Steps to Reproduce:
1. emerge mozilla-firefox-1.0_pre-r2 and make sure xprint's in your USE var
2. surf around a bit; amule.org made it crash every time for me
3.

Actual Results:  
Firefox compiles fine, but hangs or closes at random.

Expected Results:  
It should let me "take back the web"!

Portage 2.0.51-r3 (default-linux/x86/2004.0, gcc-3.3.4, glibc-2.3.4.20040808-r1,
2.6.9 i686)
=================================================================
System uname: 2.6.9 i686 Athlon XP Barton  3200+
Gentoo Base System version 1.4.16
distcc 2.16 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.59-r5
Automake: sys-devel/automake-1.8.5-r1
Binutils: sys-devel/binutils-2.14.90.0.8-r1
Headers:  sys-kernel/linux-headers-2.4.21-r1,sys-kernel/linux-headers-2.4.19
Libtools: sys-devel/libtool-1.5.2-r5
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -march=athlon-xp -pipe -mmmx -msse -m3dnow"
CHOST="i686-pc-linux-gnu"
COMPILER=""
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config
/usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -march=athlon-xp -pipe -mmmx -msse -m3dnow"
DISTDIR="/tmp/distfiles"
FEATURES="autoaddcvs candy ccache distcc distlocks nodoc noinfo sandbox sfperms"
GENTOO_MIRRORS="http://ftp.snt.utwente.nl/pub/os/linux/gentoo
http://gentoo.tiscali.nl/gentoo/ http://ftp.uni-erlangen.de/pub/mirrors/gentoo
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/root/portage-overlay"
SYNC="rsync://rsync.nl.gentoo.org/gentoo-portage"
USE="3dnow X aalib acpi alsa apm audiofile avi berkdb bitmap-fonts cdr crypt
cups divx4linux encode esd fam foomaticdb fortran gdbm geoip gif gimpprint
gphoto2 gstreamer gtk gtk2 guile imagemagick imlib java jikes jpeg libg++ libwww
mad mikmod mmx motif mpeg nas ncurses offensive oggvorbis opengl oss pam pdflib
perl png python quicktime readline samba sdl slang speex spell sse ssl svg svga
tcltk tcpd tiff truetype usb userlocales wmf x86 xml xml2 xmms xv xvid zlib"

[Comment 1 Aron Griffis (RETIRED) 2004-11-13 15:44:26 UTC]

why are you merging with xprint support?  do you need it?

[Comment 2 Ramon de Ruiter 2004-11-13 18:05:47 UTC]

First, do i need it? No i don't that's why i removed the USE flag and emerge Firefox again.
I just wanted to see what xprint is about. I'm on of those people that likes to try all sorts of new software.
If xprint is known to not work or give problems, why isn't the xprint USE flag removed then. I think that's more important than to see if i need it or not. There should be more people out there that want to, or already are using xprint, right?

[Comment 3 Aron Griffis (RETIRED) 2004-11-14 17:14:04 UTC]

You misinterpret my reason for asking.  You marked this bug "critical"; I thought maybe you had something critical hinging on xprint support.

I've just tested mozilla-firefox-1.0-r2 with xprint support enabled.  I surfed around, tried forms, etc.  Also checked out amule.org.  It seems to be working fine here.  My suspicion is that cleaning out your profile (or testing with an alternate profile) would do the trick.

Here is something you can try if you'd like:

USE=xprint emerge =mozilla-firefox-1.0-r2
firefox -ProfileManager
... create a new profile "Test" and see if it works

If that works, then you have a couple options:
1. continue to work without xprint support with your existing profile
2. use a new profile, optionally copy in user.js and bookmarks.html to jumpstart it.

[Comment 4 Aron Griffis (RETIRED) 2004-11-15 20:39:09 UTC]

If you try my suggestions in comment 3 and wish to provide further information, please feel free to re-open.  Based on my experimentation, I'm closing this bug for now.