Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 SeaMonkey/2.31a1 ID:20140723133406 c-c:acb745a4d796 m-c:d0f6259e8446 https://addons.mozilla.org/en-US/seamonkey/addon/unbubble/ Reproducible: Every time. Steps to reproduce: 0. Make sure you are using SeaMonkey and not Firefox. 1. Browse to a search plugin page (such as the one mentioned above) 2. Click "Add to SeaMonkey". Actual results: A bell sound is heard and an alert appears: “Sorry, you must use a Mozilla-based browser (such as Firefox) to install a search plugin.” Expected results: The search plugin should install normally.

I tried to download the search plugin (which is in XML format) in order to install it from my HD, but that doesn't work either. Apparently some extra magic (unknown to me) is needed.

N.B. "Google Search link fix" 1.4.6 had just been installed. Don't know if relevant.

Problem happens also in Safe Mode (after "Help → Restart with Add-ons Disabled").

does that mean that bug 1051862 is the root cause of this issue? If so, we should close this bug as duplicate, what do you think :tonymec?

(In reply to Mathieu Agopian [:magopian] from comment #4) > does that mean that bug 1051862 is the root cause of this issue? If so, we > should close this bug as duplicate, what do you think :tonymec? Completely different issues.

(In reply to Mathieu Agopian [:magopian] from comment #4) > does that mean that bug 1051862 is the root cause of this issue? If so, we > should close this bug as duplicate, what do you think :tonymec? I don't know. Mycroft is on Mozdev; OTOH the kind of language used in the error alert made me think of a server-side error at AMO (which is supposed to serve Firefox, Thunderbird and SeaMonkey equally but in practice strongly favours the former) rather than a client-side error (SeaMonkey saying that it is not Mozilla-based? Are you kidding?). OTOH bug 1051862 has a developer-oriented description ("this and that has changed in the code") while this one has a user-oriented one ("when I do this, I get an error alert with that text") which makes them dificult to compare. Finally, bug 1051861 was reported for the SeaMonkey Sidebar component (which I don't use): I was trying to add a search engine to the admittedly already long list of engines in the Search box on my Navigation toolbar (after customization from the button palette). For all these reasons I have linked these bugs by "See Also" (both are for inability to add search engines, albeit from different servers) rather than by a more direct relation such as Blocks/Depends or Duplicate. But I am not a specialist of this kind of distinction. I leave the actual evaluation (and resolution, if possible) to the AMO team if server-side, or to the Toolkit::AddonsManager team (or to whoever is responsible for managing search engines) if client-side. If this bug disappears once Neil fixes bug 1051862 I may change my mind a posteriori.

oops: s/1051861/1051862/

Bug 1051862 is fixed. Are you still seeing "Sorry, you need a Mozilla-based browser ..." ?

(In reply to Philip Chee from comment #8) > Bug 1051862 is fixed. Are you still seeing "Sorry, you need a Mozilla-based > browser ..." ? Test 1: With today's build from https://l10n.mozilla-community.org/~akalla/unofficial/seamonkey/nightly/latest-comm-central-linux64/?C=M\&O=D Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32a1 ID:20140911102607 c-c:17422c1f7444 m-c:bc7deafdac4b - The green "Add to SeaMonkey" button has been replaced by a blue "Download Now" button. - Left-clicking that blue buton does nothing. - Right-clicking, then "Save Link Target As" saves to disk as an XML file - But how am I to install it as a search plugin? - Left-clicking it in its file:///something/ directory only displays its source - about:addons has no "search plugins" tab, and the "Get more engines" link on the "Manage search plugins" item of the search bar rolldown only opens the AMO search plugins page in a tab… where each plugin has a blue "Download Now" button, which does nothing on left-click, and downloads a (useless AFAIK) XML file on right-click→Save Link Target As - Unlike what happens on Bugzilla pages (where it proposes to add "Bugzilla@Mozilla), the search bar's rolldown ha

…s no "Add" menuitem when browsing the search plugin's AMO page

Test 2: Same build as in comment #9 above, but in Safe Mode. No change (including the behaviour of the search bar, after "customizing" it back from the button palete onto a toolbar).

Test 3: In the latest "official" nightly from ftp://ftp.mozilla.org/pub/seamonkey/latest-comm-central-trunk/ Mozilla/5.0 (X11; Linux x86_64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32a1 ID:20140903003005 c-c:4f47656aa273 m-c:e58842c764dd No change.

Test 4: Same build as in comment #12 above, but in Safe Mode. No change. Only difference I notice: in tests 2 and 4 the XML is downloaded with the current datetime, in tests 1 and 3 with its own timestamp, probably due to the action of the "Preserve Download Modification Timestamp" extension. Same number of bytes in all cases. Conclusion: The popup has disappeared, but AFAICT there is still no way to add a search engine from AMO. (The Bugzila search engine _can_ be installed from a bug page, by scrolling the search bar rolldown [almost] all the way to the bottom.) I suppose this bug's Summary should be edited, but I'm not sure how. See comment #9 for a description of the new symptoms. I'll attach a stdout/stderr log from these 4 test runs (possibly with something else before). No idea if useful.

P.S. "I suppose this bug's Summary should be edited, but I'm not sure how." -- I mean: I know how to do it, but I'm not sure what the new text should be.

Related with bug 1065237 ?

Thanks for filing this. Due to resource constraints we are closing bugs which we won't realistically be able to fix. If you have a patch that applies to this bug please reopen. For more info see http://micropipes.com/blog/2014/09/24/the-great-add-on-bug-triage/

Problem has disappeared. Maybe bug 1051862 fixed it, I'm not competent to decide.

P.S. This is the build where I tried to reproduce the bug and couldn't: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33a1 ID:20141016003005 c-c:6300e54fef35 m-c:a280a03c9f3c