From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0+) Gecko/20020428 BuildID: 2002042807 starting up mozilla with imap mail, launches browser with url field containing: find:datasource=history&match=AgeInDays&method=is&text=0&groupby=Hostname ---- browser window eventually has: No P4P Id Bad or missing ASI Client Id No User Id Reproducible: Always Steps to Reproduce: 1.type mozilla (intending to start only mail-tool) 2.enter password in imap mail login field 3.watch error occur Actual Results: can still use mozilla, just strange behavior. Expected Results: only start up mail-tool and sync mail with imap server started happening with "1.0" release, tried nightly build, but still had same problem. wonder if it has anything to do with registry / internal db?

I've seen earlier reports like this but I don't think they were ever confirms. It would be nice if you could look through your profile files and see if you see anything out of the extraordinary. (such as in prefs.js)

nuking the 'localstore.rdf' file in my '.mozilla/...' directory worked for me.

This find:xxxxxxxx bug is probably caused by the same as what I have described in http://bugzilla.mozilla.org/show_bug.cgi?id=143707#c1

i noticed that if i enter the url http://find in location bar, it resolves to http://find.com which again redirects to apps5.oingo.com. Once that url is in history sidebar: Each time i click the history tab there, the url loads. Reporter: Do you have sidebar tab open in mailnews, displaying history, when this bug occures?

*** Bug 146369 has been marked as a duplicate of this bug. ***

see also bug 146619

*** Bug 146369 has been marked as a duplicate of this bug. ***

this was likely solved in bug 76621, remaining issues in bug 146619 / bug 128322 As an attempt at an immediate workaround: Try set the sidebar tab to something other than history

*** Bug 131159 has been marked as a duplicate of this bug. ***

Build 2002052309: I have noticed that the errant find is issued any time a folder-icon is highlighted but not when a actual entry is highlighted. Part of what makes the error pathological is that in the grouped-by-day configuration the default highlight is on the "Today" icon when the frame opens. If you click on a site icon/line (say "bugzilla.mozilla.org" 8-) you will get the errant find. If you click on an actual page (say "Bug 170797") after going to that page the error will not recur. That is, you can navigate freely and safely with the highlight bar left (light gray) on an actual page. This suggests that a couple peices of code are missing: (in pseudo code) if ((new_selection == enum_actual_page) && (new-selection != current_selection)) then { current_selection = new_selection; open current_selection; } else { current_selection = new_selection; } === also {possibly} === on navigate: if (history_is_open) then { current_selection = current_destination; } [or] then { current_selection = "Today" } [etc] ======== Basicaly whenever the selection is being changed/displayed it is trigering a navigate action. When the selection is first created/established it is always established on the grouping folder. Whenever the selection is set to a grouping folder it causes a pathological attempt to go to navigate to a by-definition non-existant somewhere. (e.g. I suspect that the folder entries have a "title" data element but not a "target" element defined.) Add one bad pointer or request for site "" and stir.

fix has been given for that. Check duplicates.

i encountered this bug with a configured http-proxy, which produced an errorpage (dns). trying again with a new profile, the only steps needed to reproduce this bug were: open sidebar, switch to sidebar-history. deactivating the proxy loads the mentioned page. (using the linux version of 1.0-rc3)

*** This bug has been marked as a duplicate of 128322 ***

*** Bug 151115 has been marked as a duplicate of this bug. ***

*** Bug 151243 has been marked as a duplicate of this bug. ***

*** Bug 149513 has been marked as a duplicate of this bug. ***

*** Bug 149487 has been marked as a duplicate of this bug. ***

Hi, as already stated in bug #149513, it disappears for me in 1.1alpha (2002061108). Can someone confirm this? Also it would be nice not to mark bugs as duplicates of other bugs, which are already duplicates of other bugs. Frank

please remove me from the mailling list

VERIFIED Dupe

*** Bug 157642 has been marked as a duplicate of this bug. ***

*** Bug 154043 has been marked as a duplicate of this bug. ***