Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Problem accessing the secondary search engines under V129.0.

  • Ingen svar
  • 0 har dette problem
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.

Du skal logge ind på din konto for at svare på et indlæg. Start et nyt spørgsmål, hvis du ikke har en konto endnu.