As a test, I built and installed xfree-4.3.0-r3 because 'emerge -pu world' kept
wanting to do it.
Now, once again, if mozilla (or MozillaFirebird) tries to list a garbage file, it
Steps to Reproduce:
1.emerge -u xfree
3.Try, say, a left click on
mozilla silently aborts
Filled the screen with garbage
This is an old problem, and with the upgrade for xfree-4.3.0-r2 & mozilla,
as I recall the fix was to rebuild just about everything that used any of
the X11 libraries because some packages were incompatible with the new xf86.
Problem is almost certainly in fonts, font libraries, but I don't remember the
cause from last time. (I think it was Xft processing).
Here's the system:
ferris@lacewing:~ % emerge info
Portage 2.0.49-r15 (default-sparc64-1.4, gcc-3.2.3, glibc-2.2.5-r2,2.3.2-r1,
System uname: 2.4.21-sparc-r1 sparc64 sun4u
Gentoo Base System version 18.104.22.168p1
ccache version 2.2 [enabled]
CFLAGS="-mcpu=ultrasparc -O3 -pipe"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
CXXFLAGS="-mcpu=ultrasparc -O3 -pipe -Wno-deprecated"
USE="sparc avi encode fbcon foomaticdb gif jpeg mad mikmod mpeg ncurses nls png
pdflib spell truetype xv xml2 xmms gdbm berkdb slang readline tetex tcltk java
guile X sdl gpm tcpd pam libwww ssl perl python imlib gtk qt motif opengl
mozilla cdr mysql -oggvorbis crypt -arts -alsa -esd -oss cups ruby ruby18 tiff
zlib Xaw3d bidi stroke cjk -gnome -kde"
This should better go to
Well, I'm rebuilding mozilla on one of my systems to test your hypothesis,
because reverting to xfree-4.3.0-r2 does not fix it, which tells me that
the 'emerge xfree' changed the configuration somehow that to something that
mozilla as built is not compatible with, but doesn't get put back by
'emerge -k xfree-4.3.0-r2'
Now, the no-longer-completely-working mozilla was built on August 12, and
xfree-4.3.0-r2 has been around quite a while. (Last go-around on this was last
I don't see how the problem is mozilla's, (except for its giving up silently),
since it hasn't changed.
I don't see how the problem is xfree's per se, because if so the reversion
to 4.3.0-r2 should have fixed it, unless xfree-4.3.0-r3 added something new
which mozilla is no finding instead of whatever it used to find (but just
reverting to -r2 does not remove).
I'd prefer to leave this open until I see what rebuilding mozilla does. It's
reported against sparc right now because:
1. That's all I have;
2. No one else has reported any such thing, and xfree-4.3.0-r3 has been
around for a while.
I readily admit that this is likely a result of garbage on my systems, but I
am not certain. I'd like to know what happens when someone else tries this,
but I am not going to test it on another working system of mine, right now. :-)
That first paragraph reads as nonsense. What is says is:
1. mozilla/xfree-4.3.0-r2 working;
2. emerge xfree-4.3.0-r3 & mozilla starts having problems;
3. emerge -k xfree-4.3.0-r2 & mozilla still has problems