1467032 - Search from address bar and search settings doesn't work

Status: RESOLVED DUPLICATE of bug 1467040

(Firefox :: Search, defect)

Description

[Sherzod Mutalov]

Attachment: firefox_search_bug_search_settings_01.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180605220158

Steps to reproduce:

1) Typing search keywords in address bar does'nt show suggestions. Pressing [Enter] causes no reaction. Nothing happens. Creating new tab and pasting text to search with pressing [Enter] causes "infinity loop", nothing searched or downloaded.

2) Search settings doesn't open. Open Firefox Settings and choose "Search" category. It will not show you actual search settings and keeps last opened category.

Firefox Nightly: 62.0a1 (2018-06-05) (64-бит)
OS: Debian Sid, 4.16.0-2-amd64 #1 SMP Debian 4.16.12-1 (2018-05-27) x86_64 GNU/Linux



Actual results:

1) Nothing. Search was not done by Firefox.

2) Search settings doesn't open


Expected results:

1) Firefox loads page with default search engine and shows search results

2) Search settings appeared to configure

Comment 1

[Pascal Chevrel (relman team) -> :pascalc]

Thanks Sherzod confirmed with  Mozilla/5.0 (X11; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 ID:20180605220158

Comment 2

[Pascal Chevrel (relman team) -> :pascalc]

mozregression is of no use since it seems to only affect localized builds :/

There is no search engine listed in preferences for the locales I tested (fr and es-ES), en-US is not affected and still has search engines

Flod -> FYI.
Lizz, I set this as a blocker for 62

Comment 3

[Pascal Chevrel (relman team) -> :pascalc]

Bug 1437942 landed last night, the description makes it a potential suspect.

Mike,can you investigate please?

Comment 4

[Pascal Chevrel (relman team) -> :pascalc]

Tested in a Windows 10 VM and this is is not a Linux-only bug.

Comment 5

[Seo Suchan]

this only happens at and only at the last build, as I use nightly as main and it started when I updated it to current build.
windows 10/ korean

Comment 6

[KiYugadgeter]

Also search bar on new tab page is not work on my environment. 

Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0 (2018-06-05)

Comment 7

[Axel Hecht [:Pike]]

from German mac browser console:

 [Mitteilungsdetails anzeigen/ausblenden] TypeError: currentEngine is null[Weitere Informationen]
search.xml:957:15
[Mitteilungsdetails anzeigen/ausblenden] Error: Expected an engine to be specified browser.js:3920:13
[Mitteilungsdetails anzeigen/ausblenden] [Exception... "[JavaScript Error: "Expected an engine to be specified" {file: "chrome://browser/content/browser.js" line: 3920}]'[JavaScript Error: "Expected an engine to be specified" {file: "chrome://browser/content/browser.js" line: 3920}]' when calling method: [nsIBrowserSearchInitObserver::onInitComplete]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsSearchService.js :: onSuccess :: line 3706"  data: yes]
TypeError: Services.search.currentEngine is null[Weitere Informationen] BrowserUITelemetry.jsm:556:7
[Mitteilungsdetails anzeigen/ausblenden] [Exception... "[JavaScript Error: "Services.search.currentEngine is null" {file: "resource:///modules/BrowserUITelemetry.jsm" line: 556}]'[JavaScript Error: "Services.search.currentEngine is null" {file: "resource:///modules/BrowserUITelemetry.jsm" line: 556}]' when calling method: [nsIBrowserSearchInitObserver::onInitComplete]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsSearchService.js :: onSuccess :: line 3706"  data: yes]
[Mitteilungsdetails anzeigen/ausblenden] Error: Expected an engine to be specified browser.js:3920:13
[Mitteilungsdetails anzeigen/ausblenden] [Exception... "[JavaScript Error: "Expected an engine to be specified" {file: "chrome://browser/content/browser.js" line: 3920}]'[JavaScript Error: "Expected an engine to be specified" {file: "chrome://browser/content/browser.js" line: 3920}]' when calling method: [nsIBrowserSearchInitObserver::onInitComplete]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsSearchService.js :: onSuccess :: line 3706"  data: yes]
[Mitteilungsdetails anzeigen/ausblenden] engine is null
ContentSearch.jsm:511
TypeError: Services.search.defaultEngine is null[Weitere Informationen] SnippetsFeed.jsm:80:13
[Mitteilungsdetails anzeigen/ausblenden] [Exception... "[JavaScript Error: "Services.search.defaultEngine is null" {file: "resource://activity-stream/lib/SnippetsFeed.jsm" line: 80}]'[JavaScript Error: "Services.search.defaultEngine is null" {file: "resource://activity-stream/lib/SnippetsFeed.jsm" line: 80}]' when calling method: [nsIBrowserSearchInitObserver::onInitComplete]"  nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)"  location: "JS frame :: jar:file:///Applications/FirefoxNightly.app/Contents/Resources/omni.ja!/components/nsSearchService.js :: onSuccess :: line 3706"  data: yes]
UTM:SVC TimerManager:registerTimer - id: recipe-client-addon-run
[Mitteilungsdetails anzeigen/ausblenden] TypeError: this.defaultEngine is undefined contentSearchUI.js:624:5
Content Security Policy: 'x-frame-options' wird wegen 'frame-ancestors'-Direktive ignoriert.
[Mitteilungsdetails anzeigen/ausblenden] TypeError: this.defaultEngine is undefined contentSearchUI.js:624:5

Comment 8

[Anthony B]

I confirm the issue is there on OSX 10.13 too since the last build (62.0a1 (2018-06-05) (64 bits)).

The search bar has an unexpected behaviour, sometimes when typing and hitting <enter> nothing happens,
some other times it tries to search a domain by adding "https://".

It seems I've lost my search engines too.

Comment 9

[Francesco Lodolo [:flod]]

Bug 1437942 has been backed out, and that should be the cause of this bug.

Even if counterintuitive, I'll dupe this against bug 1467040, which reported the same issue.

Comment 10

[Hunsu]

I don't know if it is related but the open in new tab doesn't work either.

Comment 11

[Pascal Chevrel (relman team) -> :pascalc]

(In reply to Hunsu from comment #10)
> I don't know if it is related but the open in new tab doesn't work either.

it is related, we have backed out the patch and produced new nightlies without these bugs (update :) )

Comment 12

[Liz Henry (:lizzard)]

Fixed in bug 1467040.