Bug: KiTTY crashes

micronix - Sat 30/10/2010 12:41:20 CEST +0200

I'm using KiTTY 0.60.67.1 (portable) to connect to my server over ssh using pubkey-auth. If a program using X11 is started when X11-forwarding is activated but no X-Server is running, the connection is aborted and two dialogs appear: "KiTTY Fatal Error" "Network error: Socket is not connected". If I deactivate X11-forwarding or start a X-Server, these dialogs won't appear.

whereisian - Sat 04/12/2010 19:21:51 CET +0100

I can confirm the same behaviour.

Cyd - Sun 05/12/2010 16:00:59 CET +0100

I'm sorry but I am unable to reproduce this issue.
I don't get a crash, but only an error message:
Error: Can't open display: 127.0.0.1:0.0

Cyd

whiteHead - Fri 07/01/2011 16:35:48 CET +0100

Hi Cyd. I can reproduce this bug. However, the crash only happens when I connect to Ubuntu 10.04 LTS, but not on CentOS 5.1.

If there is no X-server running, KiTTY just crashes when I type vi and enter. If Xming is running, vi opens perfectly.

I am using KiTTY 0.60.67.5.

whiteHead - Fri 07/01/2011 16:38:44 CET +0100

By the way, PuTTY doesn't have this issue. Thanks.

Cyd - Fri 07/01/2011 17:56:29 CET +0100

Ok
I use CentOS. So that I could not reproduce the bug.
Currently I don't have any Ubuntu.
I'll try to install an Ubuntu to check.

Cyd - Sun 09/01/2011 17:03:27 CET +0100

I have reproduced on Ubuntu.
But at first glance I guess it is a server side behavior.
There is no crash. The server ended the socket connection.

Cyd

Koma - Mon 10/01/2011 10:43:25 CET +0100

Kitty says that the program signature changes if placed in c:\windows\system32\

(i'm used to place putty in c:\windows\system32\ssh.exe to use the command line from RUN.)

micronix - Sat 29/01/2011 16:54:52 CET +0100

I use Gentoo.
Kitty 0.60.66.27p doesn't crash but if use Kitty 0.60.27.5p it's the same error as with Kitty 0.60.27.1 and Kitty crashes.

Cyd - Sun 30/01/2011 11:48:40 CET +0100

It seems it is due to very last putty snapshot I use in 0.60.67 !

murphy - Sat 14/05/2011 08:16:20 CEST +0200

Hi,

I can confirm this for the latest 0.60.67.6p.

On one machine it's vim (with syntax highlighting on), on another su or mc that terminate the connection.
Tested and reproduce-able on 2K,XP,W7 with Debian etch/lenny/testing.

I already thought it would be the color codes.
IIRC it started somewhere around the introduction of click-able URLs.

Switching off X11 forwarding fixes this.
Guess i have to make 2 connections for each I have now: one with and one without X11.
Would love to see this fixed though ;)

greetz

Trybik - Fri 13/01/2012 16:34:58 CET +0100

This bug still exists. I connect to Debian Squeeze.

Seb - Fri 13/01/2012 16:37:35 CET +0100

Hi, I have the same pb. ("KiTTY Fatal Error" "Network error: Socket is not connected") with KiTTY v0.61.1.1 loaded from Pageant (hope this helps reproduce) v0.61 when connected to an AIX 6.1.0.0 and launching vim.
Same pb. with KiTTY v0.61.1.2.
BTW: My Xming server is not running !
It seems this bug has been along for a little more than a year, It was be dissapointing to have to switch back PuTTY because of this bug.

Seb - Fri 13/01/2012 17:32:53 CET +0100

Forget what I said about my Xming Server :)
I noticed, logging off from Windows (XP) and logging back again temporarely solves the problem : hope this helps.

It would be great if you could reproduce and fix this bug.
Good luck, anyway.

Markus Henschel - Thu 19/01/2012 10:25:18 CET +0100

Yep. The bug is still present for me, too.

