On Fri, 2009-06-12 at 19:57 -0700, Ross Boylan wrote:
> On Fri, 2009-06-12 at 17:00 -0430, Patrick O'Callaghan wrote:
> > On Fri, 2009-06-12 at 11:05 -0700, Ross Boylan wrote:
> > > I'm having trouble running evolution remotely, that is
> > > ssh -X othersystem
> > > othersystem> evolution &
> > > 
> > > This used to work pretty reliably when I did an evolution
> > > --force-shutdown first, but no longer.  The window either does not
> > > appear, or appears and works for awhile, and then stops repainting.  The
> > > latter seems to happen when I switch virtual desktops and switch back.
> > > 
> > > Previous messages suggest that the problem is that evolution launches by
> > > sending a request to bonobo-activation server, which is running outside
> > > of my ssh session.
> > > 
> > > Is there a way to get things working OK, i.e., having the display appear
> > > on my local machine?  It would also be fine if I could run evo on my
> > > local machine but have it talk to the remote server.
> > 
> > The remote server for what? If it's a mail server, no problem, just
> > configure Evo as normal. Otherwise, not so much.
> I was thinking of the evolution back end.  I have feeling the only
> back-end server might evolution-data-server, and that only handles stuff
> like the address book, not email.

Indeed. The name is somewhat confusing. You reasonably can't run e-d-s
on one machine and the Evo front-end on another, and it wouldn't do you
much good even if you could.

> Either way, I think I'm in the "not
> so much" category.
> 
> > 
> > > I'm on Debian Lenny, evo 2.22.3.1
> > > libbonobo2-0                        2.22.0-1 
> > > The local and remote machines are both running KDE, though the remote
> > > session is not.
> > 
> > Not important.
> > 
> > > Any suggestions?  Thanks.
> > 
> > Sounds like you want VNC. This runs a second X server on the remote
> > machine and sends the I/O back and forth to your local machine via a VNC
> > client. The advantage is that you have an entire remote desktop session
> > (not just a remote application). Also, the I/O protocol tends to be much
> > more efficient than pure X. You can even share the same desktop session
> > between the two machines, e.g. start typing a message at the office,
> > leave Evo running, go home and continue typing the same message.
> Thanks for the tip.  It not only helps me, but someone who asked on an
> unrelated list about something that worked like screen for X.
> 
> I still wish that evo just worked with X, the way most other
> applications do.  Maybe it's a general GNOME thing?

I've no doubt this can be done, i.e. it's not a fundamental problem with
Evo (or Gnome), but VNC is probably easier.

poc

_______________________________________________
Evolution-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/evolution-list

Reply via email to