GNOME Bugzilla – Bug 585255
First time that daemon is started via dbus, it throws exception
Last modified: 2009-06-09 19:19:14 UTC
See downstream bug https://bugs.edge.launchpad.net/ubuntu/+source/bzr-gtk/+bug/377476 The first time you start seahorse-daemon via dbus activation, it dies with an error: "Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0" But it seems like a false-negative, since seahorse-daemon is actually started and will field future dbus requests. An easy test for this is: $ killall seahorse-daemon $ dbus-send --print-reply --dest=org.gnome.seahorse /org/gnome/seahorse/opengpg org.gnome.seahorse.Keys.Test Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0 $ dbus-send --print-reply --dest=org.gnome.seahorse /org/gnome/seahorse/opengpg org.gnome.seahorse.Keys.Test Error org.freedesktop.DBus.Error.UnknownMethod: Method "Test" with signature "" on interface "org.gnome.seahorse.Keys" doesn't exist $ killall seahorse-daemon $ dbus-send --print-reply --dest=org.gnome.seahorse /org/gnome/seahorse/opengpg org.gnome.seahorse.Keys.Test Error org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 0
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 583356 ***