I looked in these two directories:
C:\Documents and Settings\Mav\Application Data\Mozilla\Firefox\
C:\Documents and Settings\Mav\Local Settings\Application
Data\Mozilla\Firefox\
but found no update directory in there, nor the last-update.log file.

I also did a search for the file but the only last-update.log it found was
from Thunderbird. So I'm pretty sure it's just not there at all. Would the
fresh 3.6 install remove this file? Unfortunately I don't have an old
back-up of the "Local Settings" directories, i usually skip them and only
back-up some of the "Aplication Data" directories.

@spofer, it's not in the program files directory. I think it should actually
be in this directory, if it's exactly the same as were Thunderbird stores
the file:
C:\Documents and Settings\ <windowsusername> \Local Settings\Application
Data\Mozilla\Mozilla Firefox\updates\last-update.log



On Wed, Mar 17, 2010 at 12:18 AM, John J Barton <[email protected]
> wrote:

> The following request came from mozilla devs concerning this issue:
>
> If you can get the user's last-update.log it will show whether or not
> the update found / failed to remove these files. The last-update.log
> is in the users profile in the local appdata directory (e.g.
> %LOCALAPPDATA% on Vista and above) under Mozilla\Firefox\<install
> directory name which is typically 'Mozilla Firefox'>\updates
>
> If you can post this file to the bug I will forward it.
>
> http://code.google.com/p/fbug/issues/detail?id=2929
>
> jjb
>
> On Mar 16, 3:56 pm, Mav <[email protected]> wrote:
> > Great to hear the source of the problem has been found. If I'm not
> > mistaken those inspector files were from the DOM inspector that came
> > as an option with older versions of Firefox? I noticed from the
> > logfiles I installed my "bugged" Firefox in 2008 with version 1.9.2.
> > Was about time for a fresh install anyway hehe.
> >
> > On Mar 16, 10:18 pm, Spofer <[email protected]> wrote:
> >
> > > Hi all,
> >
> > > I've just upgraded some versions and the following happened:
> > > - Upgraded to Firefox 3.6 still using the Firebug 1.5.2 - And Firebug
> > > was back! Working normally from my dull testing.
> > > - Then I've upgraded to Firebug 1.5.3 + Java console 6.0.02.03 -
> > > Firebug died again.
> > > - Renamed the inspector files - And now Firebug is working perfectly!
> >
> > > I don't know what are these files, or what did I just do - But it
> > > works! They are old though - Dated to 2005 in my installation.
> >
> > > Anyway -  Back to normal! Thanks a lot John & Testers!!
> > > Spofer
> >
> > > On Mar 16, 10:50 pm, John J Barton <[email protected]>
> > > wrote:
> >
> > > > On Mar 16, 6:06 am, Mav <[email protected]> wrote:
> >
> > > > > Done:http://code.google.com/p/fbug/issues/detail?id=2929
> >
> > > > > I had archived it in two parts to keep it under the 10MB limit, but
> I
> > > > > couldn't attach the files. Also tried to add them in a comment but
> I
> > > > > keep getting the same Bad Request error. Seems like it logs me out
> of
> > > > > my google account before the upload can complete (gmail manager
> > > > > maybe?). So I've added a rapidshare link to the bug report instead.
> >
> > > > Ok I have tracked down the problem in Mav's case: three old files in
> > > > Mozilla Firefox/components directory called
> > > > inspector.dll
> > > > inspector.xpt
> > > > inspector-cmdLine.js
> > > > If these are deleted, Firebug will work.
> >
> > > > jjb
>
> --
> You received this message because you are subscribed to the Google Groups
> "Firebug" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<firebug%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/firebug?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Firebug" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/firebug?hl=en.

Reply via email to