[arch-general] Chromium in a systemd-nspawn container?

[Mark Raynsford]

Hello!

It seems that a recent update (unfortunately, I'm not sure exactly
which) broke my ability to run Chromium in a systemd-nspawn container.
Specifically, the symptom is that the Chromium window opens, but
remains blank and evidently doesn't respond to keyboard/mouse input.

Firefox in the same container runs without issue.

Is there something I can do to debug this issue? I'm using the standard
trick to allow containers to access X:

  https://wiki.archlinux.org/index.php/Systemd-nspawn#Use_an_X_environment

The only possibly relevant error message I see on Chromium's stderr is:

  67:67:0221/100217.520256:ERROR:gpu_channel_manager.cc(459)]
  ContextResult::kFatalFailure: Failed to create shared context for
  virtualization.

I've tried the --disable-gpu flag, but that makes no difference.

Any ideas?

-- 
Mark Raynsford | http://www.io7m.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-general/attachments/20200221/45d4f77d/attachment.sig>