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 :
> I have the same problem after upgrade from Intrepid to Jaunty.
>
> I don't know of this i
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 Maxim Levitsky :
> Thus I still thing gnome-terminal should work without gconf
>
> --
> Cannot start gnome
On Wed, 2009-04-29 at 17:44 +, bjd wrote:
> Been following these comments -- all the while finding myself more and more
> dumbfounded. This bug is over two months old.
More and more bugs lately seem to befall this fate sadly, of just
lingering on and on and nothing being done.
> There's anoth
I do not see how commenting that out is a good idea if that comment is
correct. Instead, it appears to me to be a bug in the
gconf_ping_daemon. If the gnome-terminal can run just fine under sudo,
then the gconf_ping_daemon should be using the actual user ID, not the
effective user ID to try to get
On Wed, 2009-04-29 at 13:39 +, Pibo wrote:
> @ Adam Yao:
> could you please be more specific? Are you meaning that you've found some
> applications other than the root terminal which undergo this GConf's issue,
> or that the fact the terminal is unusable affects other activities of yours?
>
