gonjyu121 / superputty

Automatically exported from code.google.com/p/superputty
MIT License
0 stars 0 forks source link

Putty session failing to anchor in SuperPuTTY 1.4.0.5 #496

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.start Superputty and connect to host 
2. Trying to start a second session within the Superputty produces 
Application_ThreadException.  

What is the expected output? What do you see instead?
Putty sessions open up outside of SuperPutty.  Have seen references to similar 
effect when usign Teamview.  No teamview involved in this session.  

What version of the product are you using? On what operating system?
 clean Win7 64 Enterprise install, Superputty 1.4.0.5, Putty 0.63

Please provide any additional information below.
This is happening to a number of colleagues with Win7.  

2015-02-06 07:41:50,496 INFO  HostConnectionString - Parsed[kal001]: proto=, 
host=hostname, port=
2015-02-06 07:41:50,499 INFO            SuperPuTTY - Opening putty session, 
id=ConnectBar/hostname
2015-02-06 07:41:50,501 INFO        PuttyStartInfo - Putty Args: '-ssh -pw 
XXXXX -P 22  -l loginname hostname'
2015-02-06 07:41:50,531 WARN      ApplicationPanel - Unable to get handle for 
process on first try.
2015-02-06 07:41:50,535 DEBUG ildWindowFocusHelper - WndProcForFocus: 
shellhook=False, wm=NOTIFYFORMAT, wParam=1049756, lParam=3
2015-02-06 07:41:50,536 DEBUG ildWindowFocusHelper - WndProcForFocus: 
shellhook=False, wm=QUERYUISTATE, wParam=0, lParam=0
2015-02-06 07:41:50,537 DEBUG ildWindowFocusHelper - WndProcForFocus: 
shellhook=False, wm=NOTIFYFORMAT, wParam=1574112, lParam=3
2015-02-06 07:41:50,538 DEBUG ildWindowFocusHelper - WndProcForFocus: 
shellhook=False, wm=QUERYUISTATE, wParam=0, lParam=0
2015-02-06 07:41:50,542 DEBUG ildWindowFocusHelper - WndProcForFocus: 
shellhook=False, wm=SETTEXT, wParam=0, lParam=50253832
2015-02-06 07:41:50,544 DEBUG           SuperPuTTY - STATUS: Opened session: 
ConnectBar/hostname [SSH]

Original issue reported on code.google.com by jiman...@gmail.com on 6 Feb 2015 at 3:59