Comment 4 for bug 1044393

MAAS uses Xvfb (via pyvirtualdisplay) for local headless JavaScript
testing. In a new, ephemeral, LXC container, I get:

  $ Xvfb -br -screen 0 1024x768x24 :1

  Fatal server error:
  Can't read lock file /tmp/.X1-lock

Xvfb accepts a -nolock option:

  $ Xvfb -br -screen 0 1024x768x24 -nolock :1
  Warning: the -nolock option can only be used by root

  Fatal server error:
  Can't read lock file /tmp/.X1-lock

So, via sudo:

  sudo Xvfb -br -screen 0 1024x768x24 -nolock :1
  [dix] Could not init font path element ...

Background it (Ctrl-z, bg) and firefox can be started:

  $ DISPLAY=:1 firefox

I don't know why locking is a problem though. Perhaps
--no-install-recommends is leaving out something that we actually
depend on.