[13:21] <shadeslayer> hi, I'm on Kubuntu and I don't seem to have a com.ubuntu.Upstart interface on the session bus
[13:22] <shadeslayer> it does sometimes appear, but currently doesn't seem to be there
[13:22] <shadeslayer> any ideas?
[13:40] <jodh> shadeslayer: yes - that is bug 1258098 - I've fixed the bug. Just needs to be reviewed by an Upstart developer such that we can get it into the next release (this/next week I'm hoping).
[13:41] <shadeslayer> aha cool, I just wanted to be informed since I landed a patch in kde-workspace that allows suspending via the logind interfaces provided by com.ubuntu.Upstart a few weeks back
[13:41] <shadeslayer> and I started noticing lately that my laptop did not suspend since there was no com.ubuntu.Upstart
[13:43] <jodh> shadeslayer: oh - are you talking about the system bus?
[13:43] <shadeslayer> jodh: no, session bus
[13:44] <jodh> shadeslayer: right, that bug is the reason then :) fwiw until recently, the Session Init didn't connect to the Session Bus at all since it has a private socket anyway.
[13:45] <shadeslayer> huh,weird, I did have a com.ubuntu.Upstart interface at some point and it did work :)
[13:45] <shadeslayer> tested it quite a bit
[13:45] <shadeslayer> ah well, /me will wait for fix to land
[13:46] <jodh> shadeslayer: it works as expected until the Session Init is restarted. This happens automatically on Ubuntu if the upstart package gets upgraded (or any of its dependencies; libc, libnih, etc).
[13:47] <shadeslayer> ahhh
[13:57] <jodh> shadeslayer: there is a work-around: run "initctl notify-dbus-address $DBUS_SESSION_BUS_ADDRESS" as required and the Session Init will reconnect to the Session Bus.
[14:02] <shadeslayer> thx, that does work