this post was submitted on 16 Mar 2024
100 points (91.0% liked)

Selfhosted

40329 readers
433 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
100
Proton Pass breaks prowlarr on firefox since today (lemmy.ml)
submitted 8 months ago* (last edited 8 months ago) by GravitySpoiled@lemmy.ml to c/selfhosted@lemmy.world
42 comments fedilink hide all child comments
 

Prowlarr returns There was an error loading this page when I click on an app and other sites. When I disable proton pass, it works as usual. Any idea how to solve it?

Permission denied to access property "matches"
  at toArray( (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:8:26)
  at toArray( (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:7:59)
  at parents.reduce(function (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:22:64)
  at parents.reduce(function (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:20:19)
  at getAllTabbableNodes (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/DOMutils.js:31:43)
  at getAllTabbableNodes (webpack://prowlarr/node_modules/focus-lock/dist/es2015/focusMerge.js:37:41)
  at setFocus (webpack://prowlarr/node_modules/focus-lock/dist/es2015/setFocus.js:21:34)
  at withinHost (webpack://prowlarr/node_modules/react-focus-lock/dist/es2015/Trap.js:125:23)
  at lastTrap.returnFocus (webpack://prowlarr/node_modules/react-focus-lock/dist/es2015/Trap.js:260:4)
  at reducePropsToState(mountedInstances.map(function (webpack://prowlarr/node_modules/react-clientside-effect/lib/index.es.js:34:6)
  at componentDidUpdate (webpack://prowlarr/node_modules/react-clientside-effect/lib/index.es.js:57:8)
  at Yi (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:219:501)
  at try{for (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:259:159)
  at unstable_next (webpack://prowlarr/node_modules/scheduler/cjs/scheduler.production.min.js:18:342)
  at eg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:122:324)
  at Uj (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:252:281)
  at Lj (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:243:370)
  at jg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:123:114)
  at unstable_next (webpack://prowlarr/node_modules/scheduler/cjs/scheduler.production.min.js:18:342)
  at eg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:122:324)
  at jg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:123:63)
  at eg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:122:427)
  at Hb (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:292:100)
  at $c (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:73:354)
you are viewing a single comment's thread
view the rest of the comments
[–] beeb@lemm.ee 2 points 8 months ago (1 children)

I reported the bug to Proton support and they said they are investigating but suggested I uninstall and reinstall the extension. I did and lo, my forms started working again. I can recommend you try to uninstall and reinstall too (disabling it was not enough).