Ko tenda hembiapoite sa’ivéta oñemba’apokuévo hese hembiapo porãve hag̃ua. Peteĩ jehaipyre nomoĩporãiramo ne apañuái ha eporanduséramo, roguerekohína ore nepytyvõ rekoha ikatútava ndeykeko @FirefoxSupport Twitter-pe ha avei /r/firefox Reddit-pe.

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Problem accessing the secondary search engines under V129.0.

  • Mbohavai’ỹre
  • 0 oguereko ko apañuãi
more options

Running macOS 14.6.1 with Firefox V129.0.2.

Since I upgraded Firefox either to 129.0 or 129.0.1 (I didn't notice the issue immediately), it seems I can't access anymore any of the secondary search engines that appear when you click on the search windows. The default search engine is DuckDuckGo and, if I wish to ask it something, it is still correctly answers. However, if I want to ask to one of the secondary search engines (for example, Google, or the French or English Wikipedia), clicking on the icon of this engine doesn't produce any result anymore.

Please note that I also upgraded from macOS Sonoma 14.5 to 14.6.1 at approximately the same time I upgraded Firefox to 129.0.1. No idea if this has any bearing on the issue.

Is this a known issue? And, if not, has anybody any idea on how to troubleshoot it?

Thanks for any help, Denis Maillard.

Running macOS 14.6.1 with Firefox V129.0.2. Since I upgraded Firefox either to 129.0 or 129.0.1 (I didn't notice the issue immediately), it seems I can't access anymore any of the secondary search engines that appear when you click on the search windows. The default search engine is DuckDuckGo and, if I wish to ask it something, it is still correctly answers. However, if I want to ask to one of the secondary search engines (for example, Google, or the French or English Wikipedia), clicking on the icon of this engine doesn't produce any result anymore. Please note that I also upgraded from macOS Sonoma 14.5 to 14.6.1 at approximately the same time I upgraded Firefox to 129.0.1. No idea if this has any bearing on the issue. Is this a known issue? And, if not, has anybody any idea on how to troubleshoot it? Thanks for any help, Denis Maillard.

Nde eikéke nde mba’etepe embohovái hag̃ua ñe’ẽmondo. Ikatúpa, emoñepyrũ peteĩ porandu, ndereguerekói gueteriramo nemba’ete.