[Bug 360360] Re: 2nd /3rd > ssh key fails to be used

2010-12-08 Thread Launchpad Bug Tracker
[Expired for seahorse (Ubuntu) because there has been no activity for 60 days.] ** Changed in: seahorse (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. https://bugs.lau

[Bug 360360] Re: 2nd /3rd > ssh key fails to be used

2010-05-21 Thread Oliver
I have a similar problem. I upgraded from karmic to lucid recently. Before that I could login to my servers with my id_rsa key. Since that upgrade it is not possible. this is the relevant part of the ssh debug: debug1: PEM_read_PrivateKey failed debug1: read PEM private key done: type -- 2nd

[Bug 360360] Re: 2nd /3rd > ssh key fails to be used

2010-03-18 Thread mrandrzejak
I am having the same problem "no setup signature found". I have a 9.10 fresh install and now trying to run a 10.04 alpha 3 disc and getting the error message when trying to install 10.04. I will try the idea above. -- 2nd /3rd > ssh key fails to be used https://bugs.launchpad.net/bugs/360360 You

[Bug 360360] Re: 2nd /3rd > ssh key fails to be used

2009-04-17 Thread xpd259
hiya it still does it but i find logging out and back in sorts the problem -- 2nd /3rd > ssh key fails to be used https://bugs.launchpad.net/bugs/360360 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs

[Bug 360360] Re: 2nd /3rd > ssh key fails to be used

2009-04-14 Thread xpd259
removing the file didn't help I'm going to reinstall as i want to use ext4 and this install was a intrepid alpha I will try again and report back with a fresh install -- 2nd /3rd > ssh key fails to be used https://bugs.launchpad.net/bugs/360360 You received this bug notification because you are

[Bug 360360] Re: 2nd /3rd > ssh key fails to be used

2009-04-13 Thread Andreas Moog
Thanks for your report. Try to remove/rename /etc/X11/Xsession.d/90gpg- agent. After that, please relogin. Does that solve your issue? ** Changed in: seahorse (Ubuntu) Importance: Undecided => High ** Changed in: seahorse (Ubuntu) Status: New => Incomplete -- 2nd /3rd > ssh key fails