In a bit of a panic. . .

John Arbash Meinel john at arbash-meinel.com
Thu May 22 15:36:29 BST 2008


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jonathan Lange wrote:
| On Thu, May 22, 2008 at 12:57 PM, Russel Winder
| <russel.winder at concertant.com> wrote:
|> Does anyone know why the message:
|>
|> bzr: ERROR: Could not understand response from smart server: ('error',
|> 'org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute
|> dbus-launch to autolaunch D-Bus session')
|>
|> might occur on a on a commit to a bound branch.  As far as I can tell I
|> have bzr, bzrtools, bzr-dbus, python-dbus, etc. all installed and all
|> the same on server and client.
|>
|> The commit happens but the checkout is not updated.  I have to do a
|> manual update to get everything synchronized again.
|>
|
| A full diagnosis will have to wait for someone who knows more about
| bzr-dbus. However, I suspect an interim fix is to disable / uninstall
| the bzr-dbus plugin on your server.
|
| Specifically, the error message indicates that Bazaar can't get a dbus
| session on the server. It won't try to do this if you don't have the
| plugin installed.
|
| jml
|
|

It seems to specifically be failing as part of the 'post-commit' steps. After
the master branch has been updated, before the local one has. (Otherwise you
wouldn't need to do the 'bzr update'.)

I'm guessing bzr-dbus is trying to do a post-branch-tip-modified announcement to
someone, but is failing to get a dbus session. I don't know if the correct thing
is to just disable dbus, to have the dbus plugin give a warning instead of a
full exception, etc.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkg1hOwACgkQJdeBCYSNAAMe8wCfbE5Hd7x2Lw6Si/78Thh8i8PN
3f8AnRmb/vfaMl13H+QPnRXqUfbH9clJ
=UAu4
-----END PGP SIGNATURE-----



More information about the bazaar mailing list