Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 168272 - [terminal-ssh] terminal not accepting input on first invocation
Summary: [terminal-ssh] terminal not accepting input on first invocation
Status: RESOLVED FIXED
Alias: None
Product: Target Management
Classification: Tools
Component: Terminal (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 2.0   Edit
Assignee: Martin Oberhuber CLA
QA Contact: Martin Oberhuber CLA
URL:
Whiteboard:
Keywords:
Depends on: 165432
Blocks:
  Show dependency tree
 
Reported: 2006-12-15 15:31 EST by David Dykstal CLA
Modified: 2008-08-13 13:20 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Dykstal CLA 2006-12-15 15:31:01 EST
Install the terminal from the update site. Use SSH to connect to the host Mac OS X (host and client are on the same machine). Terminal opens and shows correct login sequence but will not accept any input.

-----------Enter bugs above this line-----------
RSE 1.0.1 Testing
installation: eclipse-platform-3.2.1 (M20060921-0945)
RSE install: RSE-SDK-M20061215 update manager
java.runtime: Sun 1.5.0_06-112
os.arch: ppc
os.name: Mac OS X 10.4.8
------------------------------------------------
systemtype   : Unix-ssh (dstore-processes)
targetos     : Mac OS X 10.4.8
targetvm     : Sun 1.5.0_06-112
------------------------------------------------
Comment 1 David Dykstal CLA 2006-12-15 15:38:29 EST
This is apparently an error that either occurs on workspace startup or just after initial installation. Subsequent creations of the view appear to work OK.
Comment 2 Martin Oberhuber CLA 2006-12-15 16:34:09 EST
I think I also saw this on WinXP... could it be that you had a short timeout selected in the connection settings, such that the connection would have timed out before it was fully connected?
Comment 3 Masaki MURANAKA CLA 2007-01-25 10:49:48 EST
My eclipse on OSX also have same issue. 
I've tried to change parametes of timeouts on the preference page and/or the login dialog.
But it seems to be no effect.

I traced the code. When I touch my keyboard, It is called immediately that getOutputStream.write(bytetoSend) in TerminalControl.sendChar().

But no packet is reported by tcpdump. The connection has been established (according to netstat).

Maybe it caused by SshConnector.fOutputStream or JSch.
Comment 4 Masaki MURANAKA CLA 2007-01-25 12:29:01 EST
This issue is caused by Jsch.
After I create jsch-0.1.31.jar based plugin, my terminals have works fine.
According to jsch's recent ChangeLog, OSX support was rewritten.
 
Maybe developers shoud have some discussions because
jsch's fix is possible to effect not only the terminal but Team/CVS.
Comment 5 Martin Oberhuber CLA 2007-01-25 14:46:18 EST
Thanks for testing this.
There is already a plan to upgrade to jsch-0.1.31, see bug 165432.
Comment 6 Masaki MURANAKA CLA 2007-01-31 04:03:39 EST
Ooops...
This issue is caused not only by OSX. My WinXP box (i386) also similar.
(So it might a summary should be changed.)

Does the ssh access run on the other hosts like Linux, AIX?


> There is already a plan to upgrade to jsch-0.1.31, see bug 165432.

A good news.
Comment 7 Martin Oberhuber CLA 2007-01-31 04:14:08 EST
Updated summary and platform since it seems not to be mac specific.
Set target milestone 2.0M7 since Jsch-0.1.31 should be available by that time.
Comment 8 Martin Oberhuber CLA 2007-05-10 12:52:48 EDT
jsch-0.1.31 is not available yet. Changing target milestone to 2.0 -- Bug will be fixed and verified as soon as jsch-0.1.31 is available.
Comment 9 Martin Oberhuber CLA 2007-05-28 00:35:36 EDT
Platform won't get it before RC3
Comment 10 Martin Oberhuber CLA 2007-06-06 14:09:17 EDT
This should be fixed by using Eclipse 3.3RC3.

Please verify this using exactly the original steps:
 * Take eclipse-3.3RC3
 * Get TM build I20070606-1400 from the signedUpdates site at
   http://download.eclipse.org/dsdp/tm/signedUpdates
 * Verify that it works on the initial connect.
Comment 11 Martin Oberhuber CLA 2008-08-13 13:20:58 EDT
[target cleanup] 2.0 RC3 was the original target milestone for this bug