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

[Keith]

On Thu, 16 Jul 2009 13:36:49 -0700, "Kevin O'Gorman" <kogorman at gmail.com>
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

Upon reinstall the root password may have been changed use

sudo su -
passwd:

to change

gksu will always default to the root account so try gksu without 
-u root
in it. There may be protection for remote users from access the 
root account. 


>this worked fine in intrepid.

Is the user part of the adm group?
Is the user id/login listed in /etc/sudoers    ?
To enable the root account you may need to change the password. If you
can't get sudo to work use single user mode from the grub menu 'e'dit
command
http://www.cyberciti.biz/faq/grub-boot-into-single-user-mode/


>
>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?


 This tells me that sshd the daemon that runs the service is not installed
or not started at boot time. 

sudo apt-get check sshd
sudo service ssh status

will tell you what the status is of installation and the network settings.
You should be able to use Administration > Services > ssh to enable the
service if it is not enabled.

These are some ideas to help you solve the issue. 
-- 
Best Regards, Keith 
http://home.comcast.net/~kilowattradio/