On Wed, Jun 02, 1999 at 12:04:24PM -0600, Marcelo E. Magallon wrote: > > No, there are no missing dependencies, mozilla code is buggy. > > I know. I haven't submitted other bugs, have I? ;-)
:) > But I still think there's a missing dependency. I installed mozilla, it > went ok. I started mozilla, it asked something about a profile, I supplied > the information, and it immeadtly coredumped. It asked something? How about it, it never asked me anything... :) The problem is that *I* haven't tested it yet, I have just heard from two other people on IRC that it works. Yes, yes, I know that is a very bad practice, but the people WANT the new mozilla packages, and they want it. They want it NOW :) > I updated the system (notably, some gnome and gtk+ libraries), started > mozilla again, and this time it worked ok. Maybe you had libgtk1.2 version < 1.2.3 installed? That was a common problem in the last week or so, since the binary compatibility has been broken in that version, and the package wasn't really ready... > > You could have even run the mozilla packages with the same filename, but I > > have been rebuilding it not changing the version numerous times. > > ok, that's a problem. I got the files from your directory on... master? > (the URL you posted a few hours ago) Not master, pandora. Or Incoming. But I admit, there could be a problem if it was the latest version... One other problem could be having a ~/.mozilla/ directory from any other previous version of mozilla (especially the ultra-old one from slink). It causes mozilla to crash and burn, usually. Did you experience coredumps later? If you happen to run into a segfault, try deleting the ~/.mozilla dir, and then try again. -- enJoy -*/\*- http://jagor.srce.hr/~jrodin/
