Comment 42 for bug 328575

(In reply to comment #23)

> One thing I'm assuming is that there's a shared NFS homedir.

Not applicable in the two major cases of:

* ssh -Y sysadmin from laptop to server
* su -

I'm not saying there aren't cases where the homedir is shared, but there are important cases where it isn't.

Anyways a lot to think about here, let me just dump some random thoughts:

* Not a big fan of requiring a rootless X server; admittedly in reality for the next 10+ years we'll need X on the free desktop, there does exist a wayland future ideally

* NFS home directories are always going to be last-one-wins "eat my data please" semantics, unfixably broken

* One *huge* wrench in any plans we have when discussing making remoting scenarios better (ssh etc.) is the possibility of different versions of dbus/X/ssh. In reality people are going to be running slow-releasing OSes like RHEL5 on servers for many years to come. And developers/sysadmins are likely going to be running faster-releasing OSes on their laptops. If for example we fix libgconf to be a special case in any way, that doesn't help because the machine-running-libgconf (client in X terms, RHEL5 server) isn't going to have it.

* In general, this kind of thing is always going to be broken in some way. We have enough problems with the regular desktop case as is. I think the focus should be on compatibility (don't break what worked before like "ssh -Y server firefox" to download stuff on the server), and flexibility (let apps make choices).

Anyways I'll try to evaluate your possible scenarios soon.