Closed Bug 1647576 Opened 5 years ago Closed 5 years ago

Address bar in Nightly 79.0a1 (2020-06-20) on Ubuntu not responding to input

Categories

(Firefox :: Search, defect)

Product:
Firefox
Component:
Search
Version:
79 Branch
Type:
defect

Tracking

()

Status:
RESOLVED MOVED

People

(Reporter: vmarsi75-bugzilla, Unassigned)

References

Details

(Whiteboard: [ubuntu build issue])

Attachments

(4 files)

aboutsupport.txt
26.86 KB, text/plain
Details
no_search_options.png
44.78 KB, image/png
Details
Browser Console Log
13.69 KB, text/plain
Details
Browser Console Log
13.69 KB, text/plain
Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0

Steps to reproduce:

  1. Open Firefox Nightly (79.0a1, 2020-06-20) on Ubuntu
  2. Type website url or search term in address bar
  3. Press <Enter> or click on the Go button

Actual results:

Nothing happens

Expected results:

The browser should have navigated to the website or searched for the term using the configured search engine

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Component: Untriaged → Address Bar

Looks like adding the protocol portion of the url (http/https), makes it navigate properly. So typing mozilla.org doesn't do anything, but typing https://mozilla.org navigates properly.

I'm having the same issue. Also, the bar doesn't auto complete from any source (history, bookmarks, opened tabs), and the contextual menu on web page elements is completely broken (not sure there's a link though).

Adding the protocol works for me too (thanks for the tip by the way!).

I have the same issue.

I tried creating and using a new profile : everything worked fine. I added my usual extensions : still ok.

Then closed and reopened nightly : issue reappeared.

I'm having the same issue. I had it for the last two days and reported it with the Firefox Nightly menu help -> Submit Feedback feature. I just got another update to 79.0~a1~hg20200623r536655 and the problem is still present.

I've been using Nightly on Ubuntu as my main browser for about four years and this is the first bug I've hit, so kudos to the contributors for maintaining such a high level of quality.

I did some digging, and under Preferences -> Search I have no search providers listed and no option to add them. I'm sure this is related to the problem.

Also having this issue for the last two days. Affects both the address bar and the search bar.

Full Firefox Version: Mozilla Firefox 79.0a1 20200623173421 20200623173421
OS Information: Linux Mint 19.3, Kernel 5.3.0-7648-generic

Hi Ravi

I tried to reproduce on Ubuntu 18.04 64 bit with Firefox Nightly 79.0a1, 2020-06-20. When i launch firefox i can navigate to the websites, and if search any word it gives me a google search.

Can you got to about:support , then copy the text to clipboard and attach to the bug?
Also can you provide a list of addons you are using?

Also please try with a new profile?
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

thanks.

Flags: needinfo?(vmarsi75-bugzilla)

Hello Pablo,
I know I am not Ravi, but I am experiencing the same bug. I am in Ubuntu MATE 20.04 64 bit with Firefox Nightly 79.0a1, 2020-06-23 (but I also experienced the bug with 2020-06-20).

If I launch Firefox Nightly with a new profile, everything works fine.
If I launch Firefox Nightly with my previous profile and all add-ons disabled, the bug still manifests.

Again, I think this is related to the fact that the Preferences for Search seem to be broken.
I will attach my about:settings and a screenshot of the search preference.

Attached file aboutsupport.txt —
Attached image no_search_options.png —

Please note how the dropdown for "Default Search Engine" in the screenshot has no content.

Thanks mike. I tried again on ubuntu18 using the same region as you on Nightly from 2020-06-20 , launched and it worked on my computer.
Started to install the addons that you have like bitwarden, ecosia, privacy badger, video downloadhelper and qwant and it still worked.
I updated firefox and worked as usual and also restarted it and worked.

My default engine was always google, did you have any other default engine? Do you remember what other settings you had in search? (the ones below , looking at the image on comment #11)

Flags: needinfo?(mike.swierczek)

I had switched my engine to Ecosia.org (a Bing wrapper that - at least in theory - uses ad revenue to fund ecological causes). Ecosia worked for me for years.

I added Ecosia to my second all-default profile by navigating to https://ecosia.org and following the prompts, and after a browser restart the address bar search feature stopped working.

I deleted that profile, created a second new profile, changed the search to DuckDuckGo, restarted the browser, and search worked.

In my second new profile, changed the search engine to Ecosia again by adding it through the Firefox add-ons page, restarted the browser, and the address bar search feature stopped working again. I removed the add-on completely and restarted, but search in the address bar doesn't work and the search option in preferences remains disabled.

So there must be something in the Ecosia add-on that is a problem, and I'll try to contact their maintainers. But removing the add-on should fix the profile, right? Is that a Firefox bug?

Thanks for your help.

Flags: needinfo?(mike.swierczek)

I suspect this problem is due to a broken search settings file

Component: Address Bar → Search

Please can someone who can reproduce the issue do this please:

  • Start Firefox Nightly,
  • Go to the Three-bar menu -> Web Developer -> Browser console (not Web Console) and attach a copy of the output to this bug please?

If you're able to set browser.search.log to true in prefs.js in the profile, or via about:config, before invoking the failing mode, that'd be useful as well. In the meantime I'll try and reproduce this.

It may also be useful to get a copy of search.json.mozlz4 from your profile (when this is broken).

I'm very happy that my report was marked as a duplicate, because I thought I'm the only one.

Here is the output of the Browser console:

2147500037
uncaught exception: 2147500037

browser.search.log is turned on. The second line was thrown on every key input.

Is this useful for you?

Ah, when I type the protocol, e.g. https://google.com and hit enter, I get a traceback, which looks related:

2147500037 AboutReaderParent.jsm:210
    updateReaderButton resource:///actors/AboutReaderParent.jsm:210
    updateReaderButton resource:///actors/AboutReaderParent.jsm:170
    onLocationChange chrome://browser/content/browser.js:5291
    callListeners chrome://browser/content/tabbrowser.js:818
    _callProgressListeners chrome://browser/content/tabbrowser.js:832
    _callProgressListeners chrome://browser/content/tabbrowser.js:5810
    onLocationChange chrome://browser/content/tabbrowser.js:6228

(In reply to pursche from comment #18)

2147500037
uncaught exception: 2147500037

Is this useful for you?

Please can you try capturing the entire log from startup, that is where the initial error that will be that will likely tell us the actual issue?

You should be able to copy/paste as an attachment.

Also, do you have Ecosia or some other add-on installed which changes the default search engine?

Flags: needinfo?(pursche)
Attached file Browser Console Log —
(In reply to Mark Banner (:standard8) from comment #20) > (In reply to pursche from comment #18) > > ``` > > 2147500037 > > uncaught exception: 2147500037 > > ``` > > Is this useful for you? > > Please can you try capturing the entire log from startup, that is where the initial error that will be that will likely tell us the actual issue? > > You should be able to copy/paste as an attachment. > > Also, do you have Ecosia or some other add-on installed which changes the default search engine? This is the complete output after launching and typing https://google.com and hitting enter:
Attached file Browser Console Log —
(In reply to Mark Banner (:standard8) from comment #20) > (In reply to pursche from comment #18) > > ``` > > 2147500037 > > uncaught exception: 2147500037 > > ``` > > Is this useful for you? > > Please can you try capturing the entire log from startup, that is where the initial error that will be that will likely tell us the actual issue? > > You should be able to copy/paste as an attachment. > > Also, do you have Ecosia or some other add-on installed which changes the default search engine? This is the complete output after launching and typing https://google.com and hitting enter: ```

(In reply to Mark Banner (:standard8) from comment #20)

(In reply to pursche from comment #18)

2147500037
uncaught exception: 2147500037

Is this useful for you?

Please can you try capturing the entire log from startup, that is where the initial error that will be that will likely tell us the actual issue?

You should be able to copy/paste as an attachment.

This is the complete output after launching and typing https://google.com and hitting enter:

(Unfortunately I can't upload it as an attachment - the dialog throws an unexpected error)

[Exception... "Component returned failure code: 0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsICommandLine.handleFlagWithParam]"  nsresult: "0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame :: resource:///modules/BrowserContentHandler.jsm :: bch_handle :: line 415"  data: no] BrowserContentHandler.jsm:415:34
Warning: unrecognized command line flag -new-window
BrowserContentHandler.jsm:989
Error while loading 'jar:file:///usr/lib/firefox-trunk/browser/omni.ja!/chrome/browser/search-extensions/twitter/manifest.json' (NS_ERROR_FILE_NOT_FOUND) Extension.jsm:570
1593014931848	addons.xpi	WARN	Exception running bootstrap method startup on twitter@search.mozilla.org: Error: Error while loading 'jar:file:///usr/lib/firefox-trunk/browser/omni.ja!/chrome/browser/search-extensions/twitter/manifest.json' (NS_ERROR_FILE_NOT_FOUND)(resource://gre/modules/Extension.jsm:570:20) JS Stack trace: readJSON/</<@Extension.jsm:570:20
onStopRequest@NetUtil.jsm:128:18
SearchService: addEnginesFromExtension: bing@search.mozilla.org SearchService.jsm:2343:16
SearchService: addEnginesFromExtension: ddg@search.mozilla.org SearchService.jsm:2343:16
SearchService: addEnginesFromExtension: amazondotcom@search.mozilla.org SearchService.jsm:2343:16
SearchService: addEnginesFromExtension: ebay@search.mozilla.org SearchService.jsm:2343:16
SearchService: addEnginesFromExtension: google@search.mozilla.org SearchService.jsm:2343:16
SearchService: addEnginesFromExtension: wikipedia@search.mozilla.org SearchService.jsm:2343:16
SearchService: addEnginesFromExtension: Ignoring builtIn engine. 6 SearchService.jsm:2357:18
SearchService: init SearchService.jsm:2141:16
[Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIAppStartup.secondsSinceLastOSRestart]"  nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)"  location: "JS frame :: resource:///modules/BrowserGlue.jsm :: _collectStartupConditionsTelemetry :: line 1665"  data: no] BrowserGlue.jsm:1665:9
SearchService: init SearchService.jsm:2141:16
Unknown category for SetEventRecordingEnabled: fxmonitor
SearchService: _loadEngines: start SearchService.jsm:920:16
SearchService: Finding engine configuration from the selector SearchService.jsm:1654:16
SearchService: init 2 SearchService.jsm:2141:16
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 2
SearchEngineSelector: fetchEngineConfiguration en-US:DE:nightly:canonical:null:firefox:79.0a1 SearchEngineSelector.jsm:186:16
SearchService: _loadEnginesFromConfig SearchService.jsm:1100:16
SearchEngineSelector: fetchEngineConfiguration: google@search.mozilla.org,amazondotcom@search.mozilla.org,wikipedia@search.mozilla.org,bing@search.mozilla.org,ddg@search.mozilla.org SearchEngineSelector.jsm:304:18
SearchService: makeEngineFromConfig: 
Object { params: {…}, schema: 1588177680286, extraParams: (1) […], telemetryId: "google-b-d", webExtension: {…}, id: "cb8e7210-9f0b-48fa-8708-b9a03df79eea", last_modified: 1589299342048, default: "yes-if-no-other" }
SearchService.jsm:2403:16
SearchService: makeEngineFromConfig: 
Object { params: {…}, schema: 1588177681875, telemetryId: "amazondotcom", webExtension: {…}, id: "071c671c-7c1b-469d-a771-ab16ff6e8beb", last_modified: 1589299342052 }
SearchService.jsm:2403:16
SearchEngine: _setIcon: Setting icon url for Google to moz-extension://61b578d0-5f8a-43a5-8950-a69eb91e5b93/favicon.ico SearchEngine.jsm:1301:16
SearchService: makeEngineFromConfig: 
Object { schema: 1588177692141, webExtension: {…}, id: "3f3beb1d-e32e-40a4-b6ed-56741803e1d8", last_modified: 1589299342069 }
SearchService.jsm:2403:16
SearchEngine: _setIcon: Setting icon url for Amazon.com to moz-extension://e9459fa2-f98d-4b4f-a140-25abc00c8688/favicon.ico SearchEngine.jsm:1301:16
SearchEngine: _setIcon: Setting icon url for Wikipedia (en) to moz-extension://3b3a894f-d2a2-4570-8420-761f90031568/favicon.ico SearchEngine.jsm:1301:16
SearchService: makeEngineFromConfig: 
Object { params: {…}, schema: 1588177678403, extraParams: (5) […], webExtension: {…}, id: "7ec766f6-639a-4618-91bc-33eb3d4378c6", last_modified: 1589299342045 }
SearchService.jsm:2403:16
SearchService: makeEngineFromConfig: 
Object { schema: 1588177690190, extraParams: (5) […], telemetryId: "ddg", webExtension: {…}, id: "c0b26c0e-63e6-4235-b2ce-5f16b6a8bf87", last_modified: 1589299342065 }
SearchService.jsm:2403:16
SearchEngine: _setIcon: Setting icon url for Bing to moz-extension://40ddf622-d818-4076-b58d-1e07ca01adab/favicon.ico SearchEngine.jsm:1301:16
SearchEngine: _setIcon: Setting icon url for DuckDuckGo to moz-extension://9c8da3d2-dc60-42c8-9c4c-9a2a15831de8/favicon.ico SearchEngine.jsm:1301:16
SearchService: _addEngineToStore: Adding engine: Google SearchService.jsm:1461:16
SearchService: _addEngineToStore: Adding engine: Amazon.com SearchService.jsm:1461:16
SearchService: _addEngineToStore: Adding engine: Wikipedia (en) SearchService.jsm:1461:16
SearchService: _addEngineToStore: Adding engine: Bing SearchService.jsm:1461:16
SearchService: _addEngineToStore: Adding engine: DuckDuckGo SearchService.jsm:1461:16
SearchService: _loadEngines: loading 0 engines reported by AddonManager startup SearchService.jsm:968:16
SearchService: _loadEnginesFromCache: Loading 5 engines from cache SearchService.jsm:1551:16
SearchService: _init: failure initializing search: ReferenceError: skipBuiltIn is not defined
    _loadEnginesFromCache resource://gre/modules/SearchService.jsm:1566
    _loadEngines resource://gre/modules/SearchService.jsm:982
SearchService.jsm:563:18
SearchService: _ensureInitialized: failure SearchService.jsm:473:20
SearchService: Completed _init SearchService.jsm:577:16
uncaught exception: 2147500037
NS_ERROR_FAILURE: SearchService previously failed to initialize SearchService.jsm:474
uncaught exception: 2147500037 2
Uncaught (in promise) 
Exception { name: "NS_ERROR_FAILURE", message: "SearchService initialization failed", result: 2147500037, filename: "resource://gre/modules/SearchService.jsm", lineNumber: 2164, columnNumber: 0, data: null, stack: "init@resource://gre/modules/SearchService.jsm:2164:24\n", location: XPCWrappedNative_NoHelper }
SearchService.jsm:2164
SearchService: init 2 SearchService.jsm:2141:16
uncaught exception: 2147500037 2
SearchService: _handleIgnoreListUpdated SearchService.jsm:614:16
NS_ERROR_FAILURE: Should pass a non-null uri 2 URIFixup.jsm:281
primed listener not re-registered 4 ExtensionCommon.jsm:2299
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified
can't access property "getService", Cc[aContract] is undefined XPCOMUtils.jsm:215
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). injectGlobalHook.js:1:1760
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). content-script.js:3172:10
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). pagewrap.bundle.js:1:1151
Error: Invalid argument injectGlobalHook.js:1:5404
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). pagewrap.bundle.js:1:1151
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). content-script.js:3172:10
Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). injectGlobalHook.js:1:1760
Error: Invalid argument injectGlobalHook.js:1:5404
Unchecked lastError value: Error: ID already exists: /org/gnome/Shell/Extensions/GSConnect/Device/be2ec35a5e30afb1 ExtensionCommon.jsm:765
Unchecked lastError value: Error: ID already exists: /org/gnome/Shell/Extensions/GSConnect/Device/be2ec35a5e30afb1:share ExtensionCommon.jsm:765
Unchecked lastError value: Error: ID already exists: /org/gnome/Shell/Extensions/GSConnect/Device/be2ec35a5e30afb1:telephony ExtensionCommon.jsm:765
Unchecked lastError value: Error: ID already exists: /org/gnome/Shell/Extensions/GSConnect/Device/be2ec35a5e30afb1 ExtensionCommon.jsm:765
Unchecked lastError value: Error: ID already exists: /org/gnome/Shell/Extensions/GSConnect/Device/be2ec35a5e30afb1:share ExtensionCommon.jsm:765
GEThttps://bugzilla.mozilla.org/static/v20200603.1/skins/standard/fonts/FiraMono-Regular.woff2?v=3.202
[HTTP/1.1 404 Not Found 0ms]

Unchecked lastError value: Error: ID already exists: /org/gnome/Shell/Extensions/GSConnect/Device/be2ec35a5e30afb1:telephony ExtensionCommon.jsm:765
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. show_bug.cgi
GEThttps://bugzilla.mozilla.org/static/v20200603.1/skins/standard/fonts/FiraSans-Bold.woff2?v=4.203
[HTTP/1.1 404 Not Found 0ms]

GEThttps://bugzilla.mozilla.org/static/v20200603.1/skins/standard/fonts/FiraSans-Italic.woff2?v=4.203
[HTTP/1.1 404 Not Found 0ms]

GEThttps://bugzilla.mozilla.org/static/v20200603.1/skins/standard/fonts/FiraSans-Regular.woff2?v=4.203
[HTTP/1.1 404 Not Found 0ms]

GEThttps://bugzilla.mozilla.org/static/v20200603.1/skins/standard/fonts/FiraSans-SemiBold.woff2?v=4.203
[HTTP/1.1 404 Not Found 0ms]

JQMIGRATE: Migrate is installed, version 1.4.1 main.js:565:531
$ is deprecated: The global jQuery is deprecated. It will be updated to v2.4 in Nextcloud 20 and v3.x in Nextcloud 21. In later versions of Nextcloud it might be removed completely. Please ship your own. 2 main.js:1020:3628
Handlebars is deprecated: please ship your own, this will be removed in Nextcloud 20 main.js:1020:3628
$ is deprecated: The global jQuery is deprecated. It will be updated to v2.4 in Nextcloud 20 and v3.x in Nextcloud 21. In later versions of Nextcloud it might be removed completely. Please ship your own. 3 main.js:1020:3628
Notifications permissions granted notifications.js:14:337495
jQuery is deprecated: The global jQuery is deprecated. It will be updated to v2.4 in Nextcloud 20 and v3.x in Nextcloud 21. In later versions of Nextcloud it might be removed completely. Please ship your own. main.js:1020:3628
$ is deprecated: The global jQuery is deprecated. It will be updated to v2.4 in Nextcloud 20 and v3.x in Nextcloud 21. In later versions of Nextcloud it might be removed completely. Please ship your own. main.js:1020:3628
a11y.sitezoom - Unknown scalar.
Initial settings: 
Object { appVersion: "2.0.3", eventLimit: true, firstRun: true, showWeekends: true, showWeekNumbers: false, skipPopover: true, slotDuration: "00:30:00", talkEnabled: true, timezone: "automatic" }
calendar.js:2:2964568
[DEBUG] calendar: The calendar app is using version 2.2019c of the timezone database 
Object { app: "calendar", uid: "authenticated:gustav" }
calendar.js:2:2029245
Request to connect to ProcessDescriptor "111030" failed: Error: Connection closed, pending request to server1.conn0.content-process3881/console2, type startListeners failed

Request stack:
request@resource://devtools/shared/protocol/Front.js:256:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol/Front/FrontClassWithSpec.js:47:19
startListeners@resource://devtools/client/fronts/webconsole.js:526:34
attachConsole@resource://devtools/client/fronts/targets/target-mixin.js:457:26
process.js:81:17
uncaught exception: target was destroyed
falling back to english locale calendar.js:2:2665005
Fallback to locale en calendar.js:2:2653880
session heartbeat polling started main.js:489:963
$ is deprecated: The global jQuery is deprecated. It will be updated to v2.4 in Nextcloud 20 and v3.x in Nextcloud 21. In later versions of Nextcloud it might be removed completely. Please ship your own. 3 main.js:1020:3628
[DEBUG] calendar: Current user principal is /remote.php/dav/principals/users/gustav/ 
Object { app: "calendar", uid: "authenticated:gustav" }
calendar.js:2:2029245
$ is deprecated: The global jQuery is deprecated. It will be updated to v2.4 in Nextcloud 20 and v3.x in Nextcloud 21. In later versions of Nextcloud it might be removed completely. Please ship your own. main.js:1020:3628
Key event not available on some keyboard layouts: key=“r” modifiers=“accel,alt” id=“key_toggleReaderMode” browser.xhtml
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml
SearchService: init SearchService.jsm:2141:16
2147500037
SearchService: init SearchService.jsm:2141:16
2147500037 AboutReaderParent.jsm:210
SearchService: init SearchService.jsm:2141:16
2147500037 AboutReaderParent.jsm:210
SearchService: init SearchService.jsm:2141:16
2147500037 AboutReaderParent.jsm:210
[Exception... "Component returned failure code: 0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH) [nsIXPCComponents_Utils.readUTF8URI]"  nsresult: "0x80520001 (NS_ERROR_FILE_UNRECOGNIZED_PATH)"  location: "JS frame :: resource://gre/modules/L10nRegistry.jsm :: L10nRegistry.loadSync :: line 658"  data: no] L10nRegistry.jsm:658:19
Cookie “1P_JAR” has “sameSite” policy set to “lax” because it is missing a “sameSite” attribute, and “sameSite=lax” is the default value for this attribute. www.google.com:132:405
SearchService: init SearchService.jsm:2141:16
uncaught exception: 2147500037
uncaught exception: 2147500037
uncaught exception: 2147500037
uncaught exception: 2147500037
uncaught exception: 2147500037
uncaught exception: 2147500037 3
uncaught exception: 2147500037
uncaught exception: 2147500037 14
SearchService: init SearchService.jsm:2141:16
2147500037 AboutReaderParent.jsm:210
Cookie “1P_JAR” has “sameSite” policy set to “lax” because it is missing a “sameSite” attribute, and “sameSite=lax” is the default value for this attribute.

Also, do you have Ecosia or some other add-on installed which changes the default search engine?

I think I had duckduckgo as my default and might have installed it in the past, but as mentioned above: my search engines list is empty too so I can't see there anything now.

Thank you for the logs everyone. This is an issue with the Ubuntu distribution, I suspect it therefore affects Linux Mint as well.

Here's the critical error:

SearchService: _init: failure initializing search: ReferenceError: skipBuiltIn is not defined
    _loadEnginesFromCache resource://gre/modules/SearchService.jsm:1566
    _loadEngines resource://gre/modules/SearchService.jsm:982

The issue is a patch that is being applied by the distribution that is no longer required and breaks the startup of the search service completely. I am currently filing a distribution bug about this.

Flags: needinfo?(vmarsi75-bugzilla)
Flags: needinfo?(pursche)
Whiteboard: [ubuntu build issue]

We have now logged this in Ubuntu's tracker: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885006

Please track the issue there.

On a slightly separate note, I've just filed bug 1648188 to investigate seeing if we can leave some of the browser usable if the search service fails to initialise. Whilst it shouldn't happen in normal practice, it would be better to be safer if we can.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → MOVED
See Also: → https://launchpad.net/bugs/1885006

(In reply to Mark Banner (:standard8) from comment #26)

We have now logged this in Ubuntu's tracker: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1885006

Please track the issue there.

On a slightly separate note, I've just filed bug 1648188 to investigate seeing if we can leave some of the browser usable if the search service fails to initialise. Whilst it shouldn't happen in normal practice, it would be better to be safer if we can.

I can confirm, that the fix from launchpad works for me. Thanks a lot. In 3 days from report to fix is amazing. <3

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: