~/snap/chromium/common/.cache/fontconfig does not exist. After trying to
run chromium headless the first time
~/snap/chromium/current/.config/fontconfig/ is created. Deleting this
folder does not fix the crash.
You can easily reproduce this error by setting up a clean Ubuntu Core 18
instance
Does deleting ~/snap/chromium/common/.cache/fontconfig work around the
problem, by any chance?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908284
Title:
[snap] chromium headless crashes at
I seem to experience the same issue on Ubuntu Core 18.
I include the chromium snap within my snap for use with puppeteer.
Adding font packages like fonts-dejavu-core as stage-packages does not
seem to work.
Do you have any idea how to get around the issue on Ubuntu Core?
--
You received this
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908284
Title:
[snap] chromium headless crashes at
I can confirm this workaround works. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908284
Title:
[snap] chromium headless crashes at startup on non-desktop system
To manage notifications
A more minimal workaround is to "apt install fonts-dejavu-core" before
installing the chromium snap (verified working on a headless system).
This ensures that there is at least one font when the configure hook
pre-generates a font cache.
--
You received this bug notification because you are a
I can reliably observe the problem on a system without a desktop
environment, and I can confirm that installing ubuntu-desktop-minimal
and then reinstalling the snap makes the problem go away.
This is a regression that appeared when switching to using the
gnome-3-28 extension.
After removing
