Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DBus machine ID not initialised #3552

Closed
mdh34 opened this issue Sep 18, 2018 · 2 comments
Closed

DBus machine ID not initialised #3552

mdh34 opened this issue Sep 18, 2018 · 2 comments

Comments

@mdh34
Copy link

mdh34 commented Sep 18, 2018

  • 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.

@therealkenc
Copy link
Collaborator

should ideally be set on installation.

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.

@therealkenc
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants