suddenly google search engine reappeared and overwrote my duckduckgo default
Categories
(Firefox :: Search, defect, P5)
Tracking
()
People
(Reporter: blackbrand, Unassigned)
Details
Steps to reproduce:
I started firefox, typed in the address bar to search
firefox has been updated recently to 117
Actual results:
i ended up on google instead of duckduckgo.
-I had removed google and all other search engines
-I had duckduckgo as my default
i checked my search settings and google was there again, plus it suddenly was the default..
This leads to data leaking to engines for which that data is not intended and is a privacy issue considering certain companies 'kuch' fine records on this matter
Expected results:
-google should never be added once removed
-default search engine should NEVER change without user input.
|
Reporter | |
Comment 1•8 months ago
|
||
only data in search shortcuts, before firefox changed them without user consent:
-duckduckgo
-bookmarks
-tabs
-history
-actions (disabled/no checkmark?)
|
||
Comment 2•8 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Search' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 3•8 months ago
|
||
We have seen in the past that installing third party software may affect Firefox's search engine settings. Firefox will then sometimes revert to the default search engine because it detects this, but it has no idea what your previous default was (because that was overwritten by the third party).
Is it possible that you've installed software recently? If so, checking with something like MalwareBytes should detect it and remove it.
none, firefox was the only thing that updated that week.
Have not installed new software either. Didn't download any exe/dll etc either.
It was right after firefox updated from 116 to 117
also google was the only returning search engine.
windows defender scan did not detect any threats
|
|
||
Comment 5•8 months ago
|
||
I don't see anything that we changed in 117 that might have caused this, and I haven't seen any other reports of this. Whilst we have seen things in the past, it has normally been due to third party software, or other issues that we have fixed.
Hence setting as low priority until we get more reports, or we have clear steps to repeat.
|
||
Comment 6•6 months ago
|
||
Adding the qa not actionable tag for now, We tried to reproduce this issue on our end using different update methods for Firefox but I couldnt reproduce it yet. We will try again when more information is provided, maybe some steps that would cause this issue.
Description
•