Yes I have installed likewise-open5 and left a domain (and then rejoined
the domain). This does seem to be a duplicate of bug 354498. My
/etc/apparmor.d/abstractions/nameservice is attached.
** Attachment added: "/etc/apparmor.d/abstractions/nameservice"
http://launchpadlibrarian.net/24923021/n
Reading https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/339097 it looks like gnome-keyring is acting as the ssh-
agent, so maybe the problem is with that rather than seahorse.
Roger
--
ssh are using ssh-userauth but ignores private key
https://bugs.launchpad.net/bugs/348126
You rec
@rancor
Can you try your key that doesn't work using ssh-agent in a non-Gnome
session, either by switching to a different TTY or by ssh'ing into the
Jaunty box from elsewhere (without Agent Forwarding: ssh -a ...)?
It might be that the problem is with seahorse rather than openssh-
client, given m
I have a system running Jaunty Beta AMD64 with ssh 1:5.1p1-5ubuntu1.
I have two private keys, both of which are valid in a number of remote
servers. If I copy one of the keys to ~/.ssh/id_rsa everything works
correctly. If I copy the other key to ~/.ssh/id_rsa it does not work
within gnome using s
Public bug reported:
I am running Jaunty Beta on AMD64, I have dhcp3 (3.1.1-5ubuntu7)
installed.
Network Manager shows the constant spinning icon, and never gets an IP
address.
My /var/log/messages has:
Mar 31 15:54:51 hostname kernel: [ 23.264536] type=1503
audit(1238504091.637:14): operatio
