Re: Building an FAQ aka Solving the Mozilla problem

2003-02-28 Thread Kris Kennaway 
On Fri, Feb 28, 2003 at 01:40:22AM -0500, Joe Marcus Clarke wrote:

 8. Try rebuilding print/freetype2, x11-fonts/fontconfig, and
 x11-fonts/Xft.

I was also seeing when trying to rebuild phoenix to get AA font
support.  My problem turned out to be old freetype files in
/usr/X11R6.  I don't know why they weren't being deleted by the port
upgrade process.

I found them following the example in the pkg_which(1) manpage,
removed them (you'll also need to remove the dangling symlinks that
this may leave behind [1], or X ports may break at install-time
(mkhtmlindex doesn't like dangling symlinks)), rebuilt phoenix with
portupgrade -Rf phoenix, and now it works.

Kris

[1] I used the following script to find the dangling symlinks:

#!/bin/sh

for i in $(find $1 -type l); do
if [ ! -e $i/ ]; then
echo $i
fi
done



pgp0.pgp
Description: PGP signature

Re: Building an FAQ aka Solving the Mozilla problem

2003-02-28 Thread Joe Marcus Clarke 
On Fri, 2003-02-28 at 15:27, Kris Kennaway wrote:
 On Fri, Feb 28, 2003 at 01:40:22AM -0500, Joe Marcus Clarke wrote:
 
  8. Try rebuilding print/freetype2, x11-fonts/fontconfig, and
  x11-fonts/Xft.
 
 I was also seeing when trying to rebuild phoenix to get AA font
 support.  My problem turned out to be old freetype files in
 /usr/X11R6.  I don't know why they weren't being deleted by the port
 upgrade process.
 
 I found them following the example in the pkg_which(1) manpage,
 removed them (you'll also need to remove the dangling symlinks that
 this may leave behind [1], or X ports may break at install-time
 (mkhtmlindex doesn't like dangling symlinks)), rebuilt phoenix with
 portupgrade -Rf phoenix, and now it works.

Thanks for the update.  I'll make sure to mention this when I publish
this FAQ.

Joe

 
 Kris
 
 [1] I used the following script to find the dangling symlinks:
 
 #!/bin/sh
 
 for i in $(find $1 -type l); do
 if [ ! -e $i/ ]; then
 echo $i
 fi
 done
-- 
Joe Marcus Clarke
FreeBSD GNOME Team  ::  [EMAIL PROTECTED]
http://www.FreeBSD.org/gnome




signature.asc
Description: This is a digitally signed message part

Building an FAQ aka Solving the Mozilla problem

2003-02-27 Thread Joe Marcus Clarke 
Sorry for the cross-post, but this is getting a lot of air time on both
lists.  Since I have never really encountered the problems described in
the recent onslaught of emails, I can only offer regurgitated help from
other users, and some common sense best practices.  Updates to this are
welcome.  When I'm done, I'll post it to my GNOME FAQ.

Q. When I launch Mozilla, all I see is,  No running window found. and
nothing ever happens.  How do I fix this?

A. This problem is usually indicative of a font issue.  As of 1.2a,
Mozilla is built with Xft2 support by default.  This support allows
Mozilla to render anti-aliased fonts.  However, Xft2 can be problematic
if your font setup is not correct.  Here are some things you can try to
remedy the problem.

1. Decide if you really want anti-aliased fonts in Mozilla.  If not, you
can simply rebuild Mozilla after adding WITHOUT_XFT to /etc/make.conf. 
This will return Mozilla to the look and feel of 1.1 and earlier.
2. Make sure all your font files under /usr/X11R6/lib/X11/fonts have
0444 permissions.  That is, make sure the font files are readable by all
users.
3. Make sure you have the following in the Module section of your
XF86Config file:

Load  type1
Load  freetype

4. Make sure you don't have the mozilla-fonts port or package
installed.  If you do, delete it, then run fc-cache -v -f as root.
5. Make sure ${PREFIX}/etc/fonts/fonts.conf exists (where ${PREFIX} is
the prefix where Mozilla is inatalled).
6. Try running fc-cache -f -v as root to force a rebuild of the Xft
fontconfig caches.
7. Try removing or renaming ~/.mozilla.
8. Try rebuilding print/freetype2, x11-fonts/fontconfig, and
x11-fonts/Xft.
9. Remove or rename ~/.fonts.conf if it exists.
10. If you are using XFree86 from CVS (i.e. 4.2.99.x), manually install
print/freetype2, x11-fonts/fontconfig, and x11-fonts/Xft from ports.
11. Make sure you're not building Mozilla with non-default CFLAGS or CPU
optimizations.  Make sure CFLAGS is set to -O -pipe, and try commenting
out CPUTYPE in /etc/make.conf (if such an entry exists).

If none of this works, add the following to /etc/make.conf:

CFLAGS= -O -g -pipe
STRIP=

Then edit Mozilla's Makefile and remove the line that says
--enable-strip.  Then rebuild fontconfig, Xft, and Mozilla.  Then,
launch Mozilla using the command mozilla -g.  At the (gdb) prompt, type
run.  When Mozilla crashes, type bt, and send the resulting backtrace
along with the output of fc-cache -v -f and fc-list -v to
[EMAIL PROTECTED]

Joe

-- 
Joe Marcus Clarke
FreeBSD GNOME Team  ::  [EMAIL PROTECTED]
http://www.FreeBSD.org/gnome


signature.asc
Description: This is a digitally signed message part