Re: Nedit unstable after 1.7.0-56 update -- clipboard copy segfault
Yaakov (Cygwin/X) wrote: On 03/08/2009 10:49, Rob Gillen wrote: After updating my 1.7 installation to the latest cygwin DLL, my xterms were finally able to exec bash (with some issues from bash as well), but I immediately ran into segfault when copying to the clipboard from nedit. I.e. as soon as I highlighted a line of text and hit CTRL-C, it dumped core. Actually, this appears to be a known problem with lesstif (the Motif implementation which nedit and other programs use). It looks like other distros may have a fix, but it will take me a little while until I can focus on this. FWIW, if this is still in the pipeline... I'm still on cygwin 1.5, but I experienced similar crashes witn nedit. I don't remember that it crashed when hitting CTRL-C, but it crashes most of the time if I hit CTRL-V to paste some text (sometimes it works, though). The workaround is to use middle-mouse click to paste (and maybe also the edit/paste menu). Albrecht -- 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: 'run xterm' fails to open a window
On Fri, Nov 20, 2009 at 4:25 PM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 13/11/2009 03:14, Ken Brown wrote: On 11/12/2009 3:17 PM, Jon TURNEY wrote: On 10/11/2009 23:44, Mike Ayers wrote:] Apparently, run.exe is not providing stdout/stderr to dump to. The workaround: [SNIP] C:\mikeC:\cygwin\bin\run.exe -p /usr/bin sh -c gvim/dev/null 21 C:\mike [/SNIP] Wait, are you saying that the process that run starts is blocked if it tries to output anything? Ah, so this explains my xterm problem that started this thread. When I start xterm from a shell, I always get the message Warning: Missing charsets in String to FontSet conversion When I start xterm via run, this message apparently has nowhere to go and the xterm process is blocked. Mike's workaround (with 'gvim' replaced by 'xterm') solves the problem, as he said. Is this a bug in run? It does kind of look like some problem with run, but not a universal one, 'run xterm' has been working as expected for me, even when it has to output something. Experimenting a bit, this seems to be related to having CYWIN=tty set in the windows environment. If I remove that, I can reproduce the problem you see. I really don't understand the invisible console stuff well enough to attempt a fix, though... Ok thanks, yes CYGWIN=tty does fix the issue! many many thanks! JLM -- KISS! (Keep It Simple, Stupid!) (garde le simple, imbécile!) mais qu'est-ce que tu m'as pondu comme usine à gaz? fait des choses simples et qui marchent, espèce d'imbécile! - Si vous pensez que vous êtes trop petit pour changer quoique ce soit, essayez donc de dormir avec un moustique dans votre chambre. Betty Reese http://www.grainesdechangement.com/citations.htm -- 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/
xterm doesn't open on start (was: checkX problems)
Ken Brown wrote: On 11/26/2009 2:30 AM, Lothar Brendel wrote: Errh, yes. Hence, to make Cygwin/X+xterm run out of the box (using the start menu shortcut), you have to install the CJK fonts. One more There are three packages: font-isas-misc, font-jis-misc, and font-daewoo-misc. I installed those fonts, added LANG as the variable and C as the Value to the System control panel (System Properties, Advanced tab, Environ- ment Variables button, New System variables), put SET CYGWIN=%CYGWIN% tty and %RUN% sleep 5 (separately) into the startxwin.bat. Nothing works. 1.7 doesn't work for me out-of-the-box (yes, I ripped it all out and tried it fresh :-) I open a DOS box and check processes and see bash running with an l or a 1 in the left columnn, but nothing appears. If I launch an Xterm it opens up. It seems some of the login thing happen, but when I add in my ssh-agent starting script, since it requires input, it fails (http://mah.everybody.org/docs/ssh is the script I use). Any other ideas? I keep updating but so far all I can do is launch an Xterm manually and clean up, then everything seems fine til the next time I relaunch it. Brian -- 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: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: [...] Nothing works. 1.7 doesn't work for me out-of-the-box (yes, I ripped it all out and tried it fresh :-) I open a DOS box and check processes and see bash running with an l or a 1 in the left columnn, but nothing appears. If I launch an Xterm it opens up. It seems some of the login thing happen, but when I add in my ssh-agent starting script, since it requires input, it fails (http://mah.everybody.org/docs/ssh is the script I use). Any other ideas? Doen't look like the issue http://cygwin.com/ml/cygwin-xfree/2009-11/msg00174.html to me. My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when explicitely (triple-)clicking its circular double-arrow (how's that thingy called BTW?) in the Utils category. Maybe Chuck can tell why we don't get the new version as default. Ciao Lothar -- 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: checkX problems
Thomas Dickey wrote: On Thu, 26 Nov 2009, Lothar Brendel wrote: [...] Hence, to make Cygwin/X+xterm run out of the box (using the start menu shortcut), you have to install the CJK fonts. One more noob-question, otoh, (discarding run-out-of-the-box, since that doesn't give a good solution), What's wrong with it running out-of-the-box? For somebody new to Cygwin it's a positive experience when the XWin Server shortcut actually opens an xterm. Which font-package does provide the CJK fonts? I tried several ones but up to now in vain. BTW: Following Ken's info (There are three packages: font-isas-misc, font-jis-misc, and font-daewoo-misc.), I found out to need font-daewoo-misc *and* font-isas-misc to make xterm happy. Ciao Lothar -- 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: checkX problems
On Fri, 27 Nov 2009, Lothar Brendel wrote: Thomas Dickey wrote: On Thu, 26 Nov 2009, Lothar Brendel wrote: [...] Hence, to make Cygwin/X+xterm run out of the box (using the start menu shortcut), you have to install the CJK fonts. One more noob-question, otoh, (discarding run-out-of-the-box, since that doesn't give a good solution), What's wrong with it running out-of-the-box? For somebody new to Cygwin it's a positive experience when the XWin Server shortcut actually opens an xterm. out-of-the-box apparently doesn't include the small fix to make it work with Cygwin's configuration. (It wouldn't be in upstream since that would potentially break other packages which can add localized menus, and there doesn't appear to be a programmatic way for xterm to decide if it should apply the workaround). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- 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: xterm doesn't open on start (was: checkX problems)
Timares, Brian (Patriot) wrote: Lothar Brendel wrote: [...] My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when explicitely (triple-)clicking its circular double-arrow (how's that thingy called BTW?) in the Utils category. Tried it, including changing XWin Server to C:\cygwin\bin\run2.exe /usr/bin/startxwin.bat That was a misunderstanding. I didn't mean to use ``run2'' instead of ``run'' but to verify that the version of the *package* 'run2' (containing ``checkX'') is the most recent one. Did you do that? Asks Lothar -- 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: xterm doesn't open on start (was: checkX problems)
Lothar Brendel wrote: Timares, Brian (Patriot) wrote: Lothar Brendel wrote: My guess: It's the old checkX-problem again because you're using version 0.3.0-1 of the run2-package. Do to some reason unknown to me, that's the default version. But we need 0.3.1-1, which you only get when Tried it, including changing XWin Server to C:\cygwin\bin\run2.exe /usr/bin/startxwin.bat That was a misunderstanding. I didn't mean to use ``run2'' instead of ``run'' but to verify that the version of the *package* 'run2' (containing ``checkX'') is the most recent one. Did you do that? You were clear. I did get the 0.3.1-1 and it showed up just as you said. It didn't help, so then I tried changing run to run2, but changed it all back since it didn't help. Brian by the way, Outlook makes proper quoting a royal pain :-/ -- 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/
Unrecognized option: -nolock
With the latest release 1.7.0-67 Cygwin [1.7] now works glitch-free on FAT32 filesystems; but to run X on FAT32 we still have to revert to 1.7.0-60. The recommended fix (there may be more than one but this seems potentially the easiest and most effective) is to run X -nolock. But this option is unrecognised in the current XWin. Please could -nolock be reintroduced so that FAT32 users can take full advantage of the current .dll? Thank you. Fergus -- 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/
