MULTIPLE DBUS PROBLEM

[stevebovy]

Is your feature request related to a problem? Please describe.

THANKS FOR WSLG !

BUT, A problem with many puzzle pieces needs a multi-pronged solution. You have done very well with the x-window puzzle piece, and I thank you for your excellent work, but you have not yet addressed the IPC-DBUS puzzle piece which I will try to describe as follows:

THE PARENT INIT PROCESS AND SHARED DBUS INSTANCE PROBLEM

DBUS is designed to create “ONE shared instance” for all desktop apps launched from the desktop session which is the centralized parent of all subsequent apps. This is done with environment variables that are created. These variables (contain info for the DBUS-IPC mechanism) and are intended to be “inherited” by the child GUI processes.

If you independently launch individual gnome GUI apps without the proper pre-configured shared DBUS desktop instance via the INHERITED VARIABLES, then they will automatically create their own private DBUS instance . Thus you could end up with many MULTIPLES OF UNNECESSARY DBUS instances.

Describe the solution you'd like

WSL and/or WSL2 NEEDS configuration support for a PARENT INIT process that can run INIT scripts from which all subsequent child processes inherit their configuration variables.

Could we make this NEW wslg BLACK-BOX the new init process and solve two birds with one stone ?

Obviously this INIT PROBLEM has been around for a looonnnggg time , and the scope of the problem is relevant way beyond the simple reach of GUI APPS THAT USE DBUS

Additional context

A comprehensive and thorough GUI solution must address ancillary side issues like DBUS