Date: 28 Feb 2003 01:40:22 -0500 From: Joe Marcus Clarke <marcus@FreeBSD.org> To: questions@FreeBSD.org Cc: ports@FreeBSD.org Subject: Building an FAQ aka Solving the Mozilla problem Message-ID: <1046414422.44133.41.camel@shumai.marcuscom.com>
next in thread | raw e-mail | index | archive | help
--=-2HXRSgnjcELF+EOKr0cm
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
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.=20
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=3D "-O -g -pipe"
STRIP=3D
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
freebsd-gnome@freebsd.org.
Joe
--=20
Joe Marcus Clarke
FreeBSD GNOME Team :: marcus@FreeBSD.org
http://www.FreeBSD.org/gnome
--=-2HXRSgnjcELF+EOKr0cm
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQA+XwRVb2iPiv4Uz4cRAqp5AJsGrGWI+B4EUy2SrEzC2PByfFou0wCgib1M
q53p29ZGZ+Jw47xQjdZCyTk=
=ApT5
-----END PGP SIGNATURE-----
--=-2HXRSgnjcELF+EOKr0cm--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1046414422.44133.41.camel>