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)
  • Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    3
    ·
    edit-2
    9 months ago

    Isn’t that a program that is used for piracy? That seems like a reasonable thing to break for legal reasons.

    Edit: it seems like a bug

    • Midnight Wolf@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      9 months ago

      How to display the fact that you didn’t do any double-checking before posting 101. It takes 5 seconds to do a search query, cmon.

      All the *arr programs are usually file-sharing related, but come on. Quit your finger-wagging.

    • Alk@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      9 months ago

      By your metrics, possiblylinix127, Linux is also a system that is used for piracy. I can do piracy on Linux. That makes it illegal!

    • Melmi@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      9 months ago

      Why would a random browser extension take it upon itself to snoop on your traffic to ensure that the websites you’re using can’t be used for illegal things, and then intentionally break it if it detects something it thinks it’s illegitimate? That’s a huge breach of privacy. It’s just malware at that point. It’s not like a court of law would hold your browser extensions responsible for your piracy. That’s like blaming a cup holder because the car was used in a robbery.

      No, I think this is just a bug. Especially since people have reported that the extension breaks other websites too.