Mintty.exe: Process has exited, so the requested information is not available.

[neuromancerxi]

Mintty 2.1.4 (x86_64-pc-cygwin) Error on launch (but spawns separate window): Invalid Operation Error - Process has exited, so the requested information is not available.

[jimradford]

Thanks for the Bug report. Unhandled exceptions should never be thrown. @neuromancerxi can you do me a favor and try to recreate this exceptions being thrown with debug enabled? Also what version of SuperPutty are you running?

[neuromancerxi]

Superputty 1.4.0.6

Do you have directions that I can follow to provide you with greater detail? I didn't see any options in the menus or notes on running SuperPutty with debugging enabled.

Logs:

2015-09-19 21:13:33,423 DEBUG frmSuperPutty - [263126] Activated 2015-09-19 21:13:33,429 INFO TabSwitcher - Cleaning up old strategy: Visual: Left-to-Right, Top-to-Bottom 2015-09-19 21:13:33,430 INFO TabSwitcher - Initialing new strategy: Visual: Left-to-Right, Top-to-Bottom 2015-09-19 21:13:33,432 DEBUG SuperPuTTY - STATUS: Ready 2015-09-19 21:13:33,516 INFO ApplicationPanel - [15795654] ReFocusPuTTY - puttyTab=neuro@UbuntuVM: ~, caller=SHELLHOOK, result=True 2015-09-19 21:13:37,745 DEBUG frmSuperPutty - [263126] Activated 2015-09-19 21:13:37,956 INFO SuperPuTTY - Opening putty session, id=Z_Other/Cygwin 2015-09-19 21:13:37,958 INFO PuttyStartInfo - Putty Args: '-' 2015-09-19 21:13:38,159 WARN ApplicationPanel - Unable to get handle for process on first try. Polling 10 s for handle.
2015-09-19 21:13:49,218 DEBUG frmSuperPutty - [263126] Activated
2015-09-19 21:13:49,283 ERROR Program - Application_ThreadException
2015-09-19 21:13:51,567 DEBUG frmSuperPutty - [263126] Activated
2015-09-19 21:13:51,653 INFO ApplicationPanel - [15795654] ReFocusPuTTY - puttyTab=neuro@UbuntuVM: ~, caller=SHELLHOOK, result=True
2015-09-19 21:13:54,020 DEBUG frmSuperPutty - [263126] Activated

[jimradford]

@neuromancerxi Are you compiling from Source or using precombiled Binaries?

[neuromancerxi]

Pre-compiled binaries for both.

[jimradford]

@neuromancerxi will you grab the latest build from here https://ci.appveyor.com/api/buildjobs/c5p29ikv73i3xca3/artifacts/SuperPuttyInstaller/bin/Debug/SuperPuttySetup.msi It has debugging information enabled so an exception should provide better details of where this is ocurring.

[jimradford]

Going to Bump this until 1.4.0.8 since it does not appear to affect the bulk of the userbase.

[neuromancerxi]

With the debug build and now mintty 2.1.5 (x86_64-pc-cygwin):

[jimradford]

@neuromancerxi can you provide steps to reproduce? Thanks!

[atlasloewenherz]

I can provide more logs if required just let me know. I still can reproduce this problem everytime:

1) unzip SupperPutty 2) start SupperPutty 3) configure putty, pscp,mintty,... references & Submit 4) i get the first error without Stacktrace ( just process exited) 5) close SupperPutty 6) start SupperPutty again 7) start minty based console ==> Error message and the mintty windows get undocked from SupperPutty main window ( i can close superputty but mintty remains running )

$ mintty.exe --version Ignoring malformed option ':'. mintty 2.1.5 (x86_64-pc-cygwin) (C) 2013/2015 Andy Koppe / Thomas Wolff License GPLv3+: GNU GPL version 3 or later There is no warranty, to the extent permitted by law.

• Windows 7 Enterprise SP1 64BIT OS

tried "reinstalling" re unzipping more than 4 times ( even after cygwin reinstall)

still get the same problem ( see screenshot )

[neuromancerxi]

1. Download latest Cygwin Installer: https://cygwin.com/setup-x86_64.exe
2. Install Cygwin (I added only the "bind-util" package to the defaults)
3. Either Extract Superputty from zip or install via debug msi installer (Installed to C:\Program Files (x86)\SuperPutty)
4. Install Putty 0.65, defaults
5. Run SuperPutty as "Administrator"
6. Configure Super Putty by pointing it to putty, pscp and mintty
7. Create a new Session

8. Launch

[jimradford]

@neuromancerxi Thanks for the update. I'll work on this when I am back from travels. Around October 15th.

[joeyhub]

You can work around this in the meantime if you set up cygwin with sshd.

[dklawson]

I also had this issue, but was able to do some troubleshooting this evening. The issue is caused by the current version of mintty.exe distributed with cygwin. In the new version, if mintty thinks that it wasn't started from a terminal, it will fork itself and then exit. Since superputty doesn't notice this, it tries to wait on the initial mintty process, which has already exited.

Fortunately, there is a mintty config setting to disable this behavior. Just add "daemonize=false" to the .minttyrc file in your cygwin home dir.

[neuromancerxi]

@dklawson Thank you, your workaround solved my issue for the short term.

[jimradford]

The Exception being thrown I believe has been fixed. The handling of mintty will need to be addressed in documentation unless there is a commandline option that can be passed to mintty to "fix" the daemonizing behavior.

[dklawson]

I think --nodaemon should work as a command line option.

[jimradford]

@dklawson does that affect previous versions of mintty if --nodaemon is passed on the command line?

[dklawson]

Looks like the default for the 'daemon' feature was changed from off (enabled via --daemon) to on (disabled via --nodaemon), starting in v2.1.4 of mintty (commit 4e68399). It will return an error for invalid options, so there would need to be some version checking added.

[jimradford]

It appears you set options with -o = so -o daemonize=false works with the current 2.1.4 -o foo=bar still allows the shell to start properly it seems and is invalid. I'll commit the fix and see if I can find someone still using the old version to test.