Cannot Start or Stop Units anymore, when nothing reads from the job completion channel

https://github.com/coreos/go-systemd/blob/d843340ab4bd3815fda02e648f9b09ae2dc722a7/dbus/methods.go#L48
The jobHandler used e.g. by Conn.StartUnitContext blocks for ever if nothing reads from the provided channel.
I think this write to the result channel should be non-blocking, like this:

	c.jobListener.Lock()
	out, ok := c.jobListener.jobs[job]
	if ok {
		select {
		case out <- result:
		default:
			fmt.Println("failed to write result to job channel")
		}
		delete(c.jobListener.jobs, job)
	}
	c.jobListener.Unlock()

I'm not sure, what is the best way to log something or if it's even necessary,

Read dbus/methods.go at the jobHandler code around line 48, then trace how Conn.StartUnitContext uses the provided job completion channel. Reproduce the hang with no reader on that channel. Done means the call no longer blocks forever when the result channel is unread, with the handling of a dropped result made explicit.