Laph - Thu 09/02/2012 11:08:20 CET +0100

Yep, same here.
- Starting mc kills Kitty (but not Putty) with 2 "Socket not connected" messages.
- No local X-Server running.
- Kitty started from Pageant.
- vim works.
- Disabling X11 forwarding solves the issue.

Seb - Wed 22/02/2012 11:11:24 CET +0100

Hi,

I just forgot to type the 4 for letters into the box before posting which produce the loss of the message that took me 20 min to type.

Please bring a popup when the capture box is empty (or wrong) instead of printing a new page with "Bad captcha !" so that we don't loose all the message we type.

That said, the "Network error: Socket not connected" popup appears with KiTTY (PuTTY is not concerned) and VIM (but not with standard UNIX VI) when :

• local X-Server is NOT running AND X11 Forwording is enabled.

Here is my VIM version that I had to build on AIX (because I am not root and VIM was not installed) :

VIM - Vi IMproved 7.3 (2010 Aug 15, compiled May 30 2011 11:56:08)
Compiled by x064304@dela01
Normal version without GUI. Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
-conceal +cryptv -cscope +cursorbind +cursorshape +dialog_con +diff +digraphs
-dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path
+find_in_path +float +folding -footer +fork() -gettext -hangul_input -iconv
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
-mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse
+mouse_xterm -multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype
+path_extra -perl +persistent_undo +postscript +printer -profile -python
-python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
    -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup +X11 -xfontset -xim
+xsmp_interact +xterm_clipboard -xterm_save
     system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
     user exrc file: "$HOME/.exrc"
     fall-back for $VIM: "/home/x064304/gnu/share/vim"
Compilation:
/usr/vac/bin/cc -qlanglvl=extc89 -c -I. -Iproto -DHAVE_CONFIG_H -g
Linking: /usr/vac/bin/cc -qlanglvl=extc89 -o vim -lSM -lICE -lXt -lX11 -lm -lcurses

Hope this helps solving this issue.

Seb.

whiteHead - Wed 22/02/2012 18:08:14 CET +0100

Hi, thanks guys for posting the problem causing the crash. Disabling X11 forwarding does the trick but also creates the inconvenience. Would Cyd please look into this bug since PuTTY (v0.61 or 0.62) does NOT have this issue?

My current workaround is to disable X11 forwarding and to use VNC for GUI if needed.

whiteHead

Cyd - Thu 23/02/2012 10:58:53 CET +0100

It seems there is a problem with the experimental ZModem Patch, I tried to include into KiTTY.
Get that special build without that patch here.

whiteHead - Fri 24/02/2012 01:37:19 CET +0100

Cyd, this no-zmodem version is just PERFECT!
Many many thanks!

Seb - Mon 27/02/2012 14:38:15 CET +0100

Hi, instead of disabling X11Forwarding one can create an alias to vim :
alias vim="vim -X"

Just found out this one by looking at vim manpage for something else :-)

Seb.

whiteHead - Thu 15/03/2012 17:46:29 CET +0100

Hi Cyd, I've been using kitty version without zmodem for 3 whole weeks, more than 16 hours a day, at least 3 kitty windows open at the same time. I have never experience any crash or issues so far. It's really awesome!

As for file transferring, as long as we have winscp associated with kitty (triggered by Alt+F3), we don't need this zmodem feature at all. It causes stability problem. It can only upload files to home directory on the remote machine. I've never succeeded to download a file from the remote using zmodem. Perhaps it's time to remove zmodem feature in kitty. Or, please provide both versions with or without zmodem in the future updates.

That's just my 2cents.
Best,
whiteHead

Cyd - Fri 16/03/2012 12:27:56 CET +0100

Exactly, we've simply planned to remove ZModem feature in next KiTTY version that is currently in testing phase.

whiteHead - Tue 20/03/2012 00:34:10 CET +0100

Correction, it should be "Shift + F3" to trigger WinSCP. Sorry for the typo.

Answer

The forum is actually closed