On Fri, Jan 11, 2013 at 12:24:42PM +0000, steve-alug@hst.me.uk wrote:
On 10/01/13 19:48, Chris Green wrote:
I was considering using VNC to access another box on my LAN but as the remote system (which would run a VNC server) doesn't currently have X running on it (though there's a Lubuntu desktop available) it makes VNC rather awkward.
[snip]
E.g. if I try and run nm-connection-editor on the remote system via an "ssh -x remote-system" connection it pops up a window on my system but there's an error:-
** (nm-connection-editor:3088): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-9FFbE3UfRz: Connection refused... and it doesn't actually work.
Or can anyone suggest how to get around the dBus communication issue?
Have you actually tried connecting via VNC and if so, what goes wrong? What are the DBUS issues? I'm connecting to a lubuntu 12.10 desktop OK using the default gnome screen VNC server (whose name escapes me) and it works fine.
I mentioned VNC because it would solve the DBUS issues.
Running the 'classic' X client/server model the program runs on the client but the X server provides display facilities. I think the resulting problem with DBUS and such is that some of the communication 'hooks' come from the display routines and try and talk to DBUS on the wrong system.
If you run VNC (or x2go or xrdp) then the whole display is exported from one system to the other and you don't have the server/client split as you do with classic X - so, no problems with dBus. Actually x2go and xrdp start up their own desktop rather than connecting to an existing desktop like VNC, for me this is a better approach as there isn't a desktop running on the 'remote' system.
As I said in my previous response I have got xrdp working and that sorts the problem for me.