You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Your Windows build number: 10.0.17134.285 & Ubuntu 18.04.
What you're doing and what's happening: Attempting to run dbus-launch fails.
What's wrong / what should be happening instead: The DBus machine-id isn't initialised and is left empty, meaning that dbus-launch and associated tools fail with machine ID '' looks like it's the wrong length, should be 32 hex digits.
This can be fixed by running sudo systemd-machine-id-setup but should ideally be set on installation.
The text was updated successfully, but these errors were encountered:
Sadly that ask (as phrased) is tag 'external' because MSFT/WSL does not control Ubuntu userspace or the Store App or the launcher. Alternatively WSL would need to support systemd per #994, which I think (?) might set up the machine id on startup if it is missing (if it doesn't, it could). Or WSL init could do more systemd things per #2530.
Closing since there isn't a WSL actionable. You could try asking Canonical to update their launcher and make systemd-machine-id-setup part of install process. More practically, run the command yourself as suggested and grumble under your breath a little when you hit the enter key.
Your Windows build number: 10.0.17134.285 & Ubuntu 18.04.
What you're doing and what's happening: Attempting to run
dbus-launch
fails.What's wrong / what should be happening instead: The DBus machine-id isn't initialised and is left empty, meaning that
dbus-launch
and associated tools fail withmachine ID '' looks like it's the wrong length, should be 32 hex digits
.This can be fixed by running
sudo systemd-machine-id-setup
but should ideally be set on installation.The text was updated successfully, but these errors were encountered: