Ssh login problem, no proper command line is present
Hi I have setup Cygwin+ssh on my laptop, somewhat successfully. SSH seems to work finally but I have one problem. Whenever I connect to my laptop via ssh it says Last login : Some date from some computer and it is not giving me any visible other command line at all. I can type there but there does not seem to be regular bash command look. No $ is listed. Does anyone know how to solve this weird problem? None of my other computers with cygwin+ssh shows this issues. I have tried logging into ssh locally as well and the issue there regardless of ssh client I use, Putty or mintty ssh login seems to produce the same visual(I hope) problem thanks -- View this message in context: http://www.nabble.com/Ssh-login-problem%2C-no-proper-command-line-is-present-tp24350202p24350202.html Sent from the cygwin-xfree mailing list archive at Nabble.com. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: 1.7 no start menu entry to launch X Server?
On 05/07/2009 23:56, William Deegan wrote: Greetings, Some time in the last few months the X Win Server start menu item was removed. I just did a fresh install on a new machine and it's not longer there. It was really useful. Any chance of getting it reinstated? I think this is a packaging error with xinit-1.1.1-3, which seems to be missing the postinstall/preremove scripts which maintain this shortcut, which were present in xinit-1.1.1-2 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin 1.7 hangs with my .xinitrc
On 04/07/2009 17:48, David A Bagley wrote: Hi I like to start X with a whole bunch of windows instead of creating each time. In Cygwin 1.5 I did this with no problem. In 1.7 this hangs. It hangs in a way where I can't open anything else and have to pull the power to computer. If I comment out all the xterm's it works fine. What an interesting .xinitrc :-) I can reproduce the problem using it. I seem to end up with a few of the xterms spinning somewhere and trying to use 100% CPU, and outputting the following: No protocol specified xterm Xt error: Can't open display: :0 After inserting 'sleep 1' into the .xinitrc before each xterm seems to start up without trouble, so I guess there's some sort of timing condition somewhere, although I've no idea where... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: XWin freezes on xkbcomp
On 02/07/2009 19:08, Zdrojewski, Tye wrote: After recently reinstalling cygwin, XWin freezes when I try to run it. There are two XWin processes running when it is frozen. When the XWin process with the smaller memory footprint was killed, the following went into the log, and it appeared to unfreeze for a moment. (EE) XKB: Could not invoke xkbcomp (EE) XKB: Couldn't compile keymap (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap I started XWin with the -kb option, which stopped the freezing, but I don't use the standard US keyboard, so this isn't really on option for me. I suggest you test if you can run xkbcomp at all, e.g. xkbcomp --help setxkbmap de -print | xkbcomp -w3 -xkm - localhost:0.0 (replace 'de' with the secret keyboard layout you want to use) I also notice that /etc/X11/xkb/ is not there, along with several other directories that ARE there on another PC with a working cygwin install: $ ls /etc/X11 app-defaults/ system.XWinrc* xinit/ This is normal Seems like there ought to be more there, because this is what that dir looks like on the working install: app-defaults/ fs/ lbxproxy/ proxymngr/ rstart/ twm/ xdm/ xinit/ xkb/ xserver/ xsm/ This looks like an older (pre-X11R7.4) installation (or has directories left over from an older installation. For all I know that xkb/ is empty :-) ) This seems like a BIG problem. Hopefully this is something already being worked on or already fixed. I think you are the only person who has reported a problem like this, so I'm afraid I can't agree with any of those statements. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: XWin freezes on xkbcomp
I only say that this is a big problem because it cripples my ability to run cygwin/X. I guess I'm surprised no one else has reported this, because I haven't done anything unusual (that I know of). Yes, my *working* installation is a bit older. I use the dvorak layout (not trying to be secretive). Setxkbmap was not installed (missing dependency in setup?). So, I installed it, but the problem persisted. After starting XWin and killing the hung process, I am able to run the command you suggested, but it just causes another hung XWin process to be created. If I run an X client (xfontsel, rxvt, etc), THEN run the setxkbmap command, it works! But as soon as I kill the last X client window, X is frozen again with that hung process. If I wait, X does eventually come back, but it seems to take about 5 minutes. -Tye -Original Message- From: Jon TURNEY [mailto:jon.tur...@dronecode.org.uk] Sent: Monday, July 06, 2009 11:40 AM To: cygwin-xfree@cygwin.com Cc: Zdrojewski, Tye Subject: Re: XWin freezes on xkbcomp On 02/07/2009 19:08, Zdrojewski, Tye wrote: After recently reinstalling cygwin, XWin freezes when I try to run it. There are two XWin processes running when it is frozen. When the XWin process with the smaller memory footprint was killed, the following went into the log, and it appeared to unfreeze for a moment. (EE) XKB: Could not invoke xkbcomp (EE) XKB: Couldn't compile keymap (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap I started XWin with the -kb option, which stopped the freezing, but I don't use the standard US keyboard, so this isn't really on option for me. I suggest you test if you can run xkbcomp at all, e.g. xkbcomp --help setxkbmap de -print | xkbcomp -w3 -xkm - localhost:0.0 (replace 'de' with the secret keyboard layout you want to use) I also notice that /etc/X11/xkb/ is not there, along with several other directories that ARE there on another PC with a working cygwin install: $ ls /etc/X11 app-defaults/ system.XWinrc* xinit/ This is normal Seems like there ought to be more there, because this is what that dir looks like on the working install: app-defaults/ fs/ lbxproxy/ proxymngr/ rstart/ twm/ xdm/ xinit/ xkb/ xserver/ xsm/ This looks like an older (pre-X11R7.4) installation (or has directories left over from an older installation. For all I know that xkb/ is empty :-) ) This seems like a BIG problem. Hopefully this is something already being worked on or already fixed. I think you are the only person who has reported a problem like this, so I'm afraid I can't agree with any of those statements. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: fastpath 0 - xterm?
On 29/06/2009 19:29, Tom Roche wrote: Since I'm not seeing this in the FAQ, I wanted to propose the following item: what would be required to go from zero to xterm? I.e. from a Cygwin-less windows box (windows= 2k) to getting a Cygwin/X xterm up on one's screen? From my recent experience, it seems to me the minimal install would be 0whatever setup.exe wants to install by default/ 1 font-misc-misc 2 font-alias 3 ncurses 4 xinit 5 xterm I've adjusted the package dependencies for xterm so now the needed things to start it without warnings should be installed automatically Perhaps someone else can test the following underdetailed (fastpath/ debug-free) 10-step procedure to go from zero to xterm: Yes, as pointed out elsewhere, something like this is probably most appropriate in the Cygwin/X User's Guide. Patches welcome :-) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Current directory '.' included in startxwin.bat PATH bad practice
On 26/06/2009 17:53, Rob Gillen wrote: PROPOSAL: please remove the current directory from the PATH setting in startxwin.bat. Yes, that's not right. Thanks for pointing it out. I've queued up a patch to fix that. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: Cygwin 1.7 hangs with my .xinitrc
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree-ow...@cygwin.com] On Behalf Of Jon TURNEY Sent: Monday, July 06, 2009 8:16 AM I can reproduce the problem using it. I seem to end up with a few of the xterms spinning somewhere and trying to use 100% CPU, and outputting the following: No protocol specified xterm Xt error: Can't open display: :0 After inserting 'sleep 1' into the .xinitrc before each xterm seems to start up without trouble, so I guess there's some sort of timing condition somewhere, although I've no idea where... I have had `sleep 1` statements after each xterm launch in my .xinitrc for years, having encountered a similar problem. At least I'm pretty sure it was a similar problem... yes, I should have reported it then. HTH, Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
