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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
