After upgrade to jaunty, cannot use gksu or log in via ssh

[NoOp]

On 07/16/2009 01:36 PM, Kevin O'Gorman wrote:
> I have a Dell inspirion laptop on which I installed intrepid about a
> year ago when I got it.
> I upgraded to jaunty yesterday and while most things are working for
> me, there are still two things that don't.
> 
> 1) gksu does not work.  The first time I use it, it silently fails
> with return value 1.  The second time it gives an error message that
> it cannot contact the gconf daemon.  This suggests that the first
> attempt has killed the daemon as well as causing an error.  I have no
> idea what to do about this.  My usual command-line is
>    gksu -u root x-terminal-emulator
> this worked fine in intrepid.
> 
> 2) As a work-around I tried logging in via ssh, but there appears to
> be no ssh daemon despite my attempts to configure it.  The connections
> on port 22 are always refused.
> 
> Any help?
> 

See the "Cannot run root terminal via main menu" thread:

It's a bug (mine doesn't work either):
https://bugs.launchpad.net/ubuntu/+bug/326158
[Root terminal doesn't start]
https://bugs.launchpad.net/ubuntu/+source/gconf2/+bug/328575
[Cannot start gnome-terminal because of gconf error]
http://bugzilla.gnome.org/show_bug.cgi?id=564649
[should handle gconf failure more gracefully]
http://bugzilla.gnome.org/show_bug.cgi?id=555745
[Programs using Gconf fail if you start via "su"]
also
https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/120589