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 Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1837746 Title: [snap] wrapper script doesn't source ~/.chromium-browser.init Status in chromium-browser package in Ubuntu: Fix Committed Bug description: (initially reported here: https://discourse.ubuntu.com/t/call-for- testing-chromium-browser-deb-to-snap-transition/11179/82) The /usr/bin/chromium-browser script in the old deb packages had the following line: test -f ~/.chromium-browser.init && . ~/.chromium-browser.init which allowed users to customize CHROMIUM_FLAGS. This was lost when transitioning to the snap. For compatibility, it should be added back, so that users who rely on this don't observe regressions when transitioning to the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1837746/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
