Comment 12 for bug 2026200

@Nathan Teodosio:

Running either produces the same issue:

```
$ /snap/bin/chromium
cannot open path of the current working directory: Permission denied

$ /snap/bin/chromium --enable-logging=stderr
cannot open path of the current working directory: Permission denied
```

I presume these are issues with shelling into my vm as a vagrant user.

If I run under our service user I get this output:

```
sudo runuser -l xxxx -c 'chromium --headless --disable-gpu'
[0706/142016.391512:WARNING:sandbox_linux.cc(393)] InitializeSandbox() called with multiple threads in process gpu-process.
[0706/142016.397591:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.

sudo runuser -l xxxx -c 'chromium --headless --disable-gpu --disable-software-rasterizer --enable-logging=stderr'
[0706/142336.953854:WARNING:bluez_dbus_manager.cc(247)] Floss manager not present, cannot set Floss enable/disable.
```

Which is the same output I get when the snap works.

We have had to use the current/user path from the start, however I just tried replacing the setBinary call for webdriver with the /snap/bin/chromium path and it did not resolve the issue either.

Running the `snap refresh` command you provided resolves my problem. So thank you for that! But I'm still available for any debugging requests.

And finally, I only have access to headless installs for ubuntu, so I don't have a way of running it headed.