Comment 10 for bug 1477086

As far as I'm concerned, ship it! (Subject to whatever QA is needed within Ubuntu.) I'm glad the delta has got smaller.

If you badly need 1.10.0 tomorrow, that can happen. It will likely be functionally identical to 1.9.20, so that should be an easy freeze exception in any case.

Regarding your changes:

The patch for LP: #1438612 was rejected upstream: Lennart said it's wrong, and the systemd author's opinion seems relevant here. Accordingly, I'm not going to take that in Debian or upstream. If it's necessary in Ubuntu, that's your call.

dbus.user-session.upstart seems way more complicated than it needs to be, but it's what you have now, so it isn't going to be any worse than 1.8.

User session bits for future reference:

If Upstart is still a first class citizen, and you only need one socket per XDG_RUNTIME_DIR, I would recommend using unix:path=$XDG_RUNTIME_DIR/bus like dbus-user-session does under systemd, instead of doing weird things with abstract sockets. libdbus, sd-bus and recent (2.45.x) GLib will try that address by default if DBUS_SESSION_BUS_ADDRESS is not set, although I still recommend setting it for backwards compat.

If you have a requirement for multiple login sessions (with their own buses) per XDG_RUNTIME_DIR, you could use the closest possible, unix:path=$XDG_RUNTIME_DIR/$YOUR_SESSION_ID.bus or $XDG_RUNTIME_DIR/login-$YOUR_SESSION_ID/bus or something.

In the systemd --user world, I recommend the new dbus-user-session package as the best way to get a bus per XDG_RUNTIME_DIR. It is currently useless on non-systemd, but should be harmless there.

I do not plan to support dbus-launch on non-X11, and I hope it can wither into irrelevance over time. I would like to be able to say that Wayland and Mir systems will always use XDG_RUNTIME_DIR/bus for their D-Bus socket.