Abrowser update resets search engine preferences and makes Google the defaut
- Vous devez vous identifier ou créer un compte pour écrire des commentaires
Hello all,
I am just posting this as a warning to everyone else who might come across this. The most recent update to Abrowser just reset my search engine preferences, and added several other search engines including bing and ebay. The default search engine I got after the update is Google, which I never used.
Don't forget to check search engine settings after the update or you will go to Google.
(I am using Trisquel 6)
Hi there,
I have the same issue after updating Abrowser today. I'm also using Trisquel 6. I will check if that also happens in Trisquel 7 as well.
I believe this is a big issue, new users might thing Abrowser recommends Google as a search engine.
> new users might thing [sic] Abrowser recommends Google as a search engine.
That's not a problem particular to this update; Abrowser has the default
Firefox search engine list installed by default, as far as I can recall. I
still have no idea why Trisquel promotes Abrowser as part of the Trisquel DE
rather than Icecat, which is clearly more privacy/freedom-focused.
I am using 32-bit Belenos (Trisquel 7). Got the same bug with the same update. Firefox are making major architectural changes and feeding updates down the pipe thick and fast of late, perhaps ABrowser maintainers are struggling to keep up? Does anyone have the skills to help?
One solution is to switch to IceCat for the time being. I definitely recommend having both installed, so when updates break one, you can switch to the other ;)
Why not just use Icecat full stop, and not have to deal with Abrowser's
frequent silliness?
I am a member!
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have both installed, as you recommend. After my latest system
upgrade, I find that all my extensions, plugins, and search engines
still work; am using searx as my default. I haven't tried installing
new addons since, however.
On 09/25/2015 04:25 AM, name at domain wrote:
> One solution is to switch to IceCat for the time being. I
> definitely recommend having both installed, so when updates break
> one, you can switch to the other ;)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJWBXN+AAoJEPDWzxLwi2tA3LkH/09fHqRLuIQPmqLkksMmMr+7
kEfv5Dck/TQ2cjPzVY0rBjI4U7vtr3ATW43aYQwYepJw3vK+z2T/cFXVXXj8rncz
hL9tPdQDkXCJJDCiOWe8caw3zRvoamTAic/zau5Y+1sPXM7ctQj10Yz/8GKrbbkP
jl2S9x7pg7p9SLD4/B2aOqBnBfyFyui0RRdNICDEezAjGb3D+2TwzJF82UDPfx01
swtpIVFMjlr7UVvsHO85nI15f4m0/R3tK225pGWEDkYCakYPRt4ULRDyy+98Qk2M
2dNffXtzVLpOG6zZtSQKwqQ3J5WIcKOr7QuJSj67NUOcBzELyb0Lg+0CED+E2NM=
=7/hc
-----END PGP SIGNATURE-----
Here's a related bug
I had the same problem, nooooo Google not, please.
- Vous devez vous identifier ou créer un compte pour écrire des commentaires