Possible to Use Orage on Remote Systems?

[Snood]

Yves-Alexis Perez wrote:
> You might want to check the DISPLAY and other environment variables
> (like, if you ssh with -X). I guess the process is waken by dbus but I'm
> not that sure.

Tino Keitel wrote:
 > Yves already pointed to dbus and environment variables. This is also
 > my guess. A a look into the files in ~/.dbus/session-bus/ of your
 > remote host should give you the proper variables for the dbus session.


Well, it has been a bit of an adventure. At first I couldn't seem to get 
the same untoward behavior at home as I had seen at the remote LAN, but 
some persistence on my part brought out some inconsistency on the part 
of Orage's behavior in this environment. I still have no clue as to 
whether or not anything about Orage itself is the cause, or whether 
there's something in the environment settings of these Debian Squeeze / 
Xfce systems that is at fault.

Over the past couple of days the following software upgrades to Debian 
Squeeze have resulted in an absolutely consistent and more 
understandable (I think) behavior from Orage.

--begin excerpt from aptitude log--
[UPGRADE] dbus 1.2.16-2 -> 1.2.20-2
[UPGRADE] dbus-x11 1.2.16-2 -> 1.2.20-2
[UPGRADE] libdbus-1-3 1.2.16-2 -> 1.2.20-2
[UPGRADE] python-xdg 0.18-1 -> 0.19-1
---end excerpt from aptitude log---

Before these updates were applied I checked the ~/.dbus/dbus-session 
contents of all involved systems. I went through the man pages and other 
information I could find on dbus-launch. Some experimentation resulted 
in various changes in behavior, but none of those changes were of any 
real benefit to me in my intended use of Orage on the remote systems.

Since those upgrades were applied I at least can consistently choose to 
run Orage either on the local system or on a remote system, but I have 
to choose between running it on the local system or on a single remote 
system. Having more than one instance of Orage displaying data on a 
single system by whatever method seems to not be allowed.

At this point I have put rather more effort into this little project 
than a good outcome would be likely to be worth to me, so I'm going to 
throw in the towel -- at least for now. When I'm not so busy I may 
return to visit the issue.

In the meantime, if anyone is interested, I did find another person who 
has seen this same you-can-have-me-running-on-the-local-system-or-you
-can-have-me-running-on-the-remote-system-but-you-can't-have-both" 
behavior by another application. He said he saw this with a version of 
the Netscape browser years ago, and that he never found a reason or a 
solution -- until he started using different versions of everything 
(browser, Debian, etc.). He was using ssh -X sessions, same as me.

I suppose my plan to use Orage in this particular manner may be a fringe 
application of the software. I really like Orage, so I'll continue to 
use it and just forgo its use on remote systems.

Thank you for your consideration.