Created attachment 916073 [details] emerge --info Since firefox-134 there are no search engines and I can't add. firefox-133.0.3 was working.
Try a new profile? It's working fine here.
Also the usual: - try building without ccache if you used it to build firefox (it's in your FEATURES) - try firefox-bin
(In reply to Joonas Niilola from comment #1) > Try a new profile? It's working fine here. Start with firefox profile removed worked. How big is the chance that other people hit this? We don't know the bad setting that breaks the upgrade. Keep bug this open or not?
You're so far the only one I've seen with the issue :) even in their bugzilla if I search for firefox-134 related bugs, there's nothing similar to this. Nothing pops out in r/firefox either (altough I don't have a reddit account, and using reddit with vpn is hard). As to why search engines are broken for you is a bit trickier if now impossible to figure out. Hopefully your profile can be recovered. Did you try compiling without ccache? You could try your profile on firefox-bin and if it works, move it back to source-built firefox. But when playing with profiles, make sure to have backups!
(In reply to Joonas Niilola from comment #4) > You're so far the only one I've seen with the issue :) even in their > bugzilla if I search for firefox-134 related bugs, there's nothing similar > to this. Nothing pops out in r/firefox either (altough I don't have a reddit > account, and using reddit with vpn is hard). > > As to why search engines are broken for you is a bit trickier if now > impossible to figure out. Hopefully your profile can be recovered. Did you > try compiling without ccache? You could try your profile on firefox-bin and > if it works, move it back to source-built firefox. But when playing with > profiles, make sure to have backups! I copied the most important files from my original firefox profile back to the fresh profile. Now it is usable again. I don`t think it is a ccache error. A few weeks ago I tried firefox-134beta with the same result and downgraded back to 133 because of that. For reddit look for LibRedirect plugin for firefox. I can read reddit pages with that.
Let`s keep this open for now and see what happens on next release. Maybe someone steps in here. I can try the old profile or copy some files around then.
I also encountered the same issue on NixOS. After upgrading from Firefox 133 to Firefox 134, all search engines disappeared. The culprit was the `search.json.mozlz4` file in the profile folder. Removing the file resolved the issue, and searching works again.
this might be: https://bugzilla.mozilla.org/show_bug.cgi?id=1940533 fixed in 134.0.1
(In reply to tt_1 from comment #8) > this might be: https://bugzilla.mozilla.org/show_bug.cgi?id=1940533 > > fixed in 134.0.1 Sounds like it! Also, _now_ that I go through https://hg.mozilla.org/releases/mozilla-release/pushloghtml?fromchange=FIREFOX_133_0_RELEASE&tochange=FIREFOX_134_0_RELEASE ctrl+f "search engine" there are indeed related commits that would've lead to relevant bugs. Although yours still seems to be the only regression bug, so while it's confirmed, it's still not very wide-spread. Anyway will read the bug completely, but from a quick glimpse looks like 134.0.1 will hold a fix.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7f2d91b574d9f26cbcdf3fc23e33e3b3cbbc3270 commit 7f2d91b574d9f26cbcdf3fc23e33e3b3cbbc3270 Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2025-01-15 11:05:56 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2025-01-15 11:06:22 +0000 www-client/firefox: add 134.0.1 Closes: https://bugs.gentoo.org/947677 Signed-off-by: Joonas Niilola <juippis@gentoo.org> www-client/firefox/Manifest | 101 +++ www-client/firefox/firefox-134.0.1.ebuild | 1371 +++++++++++++++++++++++++++++ 2 files changed, 1472 insertions(+)
