Firefox 1.0PR1

[Vulpes Velox]

On Thu, 14 Oct 2004 00:00:48 -0400
Joe Marcus Clarke <marcus at marcuscom.com> wrote:

> On Wed, 2004-10-13 at 23:47, Vulpes Velox wrote:
> > On Tue, 12 Oct 2004 23:30:26 -0400
> > Glenn Sieb <ges at wingfoot.org> wrote:
> > 
> > > Vulpes Velox said the following on 10/12/2004 10:58 PM:
> > > 
> > > >>Hey All:
> > > >>
> > > >>I have just built firefox 1.0PR1 from the ports and I cannot
> > > >seem to>
> > > >>install any extensions or themes.  Has anyone else had these
> > > >>problems, or have any solutions?
> > > >>    
> > > >>
> > > >Yeah, I have the same problem, plus I can't change any of the
> > > >settings. Plus if I move ~/.mozilla, it wont start what so
> > > >ever, but just kicks out the following...
> > > >Xlib: connection to ":0.0" refused by server
> > > >Xlib: XDM authorization key matches an existing client!
> > > >  
> > > >
> > > Wasn't there a thing where Firefox had to be first run by root?
> > > 
> > > Dunno if this is related..?
> > 
> > Actually finally figured it out earlier today... for some reason
> > it needed xhost +127.0.0.1 or something like that ran if there was
> > no~/.mozilla
> 
> First, there is an entry pertaining to upgrading Firefox in
> /usr/ports/UPDATING.  Second, there are known issues with Firefox
> and linuxpluginwrapper.  If you have lpw installed, you will see:

I don't have it installed and got that when running it from a non-root
user.
 
> firefox-bin: Fatal IO error 78 (Function not implemented) on X
> server:0.0.
> 
> When you start Firefox 1.0PR for the first time.  Subsequent
> invocations should be okay.  However, for best operation, you are
> encouraged to uninstall this plug-in, upgrade to 1.0PR, and start
> the browser once. Afterward, you can reinstall the plug-in.
> 
> This isn't necessary, though.  You can simply follow the
> instructions in UPDATING, then start Firefox twice.  The second
> time, and all subsequent times, it should start up just fine.

They did not work...
 
> I have not found any reliable workaround for the unimplemented X
> function except for temporarily disabling lpw.  Adding 127.0.0.1 to
> the xhost database does not fix the problem.

Did for what what happening here.