If this is supposedly fixed, how come using ssh -X user@server still
hangs if you have run an X-windows program like 'eog' or similar?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
Marking Fix Released per reporter's comments. Feel free to nominate for
release for an SRU for Lucid if a minimal patch can be found to address
the issue. Thanks.
** Changed in: openssh (Ubuntu)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member
With 10.04 i386 on my Dell Latitude 2100 laptop I find that attempting
to exit from ssh -X usern...@remotemachine is not returning to the
local command prompt after using an X-session on the remote machine. It
returns fine when I don't start an X program though.
Is this related to port forwarding
** Changed in: openssh (Ubuntu)
Importance: Undecided = Medium
--
Forwarded ports not closed to remote ssh2 server in FIN_WAIT_2
https://bugs.launchpad.net/bugs/582740
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in ubuntu.
are you able to test if this issue is present in maverick , which has
1:5.5p1-4ubuntu1 ?
Additionally, in the interim, you can quite likely use Collin's ppa for
lucid:
http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2010-05-10-openssh-5.5p1
-for-lucid.html
** Changed in: openssh
Scott - I switched to Colins PPA a few hours after testing the daily
snapshot and can confirm it's fixed in his PPA, 1:5.5p1-3ubuntu1.
It'd be nice to streamline standard lucid with 5.5p1 - though I
understand 5.5 has many new features.
For me 1:5.3p1-3ubuntu3 and 1:5.3p1-3ubuntu4 has a defect
Bug doesn't occur in 5.5p1 current Openssh daily snapshot, it's specific
to 5.3
--
Forwarded ports not closed to remote ssh2 server in FIN_WAIT_2
https://bugs.launchpad.net/bugs/582740
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Update:
If I use the ssh binary from package openssh-client_5.1p1-6ubuntu2_amd64.deb
9.10 (Karmic) on my 10.04 system as the Session 2 caller to the remote ssh2
server, then session 1 shows the ports closing down correctly confirming the
channel is dead, like they would on a native 9.10 system.
Problem still present in todays proposed release
ii openssh-client1:5.3p1-3ubuntu4
secure shell (SSH) client, for secure access
ii openssh-server1:5.3p1-3ubuntu4
secure shell (SSH)
