@h8ray: Known issue on Manjaro.
https://gitlab.com/librewolf-community/browser/linux/-/issues/302
https://gitlab.com/librewolf-community/browser/arch/-/issues/85
| Git Clone URL: | https://aur.archlinux.org/librewolf-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | librewolf-bin |
| Description: | Community-maintained fork of Firefox, focused on privacy, security and freedom. |
| Upstream URL: | https://librewolf.net/ |
| Keywords: | browser web |
| Licenses: | MPL-2.0 |
| Conflicts: | librewolf |
| Provides: | librewolf |
| Submitter: | lsf |
| Maintainer: | lsf |
| Last Packager: | lsf |
| Votes: | 626 |
| Popularity: | 24.26 |
| First Submitted: | 2019-06-16 13:12 (UTC) |
| Last Updated: | 2026-05-13 07:44 (UTC) |
« First ‹ Previous 1 .. 14 15 16 17 18 19 20 21 22 23 24 .. 29 Next › Last »
@h8ray: Known issue on Manjaro.
https://gitlab.com/librewolf-community/browser/linux/-/issues/302
https://gitlab.com/librewolf-community/browser/arch/-/issues/85
Updated to 100.0.1-1, can't run the browser now:
/usr/lib/librewolf/librewolf: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.30 not found (required by /usr/lib/librewolf/librewolf)
When I run librewolf start firefox ??? librewolf ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. JavaScript error: resource://activity-stream/data/content/newtab-render.js, line 10: TypeError: window.NewtabRenderUtils is undefined console.error: BroadcastService: receivedBroadcastMessage: handler for remote-settings/monitor_changes threw error: Message: Error: Polling for changes failed: The URI is malformed.. Stack: remoteSettingsFunction/remoteSettings.pollChanges@resource://services-settings/remote-settings.js:254:13
JavaScript error: resource://gre/modules/CertUtils.jsm, line 219: NS_NOINTERFACE: JavaScript error: resource://gre/modules/CertUtils.jsm, line 219: NS_NOINTERFACE: JavaScript error: resource://gre/modules/CertUtils.jsm, line 219: NS_NOINTERFACE:
@medzik looks like an issue with the canvas. Try enabling it and seeing if the issue persists (librewolf disables it by default since it can be used for fingerprinting).
My question is am I missing any fonts or have any options turned off? For example on https://svenstaro.github.io/genact/ I have check screenshot and on ungoogled chromium works fine
For anyone still having problems with keyserver. If you're using systemd-networkd and systemd-resolved consider reading through https://wiki.archlinux.org/title/Systemd-resolved "ln -rsf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf" fixed it for me.
That fixed it, thanks!
Tried with fresh profile, still reproducible.
Can't reproduce on 98.0.2, so something in 99 broke it.
Can also reproduce with firefox 99, so apparently its an upstream issue.
@ImperatorStorm: can't reproduce this on my end. Maybe it's something with your librewolf config (fonts?), or global/system font settings? You could try running librewolf with a fresh profile to see if it's caused by your config.
Pinned Comments
lsf commented on 2021-11-10 12:14 (UTC) (edited on 2026-05-07 09:38 (UTC) by lsf)
https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)/edit: (2026-05-07): The upstream signing sub-key was rotated, and the
.tar.xztarballs will now be signed with a new subkey. The main key id (0x662E3CDD6FE329002D0CA5BB40339DD82B12EF16) remains unchanged though, so should you get an error during signature verification about a missing (sub)key, all that's required would be to refresh the key(s) viagpg --refresh-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16.