There are some dbus messages that need to be handled by the mus-ws process. I think this is mostly anything related to displays, for example TakeDisplayOwnership/RelinquishDisplayOwnership. These dbus messages are received by the Chrome browser process now.
To get things working in the short term I am adding IPCs from chrome to mus-ws but this isn't ideal. If mus-ws could receive the dbus messages instead it would remove the need for the extra IPC hop and reduce complexity.
This would require splitting LibCrosService into two services so that chrome can implement some parts and mus-ws can implement others. There are more details in https://bugs.chromium.org/p/chromium/issues/detail?id=682804.
Comment 1 by jamescook@chromium.org
, Apr 24 2018Labels: -Proj-Mustash-Mus-WS