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 jorams on Monday November 27, 2023 @05:08AM (#38430499)

To make this work you need to set the XDG_RUNTIME_DIR environment variable to the same value it has in the environment Firefox is running in. For example:

    sudo -u desktopuser XDG_RUNTIME_DIR=/run/user/1000 firefox --new-window

[ Parent | on HN ]

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

Please try this for yourself. It does not work. Gives the same "Firefox is already running, but is not responding." dialog.

[ Parent | on HN ]

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

I did try it. It even works from a different VT directly logged in as root if I also specify DISPLAY:

    sudo -u desktopuser XDG_RUNTIME_DIR=/run/user/1000 DISPLAY=:0.0 firefox --new-window

If I now switch back to the VT running my desktop, a new Firefox window has opened.

Maybe your root terminal has other environment variables set that break it? A different DBUS session maybe?

[ Parent | on HN ]

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

Oh wow, you were right! This solves it:

    sudo -u desktopuser XDG_RUNTIME_DIR=/run/user/1000 firefox

Sorry for messing it up the first time I tried!

Man, you solved it!!

Thanks a 1000 times!

[ Parent | on HN ]

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

No problem! Glad it works now.

[ Parent | on HN ]