xvfb-run fails in Cloud9

[beaufortfrancois]

After building Chromium content_unittests in Cloud9, I'm failing to run

$ xvfb-run -s "-screen 0 1024x768x24" ./out/Default/content_unittests --gtest_filter=BluetoothAllowedDevicesMapTest.*
xvfb-run: error: Xvfb failed to start

For info, it works great with noVNC.

[Coder206]

@beaufortfrancois That seems to reflect my experience with Servo. I see the command has a screen resolution, that's currently unsupported in Cloud9. Keep in mind, there are plans to embed noVNC in Cloud9

[jankeromnes]

@beaufortfrancois @Coder206 When you add the -a argument to xvfb-run, it seems to work, as it will choose a different DISPLAY than the default :99 (currently used by noVNC already).

To fix this in a nicer way, I think we should make our noVNC use a different DISPLAY (e.g. :98), that way any user-run xvfb or xvfb-run will just work.

[beaufortfrancois]

Yup!

[jankeromnes]

Fixed by making noVNC run on non-default DISPLAY :98 instead of :99 in JanitorTechnology/dockerfiles@f0d9e9a

The fix should be deployed for new Janitor containers soon (hopefully in the coming days). Thanks for reporting this issue! I'll post back here when the fix is live.

[Coder206]

@jankeromnes Can we close this?