Why Bother with uBlock Being Blocked in Chrome? Time to Switch to Firefox

Re:Why Bother with uBlock Being Blocked in Chrome? Time to S... by pmontra on Monday November 27, 2023 @04:59AM (#38430423)

I didn't test it but probably

  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus \
  DISPLAY=:1 \
  sudo -H -u normaluser \
    --preserve-env=DBUS_SESSION_BUS_ADDRESS,DISPLAY \
  firefox

I'd add -H to the options of sudo to make it set the home to normaluser's one.

I assumed that your DISPLAY is :1, which is what my Debian has set for me. That's another variable that you could read from the environment of Firefox.

You might have to pass/preserve other environment variables to make Firefox work.

[ Parent | on HN ]

Re:Why Bother with uBlock Being Blocked in Chrome? Time to S... by JonathanBeuys on Monday November 27, 2023 @05:38AM (#38430711)

Whe don't you test it? It takes less time than to guess and have a back and forth via HN comments.

[ Parent | on HN ]

Re:Why Bother with uBlock Being Blocked in Chrome? Time to S... by albertzeyer on Monday November 27, 2023 @06:57AM (#38431255)

The parent gave all information which should help you in figuring it out by yourself now. The message it, it should work with the right env vars, and you have multiple example env vars to check for (DBUS related, DISPLAY, etc) and Google for. This is your work now.

(You could also test the extreme case: Just copy all the env vars.)

[ Parent | on HN ]

Re:Why Bother with uBlock Being Blocked in Chrome? Time to S... by pmontra on Monday November 27, 2023 @06:38AM (#38431118)

Because this is not a support forum or a stack exchange. I give the idea, then all the test and debugging is for who has to actually make the code work.

[ Parent | on HN ]