"You will find this is due to SSH not being able to map your IP to name
as is normally caused by a non responding DNS server in
/etc/resolv.conf. As such if you update this with one that work you
should find it suddenly comes to (life)."
--
edgy - ssh client freeze
https://bugs.launchpad.net/bugs
[Expired for seahorse (Ubuntu) because there has been no activity for 60
days.]
--
edgy - ssh client freeze
https://bugs.launchpad.net/bugs/63479
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
This bug is related to #105818 and #91116.
Here's the fix that worked for me:
Preface: Seahorse does not work with gpg-agent (see
http://live.gnome.org/Seahorse/SessionIntegration).
The behavior that I observed is exactly the same as what others have
mentioned in this ticket and in #105818. Sea
I have been hit by this bug today as well. For some reason, seahorse
doesn't seem to respond to the auth socket. seahorse-preferences claims
there was no ssh agent running. I didn't find out what went wrong in
seahorse.
Reassigning to seahorse therefore, openssh is not at fault here.
** Changed
I also have this problem. This bug is the first sensible discussion of the
issue I have found all day. I've actually been able to do something using the
tty1, thanks for that tip!
I am using gnupg with enigmail for thunderbird. In the course of
working with it, I've installed several key age
Yes, ssh was hanging again for me again so I tried to kill
seahorse-agent and seahorse-daemon and then ssh worked. So that at
least narrows down the problem.
--
edgy - ssh client freeze
https://launchpad.net/bugs/63479
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubun
Somebody mentioned on IRC that this could be due to running both ssh-
agent and seahorse-daemon. I'm not familiar with seahorse ...
--
edgy - ssh client freeze
https://launchpad.net/bugs/63479
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
I am experiencing the same problem after an upgrade from dapper to edgy.
I do NOT, however, have ssh-agent in my gnome session. Additional
testing revealed that the ssh-agent process is being launched via
Xsession (/etc/X11/Xsession.options). It locks up so hard that it can
not even be killed but b
I think I caused the problem by adding ssh-agent into GNOME session.
Without it it's all OK
--
edgy - ssh client freeze
https://launchpad.net/bugs/63479
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I have this problem AGAIN, no idea why and why it was not happening for some
time.
With other terminals under X, like xterm it's the same.
--
edgy - ssh client freeze
https://launchpad.net/bugs/63479
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/lis
Ok this is pretty strange, and I don't really understand what is
happening. I had rebooted to see if it would resolve itslef but the
problem persisted. Then I tried to log out of gnome but it was hanging
so I killed all my user's processes. When I logged into GNOME again the
problem was resolved
I am experiencing the same behavior
([EMAIL PROTECTED]:~)% ssh -v localhost
(23:13)
OpenSSH_4.3p2 Debian-4ubuntu1, OpenSSL 0.9.8b 04 May 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to localho
I am sorry, false alarm - it seems to work now also from gnome-terminal.
It was probably some issue with my configuration. You may close this
bug.
--
edgy - ssh client freeze
https://launchpad.net/bugs/63479
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
Below is sample output
[EMAIL PROTECTED]:~$ ssh -v [EMAIL PROTECTED]
OpenSSH_4.3p2 Debian-4ubuntu1, OpenSSL 0.9.8b 04 May 2006
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to juliusz.mat.umk.pl [158.75.2.230] port 22.
debug1: Connection e
Could you please run ssh with the -v option. This will tell you at what
point the client is hanging.
** Changed in: openssh (Ubuntu)
Status: Unconfirmed => Needs Info
--
edgy - ssh client freeze
https://launchpad.net/bugs/63479
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
h
15 matches
Mail list logo
