Comment 79 for bug 328575

Let me be more accurate here. Gnome-terminal works fine, *ONLY* root terminal
fails (gksu /usr/bin/x-terminal-emulator fails to execute). Hence, GConf may be
error-free in this case.

Quoting Alwin Roosen <email address hidden>:

> I have the same problem after upgrade from Intrepid to Jaunty.
>
> I don't know of this is information is useful, but i experience this
> issue problem trying to start gnome-terminal from
> /etc/gdm/PostSession/Default. This script is run when the user logs out
> of the system. In Intrepid, a terminal pops out in front of the user,
> but it does nothing in Jaunty. The terminal does not start, and I get
> this very same error.
>
> What I don't understand is that the very same command works perfectly
> when started from /etc/gdm/PostLogin/Default. This script is run right
> after user logon.
>
> And when i try to run it between logon and logoff, manually from
> terminal, it also works.
>
> I tried the suggested workaround which seems to solve the problem when
> executed from /etc/gdm/PostSession/Default
>
> --
> Cannot start gnome-terminal because of gconf error
> https://bugs.launchpad.net/bugs/328575
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.

------------------------------------------------------------------------
This message was sent using IMP, the Webmail Program of Haifa University