John: In the upstream code GConf uses DBus now just as a naming service to avoid multiple copies, but not yet for IPC.
Halton: Clearing the environment as Erwann suggested will probably work. But I want to emphasize that having a different uid connect to your X session is not something we want to support. The reason is that the other uid has *total control* over your X session, and therefore effectively can do anything it wants to programs running as your uid.
If you are running gedit as another user to gain access to a file for example, I suggest using ACLs. If you don't want the other programs to have access to your files etc. (i.e. you're running as a test user for sandboxing reasons), then the correct thing to do is to create a new login session as that user.
John: In the upstream code GConf uses DBus now just as a naming service to avoid multiple copies, but not yet for IPC.
Halton: Clearing the environment as Erwann suggested will probably work. But I want to emphasize that having a different uid connect to your X session is not something we want to support. The reason is that the other uid has *total control* over your X session, and therefore effectively can do anything it wants to programs running as your uid.
If you are running gedit as another user to gain access to a file for example, I suggest using ACLs. If you don't want the other programs to have access to your files etc. (i.e. you're running as a test user for sandboxing reasons), then the correct thing to do is to create a new login session as that user.