WSL: Unexpected dbus-launch response leads to panic when parsing for address

[johnnymo87]

In using this library via clisso, I encountered an exception parsing the output of dbus-launch. My machine was responding to that with the following:

process 7616: D-Bus library appears to be incorrectly set up; failed to read machine uuid: UUID file '/etc/machine-id' should contain a hex string of length 32, not len
gth 0, with no other text
See the manual page for dbus-uuidgen to correct this issue.
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-0SO9YZUBGA,guid=ac22f2f3b9d228496b4d4b935cae3417
DBUS_SESSION_BUS_PID=7620
DBUS_SESSION_BUS_WINDOWID=16777217

I think this is due to the fact that I'm running WSL, and I had to do the following to get dbus properly setup on my machine.

sudo apt-get install dbus-x11
sudo service dbus start

The code assumes the = will always preceed the \n, and thus does b[i+1:j]:

	i := bytes.IndexByte(b, '=')
	j := bytes.IndexByte(b, '\n')

	env, addr := string(b[0:i]), string(b[i+1:j])

In my case, the newline came before the equals sign, and thus the slice arguments made no sense and threw panic: runtime error: slice bounds out of range.