Comment 1 for bug 1417456

Here is a minimal test program. When I run it on my snappy box I get (with dbus-moitor running).

I can usually reproduce this when I kill the daemon and it gets dbus-activated. Subsequent runs work as expected. I wonder if it could be that the signal filter is created when there is no system-image on the dbus (yet).

The output of dbus-monitor:
# ./lala
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=37 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.13"
   string ""
   string ":1.13"
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=38 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string ":1.14"
   string ""
   string ":1.14"
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=6 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged
   string "com.canonical.SystemImage"
   string ""
   string ":1.14"
signal sender=:1.14 -> dest=(null destination) serial=10 path=/Service; interface=com.canonical.SystemImage; member=UpdateAvailableStatus
   boolean true
   boolean false
   string "266"
   int32 29293320
   string "2015-02-03 07:42:10"
   string ""
panic: ERROR: timed out after 30 seconds waiting for system image server to respond