Last edited by Ionen on Tue 1:27 am edited 1 time in total (Edit: upstream does clang+lto+pgo for official binaries minus lacking a -march=native/-Ctarget-cpu=native, usage of more system libraries, and no native alsa/jack support) I feel like gentoo should default to it on firefox, albeit it does mean yet more build dependencies for a package that's already heavy on them.
Generally I just recommend to use clang USE with firefox, nothing against gcc but it's just not what upstream uses (they seem aware of this particular issue though, so I guess it'll get fixed eventually, but I'm sure there will be more). Upstream firefox barely tests gcc anymore and this leads to all kinds of complications and unexpected behavior with new versions ( 71.0 notably broke gcc+lto which also broke pgo that gentoo disabled with gcc for now - Edit2: been patched and re-enabled now, maybe also fixes plugins). Reading the bug reports, it sounds like this is """caused""" by using gcc instead of clang (are you both using gcc? firefox-bin should work in theory, if not ignore this post). It's what I get for insisting on ~amd64 firefox I suppose. I assumed I had broken some firefox dependency while tweaking the system, but Firefox 71.0 breaking local storage functionality explains all my issues, thanks for mentioning it here! I use standalone keepassxc so that is working just fine, but I have spent most of my Sunday swearing at firefox and recompiling packages trying to get my browser extensions to work again. JavaScript error:, line 0: NS_ERROR_UNEXPECTED: JavaScript error: resource://gre/actors/BrowserElementParent.jsm, line 81: TypeError: browser is null JavaScript error: moz-extension://1b2659b3-f2b8-491f-8841-65c0500fd964/background/browserAction.js, line 94: TypeError: page.tabs is undefined JavaScript error:, line 0: uncaught exception: null JavaScript error:, line 0: ConstraintError: A mutation operation in the transaction failed because a constraint was not satisfied. StateChangeProcessEnqueue: Error transitioning state JavaScript error: resource://services-common/kinto-offline-client.js, line 603: Error: IndexedDB clear() The operation failed for reasons unrelated to the database itself and not covered by any other error code.ġ575811906550 WARN Loading extension Reading manifest: Warning processing version_name: An unexpected property was found in the WebExtension manifest. JavaScript error: resource://gre/modules/AsyncShutdown.jsm, line 694: Error: Phase "xpcom-will-shutdown" is finished, it is too late to register completion condition "UserInteractionTimer 1 for document 7f41f60a1000" JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory. With the new profile the following logs are produced: I did try creating a new firefox profile and installed lastest browser extension there and nothing changed, the keepassxc browser extension cannot communicate with the keepassxc app and it can't even access its own settings. I scanned through the keepassxc issues in github ( ) and see no mention of this problem, so is it specific Gentoo? JavaScript error: moz-extension://3f0f2104-ed66-47bd-8249-bd4204cd141c/content/keepassxc-browser.js, line 0: Error: undefined When firefox is run from a console various logs are produced, the following of which are definitely from the browser extension: The keepassxc browser extension cannot communicate with the keepassxc app and it can't even access its own settings. With the new firefox 71.0 keepassxc does not work. UPDATE: Turns out this is a known issue with keepassxc-browser ( ) and it's related to "Firefox 71 breaks many extensions - can't write to local storage" ( ). Posted: Sun 1:34 pm Post subject: firefox 71.0 breaks keepassxc Gentoo Forums Forum Index Other Things Gentoo Gentoo Forums :: View topic - firefox 71.0 breaks keepassxc
0 kommentar(er)
