Date: Wed, 16 Jun 2004 17:43:44 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Joe Kelsey <joe@zircon.seattle.wa.us> Cc: freebsd-gnome@freebsd.org Subject: Re: firefox 0.9 does not work Message-ID: <1087422224.35041.1.camel@shumai.marcuscom.com> In-Reply-To: <1087420025.21533.39.camel@zircon> References: <1087418469.21533.27.camel@zircon> <1087419008.888.28.camel@gyros> <1087420025.21533.39.camel@zircon>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-acoMFt6rnnH5aNba6Y0O Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2004-06-16 at 17:07, Joe Kelsey wrote: > On Wed, 2004-06-16 at 13:50, Joe Marcus Clarke wrote: > > On Wed, 2004-06-16 at 16:41, Joe Kelsey wrote: > > > I just upgraded firefox 0.8 to firefox 0.9 and now I cannot even star= t > > > the browser! The first time it started, it came up with a configurat= ion > > > box, and I let it go with the "upgrade from 0.8" box checked (althoug= h I > > > cannot remember the exact wording...). Since then, whenever I type > > > "firefox", it pauses briefly and eventually exits with no messages > > > printed out at all. I tried reinstalling with -DWITH_LOGGING on the > > > make command line, but that has not changed the behavior. > > >=20 > > > So, currently I have no access to firefox, whereas I used to get > > > wonderful service. How do I get it to print anything at all at me > > > during loading so I can get some idea where it fails and attempt to f= ix > > > whatever has happened? > >=20 > > You should have read UPDATING, ports@, or my commit message. >=20 > What are you talking about? I run 4-STABLE, no message in UPDATING! I > do not find any reason that I need to monitor ports@ or to read CVS > commit messages, unless you have chosen to create a brand-new > requirement out of whole cloth that says that I need to monitor ports@ > all of a sudden. Look at /usr/ports/UPDATING. You should do this everytime you cvsup ports. >=20 > If you make a change like this in a standard gnome application, you need > to at least mention it on the gnome@ list or somehow make it a > requirement that everyone who monitors gnome@ no has to *also* monitor ports@. Everyone who uses ports should monitor /usr/ports/UPDATING, period. But I also included a blurb in the firefox pkg-message for those that don't. Joe >=20 > /Joe >=20 >=20 > > >=20 > > > /Joe > > >=20 > > >=20 > > > _______________________________________________ > > > freebsd-gnome@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-gnome > > > To unsubscribe, send any mail to "freebsd-gnome-unsubscribe@freebsd.o= rg" --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-acoMFt6rnnH5aNba6Y0O Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBA0L8Qb2iPiv4Uz4cRAgfwAJ0dO/hVk8MdNaMoL89N3MgwsiZz5wCgnasm BlpJwpkjpKxW6YRI6/lZWsI= =atu2 -----END PGP SIGNATURE----- --=-acoMFt6rnnH5aNba6Y0O--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1087422224.35041.1.camel>