Chrome Version       : 52.0.2743.110 (developpment) (64 bits)

Trying to improve on crouton to integrate the chromiumos host with a systemd guest running wayland/weston, it would be best to update the dBus API that allows chrome to take the DRM file descriptor (with the DRM_MASTER) from a dBus call instead of opening it directly.

It would allow the guest OS to drop the DRM_MASTER of the device in inace of the chrome process. This is a standard way of doing it in systemd-logind: 
https://freedesktop.org/wiki/Software/systemd/logind/

More specifically, the following method would be great to have:

    ResumeDisplayDevice(device file descriptor)

Would work just like TakeDisplayOwnership() but instead of taking DRM_MASTER from the already opened DRM device, it would replace the opened file descriptor (possibly using dup2) with the one given through dBus. The file descriptor is assumed to already have DRM_MASTER.

    PauseDisplayDevice()

This is a notification that whomever gave us the file descriptor through ResumeDisplayDevice() removed the DRM_MASTER bit and we should not longer use the device. Any use of the device would result in EACCESS. Basically, this is the same as ReleaseDisplayOwnership() without the ioctl.

See systemd-logind issue where I try to make the two interfaces (chromium and logind) work together : https://github.com/systemd/systemd/issues/3938