User Agent: Mozilla/5.0 (Windows NT 6.1; rv:9.0a1) Gecko/20110916 Firefox/9.0a1 SeaMonkey/2.6a1 Build ID: 20110916003001 Steps to reproduce: 1) Go to any Web page containing text, say http://www.cnn.com/ . 2) Select a word or phrase, then right click on it. 3) From the context menu, click on "Search <searchengine> for <text>" Actual results: Nothing Expected results: A tab or window should have opened displaying a search results page. I have disabled all extensions. This only happens on my Win7 PC. The problem does not occur on another machine running Ubuntu 11.04 and the same version of SeaMonkey. The problem began within the last couple of weeks as far as I can remember.

I guess you can ignore this. I rarely search from the sidebar, but after I opened the sidebar and did a search, searching from the context menu started working again. Weird. I do see the following error in the Error Console after I click on Search in the context menu, even with the search working now. Error: gContextMenu.menu is undefined Source File: chrome://navigator/content/nsBrowserStatusHandler.js Line: 307

Testing with SeaMonkey 2.4b2 I don't get that error or "nothing" with sidebar open or closed. I'll test (later) with trunk for you as well, as that would surely be a regression (if not caused by an extension) Just getting that error is enough to warrant looking into, imo. Flagging this as tracking so we don't lose it when we get close to releasing 2.6 (Incase I forget)

IanN in Bug 655863 removed nsContextMenu::menu

Oops not a blocker but a separate bug should be filed for: > Error: gContextMenu.menu is undefined > Source File: chrome://navigator/content/nsBrowserStatusHandler.js > Line: 307

This patch: * Gets the context menu using getElementById

Comment on attachment 560732 [details] [diff] [review] Find menu patch [Note: I understand the need for this fix, but not how it relates to this bug.]

BTW, a user noted at http://forums.mozillazine.org/viewtopic.php?f=40&t=2321375 that the Search button doesn't work in SM 2.4. The Search button doesn't work for me either in 2.7a1. I suspect it's the same bug as my initial report. In either case, Search button or context menu, doing a search from the sidebar enables search to work until the next time I start SeaMonkey.

Something needs to be initialized that the sidebar does but the Search button in the main window doesn't. But what? Who's our search engine expert?

If it helps at all, even when search from context menu doesn't work in the browser, it *does* work from mail.

Context menu search for selected text in the browser with the results presented in a new tab works here for (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20110928 Firefox/7.0.1 SeaMonkey/2.4.1 and for (Windows NT 5.1; rv:10.0a1) Gecko/20111006 Firefox/10.0a1 SeaMonkey/2.7a1.

IanN, Ratty, What is the state of this bug? I see a patch with r+ but I also see that IanN unassigned himself...

> IanN, Ratty, What is the state of this bug? We can't reproduce the bug so no fix is possible. > I see a patch with r+ but I also see that IanN unassigned himself... This patch fixes an unrelated error message in comment 4 and has been checked in. Andy, does this also happen in safe-mode?

Mozilla/5.0 (X11; Linux x86_64; rv:11.0a1) Gecko/20111210 Firefox/11.0a1 SeaMonkey/2.8a1 I'm no longer seeing this bug at all on my Linux machine. On Windows 7 I'm not seeing the bug if I start SM in safe-mode. Thinking it might be a problematic extension, I disabled all of them one by one, but the bug still manifests itself with all extensions disabled when not in safe-mode.

Ah there are two/three other possibilities then. 1. plugins which safe-mode doesn't disable (If I remember correctly) 2. localstore.rdf In the latter case, shut down seamonkey, temporarily move localstore.rdf (in your profile) to somewhere else. Restart SeaMonkey. 3. Some buggy search engine. Edit->Preferences->Browser->Internet Search What is the default search engine listed? 3a. Click "Manage Search Engines". What engines are listed there?

The reporter in bug 718503 confirmed that this is a localstore.rdf corruption. Note to myself: the safemode disables also the localstore.rdf !

> The main problem for us is now to find the exact value inside the file to is causing > this and probably how that can happen to contain such a broken value. One way is to bisect the broken localstore.rdf. 1. Save it somewhere else. 2. Truncate it in half. 3. See if the problem still occurs. 3a. If the problem still occurs, keep reducing the file by half. 3b. If not restore the broken localstore.rdf and this time truncate the file about 3/4 of the way down. etc.

Rightclick shows again a extended comand list ... but Google Text Search and e.g. Copy is missing

Hey Andy, Sorry to interrupt whatever you're doing at the moment. Is this still a problem for you?

No longer a problem for me.

(In reply to Andy Boze from comment #21) > No longer a problem for me. Thanks.