Ubuntu
chromium-browser package

  1. Bug #1837746
  2. Comment #9

Comment 9 for bug 1837746

Revision history for this message
Jalon Funk (francescohickle15) wrote :

I can confirm that if "personal-files" slot isn't connected and "~/.chromium-browser.init" exist then chromium snap fails to start.

The solution is to either connect "personal-files" slot or delete "~/.chromium-browser.init" (arguably it's pointless to have this file if access is blocked).

@osomon you may also use something like:

test -f $REALHOME/.chromium-browser.init && . $REALHOME/.chromium-browser.init || true

which will ignore failure of sourcing ".chromium-browser.init" and let chromium start.