On 2014-03-29 07:01, Linda Walsh wrote:
Carlos E. R. wrote:
I am getting a bit farther, but I still get a connection timeout.
Could you tell me what you get when you type: echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n'
in the local client before 'ssh', and then the same on the remote client.
+++······························· cer@Telcontar:~> echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n' unix:abstract=/tmp/dbus-jaontsAgqI,guid=4ce03300a65d0c645e8d245a533036b7 cer@Telcontar:~> ssh -X cer@AmonLanc.valinor Password: Last login: Sat Mar 29 22:14:34 2014 from telcontar.valinor Have a lot of fun... cer@AmonLanc:~> echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n' cer@AmonLanc:~> ·······························++- That's a laptop without gnome nor kde installed, because it is old and I use LXDE. It has some gtk and qt libraries, as required by dependencies by other packages - like meld, the qt flavour of yast, gkrellm... An this my relatively modern laptop, with both gnome and kde installed, I think. Gnome is installed, I tried it recently. KDE I don't remember: ······························· cer@Telcontar:~> ssh -X cer@minas-tirith.valinor Password: Last login: Sat Mar 29 22:22:22 2014 from elessar.valinor Have a lot of fun... cer@minas-tirith:~> echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n' cer@minas-tirith:~> ·······························++- On both machines meld works remotely. Both have Intel graphics.
In my case, I have: law.Bliss> echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n' tcp:host=Athenae.hs.tlinx.org,port=47000,guid=94e7aeae46abdf95e9562eea53362166
Curious, mine says "unix:abstract".
1808 12582913 law.Bliss> ssh ishtar
But it will not work that way, you need -X or -Y.
Ishtar:law> echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n' tcp:host=Athenae.hs.tlinx.org,port=47000,guid=94e7aeae46abdf95e9562eea53362166
1808 12582913 i.e. -- they show the same. But in the console, I see: (minus the python tracebacks) (meld:8431): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Because you are not using -X nor -Y, and it appears you have a dbus active, meld tries to use it, and fails, of course, it is on a different machine. In my case, I do not have a dbus on that session, so meld does not try. Look: +++······························· cer@Telcontar:~> ssh cer@AmonLanc.valinor Password: Last login: Sat Mar 29 22:18:07 2014 from telcontar.valinor Have a lot of fun... cer@AmonLanc:~> meld p p1 /usr/lib/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) /usr/bin/meld:150: GtkWarning: IA__gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed gtk.icon_theme_get_default().append_search_path(meld.paths.icon_dir()) Traceback (most recent call last): File "/usr/bin/meld", line 150, in <module> gtk.icon_theme_get_default().append_search_path(meld.paths.icon_dir()) AttributeError: 'NoneType' object has no attribute 'append_search_path' cer@AmonLanc:~> cer@AmonLanc:~> echo $DBUS_SESSION_BUS_{ADDRESS,{P,WINDOW}ID}$'\n' cer@AmonLanc:~> ·······························++- Well, I do not get a dbus, but you see meld fails completely if I don't use the "-X" option to ssh. A different reason, thoug, it doesn't say anything about dbus. Both machines behave the same. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)