On 07/01/17 09:37, Jaromil wrote:
chromium uses seccomp sandboxing internally which may fail to run inside a chroot. I run chromium regularly on jessie, also inside firejail (using https://github.com/dyne/tinfoil) so can confirm that at least outside of a chroot it works well.
Meanwhile found it out myself: it was missing /dev/shm. schroot didn't set it up automatically. Chromium should have printed a proper message. Filed upstream bug.
in general please consider these sort of reports should go to bugs.devuan.org (can be filed using reportbug)
Was down when I wrote the mail. --mtx _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
