Debian's Chromium changes default search engine to DDG
mail-archive.com
Debian's Chromium changes default search engine to DDG
1–10 of 222 posts
Re: Debian's Chromium changes default search engine to DDG
#2Some unintended consequences:
> This change caused my chromium browser to report that it's being managed by my "organization". I thought that my machine was somehow compromised. This is terrifying! I wound up deleting my entire chromium profile before I discovered that the root cause was this DuckDuckGo config change.
Re: Debian's Chromium changes default search engine to DDG
#3Some unintended consequences: > This change caused my chromium browser to report that it's being managed by my "organization". I thought that my machine was somehow compromised. This is terrifying! I wound up deleting my entire chromium profile before I discovered that the root cause was this DuckDuckGo config change. https://bugs.debian.org/956012
That sounds like a Firefox bug (and a common one I've seen in other software).
Tell me what organization. "Debian" would have been perfectly fine to show here.
Re: Debian's Chromium changes default search engine to DDG
#4Some unintended consequences: > This change caused my chromium browser to report that it's being managed by my "organization". I thought that my machine was somehow compromised. This is terrifying! I wound up deleting my entire chromium profile before I discovered that the root cause was this DuckDuckGo config change. https://bugs.debian.org/956012
That sounds like a Firefox bug (and a common one I've seen in other software). Tell me what organization. "Debian" would have been perfectly fine to show here.
How is that a Firefox bug if the software it is reported on is Chromium? Those are two very distinct projects.
Re: Debian's Chromium changes default search engine to DDG
#5Some unintended consequences: > This change caused my chromium browser to report that it's being managed by my "organization". I thought that my machine was somehow compromised. This is terrifying! I wound up deleting my entire chromium profile before I discovered that the root cause was this DuckDuckGo config change. https://bugs.debian.org/956012
If it was implemented by managed policy file, then Chrome/Chromium will complain exactly this way.
You can see the details in the chrome://policy page.
Re: Debian's Chromium changes default search engine to DDG
#6Earlier quoted context omitted.
That sounds like a Firefox bug (and a common one I've seen in other software). Tell me what organization. "Debian" would have been perfectly fine to show here.
How is that a Firefox bug if the software it is reported on is Chromium? Those are two very distinct projects.
Perhaps it reminds them of a similar bug in Firefox?
Re: Debian's Chromium changes default search engine to DDG
#7Earlier quoted context omitted.
That sounds like a Firefox bug (and a common one I've seen in other software). Tell me what organization. "Debian" would have been perfectly fine to show here.
How is that a Firefox bug if the software it is reported on is Chromium? Those are two very distinct projects.
[deleted]
Re: Debian's Chromium changes default search engine to DDG
#8Is it common for distros to have deals with search providers in exchange for keeping them as the default in their browsers ?
Re: Debian's Chromium changes default search engine to DDG
#9Earlier quoted context omitted.
That sounds like a Firefox bug (and a common one I've seen in other software). Tell me what organization. "Debian" would have been perfectly fine to show here.
How is that a Firefox bug if the software it is reported on is Chromium? Those are two very distinct projects.
No post body was provided.
Re: Debian's Chromium changes default search engine to DDG
#10Some unintended consequences: > This change caused my chromium browser to report that it's being managed by my "organization". I thought that my machine was somehow compromised. This is terrifying! I wound up deleting my entire chromium profile before I discovered that the root cause was this DuckDuckGo config change. https://bugs.debian.org/956012
Yeah, that was alarming. Figuring out that it was innocuous took me 15-30 minutes of urgent, drop-everything-else work.
I should've thought to post a Debian bug report after that (especially since the Debian bugs database was one of the first things I checked). I'd reported the cause informally to some colleagues, and then must've gotten distracted with what I was trying to do before I saw the suspicious message.