On 8/22/05, Carl Lowenstein <[EMAIL PROTECTED]> wrote:
> On 8/21/05, Stewart Stremler <[EMAIL PROTECTED]> wrote:
> > begin  quoting Carl Lowenstein as of Sun, Aug 21, 2005 at 10:39:08PM -0700:
> > > On 8/21/05, Todd Walton <[EMAIL PROTECTED]> wrote:
> > > > On 8/21/05, Carl Lowenstein <[EMAIL PROTECTED]> wrote:
> > > > > first page of results is as expected.  The second and subsequent pages
> > > > > drop all but the first search term.
> > > >
> > > > Maybe something about the JavaScript settings?  Google seems to fancy
> > > > that kind of thing.
> > >
> > > Not that I can notice.  Besides, Google is (I think) older than
> > > JavaScript.  I would not be surprised if Gmail depended on JavaScript.
> > > on the other hand.
> >
> > Gmail *used* to _require_ javascript. It no longer requires it, but
> > you need javascript to take advantage of some of the features.
> >
> > Google Maps, however, requires it.
> >
> > > An interesting further data point:  Using lynx to invoke Google.  The
> > > second page of results has the same search terms as the first page.
> >
> > What if you tweak the browser-identifier string?
> >
> > > Of course, the user interface is not so nice, but one could get used to 
> > > it.
> >
> > Especially if the alternative is "it doesn't work right".
> >
> > -Stewart "You might want to try links as well as lynx." Stremler
> 
> More information, leading to confusion:  I set up another unprivileged
> user.  When logged in as "me", Google search works as it should,
> keeping all the search terms for pages after the first.  When logged
> in as "cdl" Google has the anomalous behavior noted above.  So
> somewhere there is a configuration file that has gone bad.
> 
> By the way, there are several notes in the Google discussion board
> concerning this problem.  I deduce from reading them that it was first
> observed some time Saturday August 20.

The m$ solution:  reinstall.  Not reinstall Firefox, I had already
tried that.  Reinstall the user's configuration.

Using the "me" user as a model, I found what files were installed when
Firefox was run for the first time by a virgin user.  About two dozen
of them in $HOME/.mozilla/firefox.  So I carefully copied my
bookmarks.html file somewhere else, and wiped out the .mozilla/firefox
directory.  Ran firefox again, imported the saved bookmarks, and
everything seems to be working as it should.  I will probably have to
reconfigure some preferences, as I think of them.

So it was a botched configuration file, or a poisoned cache, or who knows.
-- 
    carl lowenstein         marine physical lab     u.c. san diego
                                                 [EMAIL PROTECTED]


--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list

Reply via email to