kogorman at gmail.com
Sat Jul 24 15:46:35 UTC 2010
On Sat, Jul 24, 2010 at 7:23 AM, Basil Chupin <blchupin at iinet.net.au> wrote:
> What I would suggest is that you go to System>Administration>Synaptic
> Package Manager and uninstall Firefox - and then re-install it. Quite
> often doing so will clear some problematic bit of an installed app -
> like FF.
> But before you do this, just to play it safe, backup your
> /home/<your-loginname>/.mozilla directory and then re-install FF.
> Oh- just in case, and before you zap FF and re-install it: what
> sometimes helps is to WIPE, ie delete, the CACHE for FF --
> ~/.mozilla/firefox/xxxxxxx.default/Cache. Simply delete it - it will
> regenerate the next time you start FF. Often something is stored in
> Cache which plays havoc with whatever you are now doing in FF, and by
> deleting the contents of Cache brings normality to the world of chaos :-) .
>  Whatever you see on the monitor screen when you are using FF is
> automatically stored in Cache - everything. You watch a YouTube flv file
> - it's in Cache; you go to a porn site - it's contents are in Cache. At
> the end of the day the Cache is compressed and archived - but you need a
> special program to be able to see what is those archives.
> And God created Woman; and to repent He then created Beer.
I also had no trouble with these sites. Reinstalling FF may or may not
work. If it does fine. If not, may I suggest a little ditty I run after
every large emerge:
I make it executable ("cleanup") and put it in /usr/local/sbin because you
need to be root. I've saved myself from a number of
invalid bug reports by doing this "whether it needs it or not". Only the
dispatch-conf is interactive, so I can just let the rest run.
Since I run stable other than a very few temporary exceptions, I've had no
problems with this at all.
Kevin O'Gorman, PhD
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ubuntu-users