[Python-apps-team] Bug#723058: xpra: fails to start remote server

[Antoine Martin]

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


> I am currently unable to start a remote server:
>
> servo:~ 0$ xpra start ssh:music at cyrano:100
> 2013-09-15 15:23:36,404 failed to locate the dbus notification service
> 2013-09-15 15:23:37,373 Connection lost
> 2013-09-15 15:23:37,373 connection closed after 0 packets received (0
bytes) and 1 packets sent (7579 bytes)
> servo:~ 0$
Looks like a bug.
Assuming this is not a Debian packaging bug (looks unlikely), can you
please file a ticket upstream with more details.
>
> The result of this apparently-successful operation (note the return
> code is 0) is no running xpra server on the remote host (cyrano).  I
> can otherwise connect to the remote server via ssh fine, and once
> there I can start a session just fine:
Please check the server log file (clearing it before testing).
It may also be something to do with your login shell.
> I'm unclear where the console messages (such as "failed to locate the
> dbus notification service") are coming from (local or remote host?).
> In either case, dbus is available on both machines.
See the man page. You need a dbus server running for the xpra server to use.
Having dbus installed is not sufficient. If you want dbus available in
your xpra server, use:
dbus-launch xpra start ...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlI2g7EACgkQGK2zHPGK1ruG8QCfW2gqCOLsbgJZXau3PIT6K92r
hPQAnjunFAzOdhYNFLM+lvScasQRfiCD
=kqy5
-----END PGP SIGNATURE-----