So, I updated my system recently, for the first time in months. Now, when I open Librewolf, the default search engine is …Google. This is funny, and wildly incorrect, considering what Librewolf’s all about.
Expected: DuckDuckGo as default browser, Google nowhere to be seen in the default search engine selection, ability to add search engines
Actual: Google as default engine, have to manually select DDG to make it the default. Also, browser now claims to be “managed by my organization”, according to a banner at the top of the settings that wasn’t there before.
It doesn’t seem like Librewolf itself updated at all, as it would usually force me to restart in such a case, which didn’t happen
nix-info:
- system:
"x86_64-linux"
- host os:
Linux 6.6.47, NixOS, 24.11 (Vicuna), 24.11.20240824.d0e1602
- multi-user?:
yes
- sandbox:
yes
- version:
nix-env (Nix) 2.18.5
- nixpkgs:
/nix/store/ia1zpg1s63v6b3vin3n7bxxjgcs51s2r-source
Librewolf is installed via home-manager, and my system config is a flake.
The part of my config that installs Librewolf is roughly:
home-manager.users.<user>.programs.librewolf.enable = true;
I’m gonna take a look through the package definitions in nixpkgs and home-manager; will post findings.
Yeah, I wouldn’t use the HM module for firefox and friends. Just add librewolf to a package list and that’ll get on better.
Of course you may need to change your profile’s config manually, as it then wouldn’t be managed by your NixOS config.
Why not? How about the NixOS module?
HM modules are pretty badly written, and in particular I’ve never gotten their FF module to behave correctly (back when I used HM).
1 Like
OTOH, all the HM module does as I’ve configured it is install Librewolf as a regular package in home-manager via home.packages. Even if I had any extra config, the way it works is pretty damn cut-and-dry; it just doesn’t do enough to have much room to fail. And it’s worked fine for me for months now, whereas the module hasn’t been changed in at least a year.
I will still try installing without the module though, at the very least for the sake of narrowing down the issue.
You’re right, I assumed the LW module would be written similar to the FF one (it’s clearly not).
In that case, it’s either a packaging issue or upstream change. Just tested on my system, I do see google as the default as well.
Ok, well, having installed it via home.packages directly, I actually have no idea if that solved the problem : |
I’ve just set it back to DDG for now; let’s hope it sticks.
Reported to nixpkgs here - librewolf: defaults to google search engine · Issue #338439 · NixOS/nixpkgs · GitHub
It seems that nixpkgs doesn’t follow the upstream scripts and just does their own thing, which causes some of these issues.
It seems that nixpkgs doesn’t follow the upstream scripts and just does their own thing, which causes some of these issues.
It’s not possible to use the upstream build scripts in a sandboxed Nix build environment.
It seems like per the linked issue above, librewolf-bin which is the offical upstream build (and does not default to google), is now in nixpkgs. So you may be able to use that if you’d like.
1 Like