| View previous topic :: View next topic |
| Author |
Message |
acmondor
n00b
Joined: 08 Aug 2014
Posts: 65
Location: Canadian Prairies
|
 Posted: Sun Dec 08, 2019 1:34 pm Post subject: [KNOWN ISSUE] firefox 71.0 breaks keepassxc |
 |
|
UPDATE: Turns out this is a known issue with keepassxc-browser (https://github.com/keepassxreboot/keepassxc-browser/issues/704) and it's related to "Firefox 71 breaks many extensions - can't write to local storage" (https://bugzilla.redhat.com/show_bug.cgi?id=1779570).
With the new firefox 71.0 keepassxc does not work. The keepassxc browser extension cannot communicate with the keepassxc app and it can't even access its own settings.
When firefox is run from a console various logs are produced, the following of which are definitely from the browser extension:
| Code: | JavaScript error: moz-extension://3f0f2104-ed66-47bd-8249-bd4204cd141c/content/keepassxc-browser.js, line 864: Error: undefined
JavaScript error: moz-extension://3f0f2104-ed66-47bd-8249-bd4204cd141c/content/keepassxc-browser.js, line 0: Error: undefined
JavaScript error: moz-extension://3f0f2104-ed66-47bd-8249-bd4204cd141c/content/keepassxc-browser.js, line 0: Error: undefined
|
I scanned through the keepassxc issues in github (https://github.com/keepassxreboot/keepassxc/issues?utf8=%E2%9C%93&q=is%3Aissue) and see no mention of this problem, so is it specific Gentoo?
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. With the new profile the following logs are produced:
| Code: | $ firefox -P
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.jsm, line 66: Error: Can't find profile directory.
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://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.
1575811906550 addons.webextension.keepassxc-browser@keepassxc.org WARN Loading extension 'keepassxc-browser@keepassxc.org': Reading manifest: Warning processing version_name: An unexpected property was found in the WebExtension manifest.
console.error: PushService:
stateChangeProcessEnqueue: Error transitioning state
UnknownError
JavaScript error: , line 0: ConstraintError: A mutation operation in the transaction failed because a constraint was not satisfied.
JavaScript error: , line 0: uncaught exception: null
JavaScript error: moz-extension://1b2659b3-f2b8-491f-8841-65c0500fd964/background/browserAction.js, line 94: TypeError: page.tabs[id] is undefined
JavaScript error: moz-extension://1b2659b3-f2b8-491f-8841-65c0500fd964/popups/popup.js, line 12: TypeError: r is undefined
JavaScript error: resource://gre/actors/BrowserElementParent.jsm, line 81: TypeError: browser is null
JavaScript error: , line 0: NS_ERROR_UNEXPECTED: |
Anybody else seeing this problem? |
|
| Back to top |
|
 |
trilithium
n00b
Joined: 18 Nov 2019
Posts: 43
|
| Posted: Sun Dec 08, 2019 9:13 pm Post subject: |
|
|
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. 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!
It's what I get for insisting on ~amd64 firefox I suppose.  |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2919
|
| Posted: Sun Dec 08, 2019 10:06 pm Post subject: |
|
|
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). 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).
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). 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.
(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)
Last edited by Ionen on Tue Dec 10, 2019 1:27 am; edited 1 time in total |
|
| Back to top |
|
|
trilithium
n00b
Joined: 18 Nov 2019
Posts: 43
|
| Posted: Sun Dec 08, 2019 11:54 pm Post subject: |
|
|
| Recompiling www-client/firefox-71.0 (and required dependencies) USEing clang appears to resolve my browser extension issues, thanks for the suggestion Ionen! |
|
| Back to top |
|
|
Tony0945
Watchman
Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA
|
| Posted: Mon Dec 09, 2019 12:10 am Post subject: |
|
|
| trilithium wrote: | 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. 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!
It's what I get for insisting on ~amd64 firefox I suppose. |
Try palemoon. https://github.com/deuiore/palemoon-overlay |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2919
|
| Posted: Tue Dec 10, 2019 12:50 pm Post subject: |
|
|
Update: I haven't tried, but since bug #702418 was marked a duplicate of #701866 this should be fixed when using gcc on gentoo (also gcc+lto+pgo is restored for a faster firefox). I'm still keeping the stance that should use clang with firefox as long as upstream doesn't "properly" test gcc, but hey  |
|
| Back to top |
|
|
acmondor
n00b
Joined: 08 Aug 2014
Posts: 65
Location: Canadian Prairies
|
| Posted: Tue Dec 10, 2019 2:45 pm Post subject: |
|
|
I just rebuilt firefox 71 with clang as suggested by Ionen and it does solve my original problem. Thanks for that suggestion!
In case anybody is interested, I originally encountered the problem and did the clang build on amd64. I also use firefox on x86, but I haven't tried firefox 71 or a build with clang there yet. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Other Things Gentoo
