From cygwin@cwilson.fastmail.fm Tue Dec 1 04:07:00 2009 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Tue, 01 Dec 2009 04:07:00 -0000 Subject: xterm not working In-Reply-To: <4B134D1C.9060404@users.sourceforge.net> References: <362945.66796.qm@web34403.mail.mud.yahoo.com> <4B134D1C.9060404@users.sourceforge.net> Message-ID: <4B14965C.8060703@cwilson.fastmail.fm> Yaakov (Cygwin/X) wrote: > On 29/11/2009 21:28, Joe Java wrote: >> Gone for Thanksgiving break, return and update cygwin, and now >> xterm does not show anymore. I have not upgraded to the latest 1.7 (I >> am waiting for the official release). I read the other messages and >> nothing seems to work. >> >> Does anyone have a SIMPLE solution to this problem. > > Downgrade the termcap package until there is another update thereto. Should be fixed by termcap-5.7_20091114-4 (cygwin-1.5) or termcap-5.7_20091114-13 (cygwin-1.7). -- Chuck -- 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/ From Brian.Timares@va.gov Tue Dec 1 14:47:00 2009 From: Brian.Timares@va.gov (Timares, Brian (Patriot)) Date: Tue, 01 Dec 2009 14:47:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) In-Reply-To: <3A87660989894F8C82CE373AC8C8382F@MultiOcke> References: <4AEAEEAB.2030009@cornell.edu> <1AF6441D7C284D86A18503A1A76C2895@MultiOcke> <4AFF1AF5.2050200@cwilson.fastmail.fm> <9D882BC2C45747B28E9A83C5F5C5B70F@MultiOcke> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> Message-ID: <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> Lothar Brendel wrote: >Timares, Brian (Patriot) wrote: >> Just to be clear from the start, Cygwin 1.7 not 1.5. > >ACK. *blush* Sorry! ... >Thus, once more: What does > md5sum /usr/bin/checkX >yield? > >a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216? The 2nd: VHAISBTIMARB@isb-timaresbrian-lt ~ $ md5sum /usr/bin/checkX a36409714f5ce9d01e8dfb4cb38b7216 */usr/bin/checkX $ checkX -v run2 0.3.0 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/ From mike_ayers@tvworks.com Tue Dec 1 17:29:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Tue, 01 Dec 2009 17:29:00 -0000 Subject: [OT] Mailing list problems Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D81CC60@mailserver.metatv-ds.metatv.com> Apologies for sending this to the list, but I could not find the answer on the web pages. I'm having a few quirks with the mailing list that I'd like to ask the postmaster about, but I can't find a contact point. Does anyone know of one? Thanks, Mike From reply-to-list-only-lh-x@cygwin.com Tue Dec 1 18:04:00 2009 From: reply-to-list-only-lh-x@cygwin.com (Larry Hall (Cygwin X)) Date: Tue, 01 Dec 2009 18:04:00 -0000 Subject: [OT] Mailing list problems In-Reply-To: <83E753BE7B6A324ABB336245BAF1DAAC0D81CC60@mailserver.metatv-ds.metatv.com> References: <83E753BE7B6A324ABB336245BAF1DAAC0D81CC60@mailserver.metatv-ds.metatv.com> Message-ID: <4B155A3B.3050603@cygwin.com> On 12/01/2009 12:29 PM, Mike Ayers wrote: > > Apologies for sending this to the list, but I could not find the answer on the web pages. I'm having a few quirks with the mailing list that I'd like to ask the postmaster about, but I can't find a contact point. Does anyone know of one? Did you try postmaster? Otherwise, I'd recommend trying the list owner as described here: -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/ From wgweis@sbcglobal.net Tue Dec 1 18:19:00 2009 From: wgweis@sbcglobal.net (wgweis@sbcglobal.net) Date: Tue, 01 Dec 2009 18:19:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? References: <4AEAEEAB.2030009@cornell.edu> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <005001ca72b2$c4bebc60$4401a8c0@BANDIT> Hi All: This is my first post here. I've never had a problem I couldn't fix with cygwin-x before. Here is the deal: I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat and see this: "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0" this seems to be coming from this command in the batch file: :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash - usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 If I kill the server and run the script again, I'll get a STATUS_ACCESS_VIOLATION error, indicating some sort of shared memory corruption. I then have to restart the PC. I checked to see if there was more than one cygwin1.dll in response to earlier posts about this error and there is only one. I tried turning off the windows firewall. That helps in other ways, because other cygwin network utilities, such as nslookup were blocked until I did that. I tried changing the display from 127.0.0.1 to the IP address of the machine. Basically, I have a fresh machine with windows 7 and a fresh install of cygwin and I can't get xterm to work. Anyone have any ideas? Or is this just a windows 7 thing, and I'll have to give up on cygwin-x for a while? BTW, other shortcuts in the cygwin-x start folder work, such as bitmap and xcalc, just not the Xwin server and xterm. Thanks in advance, George -- 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/ From lottas.junk@geekmail.de Tue Dec 1 18:48:00 2009 From: lottas.junk@geekmail.de (Lothar Brendel) Date: Tue, 01 Dec 2009 18:48:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) References: <4AEAEEAB.2030009@cornell.edu> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> Message-ID: Timares, Brian (Patriot) wrote: > Lothar Brendel wrote: [...] >> Thus, once more: What does >> md5sum /usr/bin/checkX >> yield? >> >> a827086e9cbb331ef49d416b3cb1b135 or a36409714f5ce9d01e8dfb4cb38b7216? > > The 2nd: > > VHAISBTIMARB@isb-timaresbrian-lt ~ > $ md5sum /usr/bin/checkX > a36409714f5ce9d01e8dfb4cb38b7216 */usr/bin/checkX ... and that's the checksum for the version 0.3.0 of checkX! > $ checkX -v > run2 0.3.0 Ok, yes, that's an easier version check :-) So, you've got the situation I surmised in http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html I.e. you *don't* have the new version (0.3.1) of the run2-package installed. Install that and retry, please. 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/ From Brian.Timares@va.gov Tue Dec 1 21:57:00 2009 From: Brian.Timares@va.gov (Timares, Brian (Patriot)) Date: Tue, 01 Dec 2009 21:57:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) In-Reply-To: References: <4AEAEEAB.2030009@cornell.edu> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> Lothar Brendel wrote: >Timares, Brian (Patriot) wrote: >> Lothar Brendel wrote: >> $ checkX -v >> run2 0.3.0 >So, you've got the situation I surmised in >http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html Grr, I saw that, went and _thought_ I got the right version but it seems the right version wasn't avaiable at the time and I got fooled by the 0.3.0-1 to think 0.3.1. I have carefully upgraded, and when running Setup17.exe I saw it wanted to revert, but I didn't let it. The X window showed up, but it blew up real good (the windows disappeared, then the X icon. After a reboot....it didn't launch at all. I ran startxwin.sh from the Cygwin Bash Shell, and it started. After quitting that I launched it from startxwin.bat and the windows showed up but they died after a second at most and no X icon in the taskbar tray.. Same thing after reboot. This time I after launching from a Cygwin Bash Shell (successfully) I closed the cygwin bash shell and the X Window died. The X server kept running. 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/ From lottas.junk@geekmail.de Tue Dec 1 22:45:00 2009 From: lottas.junk@geekmail.de (Lothar Brendel) Date: Tue, 01 Dec 2009 22:45:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) References: <4AEAEEAB.2030009@cornell.edu> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> Message-ID: Timares, Brian (Patriot) wrote: > Lothar Brendel wrote: >> Timares, Brian (Patriot) wrote: >>> Lothar Brendel wrote: >>> $ checkX -v >>> run2 0.3.0 > >> So, you've got the situation I surmised in >> http://cygwin.com/ml/cygwin-xfree/2009-11/msg00200.html > > Grr, I saw that, went and _thought_ I got the right version but > it seems the right version wasn't avaiable at the time and > I got fooled by the 0.3.0-1 to think 0.3.1. I have carefully > upgraded, and when running Setup17.exe I saw it wanted to > revert, but I didn't let it. Exactly, the "evil setup" tries to revert it to 0.3.0-1 every time. Quite easy to forget keeping an eye on that when tinkering with other packages. > The X window showed up, but it blew up real good (the windows > disappeared, then the X icon. After a reboot....it > didn't launch at all. I ran startxwin.sh from the Cygwin Bash > Shell, and it started. At least we're getting *somewhere* :-) Ok, what happens when entering the two vital commands by hand in the the Cygwin Bash Shell (waiting with the second until the X-icon has appeared)? XWin -multiwin & xterm -display :0 Reproducible success? 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/ From Brian.Timares@va.gov Tue Dec 1 22:58:00 2009 From: Brian.Timares@va.gov (Timares, Brian (Patriot)) Date: Tue, 01 Dec 2009 22:58:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) In-Reply-To: References: <4AEAEEAB.2030009@cornell.edu> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <270AA78168E41541833C52448F4F34AD1D3708FF@VHAISHMSGJ2.vha.med.va.gov> Lothar Brendel wrote: >Timares, Brian (Patriot) wrote: >> The X window showed up, but it blew up real good (the windows >> disappeared, then the X icon. After a reboot....it >> didn't launch at all. I ran startxwin.sh from the Cygwin Bash >> Shell, and it started. > >At least we're getting *somewhere* :-) > >Ok, what happens when entering the two vital commands by hand in the the >Cygwin Bash Shell (waiting with the second until the X-icon has appeared)? > >XWin -multiwin & >xterm -display :0 > >Reproducible success? I'll try again from home (I went into the office to simplify things). Here is what I got (sorry for the word-wrap): VHAISBTIMARB@isb-timaresbrian-lt ~ $ XWin -multiwindow & [1] 5004 VHAISBTIMARB@isb-timaresbrian-lt ~ $ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/isb-timaresbrian-lt:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winGetDisplay: DISPLAY=:0.0 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 00000007 winSetEngine - Multi Window or Rootless => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 3200 height: 1200 depth: 32 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello Screen 0 added at XINERAMA coordinate (0,0). winMultiWindowXMsgProc - Hello winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shar ed memory support in the kernel (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 1600 600 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) Using preset keyboard for "English (USA)" (409), type "4" Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" winInitMultiWindowWM - pthread_mutex_lock () returned. winInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. winGetDisplay: DISPLAY=:0.0 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=:0.0 winGetDisplay: DISPLAY=:0.0 winMultiWindowXMsgProc - DISPLAY=:0.0 winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the disp lay. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the di splay. winClipboardProc - XOpenDisplay () returned and successfully opened the display. From the xterm, which has stayed open: VHAISBTIMARB@isb-timaresbrian-lt ~ $ ps PID PPID PGID WINPID TTY UID STIME COMMAND 5516 1 5516 5516 0 180490 16:51:58 /usr/bin/bash 3868 1 3868 3868 ? 180490 16:52:02 /usr/bin/ssh-agent 5004 5516 5004 4612 0 180490 16:54:07 /usr/bin/XWin 4064 5516 4064 924 0 180490 16:56:09 /usr/bin/xterm 6012 4064 6012 5144 1 180490 16:56:10 /usr/bin/bash 2184 6012 2184 4240 1 180490 16:56:21 /usr/bin/ps Brian Timares -- 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/ From Brian.Timares@va.gov Wed Dec 2 17:26:00 2009 From: Brian.Timares@va.gov (Timares, Brian (Harris Corp.)) Date: Wed, 02 Dec 2009 17:26:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) References: <4AEAEEAB.2030009@cornell.edu> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <270AA78168E41541833C52448F4F34AD1D3DD693@VHAISHMSGJ2.vha.med.va.gov> More information as promised, after getting the new run and checkX (run2) packages announced this morning. $ checkX -v run2 0.3.2 ----- QUOTE ----- Lothar Brendel wrote: >Timares, Brian (Patriot) wrote: >> The X window showed up, but it blew up real good (the windows >> disappeared, then the X icon. After a reboot....it >> didn't launch at all. I ran startxwin.sh from the Cygwin Bash >> Shell, and it started. > >At least we're getting *somewhere* :-) > >Ok, what happens when entering the two vital commands by hand in the the >Cygwin Bash Shell (waiting with the second until the X-icon has appeared)? > >XWin -multiwin & >xterm -display :0 > >Reproducible success? I'll try again from home (I went into the office to simplify things). Here is what I got (sorry for the word-wrap): VHAISBTIMARB@isb-timaresbrian-lt ~ $ XWin -multiwindow & [1] 5004 VHAISBTIMARB@isb-timaresbrian-lt ~ $ Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 ----- UNQUOTE ----- Trying from home with the VPN active, again, it works; here is the ps from the xterm that showed up: VHAISBTIMARB@isb-timaresbrian-lt ~ $ ps PID PPID PGID WINPID TTY UID STIME COMMAND 3556 1 3556 3556 0 180490 11:11:27 /usr/bin/bash 6020 1 6020 6020 ? 180490 11:11:28 /usr/bin/ssh-agent I 2944 3556 2944 3688 0 180490 11:12:07 /usr/bin/XWin 5936 3556 5936 4060 0 180490 11:12:56 /usr/bin/xterm 4780 5936 4780 1840 1 180490 11:12:57 /usr/bin/bash 932 4780 932 4696 1 180490 11:12:59 /usr/bin/ps After quitting and destroying any processes from a DOS window, trying startxwin.bat with echo on.... First off all, nothing appeared (no X icon, no window). Here is what ps in a DOS window shows after running startxwin.bat: C:\cygwin\bin>ps PID PPID PGID WINPID TTY UID STIME COMMAND 1656 1 1656 1656 0 180490 10:57:45 /usr/bin/bash 5516 1 5516 5516 ? 180490 10:57:47 /usr/bin/ssh-agent I 4676 1656 1656 4476 0 180490 10:57:47 /usr/bin/ssh-add I 2024 1 2024 2024 1 180490 11:09:16 /usr/bin/bash 1464 1 1464 1464 2 180490 11:09:40 /usr/bin/ps Here is the output with blank lines and REM lines removed (I added the 2nd SET DISPLAY, CYGWIN is set to tty elsewhere as well as here, I don't know what that is at the end of the PATH): C:\cygwin\bin>startxwin.bat C:\cygwin\bin>SET DISPLAY=127.0.0.1:0.0 C:\cygwin\bin>SET CYGWIN=tty tty tty C:\cygwin\bin>if defined CYGWIN_ROOT goto :OK C:\cygwin\bin>SET RUN=C:\cygwin\bin\\..\bin\run -p /usr/bin C:\cygwin\bin>SET PATH=C:\cygwin\bin\\..\bin;C:\cygwin\bin\\..\bin;C:\WINDOWS\system32;C:\ WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\IBM\Personal Communications\;C:\Program Files\IBM\Trace Facility\;C:\Program Files\Common Files\InterSystems\Cache;C:\Program Files\Windows Imaging\;C:\Program Files\ActivIdentity\ActivClient\;P C:\cygwin\bin>SET XAPPLRESDIR= C:\cygwin\bin>SET XCMSDB= C:\cygwin\bin>SET XKEYSYMDB= C:\cygwin\bin>SET XNLSPATH= C:\cygwin\bin>if not exist C:\cygwin\bin\\..\tmp\.X11-unix\X0 goto CLEANUP-FINISH C:\cygwin\bin>attrib -s C:\cygwin\bin\\..\tmp\.X11-unix\X0 C:\cygwin\bin>del C:\cygwin\bin\\..\tmp\.X11-unix\X0 C:\cygwin\bin>if exist C:\cygwin\bin\\..\tmp\.X11-unix rmdir C:\cygwin\bin\\..\tmp\.X11-unix C:\cygwin\bin>SET DISPLAY=127.0.0.1:0.0 C:\cygwin\bin>C:\cygwin\bin\\..\bin\run -p /usr/bin bash -l -c "XWin -multiwindow -clipboard -silent-dup-error -winkill -emulate3buttons 100" C:\cygwin\bin>C:\cygwin\bin\\..\bin\run -p /usr/bin checkX -wait -d 127.0.0.1:0.0 -t 12 C:\cygwin\bin>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash -l C:\cygwin\bin> At this point I run "Cygwin Bash Shell" and from that window I run startxwin.bat and it works fine, even after closing the Cygwin Bash Shell. Brian Timares -- 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/ From lottas.junk@geekmail.de Wed Dec 2 23:18:00 2009 From: lottas.junk@geekmail.de (Lothar Brendel) Date: Wed, 02 Dec 2009 23:18:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) References: <4AEAEEAB.2030009@cornell.edu> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D3DD693@VHAISHMSGJ2.vha.med.va.gov > Message-ID: Hi! > More information as promised, after getting the new run and checkX > (run2) packages announced this morning. > > $ checkX -v > run2 0.3.2 0.3.2 announced? I didn't get any such message, and setup still only offers 0.3.1-1 to me. > VHAISBTIMARB@isb-timaresbrian-lt ~ > $ XWin -multiwindow & > [1] 5004 > > VHAISBTIMARB@isb-timaresbrian-lt ~ > $ Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 1.7.1.0 (10701000) > Build Date: 2009-11-11 > ----- UNQUOTE ----- Yes, the log didn't show anything unusual. (BTW: You got it from /var/log/XWin.log.0, not from stdout, right?) > After quitting and destroying any processes from a DOS window, trying > startxwin.bat with echo on.... > > First off all, nothing appeared (no X icon, no window). [...] > At this point I run "Cygwin Bash Shell" and from that window I run > startxwin.bat and it works fine, even after closing the Cygwin Bash > Shell. Brief, running ``startxwin.bat'' from the Cygwin Bash Shell works while running it from a Windows Prompt (DOS window) does not. Right? Ok, same check over there. In the Windows Prompt: C:\cygwin\bin\run XWin What does happen? Nothing? 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/ From cgf-use-the-mailinglist-please@cygwin.com Wed Dec 2 23:24:00 2009 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Wed, 02 Dec 2009 23:24:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) In-Reply-To: References: <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov> <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> <3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D3DD693@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <20091202232352.GA17116@ednor.casa.cgf.cx> On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote: >>More information as promised, after getting the new run and checkX >>(run2) packages announced this morning. >> >> $ checkX -v >> run2 0.3.2 > >0.3.2 announced? I didn't get any such message, and setup still only offers >0.3.1-1 to me. http://cygwin.com/ml/cygwin-announce/2009-12/msg00002.html http://cygwin.com/ml/cygwin/2009-12/msg00079.html cgf -- 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/ From cygwin@tlinx.org Thu Dec 3 05:27:00 2009 From: cygwin@tlinx.org (Linda Walsh) Date: Thu, 03 Dec 2009 05:27:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <4B1115EC.7010308@cornell.edu> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> Message-ID: <4B174C20.1040900@tlinx.org> Ken Brown wrote: > On 10/28/2009 6:07 PM, Andy Koppe wrote: >> 2009/10/28 Ken Brown: >>> Maybe my terminology is wrong. But if you start mintty with no >>> .minttyrc >>> and with LANG unset, mintty will set LANG=C.UTF-8. >> >> Yep. That's primarily for emacs' benefit, which parses the locale env >> variables itself instead of using setlocale(LC_CTYPE, ""), thereby >> missing out on Cygwin's default locale. > > Andy, > > I've sent a report about this to the emacs-devel list > (http://lists.gnu.org/archive/html/emacs-devel/2009-11/threads.html#01216). > But I don't have a good understanding of locale issues. Could you take > a look and see if what I said is accurate or if more should be said? C.UTF_8 doesn't exist. mintty is broken. Might want to try 'Console' nstead of using mintty. Not perfect either, but fewer compatibility problems that I've noticed. Examples of valid LANG values: C, ca_FR, en_US, fr_FR, it_IT, nl_NL, wa_BE@euro You can't have "C" and "UTF-8", because C means no encoding (default). UTF-8 IS an encoding, so they are mutually exclusive. I don't know under what circumstances "C" might imply UTF-8. If the definition of "C" changes? It might be easier than changing "c" (as used in physics). My understanding of locale issues is also limited and subject to change or re-education... :-) -- 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/ From cygwin@cwilson.fastmail.fm Thu Dec 3 07:37:00 2009 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Thu, 03 Dec 2009 07:37:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <4B174C20.1040900@tlinx.org> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> Message-ID: <4B176AC7.4030405@cwilson.fastmail.fm> Linda Walsh wrote: > C.UTF_8 doesn't exist. You're wrong. Please read the whole of this thread -- and the last two months' worth of cygwin-developers. > mintty is broken. No, it isn't. It just doesn't work the way *you* expect it to. > Might want to try 'Console' nstead of using mintty. Not perfect either, > but fewer compatibility problems that I've noticed. > > Examples of valid LANG values: > C, ca_FR, en_US, fr_FR, it_IT, nl_NL, wa_BE@euro > > You can't have "C" and "UTF-8", because C means no encoding (default). No, it doesn't. "C" means "POSIX" and is defined here: http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html Note how all the glyphs are defined in terms of character NAMES, not hexadecimal values? That's because "C", all by itself, just doesn't SPECIFY any encoding. You're still allowed to HAVE one -- in fact, you ALWAYS have one. On most systems, that has historically been the plain ASCII 7-bit encoding; many others used the EBCDIC encoding and were not considered in violation of the POSIX "C" locale specification. Now, many systems are starting to use the UTF-8 encoding by default, even in the "C" locale. "C"/"POSIX" locale (without an additional .ENCODING suffix) is encoding-AGNOSTIC, that's all. So, you're allowed to add an .ENCODING suffix to force a specific encoding if you like, without violating POSIX. (And your system is also allowed, in that case, to IGNORE that .ENCODING suffix, and still be Posix-compliant IIUC, so it's rather a hole in the spec IMO). > UTF-8 IS an encoding, so they are mutually exclusive. I don't > know under what circumstances "C" might imply UTF-8. Whenever the platform decides to use UTF-8 as its default encoding, which is perfectly acceptable according to Posix. Cygwin-1.7 has decided to do that. So, on cygwin-1.7, "C" implies .UTF-8. X11R7.5 doesn't yet know that, without outside help (e.g. explicitly setting $LANG to "C.UTF-8" by default, so that XWin "knows" about the new default behavior). > If the definition > of "C" changes? It might be easier than changing "c" (as used in physics). > > My understanding of locale issues is also limited and subject to change or > re-education... Uhm, yeah. -- Chuck -- 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/ From andy.koppe@gmail.com Thu Dec 3 07:48:00 2009 From: andy.koppe@gmail.com (Andy Koppe) Date: Thu, 03 Dec 2009 07:48:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <4B174C20.1040900@tlinx.org> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> Message-ID: <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> 2009/12/3 Linda Walsh: > C.UTF_8 doesn't exist. Well, guess what: it does in Cygwin 1.7, and it's the default locale. And it's also in the next Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522776. Cygwin 1.7 also supports "C.ISO-8859-1", "C.CP1252", ... > Might want to try 'Console' nstead of using mintty. ?Not perfect either, but > fewer compatibility problems that I've noticed. Care to provide examples, so they can be fixed? Or are you just bitter about having to tick a box to switch backspace to ^H? 'Console' is better for native Windows programs, because, well, it's a console, whereas mintty is more suited for Unix programs, because it's an xterm-compatible tty. > You can't have "C" and "UTF-8", because C means no encoding (default). > UTF-8 IS an encoding, so they are mutually exclusive. >From http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html, ?7.2: "The tables in Locale Definition describe the characteristics and behavior of the POSIX locale for data consisting entirely of characters from the portable character set and the control character set. For other characters, the behavior is unspecified." This means that characters 0..127 have to be treated as ASCII, but beyond that an implementation can do what it wants. And on Cygwin 1.7, plain "C" actually does imply UTF-8, which happily is backward-compatible with ASCII. Not that that is much to do with "C.UTF-8", which is a separate locale in any case. The meaning of locale strings is up to the OS, e.g. with the Windows C runtime you get stuff like "English_United States.1252". And 'C.' on Cygwin is intended to mean "the semantics of the C locale, but with the specified charset". However, since the 'C.' format is unlikely to be recognised by remote systems, it's recommended to set a "real" locale such as 'en_US.UTF-8'. > I don't > know under what circumstances "C" might imply UTF-8. If the definition > of "C" changes? It might be easier than changing "c" (as used in physics). How droll. Andy -- 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/ From lottas.junk@geekmail.de Thu Dec 3 08:12:00 2009 From: lottas.junk@geekmail.de (Lothar Brendel) Date: Thu, 03 Dec 2009 08:12:00 -0000 Subject: xterm doesn't open on start (was: checkX problems) References: <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov> <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> <3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D370787@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D3DD693@VHAISHMSGJ2.vha.med.va.gov> <20091202232352.GA17116@ednor.casa.cgf.cx> Message-ID: <41700259C03B49A3AB83185274738895@MultiOcke> Christopher Faylor wrote: > On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote: >>> More information as promised, after getting the new run and checkX >>> (run2) packages announced this morning. >>> >>> $ checkX -v >>> run2 0.3.2 >> >> 0.3.2 announced? I didn't get any such message, and setup still only >> offers >> 0.3.1-1 to me. > > http://cygwin.com/ml/cygwin-announce/2009-12/msg00002.html > http://cygwin.com/ml/cygwin/2009-12/msg00079.html Thanx. I had just focused on cygwin-xfree, but indeed run2 is more general. 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/ From corinna-cygwin@cygwin.com Thu Dec 3 09:09:00 2009 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Thu, 03 Dec 2009 09:09:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> Message-ID: <20091203090917.GA5487@calimero.vinschen.de> On Dec 3 07:48, Andy Koppe wrote: > 2009/12/3 Linda Walsh: > > C.UTF_8 doesn't exist. > > Well, guess what: it does in Cygwin 1.7, and it's the default locale. Not exactly. The default locale is C.UTF-8. You can also use C.UTF8 or C.utf-8 or C.utf8, but not C.UTF_8 or C.utf_8. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/ From dickey@his.com Thu Dec 3 09:55:00 2009 From: dickey@his.com (Thomas Dickey) Date: Thu, 03 Dec 2009 09:55:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> Message-ID: <20091203045401.L85368@mail101.his.com> On Thu, 3 Dec 2009, Andy Koppe wrote: > 2009/12/3 Linda Walsh: >> C.UTF_8 doesn't exist. ... >> You can't have "C" and "UTF-8", because C means no encoding (default). >> UTF-8 IS an encoding, so they are mutually exclusive. > > From http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html, > ?7.2: > > "The tables in Locale Definition describe the characteristics and > behavior of the POSIX locale for data consisting entirely of > characters from the portable character set and the control character > set. For other characters, the behavior is unspecified." > > This means that characters 0..127 have to be treated as ASCII, but > beyond that an implementation can do what it wants. And on Cygwin 1.7, > plain "C" actually does imply UTF-8, which happily is > backward-compatible with ASCII. That's an interpretation that so far hasn't been blessed by the standards people. Any discussion of this topic should mention that, as a caveat. ymmv -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- -- 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/ From andy.koppe@gmail.com Thu Dec 3 13:16:00 2009 From: andy.koppe@gmail.com (Andy Koppe) Date: Thu, 03 Dec 2009 13:16:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <20091203045401.L85368@mail101.his.com> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> <20091203045401.L85368@mail101.his.com> Message-ID: <416096c60912030516r42f67c05yfaa3b64fcca68b43@mail.gmail.com> 2009/12/3 Thomas Dickey: >> From >> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html, >> ?7.2: >> >> "The tables in Locale Definition describe the characteristics and >> behavior of the POSIX locale for data consisting entirely of >> characters from the portable character set and the control character >> set. For other characters, the behavior is unspecified." >> >> This means that characters 0..127 have to be treated as ASCII, but >> beyond that an implementation can do what it wants. And on Cygwin 1.7, >> plain "C" actually does imply UTF-8, which happily is >> backward-compatible with ASCII. > > That's an interpretation that so far hasn't been blessed by the standards > people. ?Any discussion of this topic should mention that, as a caveat. Fair point. It also means that apps are entitled to assume that "C" supports no more than ASCII, which is why Cygwin 1.7's default locale is C.UTF-8. A default locale setting based on the user's language selection would be better, but we don't have that (yet?). Andy -- 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/ From corinna-cygwin@cygwin.com Thu Dec 3 13:48:00 2009 From: corinna-cygwin@cygwin.com (Corinna Vinschen) Date: Thu, 03 Dec 2009 13:48:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: <416096c60912030516r42f67c05yfaa3b64fcca68b43@mail.gmail.com> References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> <20091203045401.L85368@mail101.his.com> <416096c60912030516r42f67c05yfaa3b64fcca68b43@mail.gmail.com> Message-ID: <20091203134837.GX8059@calimero.vinschen.de> On Dec 3 13:16, Andy Koppe wrote: > 2009/12/3 Thomas Dickey: > >> From > >> http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html, > >> ??7.2: > >> > >> "The tables in Locale Definition describe the characteristics and > >> behavior of the POSIX locale for data consisting entirely of > >> characters from the portable character set and the control character > >> set. For other characters, the behavior is unspecified." > >> > >> This means that characters 0..127 have to be treated as ASCII, but > >> beyond that an implementation can do what it wants. And on Cygwin 1.7, > >> plain "C" actually does imply UTF-8, which happily is > >> backward-compatible with ASCII. > > > > That's an interpretation that so far hasn't been blessed by the standards > > people. ??Any discussion of this topic should mention that, as a caveat. > > Fair point. It also means that apps are entitled to assume that "C" > supports no more than ASCII, which is why Cygwin 1.7's default locale > is C.UTF-8. A default locale setting based on the user's language > selection would be better, but we don't have that (yet?). Try the attached. Note: It has a hidden "--testloop" option... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -------------- next part -------------- A non-text attachment was scrubbed... Name: getlocale.cc Type: text/x-c++src Size: 4612 bytes Desc: not available URL: -------------- next part -------------- -- 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/ From fstx+u@update.uu.se Thu Dec 3 21:08:00 2009 From: fstx+u@update.uu.se (Fredrik Staxeng) Date: Thu, 03 Dec 2009 21:08:00 -0000 Subject: 1.7 - what's the right way to start X? Message-ID: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? -- Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/ From reply-to-list-only-lh-x@cygwin.com Thu Dec 3 21:36:00 2009 From: reply-to-list-only-lh-x@cygwin.com (Larry Hall (Cygwin X)) Date: Thu, 03 Dec 2009 21:36:00 -0000 Subject: 1.7 - what's the right way to start X? In-Reply-To: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> Message-ID: <4B182ECF.1040805@cygwin.com> On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: > What is the recommended/preferred way to start X in 1.7? In 1.5 > I used a modified version of startxwin.bat. And where do I > put my .xinitrc/.xsession script? What about startxwin.bat doesn't work for you? There shouldn't be differences between 1.5 and 1.7 here. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/ From wgweis@sbcglobal.net Thu Dec 3 21:46:00 2009 From: wgweis@sbcglobal.net (wgweis@sbcglobal.net) Date: Thu, 03 Dec 2009 21:46:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? References: <4AEAEEAB.2030009@cornell.edu> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> Message-ID: <016701ca7462$1de95b50$4401a8c0@BANDIT> Hi: I sent this post earlier this week and have not received any replies. If this is the wrong place to post this, please let me know where I should. Thanks ================================================ Hi All: This is my first post here. I've never had a problem I couldn't fix with cygwin-x before. Here is the deal: I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat and see this: "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0" this seems to be coming from this command in the batch file: :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash - usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 If I kill the server and run the script again, I'll get a STATUS_ACCESS_VIOLATION error, indicating some sort of shared memory corruption. I then have to restart the PC. I checked to see if there was more than one cygwin1.dll in response to earlier posts about this error and there is only one. I tried turning off the windows firewall. That helps in other ways, because other cygwin network utilities, such as nslookup were blocked until I did that. I tried changing the display from 127.0.0.1 to the IP address of the machine. Basically, I have a fresh machine with windows 7 and a fresh install of cygwin and I can't get xterm to work. Anyone have any ideas? Or is this just a windows 7 thing, and I'll have to give up on cygwin-x for a while? BTW, other shortcuts in the cygwin-x start folder work, such as bitmap and xcalc, just not the Xwin server and xterm. Thanks in advance, George -- 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/ From fstx+u@update.uu.se Thu Dec 3 21:54:00 2009 From: fstx+u@update.uu.se (Fredrik Staxeng) Date: Thu, 03 Dec 2009 21:54:00 -0000 Subject: 1.7 - what's the right way to start X? References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> <4B182ECF.1040805@cygwin.com> Message-ID: <1mvdgnsozd.fsf@Psilocybe.Update.UU.SE> "Larry Hall (Cygwin X)" writes: >On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: >> What is the recommended/preferred way to start X in 1.7? In 1.5 >> I used a modified version of startxwin.bat. And where do I >> put my .xinitrc/.xsession script? > >What about startxwin.bat doesn't work for you? There shouldn't be >differences between 1.5 and 1.7 here. Well, I did not find it, so I assumed it had been replaced with something better. Something that a) does not pop up a command window and b) calls .xinitrc or something I have to admit I did not look at the Cygwin site before posting the question. I did so after, and saw the Cygwin/X section. -- Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/ From mike_ayers@tvworks.com Thu Dec 3 22:18:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Thu, 03 Dec 2009 22:18:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? In-Reply-To: <016701ca7462$1de95b50$4401a8c0@BANDIT> References: <4AEAEEAB.2030009@cornell.edu> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D8860EE@mailserver.metatv-ds.metatv.com> > From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- > owner@cygwin.com] On Behalf Of wgweis@sbcglobal.net > Sent: Thursday, December 03, 2009 1:47 PM > I sent this post earlier this week and have not received any > replies. > If this is the wrong place to post this, > please let me know where I should. This is the place, but I don't know how many of us have tried using 64 bit Windows 7 yet. I know I haven't, but I'll offer advice anyway. (What's the smiley for "evil leer"?) > I just bought a new PC with windows 7 64 bit, build number 7600, > version 6.1. > I downloaded a fresh install of cygwin and cannot get cygwin-x xterm > running. Cygwin version is 1.7.0(0.218/5/3) > > I tried running the cygwin-x XWin Server shortcut command line from a > cmd > window to get the error output: > > C:\cygwin\bin\run.exe /usr/bin/startxwin.bat > > and see this: > > "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0" > > this seems to be coming from this command in the batch file: > :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e > /usr/bin/bash - > > usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 ...implying that the server didn't start. > If I kill the server and run the script again, I'll get a > STATUS_ACCESS_VIOLATION error, indicating > some sort of shared memory corruption. I then have to restart the PC. > I > checked to see if there > was more than one cygwin1.dll in response to earlier posts about this > error > and there is only one. > > I tried turning off the windows firewall. That helps in other ways, > because > other cygwin network > utilities, such as nslookup were blocked until I did that. > > I tried changing the display from 127.0.0.1 to the IP address of the > machine. I believe the X server listens on 0.0.0.0, so that shouldn't make a difference. > Basically, I have a fresh machine with windows 7 and a fresh install of > cygwin and I can't get > xterm to work. Anyone have any ideas? Or is this just a windows 7 > thing, > and I'll have to give > up on cygwin-x for a while? > > BTW, other shortcuts in the cygwin-x start folder work, such as bitmap > and > xcalc, just not the > Xwin server and xterm. How can xcalc work if the server doesn't start?! Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r >cygcheck.out) as attachments in the hope that they will inspire. Thanks, Mike From mike_ayers@tvworks.com Thu Dec 3 22:22:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Thu, 03 Dec 2009 22:22:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? In-Reply-To: <016701ca7462$1de95b50$4401a8c0@BANDIT> References: <4AEAEEAB.2030009@cornell.edu> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D8860F7@mailserver.metatv-ds.metatv.com> > From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- > owner@cygwin.com] On Behalf Of wgweis@sbcglobal.net > Sent: Thursday, December 03, 2009 1:47 PM > I sent this post earlier this week and have not received any > replies. > If this is the wrong place to post this, > please let me know where I should. This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet. > I just bought a new PC with windows 7 64 bit, build number 7600, > version 6.1. > I downloaded a fresh install of cygwin and cannot get cygwin-x xterm > running. Cygwin version is 1.7.0(0.218/5/3) > > I tried running the cygwin-x XWin Server shortcut command line from a > cmd > window to get the error output: > > C:\cygwin\bin\run.exe /usr/bin/startxwin.bat > > and see this: > > "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0" > > this seems to be coming from this command in the batch file: > :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e > /usr/bin/bash - > > usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 ...implying that the server didn't start. Did you run as administrator? > I > checked to see if there > was more than one cygwin1.dll in response to earlier posts about this > error > and there is only one. > > I tried turning off the windows firewall. That helps in other ways, > because > other cygwin network > utilities, such as nslookup were blocked until I did that. > > I tried changing the display from 127.0.0.1 to the IP address of the > machine. I believe the X server listens on 0.0.0.0, so that shouldn't make a difference. > Basically, I have a fresh machine with windows 7 and a fresh install of > cygwin and I can't get > xterm to work. Anyone have any ideas? Or is this just a windows 7 > thing, > and I'll have to give > up on cygwin-x for a while? > > BTW, other shortcuts in the cygwin-x start folder work, such as bitmap > and > xcalc, just not the > Xwin server and xterm. How can xcalc work if the server doesn't start?! Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r >cygcheck.out) as attachments in the hope that they will inspire. Thanks, Mike From mike_ayers@tvworks.com Thu Dec 3 22:23:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Thu, 03 Dec 2009 22:23:00 -0000 Subject: FW: cygwin-x xterm not compatible with windows 7? Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D8860FB@mailserver.metatv-ds.metatv.com> > From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- > owner@cygwin.com] On Behalf Of wgweis@sbcglobal.net > Sent: Thursday, December 03, 2009 1:47 PM > I sent this post earlier this week and have not received any > replies. > If this is the wrong place to post this, > please let me know where I should. This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet. > I just bought a new PC with windows 7 64 bit, build number 7600, > version 6.1. > I downloaded a fresh install of cygwin and cannot get cygwin-x xterm > running. Cygwin version is 1.7.0(0.218/5/3) > > I tried running the cygwin-x XWin Server shortcut command line from a > cmd > window to get the error output: > > C:\cygwin\bin\run.exe /usr/bin/startxwin.bat > > and see this: > > "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0" > > this seems to be coming from this command in the batch file: > :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e > /usr/bin/bash - > > usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 ...implying that the server didn't start. Did you run as administrator? > I > checked to see if there > was more than one cygwin1.dll in response to earlier posts about this > error > and there is only one. > > I tried turning off the windows firewall. That helps in other ways, > because > other cygwin network > utilities, such as nslookup were blocked until I did that. > > I tried changing the display from 127.0.0.1 to the IP address of the > machine. I believe the X server listens on 0.0.0.0, so that shouldn't make a difference. > Basically, I have a fresh machine with windows 7 and a fresh install of > cygwin and I can't get > xterm to work. Anyone have any ideas? Or is this just a windows 7 > thing, > and I'll have to give > up on cygwin-x for a while? > > BTW, other shortcuts in the cygwin-x start folder work, such as bitmap > and > xcalc, just not the > Xwin server and xterm. How can xcalc work if the server doesn't start?! Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r >cygcheck.out) as attachments in the hope that they will inspire. Thanks, Mike From jjreisert@alum.mit.edu Thu Dec 3 22:40:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Thu, 03 Dec 2009 22:40:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? In-Reply-To: <83E753BE7B6A324ABB336245BAF1DAAC0D8860F7@mailserver.metatv-ds.metatv.com> References: <4AEAEEAB.2030009@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca7462$1de95b50$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D8860F7@mailserver.metatv-ds.metatv.com> Message-ID: <806a89db0912031440g4e704cf6x5a44b95458e953ad@mail.gmail.com> On Thu, Dec 3, 2009 at 3:22 PM, Mike Ayers wrote: > This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet. I'm running Windows 7 Professional, 64-bit. I have been using Cygwin 1.7 with latest X, etc. for some time without any problems. I haven't done anything special, so I haven't run into any of the same problems as the OP. - Jim -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From cgf-use-the-mailinglist-please@cygwin.com Thu Dec 3 23:25:00 2009 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Thu, 03 Dec 2009 23:25:00 -0000 Subject: FW: cygwin-x xterm not compatible with windows 7? In-Reply-To: <83E753BE7B6A324ABB336245BAF1DAAC0D8860FB@mailserver.metatv-ds.metatv.com> References: <83E753BE7B6A324ABB336245BAF1DAAC0D8860FB@mailserver.metatv-ds.metatv.com> Message-ID: <20091203232506.GA23996@ednor.casa.cgf.cx> On Thu, Dec 03, 2009 at 02:23:53PM -0800, Mike Ayers wrote: You really only need to send this type of thing once. Three times is overkill. -- 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/ From proweb@ibuzzprosecret.com Thu Dec 3 23:38:00 2009 From: proweb@ibuzzprosecret.com (Web Solutions) Date: Thu, 03 Dec 2009 23:38:00 -0000 Subject: Who would have figured... Message-ID: <5e88e7980e61925ff97ba3331dd83c5b@ibuzzprosecret.com> Who Would Have Figured You Could... Do Everything 10,000 Times Faster? Now You Can. Discover How Easy it Is Here http://ez-web-solutions.net.tc Much Success in all Your Endeavors, ~David -- 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/ From cygwin@tlinx.org Thu Dec 3 23:52:00 2009 From: cygwin@tlinx.org (Linda Walsh) Date: Thu, 03 Dec 2009 23:52:00 -0000 Subject: xterm doesn't open on start In-Reply-To: <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> References: <4AEAEEAB.2030009@cornell.edu> <4AFC7EA3.4040908@dronecode.org.uk> <764E086205BD4C2FB577A5F318234A22@MultiOcke> <4AFCC408.7040005@cwilson.fastmail.fm> <01CC888973B04485A45E000E506E8BE2@MultiOcke> <83E753BE7B6A324ABB336245BAF1DAAC0D675503@mailserver.metatv-ds.metatv.com> <1AF6441D7C284D86A18503A1A76C2895@MultiOcke> <4AFF1AF5.2050200@cwilson.fastmail.fm> <9D882BC2C45747B28E9A83C5F5C5B70F@MultiOcke> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <4B184F47.6010400@tlinx.org> Timares, Brian (Patriot) wrote: > 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. --- Do you have DISPLAY=:0 set in your Windows environment? (system properties, Advanced, Env Vars). I put mine in the System Environment so it's there no matter how I'm logged in. -- 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/ From mike_ayers@tvworks.com Fri Dec 4 00:01:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Fri, 04 Dec 2009 00:01:00 -0000 Subject: FW: cygwin-x xterm not compatible with windows 7? In-Reply-To: <20091203232506.GA23996@ednor.casa.cgf.cx> References: <83E753BE7B6A324ABB336245BAF1DAAC0D8860FB@mailserver.metatv-ds.metatv.com> <20091203232506.GA23996@ednor.casa.cgf.cx> Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D8861E0@mailserver.metatv-ds.metatv.com> > From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- > owner@cygwin.com] On Behalf Of Christopher Faylor > You really only need to send this type of thing once. Three times is > overkill. The first two came back to me from cygwin-xfree-return-*@cygwin.com addresses with the first part garbled, so I thought they were mangled by my mailer and not getting sent to the list. Apologies for the inconvenience - still not sure what happened. Mike From Brian.Timares@va.gov Fri Dec 4 03:51:00 2009 From: Brian.Timares@va.gov (Timares, Brian (Harris Corp.)) Date: Fri, 04 Dec 2009 03:51:00 -0000 Subject: xterm doesn't open on start In-Reply-To: <4B184F47.6010400@tlinx.org> References: <4AEAEEAB.2030009@cornell.edu> <4AFC7EA3.4040908@dronecode.org.uk> <764E086205BD4C2FB577A5F318234A22@MultiOcke> <4AFCC408.7040005@cwilson.fastmail.fm> <01CC888973B04485A45E000E506E8BE2@MultiOcke> <83E753BE7B6A324ABB336245BAF1DAAC0D675503@mailserver.metatv-ds.metatv.com> <1AF6441D7C284D86A18503A1A76C2895@MultiOcke> <4AFF1AF5.2050200@cwilson.fastmail.fm> <9D882BC2C45747B28E9A83C5F5C5B70F@MultiOcke> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <4B184F47.6010400@tlinx.org> Message-ID: <270AA78168E41541833C52448F4F34AD1D525275@VHAISHMSGJ2.vha.med.va.gov> Linda Walsh wrote: >Timares, Brian (Patriot) wrote: >> 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. > Do you have >DISPLAY=:0 >set in your Windows environment? I didn't, but I do now. I am forced to use Outlook so I forwarded the more extensive email to my personal account so I can edit it more easily/correctly and because my work got pretty busy. I reverted to 1.5 to see if that would work better, it doesn't really, so I'll try to install 1.7 in parallel when I get a chance (I have servers doing things now so I have to let it alone for awhile). I do appreciate all the terrific replies--I've been on the net for awhile and this is one of the friendliest lists I've been on. Brian Timares oh and then there is the 7-year-old, he is taking lots of time :) -- 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/ From reply-to-list-only-lh-x@cygwin.com Fri Dec 4 03:55:00 2009 From: reply-to-list-only-lh-x@cygwin.com (Larry Hall (Cygwin X)) Date: Fri, 04 Dec 2009 03:55:00 -0000 Subject: xterm doesn't open on start In-Reply-To: <270AA78168E41541833C52448F4F34AD1D525275@VHAISHMSGJ2.vha.med.va.gov> References: <4AEAEEAB.2030009@cornell.edu> <764E086205BD4C2FB577A5F318234A22@MultiOcke> <4AFCC408.7040005@cwilson.fastmail.fm> <01CC888973B04485A45E000E506E8BE2@MultiOcke> <83E753BE7B6A324ABB336245BAF1DAAC0D675503@mailserver.metatv-ds.metatv.com> <1AF6441D7C284D86A18503A1A76C2895@MultiOcke> <4AFF1AF5.2050200@cwilson.fastmail.fm> <9D882BC2C45747B28E9A83C5F5C5B70F@MultiOcke> <4B000E98.7070209@cwilson.fastmail.fm> <4B06CE7D.6060709@cwilson.fastmail.fm> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <4B184F47.6010400@tlinx.org> <270AA78168E41541833C52448F4F34AD1D525275@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <4B1887B7.6080208@cygwin.com> On 12/03/2009 10:47 PM, Timares, Brian (Harris Corp.) wrote: > I do appreciate all the terrific replies--I've been on the net for > awhile and this is one of the friendliest lists I've been on. Do you mind if I frame this and hang it on the Cygwin home page. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/ From ebb9@byu.net Fri Dec 4 04:30:00 2009 From: ebb9@byu.net (Eric Blake) Date: Fri, 04 Dec 2009 04:30:00 -0000 Subject: X11R7.5 and C.UTF-8 References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> <20091203045401.L85368@mail101.his.com> Message-ID: Thomas Dickey his.com> writes: > > This means that characters 0..127 have to be treated as ASCII, but No, it means that portable characters and control characters must be < 128. ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C locale also implies that you can manipulate bytes >= 128 in the naive manner, so long as you don't care about characters embedded in those bytes. And what do you know - ASCII, EBCDIC, and UTF-8 all meet this property, too. > > beyond that an implementation can do what it wants. And on Cygwin 1.7, > > plain "C" actually does imply UTF-8, which happily is > > backward-compatible with ASCII. > > That's an interpretation that so far hasn't been blessed by the standards > people. Any discussion of this topic should mention that, as a caveat. Actually, the standards people HAVE spoken - and they agreed with our interpretation. POSIX was INTENTIONALLY written with the intent that a UTF-8 encoding is valid for the C locale, for the same reason that it was written that an EBCDIC encoding is valid for the C locale. These emails from the Austin Group (the folks that write POSIX) are telling: https://www.opengroup.org/sophocles/show_mail.tpl? CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=12982 https://www.opengroup.org/sophocles/show_mail.tpl? CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=13012 But they also admitted that there is still more work needed in POSIX to make this intent clearly codified (for example, that control characters must be single bytes < 128). -- Eric Blake -- 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/ From reid.thompson@ateb.com Fri Dec 4 04:51:00 2009 From: reid.thompson@ateb.com (Reid Thompson) Date: Fri, 04 Dec 2009 04:51:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? In-Reply-To: <016701ca7462$1de95b50$4401a8c0@BANDIT> References: <4AEAEEAB.2030009@cornell.edu> <4B0A8AC5.9080305@cwilson.fastmail.fm> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca7462$1de95b50$4401a8c0@BANDIT> Message-ID: <4B18953E.3020401@ateb.com> wgweis@sbcglobal.net wrote: > Hi: > I sent this post earlier this week and have not received any replies. > If this is the wrong place to post this, > please let me know where I should. > > Thanks > ================================================ > Hi All: > This is my first post here. I've never had a problem I couldn't fix > with cygwin-x before. > Here is the deal: > > I just bought a new PC with windows 7 64 bit, build number 7600, > version 6.1. > I downloaded a fresh install of cygwin and cannot get cygwin-x xterm > running. Cygwin version is 1.7.0(0.218/5/3) > > I tried running the cygwin-x XWin Server shortcut command line from a cmd > window to get the error output: > > C:\cygwin\bin\run.exe /usr/bin/startxwin.bat try this -- edit /usr/bin/startxwin.bat and put a 5 second sleep between the call to Xwin and the call to xterm, and see what happens -- 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/ From dickey@his.com Fri Dec 4 09:45:00 2009 From: dickey@his.com (Thomas Dickey) Date: Fri, 04 Dec 2009 09:45:00 -0000 Subject: X11R7.5 and C.UTF-8 In-Reply-To: References: <4AE8539E.9080004@cornell.edu> <20091028172216.P60895@mail101.his.com> <4AE8BC12.1060109@cornell.edu> <416096c60910281507n4774534dode1d24ac47d5b0a2@mail.gmail.com> <4B1115EC.7010308@cornell.edu> <4B174C20.1040900@tlinx.org> <416096c60912022348i36504e14l726efc9fc9c360e6@mail.gmail.com> <20091203045401.L85368@mail101.his.com> Message-ID: <20091204044346.M57150@mail101.his.com> On Thu, 3 Dec 2009, Eric Blake wrote: > Thomas Dickey his.com> writes: > >>> This means that characters 0..127 have to be treated as ASCII, but > > No, it means that portable characters and control characters must be < 128. > ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C > locale also implies that you can manipulate bytes >= 128 in the naive manner, > so long as you don't care about characters embedded in those bytes. And what > do you know - ASCII, EBCDIC, and UTF-8 all meet this property, too. > >>> beyond that an implementation can do what it wants. And on Cygwin 1.7, >>> plain "C" actually does imply UTF-8, which happily is >>> backward-compatible with ASCII. >> >> That's an interpretation that so far hasn't been blessed by the standards >> people. Any discussion of this topic should mention that, as a caveat. > > Actually, the standards people HAVE spoken - and they agreed with our > interpretation. POSIX was INTENTIONALLY written with the intent that a UTF-8 > encoding is valid for the C locale, for the same reason that it was written > that an EBCDIC encoding is valid for the C locale. These emails from the > Austin Group (the folks that write POSIX) are telling: > > https://www.opengroup.org/sophocles/show_mail.tpl? > CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=12982 This is basically your email on the matter. > https://www.opengroup.org/sophocles/show_mail.tpl? > CALLER=show_archive.tpl&source=L&listname=austin-group-l&id=13012 > > But they also admitted that there is still more work needed in POSIX to make > this intent clearly codified (for example, that control characters must be > single bytes < 128). But they have not actually agreed with you yet. -- 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/ From WendelDRenner@comcast.net Fri Dec 4 14:44:00 2009 From: WendelDRenner@comcast.net (Wendel Dean Renner) Date: Fri, 04 Dec 2009 14:44:00 -0000 Subject: how do I get help if I can't figure out how to do anything? Message-ID: <4B192052.6000808@comcast.net> Do you have a list of consultants? And it is not like I am ignorant of computers. I write c++ code. Without help, who is going to be able to use anything provided? Have managed to compile and link a Open GL, X/Motif program (using lesstif) and get Error: Can't open display. Need to be able to run program remotely on a ubuntu system. I can't get beyond connection refused. Ran xstartwin.bat and lost control c - control V on Windows. -- 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/ From mbreuer@majjas.com Fri Dec 4 15:41:00 2009 From: mbreuer@majjas.com (Michael Breuer) Date: Fri, 04 Dec 2009 15:41:00 -0000 Subject: how do I get help if I can't figure out how to do anything? In-Reply-To: <4B192052.6000808@comcast.net> References: <4B192052.6000808@comcast.net> Message-ID: <4B192D89.9050707@majjas.com> Have you looked at the troubleshooting documentation? You know you can run with verbose and log options. My guess is that the reason the display can't be opened is made reasonable clear in your log file(s). I'm also going to hazard a guess that your xserver doesn't have opengl support. Wendel Dean Renner wrote: > Do you have a list of consultants? And it is not like I am ignorant of > computers. I write c++ code. Without help, who is going to be able to > use anything provided? > > Have managed to compile and link a Open GL, X/Motif program (using > lesstif) and > get Error: Can't open display. > > Need to be able to run program remotely on a ubuntu system. I can't > get beyond connection refused. > > Ran xstartwin.bat and lost control c - control V on Windows. > -- > 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/ -- 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/ From cgf-use-the-mailinglist-please@cygwin.com Fri Dec 4 16:01:00 2009 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Fri, 04 Dec 2009 16:01:00 -0000 Subject: how do I get help if I can't figure out how to do anything? In-Reply-To: <4B192052.6000808@comcast.net> References: <4B192052.6000808@comcast.net> Message-ID: <20091204160109.GB29605@ednor.casa.cgf.cx> On Fri, Dec 04, 2009 at 09:44:34AM -0500, Wendel Dean Renner wrote: >Do you have a list of consultants? >And it is not like I am ignorant of computers. I write c++ code. >Without help, who is going to be able to use anything provided? What is a "consultant"? Are you actualy saying that you will be willing to pay someone to help you? If not, then this list is your "consultant". If so, then the answer is probably "no". It's free software so if you don't understand something then you read the documentation. If the documentation doesn't help then you ask in an appropriate forum and are grateful when someone volunteers time to help you. cgf -- 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/ From fstx+u@update.uu.se Fri Dec 4 16:13:00 2009 From: fstx+u@update.uu.se (Fredrik Staxeng) Date: Fri, 04 Dec 2009 16:13:00 -0000 Subject: 1.7 - what's the right way to start X? References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> <4B182ECF.1040805@cygwin.com> Message-ID: <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> "Larry Hall (Cygwin X)" writes: >On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: >> What is the recommended/preferred way to start X in 1.7? In 1.5 >> I used a modified version of startxwin.bat. And where do I >> put my .xinitrc/.xsession script? > >What about startxwin.bat doesn't work for you? There shouldn't be >differences between 1.5 and 1.7 here. Now I have gotten startxwin.bat to work, and modified it to run my bash script. I had some strange problems on the way though. Previously, I had used the Cygwin Bash Shell to make some changes. I use mount -c /, change /etc/passwd to refer to right home directory /c/home/fstx, and put in my .profile and .bash_rc files. I don't remember doing the mkpasswd/mkgroup thing, but I could have. When I double-clicked startxwin.bat for the first time, it failed. I think XWin.exe did not start dfor some reason. But I immediately tried again, and this time I got an XTerm. However, I was in /home/fstx, not /c/home/fstx, and I got the mkpasswd message. When I tried to fix things, I discovered that the mount prefix was set back to /cygdrive. I can change it, but when I restart cygwin it goes back to /cygdrive. I can live with that (at least for now) But starting xterms seems to be very slow, and about 25% of time it fails with 2 [main] xterm 3128 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0xC0000005, errno 11 xterm: Error 29, errno 11: Resource temporarily unavailable Reason: spawn: fork() failed I have seen this problem before, and the solution was to run rebaseall, which broke emacs, and then reinstall libncurses to fix emacs. Is this the way to do it? Will it still break emacs? Will other things break? Will it break again when updating cygwin? I am running Windows 7 64-bit Enterprise. Despite the troubles I have had, I must say that I admire Cygwin for doing a very good job at an almost impossible task, and the developers for the heroic efforts to bring Cygwin to each new version of Windows, despite that Microsoft apparently couldn't care less about breaking it. -- Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/ From jrdepriest@gmail.com Fri Dec 4 16:58:00 2009 From: jrdepriest@gmail.com (DePriest, Jason R.) Date: Fri, 04 Dec 2009 16:58:00 -0000 Subject: 1.7 - what's the right way to start X? In-Reply-To: <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> <4B182ECF.1040805@cygwin.com> <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> Message-ID: <31b7d2790912040857n6ffd33e7jf8fe578c6432baaa@mail.gmail.com> On Fri, Dec 4, 2009 at 10:12 AM, Fredrik Staxeng <> wrote: > "Larry Hall (Cygwin X)" <> writes: > >>On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: >>> What is the recommended/preferred way to start X in 1.7? In 1.5 >>> I used a modified version of startxwin.bat. And where do I >>> put my .xinitrc/.xsession script? >> >>What about startxwin.bat doesn't work for you? ?There shouldn't be >>differences between 1.5 and 1.7 here. > 1.7 makes some pretty significant changes on how 'mount' works. Basically, Cygwin 1.7 uses a real fstab file instead of a bunch of registry entries and 'mount' only creates temporary mounts. If you want a permanent mount, use the fstab file. In a little bit more detail, see below. From: http://cygwin.com/1.7/cygwin-ug-net/ov-new1.7.html - Mount points are no longer stored in the registry. Use /etc/fstab and /etc/fstab.d/$USER instead. Mount points created with mount(1) are only local to the current session and disappear when the last Cygwin process in the session exits. - Cygwin creates the mount points for /, /usr/bin, and /usr/lib automatically from it's own position on the disk. They don't have to be specified in /etc/fstab. This discusses the mount table in more detail: http://cygwin.com/1.7/cygwin-ug-net/using.html#mount-table This is the help information for mount under 1.7: http://cygwin.com/1.7/cygwin-ug-net/using-utils.html#mount Thanks. -Jason -- 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/ From kbrown@cornell.edu Fri Dec 4 18:43:00 2009 From: kbrown@cornell.edu (Ken Brown) Date: Fri, 04 Dec 2009 18:43:00 -0000 Subject: 1.7 - what's the right way to start X? In-Reply-To: <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> <4B182ECF.1040805@cygwin.com> <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> Message-ID: <4B19583D.40906@cornell.edu> On 12/4/2009 11:12 AM, Fredrik Staxeng wrote: > I have seen this problem before, and the solution was to run rebaseall, > which broke emacs, and then reinstall libncurses to fix emacs. > > Is this the way to do it? > Will it still break emacs? I haven't seen any reports of emacs problems in 1.7 after rebasing. Ken Brown Cygwin's emacs maintainer -- 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/ From gcruzicka@comcast.net Sat Dec 5 01:50:00 2009 From: gcruzicka@comcast.net (Gene C. Ruzicka) Date: Sat, 05 Dec 2009 01:50:00 -0000 Subject: how do I get help if I can't figure out how to do anything? In-Reply-To: <4B192052.6000808@comcast.net> References: <4B192052.6000808@comcast.net> Message-ID: <4B19BC7E.9060008@comcast.net> Wendel Dean Renner wrote: > Do you have a list of consultants? And it is not like I am ignorant of > computers. I write c++ code. Without help, who is going to be able to > use anything provided? > > Have managed to compile and link a Open GL, X/Motif program (using > lesstif) and > get Error: Can't open display. > > Need to be able to run program remotely on a ubuntu system. I can't > get beyond connection refused. > > Ran xstartwin.bat and lost control c - control V on Windows. > -- > 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/ > > One issue that comes to mind is your environment. Have you tried running other x-clients such as xterm or xclock? Is the $DISPLAY environmental variable set? Cygwin is a tremendously useful bridge between Windows and Linux but it's often frustrating to use. -- 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/ From scott@ohelp.com Sat Dec 5 02:25:00 2009 From: scott@ohelp.com (Scott Fordin) Date: Sat, 05 Dec 2009 02:25:00 -0000 Subject: how do I get help if I can't figure out how to do anything? In-Reply-To: <4B19BC7E.9060008@comcast.net> References: <4B192052.6000808@comcast.net> <4B19BC7E.9060008@comcast.net> Message-ID: <4B19C4AA.4070402@ohelp.com> Have you tried starting the Cygwin X Server with the -ac option to disable access control? Scott Gene C. Ruzicka wrote: > Wendel Dean Renner wrote: >> Do you have a list of consultants? And it is not like I am ignorant of >> computers. I write c++ code. Without help, who is going to be able to >> use anything provided? >> >> Have managed to compile and link a Open GL, X/Motif program (using >> lesstif) and >> get Error: Can't open display. >> >> Need to be able to run program remotely on a ubuntu system. I can't >> get beyond connection refused. >> >> Ran xstartwin.bat and lost control c - control V on Windows. -- >> 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/ >> >> > One issue that comes to mind is your environment. Have you tried running > other x-clients such > as xterm or xclock? Is the $DISPLAY environmental variable set? > Cygwin is a tremendously useful bridge between Windows and Linux but > it's often frustrating to > use. > > > > -- > 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/ > -- 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/ From jjreisert@alum.mit.edu Sat Dec 5 04:46:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Sat, 05 Dec 2009 04:46:00 -0000 Subject: Can't start Xwin server using latest Cygwin 1.7, Xorg server, etc. Message-ID: <4B19E5A0.3010601@alum.mit.edu> I'm having problems again getting the X server to start from startxwin.bat. My environment contains: LANG=C LC_TIME=C Here are parts of my environment: base-cygwin 2.0-1 OK cygrunsrv 1.34-1 OK cygutils 1.4.1-2 OK cygwin 1.7.0-68 OK cygwin-doc 1.5-1 OK emacs-X11 23.1-10 OK expat 2.0.1-1 OK font-adobe-dpi75 1.0.1-1 OK font-alias 1.0.2-1 OK font-daewoo-misc 1.0.1-1 OK font-encodings 1.0.3-1 OK font-isas-misc 1.0.1-1 OK font-jis-misc 1.0.1-1 OK font-misc-misc 1.1.0-1 OK gettext 0.17-11 OK libexpat1 2.0.1-1 OK libexpat1-devel 2.0.1-1 OK libpixman1_0 0.16.2-1 OK libX11_6 1.3.2-2 OK libXau6 1.0.5-1 OK libXaw3d7 1.5D-8 OK libXaw7 1.0.7-1 OK libxcb1 1.4-2 OK libXdmcp6 1.0.3-1 OK libXext6 1.1.1-1 OK libXft2 2.1.14-1 OK libxkbfile1 1.0.6-1 OK libxml2 2.7.4-1 OK libXmu6 1.0.5-1 OK libXmuu1 1.0.5-1 OK libXpm4 3.5.8-1 OK libXrender1 0.9.5-1 OK libXt6 1.0.7-1 OK lynx 2.8.5-4 OK run 1.1.12-11 OK run2 0.3.2-1 OK texinfo 4.13-3 OK util-linux 2.14.1-1 OK xauth 1.0.4-1 OK xcursor-themes 1.0.2-1 OK xemacs-emacs-common 21.4.22-1 OK xinit 1.2.0-1 OK xkbcomp 1.1.1-1 OK xkeyboard-config 1.7-1 OK xmodmap 1.0.4-1 OK xorg-server 1.7.1-3 OK xrdb 1.0.6-1 OK xterm 251-1 OK Here is the log file: d:\cygwin\bin>startxwin.bat Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard -silent-dup-error winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /cygdrive/d/Home/.XWinrc LoadPreferences: Done parsing the configuration file... winGetDisplay: DISPLAY=:0.0 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 00000007 winSetEngine - Multi Window or Rootless => ShadowGDI winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello Screen 0 added at XINERAMA coordinate (0,0). winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! winPointerWarpCursor - Discarding first warp: 840 525 (--) 16 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) Using preset keyboard for "English (USA)" (409), type "4" Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" winInitMultiWindowWM - pthread_mutex_lock () returned. winProcEstablishConnection - Hello winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winInitMultiWindowWM - pthread_mutex_unlock () returned. winGetDisplay: DISPLAY=:0.0 winMultiWindowXMsgProc - pthread_mutex_lock () returned. winGetDisplay: DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 d:\cygwin\bin>winMultiWindowXMsgProc - pthread_mutex_unlock () returned. winInitMultiWindowWM - DISPLAY=:0.0 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information winPrefsLoadPreferences: /cygdrive/d/Home/.XWinrc LoadPreferences: Done parsing the configuration file... winGetDisplay: DISPLAY=:0.0 winDetectSupportedEngines - Windows NT/2000/XP winDetectSupportedEngines - DirectDraw installed winDetectSupportedEngines - DirectDraw4 installed winDetectSupportedEngines - Returning, supported engines 00000007 winSetEngine - Multi Window or Rootless => ShadowGDI winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 null screen fn ReparentWindow null screen fn RestackWindow InitQueue - Calling pthread_mutex_init InitQueue - pthread_mutex_init returned InitQueue - Calling pthread_cond_init InitQueue - pthread_cond_init returned winInitMultiWindowWM - Hello winMultiWindowXMsgProc - Hello Screen 0 added at XINERAMA coordinate (0,0). winInitMultiWindowWM - Calling pthread_mutex_lock () winMultiWindowXMsgProc - Calling pthread_mutex_lock () MIT-SHM extension disabled due to lack of kernel support winGetDisplay: DISPLAY=:0.0 winClipboardProc - Could not open display, try: 1, sleeping: 4 winMultiWindowXMsgProc - DISPLAY=:0.0 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel winInitMultiWindowWM - Could not open display, try: 1, sleeping: 5 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! (--) 16 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) winConfigKeyboard - Layout: "00000409" (00000409) (--) Using preset keyboard for "English (USA)" (409), type "4" Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" winInitMultiWindowWM - pthread_mutex_lock () returned. _XSERVTranswinInitMultiWindowWM - pthread_mutex_unlock () returned. winMultiWindowXMsgProc - pthread_mutex_lock () returned. SocketUNIXAccept: accept() failed winMultiWindowXMsgProc - pthread_mutex_unlock () returned. _XSERVTransSocketUNIXAccept: accept() failed winInitClipboard () winProcEstablishConnection - winInitClipboard returned. winClipboardProc - Hello DetectUnicodeSupport - Windows NT/2000/XP winClipboardProc - XOpenDisplay () returned and successfully opened the display. winGetDisplay: DISPLAY=:0.0 winGetDisplay: DISPLAY=:0.0 winGetDisplay: DISPLAY=:0.0 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winInitMultiWindowWM - DISPLAY=:0.0 winMultiWindowXMsgProc - DISPLAY=:0.0 winClipboardProc - DISPLAY=:0.0 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. winClipboardProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. winMultiWindowXMsgProc - another window manager is running. Exiting. winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winClipboardIOErrorHandler! winClipboardIOErrorHandler! winInitMultiWindowWM - Could not open display, try: 2, sleeping: 5 winDeinitMultiWindowWM - Noting shutdown in progress -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From frederic.bron@m4x.org Sat Dec 5 09:03:00 2009 From: frederic.bron@m4x.org (=?UTF-8?B?RnLDqWTDqXJpYyBCcm9u?=) Date: Sat, 05 Dec 2009 09:03:00 -0000 Subject: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-68 In-Reply-To: References: Message-ID: > I just uploaded a new Cygwin 1.7 test release, 1.7.0-68. Installed this version and cannot start Xwin anymore. Here is the content of /var/log/XWin.0.log: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1920 h 1200 winInitializeDefaultScreens - Returning 2009-12-04 20:36:21 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2009-12-04 20:36:21 _XSERVTransOpen: transport open failed for inet6/VOR-CRV-01660:0 2009-12-04 20:36:21 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2009-12-04 20:36:22 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-12-04 20:36:22 (II) xorg.conf is not supported 2009-12-04 20:36:22 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-12-04 20:36:22 winPrefsLoadPreferences: /cygdrive/d/Documents/.XWinrc 2009-12-04 20:36:22 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:22 winDetectSupportedEngines - Windows NT/2000/XP 2009-12-04 20:36:22 winDetectSupportedEngines - DirectDraw installed 2009-12-04 20:36:22 winDetectSupportedEngines - DirectDraw4 installed 2009-12-04 20:36:22 winDetectSupportedEngines - Returning, supported engines 00000007 2009-12-04 20:36:22 winSetEngine - Multi Window or Rootless => ShadowGDI 2009-12-04 20:36:22 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-12-04 20:36:22 winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1200 depth: 32 2009-12-04 20:36:22 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff 2009-12-04 20:36:22 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 2009-12-04 20:36:22 null screen fn ReparentWindow 2009-12-04 20:36:22 null screen fn RestackWindow 2009-12-04 20:36:22 InitQueue - Calling pthread_mutex_init 2009-12-04 20:36:22 InitQueue - pthread_mutex_init returned 2009-12-04 20:36:22 InitQueue - Calling pthread_cond_init 2009-12-04 20:36:22 InitQueue - pthread_cond_init returned 2009-12-04 20:36:22 winInitMultiWindowWM - Hello 2009-12-04 20:36:22 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-12-04 20:36:22 Screen 0 added at XINERAMA coordinate (0,0). 2009-12-04 20:36:22 winMultiWindowXMsgProc - Hello 2009-12-04 20:36:22 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-12-04 20:36:22 MIT-SHM extension disabled due to lack of kernel support 2009-12-04 20:36:22 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-12-04 20:36:22 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-12-04 20:36:22 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-12-04 20:36:23 winPointerWarpCursor - Discarding first warp: 960 600 2009-12-04 20:36:23 (--) 3 mouse buttons found 2009-12-04 20:36:23 (--) Setting autorepeat to delay=500, rate=31 2009-12-04 20:36:23 (--) winConfigKeyboard - Layout: "0000040C" (0000040c) 2009-12-04 20:36:23 (--) Using preset keyboard for "French (Standard)" (40c), type "4" 2009-12-04 20:36:23 Rules = "base" Model = "pc105" Layout = "fr" Variant = "none" Options = "none" 2009-12-04 20:36:24 winInitMultiWindowWM - pthread_mutex_lock () returned. 2009-12-04 20:36:24 winProcEstablishConnection - Hello 2009-12-04 20:36:24 winInitClipboard () 2009-12-04 20:36:24 winClipboardProc - Hello 2009-12-04 20:36:24 winProcEstablishConnection - winInitClipboard returned. 2009-12-04 20:36:24 DetectUnicodeSupport - Windows NT/2000/XP 2009-12-04 20:36:24 winInitMultiWindowWM - pthread_mutex_unlock () returned. 2009-12-04 20:36:24 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:24 winMultiWindowXMsgProc - pthread_mutex_lock () returned. 2009-12-04 20:36:24 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:24 winClipboardProc - DISPLAY=:0.0 2009-12-04 20:36:24 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. 2009-12-04 20:36:24 winInitMultiWindowWM - DISPLAY=:0.0 2009-12-04 20:36:24 (II) xorg.conf is not supported 2009-12-04 20:36:24 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-12-04 20:36:24 winPrefsLoadPreferences: /cygdrive/d/Documents/.XWinrc 2009-12-04 20:36:24 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:24 winDetectSupportedEngines - Windows NT/2000/XP 2009-12-04 20:36:24 winDetectSupportedEngines - DirectDraw installed 2009-12-04 20:36:24 winDetectSupportedEngines - DirectDraw4 installed 2009-12-04 20:36:24 winDetectSupportedEngines - Returning, supported engines 00000007 2009-12-04 20:36:24 winSetEngine - Multi Window or Rootless => ShadowGDI 2009-12-04 20:36:24 winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1200 depth: 32 2009-12-04 20:36:24 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff 2009-12-04 20:36:24 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 2009-12-04 20:36:24 null screen fn ReparentWindow 2009-12-04 20:36:24 null screen fn RestackWindow 2009-12-04 20:36:24 InitQueue - Calling pthread_mutex_init 2009-12-04 20:36:24 InitQueue - pthread_mutex_init returned 2009-12-04 20:36:24 InitQueue - Calling pthread_cond_init 2009-12-04 20:36:24 InitQueue - pthread_cond_init returned 2009-12-04 20:36:24 winInitMultiWindowWM - Hello 2009-12-04 20:36:24 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-12-04 20:36:24 winMultiWindowXMsgProc - Hello 2009-12-04 20:36:24 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-12-04 20:36:24 Screen 0 added at XINERAMA coordinate (0,0). 2009-12-04 20:36:24 MIT-SHM extension disabled due to lack of kernel support 2009-12-04 20:36:24 winClipboardProc - Could not open display, try: 1, sleeping: 4 2009-12-04 20:36:24 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:24 winMultiWindowXMsgProc - DISPLAY=:0.0 2009-12-04 20:36:24 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-12-04 20:36:24 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-12-04 20:36:24 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-12-04 20:36:25 (--) 3 mouse buttons found 2009-12-04 20:36:25 (--) Setting autorepeat to delay=500, rate=31 2009-12-04 20:36:25 (--) winConfigKeyboard - Layout: "0000040C" (0000040c) 2009-12-04 20:36:25 (--) Using preset keyboard for "French (Standard)" (40c), type "4" 2009-12-04 20:36:25 Rules = "base" Model = "pc105" Layout = "fr" Variant = "none" Options = "none" 2009-12-04 20:36:26 winInitMultiWindowWM - pthread_mutex_lock () returned. 2009-12-04 20:36:26 winInitMultiWindowWM - pthread_mutex_unlock () returned. 2009-12-04 20:36:26 winMultiWindowXMsgProc - pthread_mutex_lock () returned. 2009-12-04 20:36:26 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. 2009-12-04 20:36:26 _XSERVTransSocketUNIXAccept: accept() failed 2009-12-04 20:36:26 winInitClipboard () 2009-12-04 20:36:26 winClipboardProc - Hello 2009-12-04 20:36:26 winProcEstablishConnection - winInitClipboard returned. 2009-12-04 20:36:26 DetectUnicodeSupport - Windows NT/2000/XP 2009-12-04 20:36:26 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. 2009-12-04 20:36:26 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:26 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:26 winInitMultiWindowWM - DISPLAY=:0.0 2009-12-04 20:36:26 winMultiWindowXMsgProc - DISPLAY=:0.0 2009-12-04 20:36:26 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-04 20:36:26 winGetDisplay: DISPLAY=:0.0 2009-12-04 20:36:26 winClipboardProc - DISPLAY=:0.0 2009-12-04 20:36:26 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-04 20:36:26 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. 2009-12-04 20:36:26 winMultiWindowXMsgProc - another window manager is running. ?Exiting. 2009-12-04 20:36:26 winClipboardIOErrorHandler! 2009-12-04 20:36:26 winClipboardProc - setjmp returned for IO Error Handler. 2009-12-04 20:36:26 Segmentation fault at address 0xfb8 2009-12-04 20:36:26 Fatal server error: 2009-12-04 20:36:26 Caught signal 11 (Segmentation fault). Server aborting 2009-12-04 20:36:26 -- 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/ From Kamal.Benslama@uregina.ca Sat Dec 5 23:49:00 2009 From: Kamal.Benslama@uregina.ca (Kamal Benslama) Date: Sat, 05 Dec 2009 23:49:00 -0000 Subject: error with startx Message-ID: <4B1A9D17020000340029B617@gw004.cc.uregina.ca> Hi, I installed cygwin with statx then I get the following error: /usr/bin/X:0-auth /home/kamal.serveauth.6444 any idea? Thanks Kamal Kamal Benslama Physics Department University of Regina Tel:306-585-5384 fax:306-585-5659 http://uregina.ca/~benslamk -- 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/ From wgweis@sbcglobal.net Sun Dec 6 00:33:00 2009 From: wgweis@sbcglobal.net (wgweis@sbcglobal.net) Date: Sun, 06 Dec 2009 00:33:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? References: <4AEAEEAB.2030009@cornell.edu> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D8860EE@mailserver.metatv-ds.metatv.com> Message-ID: <005e01ca760b$c0e93ff0$4401a8c0@BANDIT> Hi Mike: Sorry to take a bit of time to get back to you. I am attaching the files you requested. I am not familar with the cygwin x server log, but it looks like *that* starts up. It's just that xterm cannot connect. You mentioned that the server listenens on 0.0.0.0. You mean a port? I'm asking because what I have noticed about Windows 7 Home Edition is that even though I have created a user for myself with administrative priveleges, unless I tell the OS that I want to run a program as the administrator it will default to the privileges for an ordinary user. I don't know a way to turn this off, yet. So, is it possible that the port that the cygwin-x server is listening on belongs to the administrator and the xterm session when it is launched cannot write to this port as a result? I tried running DOS cmd as the administrator btw, with no better results. thanks, George ----- Original Message ----- From: "Mike Ayers" To: Sent: Thursday, December 03, 2009 2:18 PM Subject: RE: cygwin-x xterm not compatible with windows 7? >> From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- >> owner@cygwin.com] On Behalf Of wgweis@sbcglobal.net >> Sent: Thursday, December 03, 2009 1:47 PM > >> I sent this post earlier this week and have not received any >> replies. >> If this is the wrong place to post this, >> please let me know where I should. > > This is the place, but I don't know how many of us have tried using 64 bit > Windows 7 yet. I know I haven't, but I'll offer advice anyway. (What's > the smiley for "evil leer"?) > >> I just bought a new PC with windows 7 64 bit, build number 7600, >> version 6.1. >> I downloaded a fresh install of cygwin and cannot get cygwin-x xterm >> running. Cygwin version is 1.7.0(0.218/5/3) >> >> I tried running the cygwin-x XWin Server shortcut command line from a >> cmd >> window to get the error output: >> >> C:\cygwin\bin\run.exe /usr/bin/startxwin.bat >> >> and see this: >> >> "/usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0" >> >> this seems to be coming from this command in the batch file: >> :\Users\princess>C:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e >> /usr/bin/bash - >> >> usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 > > ...implying that the server didn't start. > >> If I kill the server and run the script again, I'll get a >> STATUS_ACCESS_VIOLATION error, indicating >> some sort of shared memory corruption. I then have to restart the PC. >> I >> checked to see if there >> was more than one cygwin1.dll in response to earlier posts about this >> error >> and there is only one. >> >> I tried turning off the windows firewall. That helps in other ways, >> because >> other cygwin network >> utilities, such as nslookup were blocked until I did that. >> >> I tried changing the display from 127.0.0.1 to the IP address of the >> machine. > > I believe the X server listens on 0.0.0.0, so that shouldn't make a > difference. > >> Basically, I have a fresh machine with windows 7 and a fresh install of >> cygwin and I can't get >> xterm to work. Anyone have any ideas? Or is this just a windows 7 >> thing, >> and I'll have to give >> up on cygwin-x for a while? >> >> BTW, other shortcuts in the cygwin-x start folder work, such as bitmap >> and >> xcalc, just not the >> Xwin server and xterm. > > How can xcalc work if the server doesn't start?! > > Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r > >cygcheck.out) as attachments in the hope that they will inspire. > > > Thanks, > > Mike > > -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 4206 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 196453 bytes Desc: not available URL: -------------- next part -------------- -- 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/ From yselkowitz@users.sourceforge.net Sun Dec 6 01:02:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Sun, 06 Dec 2009 01:02:00 -0000 Subject: 1.7 - what's the right way to start X? In-Reply-To: <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> <4B182ECF.1040805@cygwin.com> <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> Message-ID: <4B1B028C.2000407@users.sourceforge.net> On 04/12/2009 10:12, Fredrik Staxeng wrote: > I have seen this problem before, and the solution was to run rebaseall, > which broke emacs, and then reinstall libncurses to fix emacs. > > Is this the way to do it? > Will it still break emacs? > Will other things break? > Will it break again when updating cygwin? This was only true with the old version of emacs which depended on libncurses7, as the latter was not rebase-able. This is no longer an issue with the latest version of emacs; just rebase and you should be fine. Yaakov Cygwin/X -- 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/ From fstx+u@update.uu.se Mon Dec 7 09:43:00 2009 From: fstx+u@update.uu.se (Fredrik Staxeng) Date: Mon, 07 Dec 2009 09:43:00 -0000 Subject: 1.7 - what's the right way to start X? References: <1mzl5zsr54.fsf@Psilocybe.Update.UU.SE> <4B182ECF.1040805@cygwin.com> <1miqcmsoph.fsf@Psilocybe.Update.UU.SE> <4B1B028C.2000407@users.sourceforge.net> Message-ID: <1mljhf2k87.fsf@Psilocybe.Update.UU.SE> "Yaakov (Cygwin/X)" writes: >On 04/12/2009 10:12, Fredrik Staxeng wrote: >> I have seen this problem before, and the solution was to run rebaseall, >> which broke emacs, and then reinstall libncurses to fix emacs. >> >> Is this the way to do it? >> Will it still break emacs? >> Will other things break? >> Will it break again when updating cygwin? > >This was only true with the old version of emacs which depended on >libncurses7, as the latter was not rebase-able. This is no longer an >issue with the latest version of emacs; just rebase and you should be >fine. Thanks. I just upgraded to the version released this Friday, and I haven't seen the message yet. But if I do, I know what to do. -- Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/ From kbrown@cornell.edu Mon Dec 7 16:06:00 2009 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 07 Dec 2009 16:06:00 -0000 Subject: GSlice problem with emacs Gtk+ build Message-ID: <4B1D2800.4060909@cornell.edu> There's been a longstanding problem with emacs if it is configured to use Gtk+ in Cygwin. The relevant threads begin here: http://cygwin.com/ml/cygwin/2006-07/threads.html#00823 http://cygwin.com/ml/cygwin/2007-02/threads.html#00469 http://cygwin.com/ml/cygwin/2007-02/threads.html#00503 Briefly, the problem is the following (quoted from the emacs etc/PROBLEMS file): "Emacs supplies its own malloc, but glib (part of Gtk+) calls memalign and on Cygwin, that becomes the Cygwin supplied memalign. As malloc is not the Cygwin malloc, the Cygwin memalign always returns ENOSYS." The symptom is that emacs crashes with an error message like the following: ***MEMORY-ERROR***: [2428]: GSlice: failed to allocate 120 bytes (alignment: 128): Function not implemented Fatal error (6)Aborted (core dumped) There's a known workaround, which is to set G_SLICE=always-malloc before starting emacs. As emacs maintainer, I've been reluctant to provide the Gtk+ version of emacs, because I don't want to answer hundreds of emails telling people about the workaround. I could supply a wrapper script that sets G_SLICE, but I'm still afraid that would cause a lot of confusion; I suspect many people are in the habit of calling emacs-X11.exe directly. I have therefore configured the emacs-X11 package to use Xaw instead of Gtk+. But Gtk+ is really much nicer, and I would like to be able to provide an emacs-X11 that uses it. At the time this was first discussed, Cygwin did not have an X maintainer. Now that we have Jon and Yaakov actively providing Cygwin/X support, I wonder if it would be possible to revisit the issue and try to fix the problem. For example, might it be as simple as patching the Cygwin port of glib to achieve the same effect as setting G_SLICE=always-malloc? Ken -- 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/ From yselkowitz@users.sourceforge.net Mon Dec 7 19:13:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Mon, 07 Dec 2009 19:13:00 -0000 Subject: GSlice problem with emacs Gtk+ build In-Reply-To: <4B1D2800.4060909@cornell.edu> References: <4B1D2800.4060909@cornell.edu> Message-ID: <4B1D53C7.5060703@users.sourceforge.net> On 07/12/2009 10:06, Ken Brown wrote: > There's a known workaround, which is to set G_SLICE=always-malloc before > starting emacs. As emacs maintainer, I've been reluctant to provide the > Gtk+ version of emacs, because I don't want to answer hundreds of emails > telling people about the workaround. I could supply a wrapper script > that sets G_SLICE, but I'm still afraid that would cause a lot of > confusion; I suspect many people are in the habit of calling > emacs-X11.exe directly. I have therefore configured the emacs-X11 > package to use Xaw instead of Gtk+. But Gtk+ is really much nicer, and I > would like to be able to provide an emacs-X11 that uses it. What about adding to the beginning of main(): #ifdef __CYGWIN__ setenv("G_SLICE", "always-malloc", 1); #endif Yaakov Cygwin/X -- 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/ From kbrown@cornell.edu Mon Dec 7 22:18:00 2009 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 07 Dec 2009 22:18:00 -0000 Subject: GSlice problem with emacs Gtk+ build In-Reply-To: <4B1D53C7.5060703@users.sourceforge.net> References: <4B1D2800.4060909@cornell.edu> <4B1D53C7.5060703@users.sourceforge.net> Message-ID: <4B1D7F17.8090901@cornell.edu> On 12/7/2009 2:13 PM, Yaakov (Cygwin/X) wrote: > On 07/12/2009 10:06, Ken Brown wrote: >> There's a known workaround, which is to set G_SLICE=always-malloc before >> starting emacs. As emacs maintainer, I've been reluctant to provide the >> Gtk+ version of emacs, because I don't want to answer hundreds of emails >> telling people about the workaround. I could supply a wrapper script >> that sets G_SLICE, but I'm still afraid that would cause a lot of >> confusion; I suspect many people are in the habit of calling >> emacs-X11.exe directly. I have therefore configured the emacs-X11 >> package to use Xaw instead of Gtk+. But Gtk+ is really much nicer, and I >> would like to be able to provide an emacs-X11 that uses it. > > What about adding to the beginning of main(): > > #ifdef __CYGWIN__ > setenv("G_SLICE", "always-malloc", 1); > #endif Thanks, Yaakov! I was looking for more complicated solutions and never thought of the easy one. That fixes it. Ken -- 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/ From mike_ayers@tvworks.com Mon Dec 7 23:13:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Mon, 07 Dec 2009 23:13:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? In-Reply-To: <005e01ca760b$c0e93ff0$4401a8c0@BANDIT> References: <4AEAEEAB.2030009@cornell.edu> <4B0B4728.40300@cwilson.fastmail.fm> <6BA35940945A4A9D87019C6253F94814@MultiOcke> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D8860EE@mailserver.metatv-ds.metatv.com> <005e01ca760b$c0e9 3ff0$4401a8c0@BANDIT> Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D886B95@mailserver.metatv-ds.metatv.com> > From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- > owner@cygwin.com] On Behalf Of wgweis@sbcglobal.net > Sent: Saturday, December 05, 2009 4:34 PM > Sorry to take a bit of time to get back to you. I am attaching the > files you requested. I am not familar with the cygwin x server log, > but it looks like *that* starts up. It's just that xterm cannot > connect. That does appear to be the case. > You mentioned that the server listenens on 0.0.0.0. You mean a > port? No. "0.0.0.0" is the broadcast IP address. When a server listens on that address, it listens to every interface on the computer, so it wouldn't matter if you tried connecting to localhost or the external address (i.e. leave your DISPLAY pointing to 127.0.0.1:0). > I'm asking because what I have noticed about Windows 7 > Home Edition is that even though I have created a user for myself with > administrative priveleges, unless I tell the OS that I want to > run a program as the administrator it will default to the privileges > for an > ordinary user. I don't know a way to turn this off, yet. I don't believe there is a workaround, unfortunately. Vista has the same issue. > So, is it possible that the port that the cygwin-x server is listening > on > belongs to the administrator and the xterm session when it is > launched cannot write to this port as a result? No, there are no ownership issues sending packets to ports. My suspicion would be that the non-administrator X server process would not be allowed to open the listeneing port, or be firewalled off, but neither can be the case if xcalc works. Have you tried running xterm from a cygwin console after the server has started? > I tried running DOS > cmd as > the administrator btw, with no better results. Which DOS command? Thanks, Mike From reply-to-list-only-lh-x@cygwin.com Mon Dec 7 23:55:00 2009 From: reply-to-list-only-lh-x@cygwin.com (Larry Hall (Cygwin X)) Date: Mon, 07 Dec 2009 23:55:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? In-Reply-To: <83E753BE7B6A324ABB336245BAF1DAAC0D886B95@mailserver.metatv-ds.metatv.com> References: <4AEAEEAB.2030009@cornell.edu> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D8860EE@mailserver.metatv-ds.metatv.com> <005e01ca760b$c0e9 3ff0$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D886B95@mailserver.metatv-ds.metatv.com> Message-ID: <4B1D9568.5010506@cygwin.com> On 12/07/2009 06:13 PM, Mike Ayers wrote: >> I'm asking because what I have noticed about Windows 7 >> > Home Edition is that even though I have created a user for myself with >> > administrative priveleges, unless I tell the OS that I want to >> > run a program as the administrator it will default to the privileges >> > for an >> > ordinary user. I don't know a way to turn this off, yet. > I don't believe there is a workaround, unfortunately. Vista has the same issue. > Isn't this just UAC? You can turn that off for a user if you want. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- 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/ From feig@msu.edu Tue Dec 8 13:46:00 2009 From: feig@msu.edu (Michael Feig) Date: Tue, 08 Dec 2009 13:46:00 -0000 Subject: font issues on Windows 7? Message-ID: <004e01ca780c$caf624b0$60e26e10$@msu.edu> Hi! I have a problem with spurious pixels showing up in my xterm window with the latest 1.7-beta on Windows 7. I open a new xterm (after starting Xwin in multiwindow mode) with: xterm -sb -sl 1000 +tb -fg white -bg black -font -adobe-courier-bold-r-normal--20-140-100-100-m-110-iso8859-1 Initially, all is well, but eventually I get more and more spurious pixel-size dots on the left-most line of a character box. Usually, this affects only the first column, but I have seen it in other columns as well. It's a bit hard to describe but the net effect is that after using a window for a while there is effectively an irregularly dotted line between the left scrollbar and the first character column, and typically the prompt '$' will have a few dots on the left side of the character. It may not show up with a white-background window and it's not really a big deal but it does get annoying after a while. I never seen this problem before when I used previous versions of Cygwin/X on Windows XP. Does anybody else have a similar experience? Thanks, Michael. -- 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/ From gbarrick@walsh.edu Tue Dec 8 15:10:00 2009 From: gbarrick@walsh.edu (George Barrick) Date: Tue, 08 Dec 2009 15:10:00 -0000 Subject: Can't start Xwin server using latest Cygwin 1.7, Xorg server, etc. Message-ID: <4B30AD0BED19E842AAE88DC39736493123FDC71F81@mail3.walsh.edu> 2009.12.08.13:41:22 UT Hi Jim, I've been having the same difficulty. I start Xwin via the startxwin.bat script, my xterm is then spawned, but crashes taking Xwin with it. I thought that I had solved the problem last week when I read on the regular cygwin newsgroup about setting the CGWIN and LANG environment variables. I now have things set up as: CYGWIN tty notitle glob DISPLAY 127.0.0.1:0.0 HOME E:\gbarrick LANG en_US.UTF-8 I have not seen any discussion of the LC_TIME variable, and had the impression from several threads that my setting of LANG would help with this problem. The problem recurred a few days later, and I kind of gave up, deciding to wait for the next cygwin-1.7 dll. When I got the cygwin-1.7.0-68, my xterm worked again, but then the next morning it was crashing on start-up as before in a situation where I had installed nothing that was new. I tried the 'rebaseall' trick, as my reading hinted that this might alleviate the problem: D:\cygwin\bin> ash.exe $ PATH=. rebaseall -v And I got no change in the behavior. I've appended my startxwin.bat file, and some abbreviated versions of my XWin.0.log file and the output of cygcheck -v to the end of this message. I'm pretty certain that I have no other window managers running when I try to start XWin, as I visit the windows task manager and kill off any orphaned xwin and bash processes that I see (ninety-nine percent are bash). I've run the experiment where I do not use the -multiwindow option of XWin, and it _does_ work under those circumstances, but that configuration really cramps my work-flow. My alternative over the past few days has been to use the rxvt-native command window. Like you, I'm hoping that better informed folks will read this. George gbarrick@walsh.edu @echo off SET DISPLAY=127.0.0.1:0.0 if defined CYGWIN_ROOT goto :OK set CYGWIN_ROOT=%~dp0\.. :OK SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET RUNTWO=%CYGWIN_ROOT%\bin\run2 -p /usr/bin SET PATH=%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error" REM %RUN% bash -l -c "XWin -multiwindow -silent-dup-error" REM %RUN% bash -l -c "XWin -silent-dup-error" REM %RUNTWO% /usr/bin/XWin.xml %RUN% checkX -wait -d %DISPLAY% -t 12 REM %RUN% xterm -e /usr/bin/bash -l %RUN% xterm -rw -sb -rightbar -geometry 128x44+72+60 -e /usr/bin/bash -l 2009-12-08 07:50:44 winClipboardProc - DISPLAY=:0.0 2009-12-08 07:50:44 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:44 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:44 winClipboardProc - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:47 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:47 winMultiWindowXMsgProc - another window manager is running. Exiting. 2009-12-08 07:50:47 winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. 2009-12-08 07:50:47 winClipboardProc - XDestroyWindow succeeded. 2009-12-08 07:50:47 winClipboardIOErrorHandler! Cygwin Package Information Package Version Status _update-info-dir 00834-1 OK base-cygwin 2.0-1 OK base-files 3.9-2 OK base-passwd 3.1-1 OK bash 3.2.49-23 OK bc 1.06-2 OK binutils 2.19.51-1 OK bzip2 1.0.5-10 OK cdrecord 1.1.7.1-1 OK coreutils 7.0-2 OK cygrunsrv 1.34-1 OK cygutils 1.4.1-2 OK cygwin 1.7.0-68 OK cygwin-doc 1.5-1 OK font-adobe-dpi75 1.0.1-1 OK font-alias 1.0.2-1 OK font-daewoo-misc 1.0.1-1 OK font-encodings 1.0.3-1 OK font-isas-misc 1.0.1-1 OK font-jis-misc 1.0.1-1 OK font-misc-misc 1.1.0-1 OK font-xfree86-type1 1.0.2-1 OK fontconfig 2.7.3-1 OK mkfontdir 1.0.5-1 OK mkfontscale 1.0.7-1 OK ncurses 5.7-16 OK openssh 5.3p1-1 OK openssl 0.9.8l-2 OK rebase 3.0.1-1 OK run 1.1.12-11 OK run2 0.3.2-1 OK rxvt 20050409-21 OK tar 1.22-1 OK termcap 5.7_20091114-13 OK terminfo 5.7_20091114-13 OK terminfo0 5.5_20061104-11 OK util-linux 2.14.1-1 OK w32api 3.14-1 OK wget 1.11.4-4 OK which 2.20-2 OK wodim 1.1.7.1-1 OK X-start-menu-icons 1.0.4-1 OK xauth 1.0.4-1 OK xcursor-themes 1.0.2-1 OK xfig 3.2.4-7 Incomplete xfig-lib 3.2.4-7 OK xfontsel 1.0.2-2 OK xinit 1.2.0-1 OK xkbcomp 1.1.1-1 OK xkeyboard-config 1.7-1 OK xlsfonts 1.0.2-1 OK xmodmap 1.0.4-1 OK xorg-scripts 1.0.1-1 OK xorg-server 1.7.1-3 OK xrdb 1.0.6-1 OK xterm 251-1 OK xwininfo 1.0.5-1 OK xz 4.999.9beta-10 OK -- 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/ From wgweis@sbcglobal.net Tue Dec 8 22:06:00 2009 From: wgweis@sbcglobal.net (wgweis@sbcglobal.net) Date: Tue, 08 Dec 2009 22:06:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? References: <4AEAEEAB.2030009@cornell.edu> <4B0D2EB3.6020102@cwilson.fastmail.fm> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D8860EE@mailserver.metatv-ds.metatv.com> <005e01ca760b$c0e9 3ff0$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D886B95@mailserver.metatv-ds.metatv.com> <4B1D9568.5010506@cygwin.com> Message-ID: <007e01ca7852$9caee740$4401a8c0@BANDIT> I turned off UAC, or so I am told. The server seems to start up OK. But xterm cannot access the shared memory? I ran this from the Cygwin.bat and got this stack dump. Exception: STATUS_ACCESS_VIOLATION at eip=3D73693A^M eax=00CA9719 ebx=5C3D6F68 ecx=0028B98D edx=0000038D esi=3A485B45 edi=5C3D6D69^M ebp=68345B45 esp=0028BB60 program=C:\cygwin\bin\xterm.exe, pid 168, thread main^ M cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B^M Stack trace:^M Frame Function Args^M End of stack trace ~ ----- Original Message ----- From: "Larry Hall (Cygwin X)" To: Sent: Monday, December 07, 2009 3:53 PM Subject: Re: cygwin-x xterm not compatible with windows 7? > On 12/07/2009 06:13 PM, Mike Ayers wrote: >>> I'm asking because what I have noticed about Windows 7 >>> > Home Edition is that even though I have created a user for myself >>> > with >>> > administrative priveleges, unless I tell the OS that I want to >>> > run a program as the administrator it will default to the privileges >>> > for an >>> > ordinary user. I don't know a way to turn this off, yet. >> I don't believe there is a workaround, unfortunately. Vista has the same >> issue. >> > > Isn't this just UAC? You can turn that off for a user if you want. > > -- > Larry Hall http://www.rfk.com > RFK Partners, Inc. (508) 893-9779 - RFK Office > 216 Dalton Rd. (508) 893-9889 - FAX > Holliston, MA 01746 > > _____________________________________________________________________ > > A: Yes. > > Q: Are you sure? > >> A: Because it reverses the logical flow of conversation. > >>> Q: Why is top posting annoying in email? > > -- > 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/ > -- 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/ From gbarrick@walsh.edu Tue Dec 8 22:57:00 2009 From: gbarrick@walsh.edu (George Barrick) Date: Tue, 08 Dec 2009 22:57:00 -0000 Subject: Can't start Xwin server using latest Cygwin 1.7, Xorg server, etc. Message-ID: <4B30AD0BED19E842AAE88DC39736493123FDC71F84@mail3.walsh.edu> 2009.12.08.22:57:03 UT Hello cygwin-xfree folks, I found the solution to my problem. I was not reading far enough back into this news archive. In a thread from late November, Reid Thomson suggested to someone that he insert the command: sleep 5 between the Xwin startup and the xterm invocation in the startxwin.bat file. This worked for me. George gbarrick@walsh.edu "George Barrick" wrote in message news:<4B30AD0BED19E842AAE88DC39736493123FDC71F81@mail3.walsh.edu>... 2009.12.08.13:41:22 UT Hi Jim, I've been having the same difficulty. I start Xwin via the startxwin.bat script, my xterm is then spawned, but crashes taking Xwin with it. I thought that I had solved the problem last week when I read on the regular cygwin newsgroup about setting the CGWIN and LANG environment variables. I now have things set up as: CYGWIN tty notitle glob DISPLAY 127.0.0.1:0.0 HOME E:\gbarrick LANG en_US.UTF-8 I have not seen any discussion of the LC_TIME variable, and had the impression from several threads that my setting of LANG would help with this problem. The problem recurred a few days later, and I kind of gave up, deciding to wait for the next cygwin-1.7 dll. When I got the cygwin-1.7.0-68, my xterm worked again, but then the next morning it was crashing on start-up as before in a situation where I had installed nothing that was new. I tried the 'rebaseall' trick, as my reading hinted that this might alleviate the problem: D:\cygwin\bin> ash.exe $ PATH=. rebaseall -v And I got no change in the behavior. I've appended my startxwin.bat file, and some abbreviated versions of my XWin.0.log file and the output of cygcheck -v to the end of this message. I'm pretty certain that I have no other window managers running when I try to start XWin, as I visit the windows task manager and kill off any orphaned xwin and bash processes that I see (ninety-nine percent are bash). I've run the experiment where I do not use the -multiwindow option of XWin, and it _does_ work under those circumstances, but that configuration really cramps my work-flow. My alternative over the past few days has been to use the rxvt-native command window. Like you, I'm hoping that better informed folks will read this. George gbarrick@walsh.edu @echo off SET DISPLAY=127.0.0.1:0.0 if defined CYGWIN_ROOT goto :OK set CYGWIN_ROOT=%~dp0\.. :OK SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET RUNTWO=%CYGWIN_ROOT%\bin\run2 -p /usr/bin SET PATH=%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error" REM %RUN% bash -l -c "XWin -multiwindow -silent-dup-error" REM %RUN% bash -l -c "XWin -silent-dup-error" REM %RUNTWO% /usr/bin/XWin.xml %RUN% checkX -wait -d %DISPLAY% -t 12 REM %RUN% xterm -e /usr/bin/bash -l %RUN% xterm -rw -sb -rightbar -geometry 128x44+72+60 -e /usr/bin/bash -l 2009-12-08 07:50:44 winClipboardProc - DISPLAY=:0.0 2009-12-08 07:50:44 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:44 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:44 winClipboardProc - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:47 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-08 07:50:47 winMultiWindowXMsgProc - another window manager is running. Exiting. 2009-12-08 07:50:47 winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. 2009-12-08 07:50:47 winClipboardProc - XDestroyWindow succeeded. 2009-12-08 07:50:47 winClipboardIOErrorHandler! Cygwin Package Information Package Version Status _update-info-dir 00834-1 OK base-cygwin 2.0-1 OK base-files 3.9-2 OK base-passwd 3.1-1 OK bash 3.2.49-23 OK bc 1.06-2 OK binutils 2.19.51-1 OK bzip2 1.0.5-10 OK cdrecord 1.1.7.1-1 OK coreutils 7.0-2 OK cygrunsrv 1.34-1 OK cygutils 1.4.1-2 OK cygwin 1.7.0-68 OK cygwin-doc 1.5-1 OK font-adobe-dpi75 1.0.1-1 OK font-alias 1.0.2-1 OK font-daewoo-misc 1.0.1-1 OK font-encodings 1.0.3-1 OK font-isas-misc 1.0.1-1 OK font-jis-misc 1.0.1-1 OK font-misc-misc 1.1.0-1 OK font-xfree86-type1 1.0.2-1 OK fontconfig 2.7.3-1 OK mkfontdir 1.0.5-1 OK mkfontscale 1.0.7-1 OK ncurses 5.7-16 OK openssh 5.3p1-1 OK openssl 0.9.8l-2 OK rebase 3.0.1-1 OK run 1.1.12-11 OK run2 0.3.2-1 OK rxvt 20050409-21 OK tar 1.22-1 OK termcap 5.7_20091114-13 OK terminfo 5.7_20091114-13 OK terminfo0 5.5_20061104-11 OK util-linux 2.14.1-1 OK w32api 3.14-1 OK wget 1.11.4-4 OK which 2.20-2 OK wodim 1.1.7.1-1 OK X-start-menu-icons 1.0.4-1 OK xauth 1.0.4-1 OK xcursor-themes 1.0.2-1 OK xfig 3.2.4-7 Incomplete xfig-lib 3.2.4-7 OK xfontsel 1.0.2-2 OK xinit 1.2.0-1 OK xkbcomp 1.1.1-1 OK xkeyboard-config 1.7-1 OK xlsfonts 1.0.2-1 OK xmodmap 1.0.4-1 OK xorg-scripts 1.0.1-1 OK xorg-server 1.7.1-3 OK xrdb 1.0.6-1 OK xterm 251-1 OK xwininfo 1.0.5-1 OK xz 4.999.9beta-10 OK -- 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/ ---------- -- 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/ From wgweis@sbcglobal.net Wed Dec 9 17:31:00 2009 From: wgweis@sbcglobal.net (wgweis@sbcglobal.net) Date: Wed, 09 Dec 2009 17:31:00 -0000 Subject: cygwin-x xterm not compatible with windows 7? Solution Found References: <4AEAEEAB.2030009@cornell.edu> <4B0E9679.5050108@cornell.edu> <270AA78168E41541833C52448F4F34AD1D16D2C4@VHAISHMSGJ2.vha.med.va.gov> <270AA78168E41541833C52448F4F34AD1D16D545@VHAISHMSGJ2.vha.med.va.gov> <3 4FC5A3DFA88402C87957FC903ED71A2@MultiOcke> <270AA78168E41541833C52448F4F34AD1D16D5E4@VHAISHMSGJ2.vha.med.va.gov > <64D542799A7246F4A7712FD0F65274D7@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B13A0@VHAISHMSGJ2.vha.med.va.gov> < 3A87660989894F8C82CE373AC8C8382F@MultiOcke> <270AA78168E41541833C52448F4F34AD1D2B1C41@VHAISHMSGJ2.vha.med.va.gov> <005001ca72b2$c4bebc60$4401a8c0@BANDIT> <016701ca746 2$1de95b50$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D8860EE@mailserver.metatv-ds.metatv.com> <005e01ca760b$c0e9 3ff0$4401a8c0@BANDIT> <83E753BE7B6A324ABB336245BAF1DAAC0D886B95@mailserver.metatv-ds.metatv.com> <4B1D9568.5010506@cygwin.com> <007e01ca7852$9caee740$4401a8c0@BANDIT> Message-ID: <003801ca78f5$6c4aea10$4401a8c0@BANDIT> Hi All: I fixed this problem. I was using the cygwin beta 1.7. I reinstalled cygwin using the last stable release, 1.5.25. I also had to add the "sleep 5" line to startxwin.bat and startxwin.sh. So, I guess this is a defect to log against the 1.7 beta: the xterm executable can't seem to connect to shared memory for windows 7, home edition. George ----- Original Message ----- From: To: Sent: Tuesday, December 08, 2009 2:05 PM Subject: Re: cygwin-x xterm not compatible with windows 7? >I turned off UAC, or so I am told. > > The server seems to start up OK. But xterm cannot access the shared > memory? I ran this from the Cygwin.bat and got this stack dump. > > > Exception: STATUS_ACCESS_VIOLATION at eip=3D73693A^M > eax=00CA9719 ebx=5C3D6F68 ecx=0028B98D edx=0000038D esi=3A485B45 > edi=5C3D6D69^M > ebp=68345B45 esp=0028BB60 program=C:\cygwin\bin\xterm.exe, pid 168, > thread main^ > M > cs=0023 ds=002B es=002B fs=0053 gs=002B ss=002B^M > Stack trace:^M > Frame Function Args^M > End of stack trace > ~ > > ----- Original Message ----- > From: "Larry Hall (Cygwin X)" > To: > Sent: Monday, December 07, 2009 3:53 PM > Subject: Re: cygwin-x xterm not compatible with windows 7? > > >> On 12/07/2009 06:13 PM, Mike Ayers wrote: >>>> I'm asking because what I have noticed about Windows 7 >>>> > Home Edition is that even though I have created a user for myself >>>> > with >>>> > administrative priveleges, unless I tell the OS that I want to >>>> > run a program as the administrator it will default to the privileges >>>> > for an >>>> > ordinary user. I don't know a way to turn this off, yet. >>> I don't believe there is a workaround, unfortunately. Vista has the >>> same issue. >>> >> >> Isn't this just UAC? You can turn that off for a user if you want. >> >> -- >> Larry Hall http://www.rfk.com >> RFK Partners, Inc. (508) 893-9779 - RFK Office >> 216 Dalton Rd. (508) 893-9889 - FAX >> Holliston, MA 01746 >> >> _____________________________________________________________________ >> >> A: Yes. >> > Q: Are you sure? >> >> A: Because it reverses the logical flow of conversation. >> >>> Q: Why is top posting annoying in email? >> >> -- >> 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/ >> > > > -- > 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/ > -- 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/ From mike_ayers@tvworks.com Wed Dec 9 18:42:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Wed, 09 Dec 2009 18:42:00 -0000 Subject: Note on 1.7 startxwin.bat Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0D9006D2@mailserver.metatv-ds.metatv.com> Just thought I'd throw this out for those of you having trouble starting the X server. I had been using the stock icon to launch the X server, which shortcuts to: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat This worked fine, except that the xterm did not appear. I could click the xterm icon, and that xterm would appear. After a little testing, I found that changing it to: C:\cygwin\bin\startxwin.bat ...caused server startup with the xterm. Setting the shortcut to run minimized mitigated the pop-and-poof console. HTH, Mike From jjreisert@alum.mit.edu Thu Dec 10 18:18:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Thu, 10 Dec 2009 18:18:00 -0000 Subject: Cut/paste in an xterm takes extraordinarily long time Message-ID: <806a89db0912101018o4f00c06eo1d8d85c2334348f6@mail.gmail.com> I'm having problems with copying text from a Windows application (Firefox) and pasting into Cygwin Emacs (23.1.1). I'm running Cygwin 1.7 (latest) and Xorg (latest). When pasting into Emacs, my mouse pointer changes to an hourglass, and after what seems like an eternity (10-30 seconds), the paste will finish, often times with the wrong text, rarely with the correct test. I am running RealVNC also. I remember several/many months back, there seems to be a cut/paste issue with Cygwin that was exacerbated by running VNC. Could that problem have returned? How can I help debug this? I've attached my cygcheck output. - Jim -- Jim Reisert AD1C, , http://www.ad1c.us -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 6647 bytes Desc: not available URL: -------------- next part -------------- -- 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/ From yselkowitz@users.sourceforge.net Thu Dec 10 21:13:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 10 Dec 2009 21:13:00 -0000 Subject: [ANNOUNCEMENT] Updated: openbox-3.4.7.2-10, New: obconf-2.0.3-10 Message-ID: The following package has been updated for Cygwin 1.7: *** openbox-3.4.7.2-10 *** obconf-2.0.3-10 (NEW) Openbox is a highly configurable, next generation window manager with extensive standards support. Obconf is a configuration manager for Openbox. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From jose_luis_fdez_diaz@yahoo.es Fri Dec 11 10:21:00 2009 From: jose_luis_fdez_diaz@yahoo.es (Jose Luis) Date: Fri, 11 Dec 2009 10:21:00 -0000 Subject: Newbie: idle doesn't run Message-ID: <26741790.post@talk.nabble.com> Hi, Below are the traces for "checkx" and "idle": $ checkx --debug=2 checkx.exe DEBUG: opt_location: 0 checkx.exe DEBUG: opt_loglevel: 8 checkx.exe DEBUG: opt_nogui : 0 checkx.exe DEBUG: opt_notty : 0 checkx.exe DEBUG: opt_timeout : 0.50 checkx.exe DEBUG: (adjust_path) path is : /usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:.:/usr/bin:/cygdrive/c/oracle/ora81/bin:/cygdrive/c/Archivos de programa/Oracle/jre/1.1.7/bin:/cygdrive/c/WINDOWS/SYSTEM32:/cygdrive/c/WINDOWS:/cygdrive/c/Serena/CHANGE~1/DIMENS~1/9.1/PROG:/cygdrive/c/sybase/OLEDB:/cygdrive/c/sybase/ODBC:/cygdrive/c/sybase/ASEP_Win32:/cygdrive/c/sybase/OCS-12_5/dll:/cygdrive/c/sybase/OCS-12_5/lib3p:/cygdrive/c/sybase/OCS-12_5/bin:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/orawin95/Bin:/cygdrive/c/Archivos de programa/Java/jdk1.6.0_02/bin:/cygdrive/c/Archivos de programa/QuickTime/QTSystem/:/cygdrive/c/Archivos de programa/Windows Imaging/:/cygdrive/c/Archivos de programa/Microsoft SQL Server/90/Tools/binn/:/cygdrive/c/Archivos de programa/Microsoft Visual Studio/Common/Tools/WinNT:/cygdrive/c/Archivos de programa/Microsoft Visual Studio/Common/MSDev98/Bin:/cygdrive/c/Archivos de programa/Microsoft Visual Studio/Common/Tools:/cygdrive/c/Archivos de programa/Microsoft Visual Studio/VC98/bin:/cygdrive/c/ORAWIN95/BIN:/usr/bin:/usr/bin:/usr/bin:/usr/share/vim/vim72:.:/usr/X11R6/bin:/usr/bin checkx.exe DEBUG: (find_X11_lib) DLL is /usr/bin/cygX11-6.dll checkx.exe DEBUG: (dlopen_X11_lib) /usr/bin/cygX11-6.dll dlopen'ed successfully. checkx.exe DEBUG: (load_X11_symbols) symbol XOpenDisplay loaded ok checkx.exe DEBUG: (load_X11_symbols) symbol XCloseDisplay loaded ok checkx.exe DEBUG: (try_with_timeout) Using delay of 0 secs, 500000000 nanosecs ( 0.50) checkx.exe DEBUG: (try_with_timeout) xserver search was a success! checkx.exe Info: X display '127.0.0.1:0.0' successfully opened checkx.exe DEBUG: returning with status 0 checkx.exe Info: Exiting with status 0 jlfdiaz@JLFDIAZWXP ~ $ idle 4 [main] python 2500 C:\cygwin\bin\python.exe: *** fatal error - unable to remap C:\cygwin\bin\tk84.dll to same address as parent(0x18760000) != 0x18C50000 9 [main] python 3876 fork: child 2500 - died waiting for dll loading, errno 11 Traceback (most recent call last): File "/usr/bin/idle", line 5, in main() File "/usr/lib/python2.5/idlelib/PyShell.py", line 1404, in main shell = flist.open_shell() File "/usr/lib/python2.5/idlelib/PyShell.py", line 277, in open_shell if not self.pyshell.begin(): File "/usr/lib/python2.5/idlelib/PyShell.py", line 983, in begin client = self.interp.start_subprocess() File "/usr/lib/python2.5/idlelib/PyShell.py", line 374, in start_subprocess self.spawn_subprocess() File "/usr/lib/python2.5/idlelib/PyShell.py", line 350, in spawn_subprocess self.rpcpid = os.spawnv(os.P_NOWAIT, sys.executable, args) File "/usr/lib/python2.5/os.py", line 562, in spawnv return _spawnvef(mode, file, args, None, execv) File "/usr/lib/python2.5/os.py", line 530, in _spawnvef pid = fork() OSError: [Errno 11] Resource temporarily unavailable Thanks for your help, Jose Luis -- View this message in context: http://old.nabble.com/Newbie%3A-idle-doesn%27t-run-tp26741790p26741790.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/ From cabrera@wrc.xerox.com Fri Dec 11 15:28:00 2009 From: cabrera@wrc.xerox.com (jose isaias cabrera) Date: Fri, 11 Dec 2009 15:28:00 -0000 Subject: [ANNOUNCEMENT] Updated: openbox-3.4.7.2-10, New: obconf-2.0.3-10 Message-ID: <9239F6FC0D704846842856C0541123AD@stso.mc.xerox.com> "Yaakov (Cygwin/X)" wrote... > The following package has been updated for Cygwin 1.7: > > *** openbox-3.4.7.2-10 > *** obconf-2.0.3-10 (NEW) This is not accessible through the new setup-1.7.exe. I can see openbox, but the version there is is 0.99.1-4. I am using mirrors.xmission.com. Is there a different way of getting these? thanks, jos?? -- 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/ From deepali.shefali@gmail.com Mon Dec 14 06:42:00 2009 From: deepali.shefali@gmail.com (Dees) Date: Mon, 14 Dec 2009 06:42:00 -0000 Subject: Running Java application with drag and drop support in cygwin In-Reply-To: <4AFD73A0.5030407@dronecode.org.uk> References: <15fe165d0910272257x18264be8sadf9d778e15d8f25@mail.gmail.com> <4AE9A9A3.7090704@dronecode.org.uk> <15fe165d0910300206n2fad7c58p9c9e69ccb5fae959@mail.gmail.com> <4AFD73A0.5030407@dronecode.org.uk> Message-ID: <15fe165d0912132242h3626f4f2k7eccb1e652300a63@mail.gmail.com> On Fri, Nov 13, 2009 at 8:26 PM, Jon TURNEY wrote: > On 30/10/2009 09:06, Dees wrote: >> >> Your reply is much appreciated Jon. I will try to be more specific >> about the problem in further mails. >> >> On Thu, Oct 29, 2009 at 8:11 PM, Jon TURNEY >> ?wrote: >>> >>> On 28/10/2009 05:57, Dees wrote: >>>> >>>> I have developed a Java application involving jTree with extensive >>>> drag and drop support, which runs correctly in my Linux box. However, >>>> when I switch to a windows box and access the same Linux box using >>>> cygwin x-server, the drag and drop in jTree stops working. >>>> Interestingly, rest of the application still works fine. After >>>> analyzing a bit I found that x-server is able to recognize the drag >>>> event but fails to recognize a drop event. >>> >>> Details? >> >> OS : Suse Linux Enterprise Server 10 (i586) >> Version : 10 >> Patch level : 3 >> Other version information: >> Java : JDK 5 >> Cygwin setup-version: 2.573.2.3 >> Also tried using Xming 6.9.0.31 ssh same Linux setup from Windows, but >> that also doesn't solve the problem. >> >>> >>>> Is there any setting, which should be done prior to running the Java >>>> swing applications? >>>> >>>> Here is a sample code which behaves in exactly same way. >>>> http://www.java2s.com/Code/Java/Swing-JFC/TreeDragandDrop.htm >>> >>> I have no idea how to use that java code to reproduce the problem you are >>> seeing. >> >> Using the above java code in Linux: >> 1. Download and Install Java Development Toolkit on your Linux box >> (Java sun download site: >> http://java.sun.com/javase/downloads/index.jsp), if you do not have it >> already. >> 2. Save the sample code in the above link with the file name >> TreeTester.java, say in /home/user/ >> 3. Navigate to TreeTester.java from shell, and compile the java code: >> ? ? ? ?# cd /home/user/ >> ? ? ? ?# /usr/java/jdk1.5.0_14/bin/javac TreeTester.java >> ? ?Ignore any warnings of deprecated APIs. >> 4. This will create a few .class files in /home/user/ directory. Final >> step is to run the Java code, using: >> ? ? ? ?# /usr/java/jdk1.5.0_14/bin/java -classpath . TreeTester >> ? ?This will open up a GUI, with a jTree each on left and right pane. >> You can drag and drop any of the leaf nodes from one jTree to the root >> node of the other jTree and this should add a new node in the other >> jTree. You will get messages on console for the operations being >> performed. Now ssh the same box using cygwin/xming from any other >> windows box, and run the application using command in step 4. You >> should be able to drag (a small icon will come under cursor indicating >> that something is being dragged) but when you will drop it, the new >> node would not be added to the tree. Thats where lies my problem!!! > > Thanks for the test case and instructions, this makes it much easier for me > to try it out. > > However, this testcase and your jar archive both work fine for me (using > Xserver 1.7.1-3)! > >>>> May be my problem is related to some setting. Though, not sure. >>>> Has anybody come across something similar? What should be done then? >>>> Please let me know. >>> >>> No it's probably a bug in Cygwin/X. ?But you're going to need to be a lot >>> more specific about the problem before any progress can be made on fixing >>> it. > >> Also, putting some debug messages in the code lets me conclude that >> it's the drop event which is not being recognized, as the main control >> never reaches there. > > There is not really any drop event, as far as the X server is concerned, > just mouse click and motion events, which are passed on to you application > (which has a framework to interpret them as dragging and dropping an item). > > Now having a better idea of the problem, it seems less likely it is an > Xserver bug at all. ?The only Xserver cause I can think of would be if it > was somehow not sending the correct events to your applications window, > which you could test using xev -id (you can > use xwininfo to find the window id) > I have tried this, but could not get any idea if any event is going wrong. Here is the output of xev -id 0xe00021 (only for drag and drop event): LeaveNotify event, serial 13, synthetic NO, window 0xe00021, root 0x5a, subw 0xe00025, time 3560250, (87,65), root:(91,95), mode NotifyGrab, detail NotifyVirtual, same_screen YES, focus YES, state 256 FocusOut event, serial 13, synthetic NO, window 0xe00021, mode NotifyGrab, detail NotifyAncestor EnterNotify event, serial 13, synthetic NO, window 0xe00021, root 0x5a, subw 0xe00025, time 3565375, (212,48), root:(216,78), mode NotifyUngrab, detail NotifyVirtual, same_screen YES, focus YES, state 0 KeymapNotify event, serial 13, synthetic NO, window 0x0, keys: 90 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 FocusIn event, serial 13, synthetic NO, window 0xe00021, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 13, synthetic NO, window 0x0, keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 LeaveNotify event, serial 13, synthetic NO, window 0xe00021, root 0x5a, subw 0xe00025, time 3569046, (205,211), root:(209,241), mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, focus YES, state 0 Does the window 0x0 in two events in the log(above) signify anything misbehaving? Your reply is much awaited and appreciated. > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer > -- 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/ From fabricio.silva@signove.com Mon Dec 14 14:23:00 2009 From: fabricio.silva@signove.com (=?ISO-8859-1?Q?Fabr=EDcio_Silva?=) Date: Mon, 14 Dec 2009 14:23:00 -0000 Subject: Error in Xwin with Windows 7 (Cygwin 1.7) In-Reply-To: <1203d4320912140617q55351819v1bf4c58d910a9ea6@mail.gmail.com> References: <1203d4320912140556m22ae62f6j69990fcbd20de4db@mail.gmail.com> <1203d4320912140605x396a82a6k4c4829df63be7bd0@mail.gmail.com> <1203d4320912140616q36bd4065t6a02c0faad18cb5a@mail.gmail.com> <1203d4320912140617q55351819v1bf4c58d910a9ea6@mail.gmail.com> Message-ID: <1203d4320912140623v30d3ecaei3199f2dbfe98bcd3@mail.gmail.com> Hi fellows, ?We are developing an IDE?(Integrated Development Environment) for Nokia Maemo Platform and it uses some cygwin features like Xwin.?We decide to try our product with cygwin 1.7 beta version, but we are facing one problem with Xwin, see: Problem description: ??The Xwin fails while displaying maemo application UI ?and it handles a mouse click event, it shows a?segmentation fault error. The same application runs fine in cygwin 1.5.3.0 (20090222) ?? Well, It possible that you?may not have been introduced to?maemo development, but to summarize, we have a "device emulator" program that runs and shows in a XWindow the device screen, so we can run GUI applications and see the results on this screen. Background: ?- SO: Windows 7 ?- Cygwin 1.7.1.0 (10701000) ?- Installed Packages: ?xorg server, xinit, xpdinfo. ?- Workstation: Notebook Dell, Vostro, 4Gb, Display 1280 x 800 (true Color 32 bits), Steps: ??1) Start maemo maemosdk platform: it shows the maemo device screen in a Xwindow ??2) Run a maemo application: a simple C++ graphic application. ??3) Click in application title, the button "say hello button" will be shown, click on it. ??4) Verify the error screen. We had problems to post the attachments, so please see logs and pictures available in bug tracker: https://garage.maemo.org/tracker/index.php?func=detail&aid=4897&group_id=192&atid=1420 ?You can get more details about IDE Integration project at http://maemo.org/development/documentation/ide_integration/?and maemo development at maemo.org Thanks -- Fabr?cio Silva Epaminondas Enterprise/Mobile Software Engineer at Signove - signove.com fabricio.silva@signove.com http://fabricioepa.googlepages.com/home -- 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/ From fstx+u@update.uu.se Mon Dec 14 15:07:00 2009 From: fstx+u@update.uu.se (Fredrik Staxeng) Date: Mon, 14 Dec 2009 15:07:00 -0000 Subject: startxwin.bat - Can't open display, but taskbar icon appears Message-ID: <1m1vixbnt4.fsf@Psilocybe.Update.UU.SE> and I can start xterm from that! I changed the timeoutfor checkX to 60, and then it works. What can make XWin.exe take so long to start up? Could it be reverse name lookup? If so, how can I solve that without providing working reverse lookup? -- Fredrik Stax\"ang | rot13: sfgk@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- 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/ From kbrown@cornell.edu Mon Dec 14 15:16:00 2009 From: kbrown@cornell.edu (Ken Brown) Date: Mon, 14 Dec 2009 15:16:00 -0000 Subject: Should xterm require xbitmaps? Message-ID: <4B2656DC.9080908@cornell.edu> After putting "XTerm*scrollBar: true" into my .Xdefaults, I started getting a new xterm warning: Warning: Cannot convert string "vlines2" to type Pixmap The cause is the following line in /etc/X11/app-defaults/ XTerm-color: *VT100.scrollbar.thumb: vlines2 and the vlines2 pixmap is in the xbitmaps package. Should xterm require xbitmaps? Ken -- 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/ From cygwin@tlinx.org Tue Dec 15 19:01:00 2009 From: cygwin@tlinx.org (Linda Walsh) Date: Tue, 15 Dec 2009 19:01:00 -0000 Subject: extensions (shared mem, security) Message-ID: <4B27DCE4.7090801@tlinx.org> looking at the startup log, I don't see the X-Security extension being initialized. Is it not supported? Also, perhaps more important for me is the message: 2009-12-15 10:39:27 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel NT supports shared memory objects and I thought cygwin uses shared memory for cross-process communication. So what's this about X not knowing about the shared memory support? linda -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 15 19:45:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 15 Dec 2009 19:45:00 -0000 Subject: extensions (shared mem, security) In-Reply-To: <4B27DCE4.7090801@tlinx.org> References: <4B27DCE4.7090801@tlinx.org> Message-ID: <4B27E73E.7040101@users.sourceforge.net> On 15/12/2009 13:00, Linda Walsh wrote: > looking at the startup log, I don't see the X-Security extension being > initialized. Is it not supported? http://cygwin.com/ml/cygwin-xfree/2008-11/msg00154.html > Also, perhaps more important for me is the message: > > 2009-12-15 10:39:27 XFree86-Bigfont extension local-client optimization > disabled > due to lack of shared memory support in the kernel > > NT supports shared memory objects and I thought cygwin uses shared > memory for cross-process communication. So what's this about X not > knowing about the shared memory support? You need to install and run the cygserver service before launching XWin in order to have support for XFree86-Bigfont and MIT-SHM. Yaakov Cygwin/X -- 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/ From cygwin@tlinx.org Tue Dec 15 20:50:00 2009 From: cygwin@tlinx.org (Linda Walsh) Date: Tue, 15 Dec 2009 20:50:00 -0000 Subject: extensions (shared mem, security) In-Reply-To: <4B27E73E.7040101@users.sourceforge.net> References: <4B27DCE4.7090801@tlinx.org> <4B27E73E.7040101@users.sourceforge.net> Message-ID: <4B27F670.4020105@tlinx.org> Yaakov (Cygwin/X) wrote: > On 15/12/2009 13:00, Linda Walsh wrote: >> looking at the startup log, I don't see the X-Security extension being >> initialized. Is it not supported? > > http://cygwin.com/ml/cygwin-xfree/2008-11/msg00154.html > ...and... > > You need to install and run the cygserver service before launching XWin > in order to have support for XFree86-Bigfont and MIT-SHM. --- Damn useful response. What can I say, but thanks for the str8-up. :-) Guess I have more configurations changes to make... -l -- 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/ From hemal.pandya@gmail.com Wed Dec 16 07:45:00 2009 From: hemal.pandya@gmail.com (Hemal Pandya) Date: Wed, 16 Dec 2009 07:45:00 -0000 Subject: timed out waiting for reply from selection owner Message-ID: <50be591b0912152345l696732c1u878ce62e9db01b8@mail.gmail.com> This is rather strange and I don't even know if I have a correct repro. The symptoms I see is that I am able to copy in X (XEmacs or xterm) and paste in Windows but not vice-versa. Immediately after I start X copy/paste works both ways. I suspect this has something to do with Microsoft Visual Studio. It seems to hijack the clipboard and copy/paste stops working altogether. I found this using a utility GetOpenClipboardWindow I found on the net. When copy/paste across windows Apps stops working, this utility always reports that VSS owns the clipboard. I often have to kill VS to get other programs to interact with the clipboard. But even after I kill VS Studio, Cygwin-X is not able to get data from the clipboard. Any time I paste in X I see the above message in /var/log/XWin.0.log Any suggestions what might be wrong and how I can work-around this issue? Thanks in advance - hemal -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 20:11:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 20:11:00 -0000 Subject: Problem with new xinit - console window doesn't open (but bash starts) In-Reply-To: <4B099DF8.7040101@dronecode.org.uk> References: <4B0613C6.3040800@alum.mit.edu> <4B06161A.6040201@alum.mit.edu> <4B069020.8040407@cornell.edu> <4B06B042.1030003@alum.mit.edu> <4B099DF8.7040101@dronecode.org.uk> Message-ID: <4B293F00.5030005@dronecode.org.uk> On 22/11/2009 20:24, Jon TURNEY wrote: > On 20/11/2009 15:05, Jim Reisert AD1C wrote: >> I tried adding the missing fonts. I tried SET LANG=C >> Starting the X server is still unpredictable. > > Does this mean it sometimes works and sometimes doesn't? > Or does it mean it fails in different ways each time you try? > >> Now my log file (attached) shows: >> >> It also claims another window manage is running (and therefore shuts >> down), which is untrue (there is no other Xwin process running). > > Since I have touched 'check for another window manager' code recently, I > was kind of expecting to see that I'd managed to break it in some way, > but.. > > I'm not quite sure what to make of that log file. This is very strange. > > If you look for "(II) xorg.conf is not supported", you'll see that it > looks like that server starts again about half-way through. > > I did wonder if you were managing to somehow start two copies of XWin > near-simultaneously, but I don't think that would produce a logfile like > that (since it's not opened in append mode, you probably get the logfile > from the last process to close it or something like that) > > An alternative explanation is that there is a really inconveniently > timed server regeneration happening: just after the internal client > threads have been created, but before they can connect, so they are > still hanging around to be accepted by the next server generation. > > If we did have twice as many threads as we are supposed to, that would > explain the final failure due to another WM running (as there's another > WM thread, note that there are two 'winMultiWindowXMsgProc - Hello' lines) > > No idea why the server is regenerating though, needs more meditation :-) After some meditation, I think that the server regeneration may be being caused by a race condition introduced by the use of checkX in the startxwin.bat script: If checkX connects to and then disconnects from the Xserver before the internal client threads get a chance to connect, the Xserver will restart when checkX disconnects, causing these duplicate threads. Fortunately, this should have a simple workaround of removing the checkX line from startxwin.bat (or replacing it with a delay if you care about getting an xterm started by it) The correct fix for this behaviour is not immediately obvious, and I don't really have time to work on it at the moment, so I don't have a patch for this. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 20:19:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 20:19:00 -0000 Subject: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-68 In-Reply-To: References: Message-ID: <4B2940E1.4080302@dronecode.org.uk> On 05/12/2009 09:03, Fr??d??ric Bron wrote: >> I just uploaded a new Cygwin 1.7 test release, 1.7.0-68. > > Installed this version and cannot start Xwin anymore. Here is the content of > /var/log/XWin.0.log: This looks to be the same problem as in [1]. You might try the workaround of removing the checkX line from startxwin.bat [1] http://cygwin.com/ml/cygwin-xfree/2009-12/msg00074.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 20:26:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 20:26:00 -0000 Subject: timed out waiting for reply from selection owner In-Reply-To: <50be591b0912152345l696732c1u878ce62e9db01b8@mail.gmail.com> References: <50be591b0912152345l696732c1u878ce62e9db01b8@mail.gmail.com> Message-ID: <4B294258.8000804@dronecode.org.uk> On 16/12/2009 07:45, Hemal Pandya wrote: > This is rather strange and I don't even know if I have a correct > repro. The symptoms I see is that I am able to copy in X (XEmacs or > xterm) and paste in Windows but not vice-versa. > > Immediately after I start X copy/paste works both ways. > > I suspect this has something to do with Microsoft Visual Studio. It > seems to hijack the clipboard and copy/paste stops working altogether. > I found this using a utility GetOpenClipboardWindow I found on the > net. When copy/paste across windows Apps stops working, this utility > always reports that VSS owns the clipboard. > > I often have to kill VS to get other programs to interact with the > clipboard. But even after I kill VS Studio, Cygwin-X is not able to > get data from the clipboard. Any time I paste in X I see the above > message in /var/log/XWin.0.log > > Any suggestions what might be wrong and how I can work-around this issue? Thanks for the problem report. Unfortunately it is lacking information to be useful. You might consider reading the problem reporting guidelines at [1] and trying again. In this particular case, attaching the /var/log/XWin.0.log to show the context for the error message is would be sensible. [1] http://cygwin.com/problems.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 20:31:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 20:31:00 -0000 Subject: extensions (shared mem, security) In-Reply-To: <4B27DCE4.7090801@tlinx.org> References: <4B27DCE4.7090801@tlinx.org> Message-ID: <4B29438D.3040606@dronecode.org.uk> On 15/12/2009 19:00, Linda Walsh wrote: > looking at the startup log, I don't see the X-Security extension being > initialized. Is it not supported? Also discussed in the Cyginw/X FAQ at [1] > Also, perhaps more important for me is the message: > > 2009-12-15 10:39:27 XFree86-Bigfont extension local-client optimization > disabled > due to lack of shared memory support in the kernel > > NT supports shared memory objects and I thought cygwin uses shared > memory for cross-process communication. So what's this about X not > knowing about the shared memory support? I don't know how this can be made clearer than [2] [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#AEN569 [2] http://x.cygwin.com/docs/ug/using-shared-memory.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 20:52:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 20:52:00 -0000 Subject: Cut/paste in an xterm takes extraordinarily long time In-Reply-To: <806a89db0912101018o4f00c06eo1d8d85c2334348f6@mail.gmail.com> References: <806a89db0912101018o4f00c06eo1d8d85c2334348f6@mail.gmail.com> Message-ID: <4B294884.3010003@dronecode.org.uk> On 10/12/2009 18:18, Jim Reisert AD1C wrote: > I'm having problems with copying text from a Windows application > (Firefox) and pasting into Cygwin Emacs (23.1.1). I'm running Cygwin > 1.7 (latest) and Xorg (latest). When pasting into Emacs, my mouse > pointer changes to an hourglass, and after what seems like an eternity > (10-30 seconds), the paste will finish, often times with the wrong > text, rarely with the correct test. When the text is wrong, how is it wrong? Scrambled? Previous paste? Backwards? Random letters? Translated to Urdu? > I am running RealVNC also. I remember several/many months back, there > seems to be a cut/paste issue with Cygwin that was exacerbated by > running VNC. Could that problem have returned? You could test this by closing RealVNC and seeing if the problem doesn't occur? > How can I help debug this? I've attached my cygcheck output. If you could follow the steps I outlined in my email replying to the last time you mentioned this [1], that would be helpful? http://sourceware.org/ml/cygwin-xfree/2009-10/msg00129.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 21:03:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 21:03:00 -0000 Subject: [PATCH] Repair '-nolock' In-Reply-To: <4B137AF0.8040407@bonhard.uklinux.net> References: <4B137AF0.8040407@bonhard.uklinux.net> Message-ID: <4B294B29.9010401@dronecode.org.uk> On 30/11/2009 07:57, Fergus wrote: > (Sorry to send twice: originally sent yesterday Sunday 0728 GMT but > never arrived at cygwin-xfree at cygwin dot com; 2nd attempt today > Monday 0752 GMT and hope for better progress.) Message was: The reason why your first message did not arrive at the mailing list was because you only sent it to me, personally. Such mails get ignored for reasons laid out at [1]. Please be more careful in future :-) [1] http://cygwin.com/problems.html > > Thank you. > > 1 Will this amendment eventually be incorporated into an updated .bz2 > file under /release? Assuming it works and doesn't break anything else, yes. > 2 If not then (I am sorry) I do not know how to introduce a patch into > an existing executable. > > If this is something everybody in the world except me knows, can you > direct me to a howto? http://en.wikipedia.org/wiki/Patch_%28Unix%29 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/ From jon.turney@dronecode.org.uk Wed Dec 16 21:30:00 2009 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 16 Dec 2009 21:30:00 -0000 Subject: extensions (shared mem, security) In-Reply-To: <4B29438D.3040606@dronecode.org.uk> References: <4B27DCE4.7090801@tlinx.org> <4B29438D.3040606@dronecode.org.uk> Message-ID: <4B295181.7080609@dronecode.org.uk> On 16/12/2009 20:31, Jon TURNEY wrote: > On 15/12/2009 19:00, Linda Walsh wrote: >> looking at the startup log, I don't see the X-Security extension being >> initialized. Is it not supported? > > Also discussed in the Cyginw/X FAQ at [1] > > [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#AEN569 Hmm... Fixed an error in the docbook source so that anchor has a proper name which doesn't change every time the documentation is rebuilt. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trusted-untrusted-x11-forwarding -- 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/ From jjreisert@alum.mit.edu Wed Dec 16 22:01:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Wed, 16 Dec 2009 22:01:00 -0000 Subject: Cut/paste in an xterm takes extraordinarily long time In-Reply-To: <4B294884.3010003@dronecode.org.uk> References: <806a89db0912101018o4f00c06eo1d8d85c2334348f6@mail.gmail.com> <4B294884.3010003@dronecode.org.uk> Message-ID: <806a89db0912161401h21fed380ke97fc21b72d3c8df@mail.gmail.com> I'll save this in case it happens again. It hasn't been a problem this week. - Jim On Wed, Dec 16, 2009 at 1:52 PM, Jon TURNEY wrote: > On 10/12/2009 18:18, Jim Reisert AD1C wrote: >> >> I'm having problems with copying text from a Windows application >> (Firefox) and pasting into Cygwin Emacs (23.1.1). ?I'm running Cygwin >> 1.7 (latest) and Xorg (latest). ?When pasting into Emacs, my mouse >> pointer changes to an hourglass, and after what seems like an eternity >> (10-30 seconds), the paste will finish, often times with the wrong >> text, rarely with the correct test. > > When the text is wrong, how is it wrong? Scrambled? Previous paste? > Backwards? Random letters? Translated to Urdu? > >> I am running RealVNC also. ?I remember several/many months back, there >> seems to be a cut/paste issue with Cygwin that was exacerbated by >> running VNC. ?Could that problem have returned? > > You could test this by closing RealVNC and seeing if the problem doesn't > occur? > >> How can I help debug this? ?I've attached my cygcheck output. > > If you could follow the steps I outlined in my email replying to the last > time you mentioned this [1], that would be helpful? > > http://sourceware.org/ml/cygwin-xfree/2009-10/msg00129.html -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From frederic.bron@m4x.org Thu Dec 17 05:43:00 2009 From: frederic.bron@m4x.org (=?UTF-8?B?RnLDqWTDqXJpYyBCcm9u?=) Date: Thu, 17 Dec 2009 05:43:00 -0000 Subject: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-68 In-Reply-To: <4B2940E1.4080302@dronecode.org.uk> References: <4B2940E1.4080302@dronecode.org.uk> Message-ID: >>> I just uploaded a new Cygwin 1.7 test release, 1.7.0-68. >> >> Installed this version and cannot start Xwin anymore. Here is the content >> of >> /var/log/XWin.0.log: > > This looks to be the same problem as in [1]. > > You might try the workaround of removing the checkX line from startxwin.bat It is strange as it reworked alone. I also removed the checkX line as I do not start xterm. Thanks, Fr?d?ric -- 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/ From hemal.pandya@gmail.com Thu Dec 17 06:34:00 2009 From: hemal.pandya@gmail.com (Hemal Pandya) Date: Thu, 17 Dec 2009 06:34:00 -0000 Subject: timed out waiting for reply from selection owner In-Reply-To: <4B294258.8000804@dronecode.org.uk> References: <50be591b0912152345l696732c1u878ce62e9db01b8@mail.gmail.com> <4B294258.8000804@dronecode.org.uk> Message-ID: <50be591b0912162234r18c1097ehad7867a47653ccfa@mail.gmail.com> On Thu, Dec 17, 2009 at 1:56 AM, Jon TURNEY wrote: > [....]> > Thanks for the problem report. Unfortunately it is lacking information to be useful. > > You might consider reading the problem reporting guidelines at [1] and trying again. ?In this particular case, attaching the /var/log/XWin.0.log to show the context for the error message is would be sensible. I apologize for incomplete information. Today I found XEmacs reporting timeout almost immediately after starting Visual Studio. I have attached both ?XWin.0.log and output from cygcheck. Best regards, - hemal > > [1] http://cygwin.com/problems.html > > -- > Jon TURNEY > Volunteer Cygwin/X X Server maintainer -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 26127 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 23179 bytes Desc: not available URL: -------------- next part -------------- -- 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/ From rcsaba@gmail.com Thu Dec 17 13:48:00 2009 From: rcsaba@gmail.com (Csaba Raduly) Date: Thu, 17 Dec 2009 13:48:00 -0000 Subject: X server fails to start Message-ID: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> X used to work for quite a while but now it doesn't. The X icon appears and disappears. It seems to have developed a fixation with "another window manager", according to the log. Not even a reboot helps. Here's startxwin.bat (in C:\cygwin17\bin) @echo off SET DISPLAY=127.0.0.1:0.0 REM SET CYGWIN_ROOT=C:\cygwin if defined CYGWIN_ROOT goto :OK set CYGWIN_ROOT=%~dp0.. :OK SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET PATH=%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix del %CYGWIN_ROOT%\tmp\.X*-lock REM REM Startup the programs REM REM Startup the X Server with the integrated Windows-based window manager. REM WARNING: Do not use 'xwinclip' in conjunction with the ``-clipboard'' REM command-line parameter for XWin. Doing so would start two clipboard REM managers, which is never supposed to happen. REM Description of XWin-specific options is in XWin(1) manpage. %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error -multiplemonitors" REM Make sure XWin is ready to accept connections before proceeding %RUN% checkX -wait -d %DISPLAY% -t 12 REM Startup an xterm, using bash as the shell. REM %RUN% xterm -e /usr/bin/bash -l Oddly, the stock startx works with the following command line: startx -- -multiwindow -clipboard -silent-dup-error -multiplemonitors Csaba -- Life is complex, with real and imaginary parts -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 79133 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 8303 bytes Desc: not available URL: -------------- next part -------------- -- 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/ From radu.berinde@gmail.com Thu Dec 17 14:37:00 2009 From: radu.berinde@gmail.com (Radu Berinde) Date: Thu, 17 Dec 2009 14:37:00 -0000 Subject: 1.7.1 - problem with moving mouse programmatically with xte Message-ID: I am using Cygwin/X 1.7.1 and I am running applications on this X server from a Slackware virtual machine. I am using xte v1.03 to move the mouse using keyboard shortcuts. Using ion3 as the window manager. When running e.g. # xte 'mousermove +250 0' the mouse cursor should move to the right; indeed, the window manager changes focus as if moved to the right, but the cursor doesn't visibly move. When mouse is moved, movement continues from the visible location (the xte movement is 'forgot'). I am starting the X server with this command (inside startx.bat file which is ran with bin/run.exe) XWin -ac -clipboard -silent-dup-error Note that the exact thing works perfectly with the stable 1.5 version. Hope this helps identify a problem. Thank you for developing Cygwin/X. Best, Radu -- 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/ From john_watts@isoparix.com Thu Dec 17 21:58:00 2009 From: john_watts@isoparix.com (John Watts) Date: Thu, 17 Dec 2009 21:58:00 -0000 Subject: Problem report: ' fatal IO error 11' in xwin.exe Message-ID: <4B2AA95F.5070406@isoparix.com> I try to start two X-windows by using the following commands. Two (superimposed) windows do appear, briefly, and then vanish with the 'fatal IO error 11' message -- Regards, John Watts john_watts@isoparix.com Skype: JS.Watts Tel: +44 (0)20 8549 6501 Car: +44 (0)774 694 9715 Everything that is Proveable is True. But not everything that is True is Proveable - and we can prove that. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: xwin_problem.txt URL: -------------- next part -------------- -- 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/ From frederic.bron@m4x.org Thu Dec 17 22:47:00 2009 From: frederic.bron@m4x.org (=?UTF-8?B?RnLDqWTDqXJpYyBCcm9u?=) Date: Thu, 17 Dec 2009 22:47:00 -0000 Subject: screen not updated outside 1680x1050 Message-ID: My screen resolution is 1920x1200. The X windows are badly updated (sometimes yes, most of the time no) outside the top-left area 1680x1050. My problems are seen with xterm, gv, gvim, rxvt-x... so I think comes from X.org. To produce the problem: start an X windows program, then move the window to the right and go back to the left. For gvim, it is particularly annoying when maximizing the window. However /var/log/XWin.0.log says it read the good screen dimensions: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: XWin -multiwindow -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1680 h 1050 winInitializeDefaultScreens - Returning 2009-12-17 13:37:31 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2009-12-17 13:37:31 _XSERVTransOpen: transport open failed for inet6/VOR-CRV-01660:0 2009-12-17 13:37:31 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2009-12-17 13:37:35 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-12-17 13:37:35 (II) xorg.conf is not supported 2009-12-17 13:37:35 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-12-17 13:37:35 winPrefsLoadPreferences: /cygdrive/d/Documents/.XWinrc 2009-12-17 13:37:35 winGetDisplay: DISPLAY=:0.0 2009-12-17 13:37:37 winDetectSupportedEngines - Windows NT/2000/XP 2009-12-17 13:37:37 winDetectSupportedEngines - DirectDraw installed 2009-12-17 13:37:37 winDetectSupportedEngines - DirectDraw4 installed 2009-12-17 13:37:37 winDetectSupportedEngines - Returning, supported engines 00000007 2009-12-17 13:37:37 winSetEngine - Multi Window or Rootless => ShadowGDI 2009-12-17 13:37:37 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-12-17 13:37:38 winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 2009-12-17 13:37:38 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff 2009-12-17 13:37:38 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 2009-12-17 13:37:38 null screen fn ReparentWindow 2009-12-17 13:37:38 null screen fn RestackWindow 2009-12-17 13:37:38 InitQueue - Calling pthread_mutex_init 2009-12-17 13:37:38 InitQueue - pthread_mutex_init returned 2009-12-17 13:37:38 InitQueue - Calling pthread_cond_init 2009-12-17 13:37:38 InitQueue - pthread_cond_init returned 2009-12-17 13:37:38 winInitMultiWindowWM - Hello 2009-12-17 13:37:38 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-12-17 13:37:38 Screen 0 added at XINERAMA coordinate (0,0). 2009-12-17 13:37:38 winMultiWindowXMsgProc - Hello 2009-12-17 13:37:38 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-12-17 13:37:38 MIT-SHM extension disabled due to lack of kernel support 2009-12-17 13:37:38 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-12-17 13:37:39 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-12-17 13:37:39 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-12-17 13:37:55 winPointerWarpCursor - Discarding first warp: 840 525 2009-12-17 13:37:55 (--) 3 mouse buttons found 2009-12-17 13:37:55 (--) Setting autorepeat to delay=500, rate=31 2009-12-17 13:37:55 (--) winConfigKeyboard - Layout: "0000040C" (0000040c) 2009-12-17 13:37:55 (--) Using preset keyboard for "French (Standard)" (40c), type "4" 2009-12-17 13:37:55 Rules = "base" Model = "pc105" Layout = "fr" Variant = "none" Options = "none" 2009-12-17 13:38:00 winInitMultiWindowWM - pthread_mutex_lock () returned. 2009-12-17 13:38:00 winInitMultiWindowWM - pthread_mutex_unlock () returned. 2009-12-17 13:38:00 winMultiWindowXMsgProc - pthread_mutex_lock () returned. 2009-12-17 13:38:00 winGetDisplay: DISPLAY=:0.0 2009-12-17 13:38:00 winMultiWindowXMsgProc - pthread_mutex_unlock () returned. 2009-12-17 13:38:00 winInitMultiWindowWM - DISPLAY=:0.0 2009-12-17 13:38:00 winGetDisplay: DISPLAY=:0.0 2009-12-17 13:38:00 winMultiWindowXMsgProc - DISPLAY=:0.0 2009-12-17 13:38:00 winProcEstablishConnection - Hello 2009-12-17 13:38:00 winInitClipboard () 2009-12-17 13:38:00 winClipboardProc - Hello 2009-12-17 13:38:00 winProcEstablishConnection - winInitClipboard returned. 2009-12-17 13:38:00 DetectUnicodeSupport - Windows NT/2000/XP 2009-12-17 13:38:00 winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. 2009-12-17 13:38:00 winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. 2009-12-17 13:38:01 winGetDisplay: DISPLAY=:0.0 2009-12-17 13:38:01 winClipboardProc - DISPLAY=:0.0 2009-12-17 13:38:02 winClipboardProc - XOpenDisplay () returned and successfully opened the display. 2009-12-17 13:47:46 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32 2009-12-17 13:47:46 winWindowProc - WM_DISPLAYCHANGE - new width: 1920 new height: 1200 -- 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/ From mike_ayers@tvworks.com Fri Dec 18 00:03:00 2009 From: mike_ayers@tvworks.com (Mike Ayers) Date: Fri, 18 Dec 2009 00:03:00 -0000 Subject: screen not updated outside 1680x1050 In-Reply-To: References: Message-ID: <83E753BE7B6A324ABB336245BAF1DAAC0DA068D5@mailserver.metatv-ds.metatv.com> > From: cygwin-xfree-owner@cygwin.com [mailto:cygwin-xfree- > owner@cygwin.com] On Behalf Of Fr?d?ric Bron > Sent: Thursday, December 17, 2009 2:47 PM > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 1.7.1.0 (10701000) > Build Date: 2009-11-11 > > Contact: cygwin-xfree@cygwin.com > > XWin was started with the following command line: > > XWin -multiwindow -clipboard -silent-dup-error > > ddxProcessArgument - Initializing default screens > winInitializeDefaultScreens - w 1680 h 1050 ^^^^^^^^^^^^^ Looks like the system doesn't see your whole resolution at startup. I'd pass "-screen 0 1920x1200" to XWin.exe. I tried this to reduce my screen resolution, and saw things similar to what you describe outside the declared screensize. HTH, Mike From deepali.shefali@gmail.com Fri Dec 18 05:54:00 2009 From: deepali.shefali@gmail.com (Dees) Date: Fri, 18 Dec 2009 05:54:00 -0000 Subject: Running Java application with drag and drop support in cygwin In-Reply-To: <15fe165d0912132242h3626f4f2k7eccb1e652300a63@mail.gmail.com> References: <15fe165d0910272257x18264be8sadf9d778e15d8f25@mail.gmail.com> <4AE9A9A3.7090704@dronecode.org.uk> <15fe165d0910300206n2fad7c58p9c9e69ccb5fae959@mail.gmail.com> <4AFD73A0.5030407@dronecode.org.uk> <15fe165d0912132242h3626f4f2k7eccb1e652300a63@mail.gmail.com> Message-ID: <15fe165d0912172153o5c48e300s63d80704d0c504c8@mail.gmail.com> Hi Jon, Did you get a chance to look at this? >From whatever posts available online, I could not get a clue what is going wrong. Please respond. Thanks, Shefali On Mon, Dec 14, 2009 at 12:12 PM, Dees wrote: > On Fri, Nov 13, 2009 at 8:26 PM, Jon TURNEY wrote: >> On 30/10/2009 09:06, Dees wrote: >>> >>> Your reply is much appreciated Jon. I will try to be more specific >>> about the problem in further mails. >>> >>> On Thu, Oct 29, 2009 at 8:11 PM, Jon TURNEY >>> wrote: >>>> >>>> On 28/10/2009 05:57, Dees wrote: >>>>> >>>>> I have developed a Java application involving jTree with extensive >>>>> drag and drop support, which runs correctly in my Linux box. However, >>>>> when I switch to a windows box and access the same Linux box using >>>>> cygwin x-server, the drag and drop in jTree stops working. >>>>> Interestingly, rest of the application still works fine. After >>>>> analyzing a bit I found that x-server is able to recognize the drag >>>>> event but fails to recognize a drop event. >>>> >>>> Details? >>> >>> OS : Suse Linux Enterprise Server 10 (i586) >>> Version : 10 >>> Patch level : 3 >>> Other version information: >>> Java : JDK 5 >>> Cygwin setup-version: 2.573.2.3 >>> Also tried using Xming 6.9.0.31 ssh same Linux setup from Windows, but >>> that also doesn't solve the problem. >>> >>>> >>>>> Is there any setting, which should be done prior to running the Java >>>>> swing applications? >>>>> >>>>> Here is a sample code which behaves in exactly same way. >>>>> http://www.java2s.com/Code/Java/Swing-JFC/TreeDragandDrop.htm >>>> >>>> I have no idea how to use that java code to reproduce the problem you are >>>> seeing. >>> >>> Using the above java code in Linux: >>> 1. Download and Install Java Development Toolkit on your Linux box >>> (Java sun download site: >>> http://java.sun.com/javase/downloads/index.jsp), if you do not have it >>> already. >>> 2. Save the sample code in the above link with the file name >>> TreeTester.java, say in /home/user/ >>> 3. Navigate to TreeTester.java from shell, and compile the java code: >>> # cd /home/user/ >>> # /usr/java/jdk1.5.0_14/bin/javac TreeTester.java >>> Ignore any warnings of deprecated APIs. >>> 4. This will create a few .class files in /home/user/ directory. Final >>> step is to run the Java code, using: >>> # /usr/java/jdk1.5.0_14/bin/java -classpath . TreeTester >>> This will open up a GUI, with a jTree each on left and right pane. >>> You can drag and drop any of the leaf nodes from one jTree to the root >>> node of the other jTree and this should add a new node in the other >>> jTree. You will get messages on console for the operations being >>> performed. Now ssh the same box using cygwin/xming from any other >>> windows box, and run the application using command in step 4. You >>> should be able to drag (a small icon will come under cursor indicating >>> that something is being dragged) but when you will drop it, the new >>> node would not be added to the tree. Thats where lies my problem!!! >> >> Thanks for the test case and instructions, this makes it much easier for me >> to try it out. >> >> However, this testcase and your jar archive both work fine for me (using >> Xserver 1.7.1-3)! >> >>>>> May be my problem is related to some setting. Though, not sure. >>>>> Has anybody come across something similar? What should be done then? >>>>> Please let me know. >>>> >>>> No it's probably a bug in Cygwin/X. But you're going to need to be a lot >>>> more specific about the problem before any progress can be made on fixing >>>> it. >> >>> Also, putting some debug messages in the code lets me conclude that >>> it's the drop event which is not being recognized, as the main control >>> never reaches there. >> >> There is not really any drop event, as far as the X server is concerned, >> just mouse click and motion events, which are passed on to you application >> (which has a framework to interpret them as dragging and dropping an item). >> >> Now having a better idea of the problem, it seems less likely it is an >> Xserver bug at all. The only Xserver cause I can think of would be if it >> was somehow not sending the correct events to your applications window, >> which you could test using xev -id (you can >> use xwininfo to find the window id) >> > I have tried this, but could not get any idea if any event is going wrong. > Here is the output of xev -id 0xe00021 (only for drag and drop event): > > LeaveNotify event, serial 13, synthetic NO, window 0xe00021, > root 0x5a, subw 0xe00025, time 3560250, (87,65), root:(91,95), > mode NotifyGrab, detail NotifyVirtual, same_screen YES, > focus YES, state 256 > > FocusOut event, serial 13, synthetic NO, window 0xe00021, > mode NotifyGrab, detail NotifyAncestor > > EnterNotify event, serial 13, synthetic NO, window 0xe00021, > root 0x5a, subw 0xe00025, time 3565375, (212,48), root:(216,78), > mode NotifyUngrab, detail NotifyVirtual, same_screen YES, > focus YES, state 0 > > KeymapNotify event, serial 13, synthetic NO, window 0x0, > keys: 90 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > FocusIn event, serial 13, synthetic NO, window 0xe00021, > mode NotifyUngrab, detail NotifyAncestor > > KeymapNotify event, serial 13, synthetic NO, window 0x0, > keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > > LeaveNotify event, serial 13, synthetic NO, window 0xe00021, > root 0x5a, subw 0xe00025, time 3569046, (205,211), root:(209,241), > mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, > focus YES, state 0 > > Does the window 0x0 in two events in the log(above) signify anything > misbehaving? > Your reply is much awaited and appreciated. > > >> -- >> Jon TURNEY >> Volunteer Cygwin/X X Server maintainer >> > -- 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/ From frederic.bron@m4x.org Fri Dec 18 06:11:00 2009 From: frederic.bron@m4x.org (=?UTF-8?B?RnLDqWTDqXJpYyBCcm9u?=) Date: Fri, 18 Dec 2009 06:11:00 -0000 Subject: screen not updated outside 1680x1050 In-Reply-To: <83E753BE7B6A324ABB336245BAF1DAAC0DA068D5@mailserver.metatv-ds.metatv.com> References: <83E753BE7B6A324ABB336245BAF1DAAC0DA068D5@mailserver.metatv-ds.metatv.com> Message-ID: >> XWin -multiwindow -clipboard -silent-dup-error >> >> ddxProcessArgument - Initializing default screens >> winInitializeDefaultScreens - w 1680 h 1050 > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?^^^^^^^^^^^^^ > Looks like the system doesn't see your whole resolution at startup. > I'd pass "-screen 0 1920x1200" to XWin.exe. ?I tried this to reduce my screen resolution, > and saw things similar to what you describe outside the declared screensize. Works fine, thanks a lot! In fact I saw only the following lines so that I thought it was OK with the resolution: 2009-12-17 13:47:46 winWindowProc - WM_DISPLAYCHANGE - orig bpp: 32, last bpp: 32, new bpp: 32 2009-12-17 13:47:46 winWindowProc - WM_DISPLAYCHANGE - new width: 1920 new height: 1200 Regards, Fr?d?ric -- 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/ From gjerlufsen@gmail.com Sat Dec 19 22:16:00 2009 From: gjerlufsen@gmail.com (gjerlufsen@gmail.com) Date: Sat, 19 Dec 2009 22:16:00 -0000 Subject: =?GB2312?B?Z2plcmx1ZnNlbiBpcyBpbnZpdGluZyB5b3UgdG8gcGxheSBFdm9ueSE=?= Message-ID: <4b2d50b4.0d67f10a.0997.577f@mx.google.com> Hello, Your friend, gjerlufsen, has invited you to play EVONY, a free online Web Browser MMOG Game that allows you to build your own empire, launch fights and trade properties. Sign up today for totally FREE! Click on the following link to sign up: http://tigj.evony.com/ Have fun! Evony Team. -- 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/ From hemal.pandya@gmail.com Sun Dec 20 06:14:00 2009 From: hemal.pandya@gmail.com (Hemal Pandya) Date: Sun, 20 Dec 2009 06:14:00 -0000 Subject: timed out waiting for reply from selection owner In-Reply-To: <50be591b0912162234r18c1097ehad7867a47653ccfa@mail.gmail.com> References: <50be591b0912152345l696732c1u878ce62e9db01b8@mail.gmail.com> <4B294258.8000804@dronecode.org.uk> <50be591b0912162234r18c1097ehad7867a47653ccfa@mail.gmail.com> Message-ID: <50be591b0912192214v2bb09c87o89d3ca0d171ff74c@mail.gmail.com> Any thoughts on this? I am heavily dependent on XEmacs/cygwin and with cut paste broken I am feeling very handicapped. Any work-around? On Thu, Dec 17, 2009 at 12:04 PM, Hemal Pandya wrote: > On Thu, Dec 17, 2009 at 1:56 AM, Jon TURNEY wrote: >> > [....]> >> Thanks for the problem report. Unfortunately it is lacking information to be useful. >> >> You might consider reading the problem reporting guidelines at [1] and trying again. ?In this particular case, attaching the /var/log/XWin.0.log to show the context for the error message is would be sensible. > > I apologize for incomplete information. > > Today I found XEmacs reporting timeout almost immediately after > starting Visual Studio. I have attached both ?XWin.0.log and output > from cygcheck. > > Best regards, > - hemal > >> >> [1] http://cygwin.com/problems.html >> >> -- >> Jon TURNEY >> Volunteer Cygwin/X X Server maintainer > -- 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/ From aw3165@att.com Mon Dec 21 16:06:00 2009 From: aw3165@att.com (WALLACE, ANDREW F (ATTLABS)) Date: Mon, 21 Dec 2009 16:06:00 -0000 Subject: RAM requirements for Cygwin/x Message-ID: Dear Cygwin/x developers, I have a laptop with 2 GB of RAM running Window XP Professional Version 2002. Do I need more RAM for Cygwin/x to work effectively? (I don't know if it matter, but I have 94 GB of hard disk memory free and a 2.26 GHz processor.) Thanks, Andrew Wallace -- 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/ From n8tm@aol.com Mon Dec 21 17:43:00 2009 From: n8tm@aol.com (Tim Prince) Date: Mon, 21 Dec 2009 17:43:00 -0000 Subject: RAM requirements for Cygwin/x In-Reply-To: References: Message-ID: <4B2FB396.3020701@aol.com> WALLACE, ANDREW F (ATTLABS) wrote: > I have a laptop with 2 GB of RAM running Window XP Professional Version > 2002. Do I need more RAM for Cygwin/x to work effectively? That seems unlikely. All problems I have with it, on a less powerful machine, go away upon reboot. This is Windows, after all. -- 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/ From reid.thompson@ateb.com Tue Dec 22 02:36:00 2009 From: reid.thompson@ateb.com (Reid Thompson) Date: Tue, 22 Dec 2009 02:36:00 -0000 Subject: RAM requirements for Cygwin/x In-Reply-To: References: Message-ID: <4B3030BF.2050204@ateb.com> WALLACE, ANDREW F (ATTLABS) wrote: > Dear Cygwin/x developers, > > I have a laptop with 2 GB of RAM running Window XP Professional Version > 2002. Do I need more RAM for Cygwin/x to work effectively? No. i've ran X with 512, 768, and 1000MB fine. I wasn't attempting to run Gnome or KDE desktops, only X applications. Not sure how resource intensive the entire desktop suite is. -- 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/ From fred@wisoft.com.br Tue Dec 22 23:38:00 2009 From: fred@wisoft.com.br (fred@wisoft.com.br) Date: Tue, 22 Dec 2009 23:38:00 -0000 Subject: Íàåìíèêè ñëåä ïîòåðÿëè Message-ID: <01ca835e.544e7c96@localhost> ????????????????, ???????????????? ?????????? ?? ?????????? ??????????????. ?????????? ?????? ?????????? ???? ?????????? ????????????! http://terapistaocupacional.com/sn/ow/ ?????? ???????? ?????????? ???????????? ?? ?????? ?????? ???????? ??????????????????. ???????????? ?? ?????? ???????????? ?????????? ???? ?????????????????? ???????????????? ???? ???????? ?????????????????????????? ?????????????????? ????????????????, ???????????????????????? ?????? ??????????????????. -- 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/ From deepali.shefali@gmail.com Wed Dec 23 12:56:00 2009 From: deepali.shefali@gmail.com (Dees) Date: Wed, 23 Dec 2009 12:56:00 -0000 Subject: Running Java application with drag and drop support in cygwin In-Reply-To: <15fe165d0912172153o5c48e300s63d80704d0c504c8@mail.gmail.com> References: <15fe165d0910272257x18264be8sadf9d778e15d8f25@mail.gmail.com> <4AE9A9A3.7090704@dronecode.org.uk> <15fe165d0910300206n2fad7c58p9c9e69ccb5fae959@mail.gmail.com> <4AFD73A0.5030407@dronecode.org.uk> <15fe165d0912132242h3626f4f2k7eccb1e652300a63@mail.gmail.com> <15fe165d0912172153o5c48e300s63d80704d0c504c8@mail.gmail.com> Message-ID: <15fe165d0912230456uc64b0fenfd4bf808c8dcecd2@mail.gmail.com> People, any clue? Struggling really hard. On Fri, Dec 18, 2009 at 11:23 AM, Dees wrote: > Hi Jon, > > Did you get a chance to look at this? > From whatever posts available online, I could not get a clue what is > going wrong. > Please respond. > > Thanks, > Shefali > > On Mon, Dec 14, 2009 at 12:12 PM, Dees wrote: >> On Fri, Nov 13, 2009 at 8:26 PM, Jon TURNEY wrote: >>> On 30/10/2009 09:06, Dees wrote: >>>> >>>> Your reply is much appreciated Jon. I will try to be more specific >>>> about the problem in further mails. >>>> >>>> On Thu, Oct 29, 2009 at 8:11 PM, Jon TURNEY >>>> wrote: >>>>> >>>>> On 28/10/2009 05:57, Dees wrote: >>>>>> >>>>>> I have developed a Java application involving jTree with extensive >>>>>> drag and drop support, which runs correctly in my Linux box. However, >>>>>> when I switch to a windows box and access the same Linux box using >>>>>> cygwin x-server, the drag and drop in jTree stops working. >>>>>> Interestingly, rest of the application still works fine. After >>>>>> analyzing a bit I found that x-server is able to recognize the drag >>>>>> event but fails to recognize a drop event. >>>>> >>>>> Details? >>>> >>>> OS : Suse Linux Enterprise Server 10 (i586) >>>> Version : 10 >>>> Patch level : 3 >>>> Other version information: >>>> Java : JDK 5 >>>> Cygwin setup-version: 2.573.2.3 >>>> Also tried using Xming 6.9.0.31 ssh same Linux setup from Windows, but >>>> that also doesn't solve the problem. >>>> >>>>> >>>>>> Is there any setting, which should be done prior to running the Java >>>>>> swing applications? >>>>>> >>>>>> Here is a sample code which behaves in exactly same way. >>>>>> http://www.java2s.com/Code/Java/Swing-JFC/TreeDragandDrop.htm >>>>> >>>>> I have no idea how to use that java code to reproduce the problem you are >>>>> seeing. >>>> >>>> Using the above java code in Linux: >>>> 1. Download and Install Java Development Toolkit on your Linux box >>>> (Java sun download site: >>>> http://java.sun.com/javase/downloads/index.jsp), if you do not have it >>>> already. >>>> 2. Save the sample code in the above link with the file name >>>> TreeTester.java, say in /home/user/ >>>> 3. Navigate to TreeTester.java from shell, and compile the java code: >>>> # cd /home/user/ >>>> # /usr/java/jdk1.5.0_14/bin/javac TreeTester.java >>>> Ignore any warnings of deprecated APIs. >>>> 4. This will create a few .class files in /home/user/ directory. Final >>>> step is to run the Java code, using: >>>> # /usr/java/jdk1.5.0_14/bin/java -classpath . TreeTester >>>> This will open up a GUI, with a jTree each on left and right pane. >>>> You can drag and drop any of the leaf nodes from one jTree to the root >>>> node of the other jTree and this should add a new node in the other >>>> jTree. You will get messages on console for the operations being >>>> performed. Now ssh the same box using cygwin/xming from any other >>>> windows box, and run the application using command in step 4. You >>>> should be able to drag (a small icon will come under cursor indicating >>>> that something is being dragged) but when you will drop it, the new >>>> node would not be added to the tree. Thats where lies my problem!!! >>> >>> Thanks for the test case and instructions, this makes it much easier for me >>> to try it out. >>> >>> However, this testcase and your jar archive both work fine for me (using >>> Xserver 1.7.1-3)! >>> >>>>>> May be my problem is related to some setting. Though, not sure. >>>>>> Has anybody come across something similar? What should be done then? >>>>>> Please let me know. >>>>> >>>>> No it's probably a bug in Cygwin/X. But you're going to need to be a lot >>>>> more specific about the problem before any progress can be made on fixing >>>>> it. >>> >>>> Also, putting some debug messages in the code lets me conclude that >>>> it's the drop event which is not being recognized, as the main control >>>> never reaches there. >>> >>> There is not really any drop event, as far as the X server is concerned, >>> just mouse click and motion events, which are passed on to you application >>> (which has a framework to interpret them as dragging and dropping an item). >>> >>> Now having a better idea of the problem, it seems less likely it is an >>> Xserver bug at all. The only Xserver cause I can think of would be if it >>> was somehow not sending the correct events to your applications window, >>> which you could test using xev -id (you can >>> use xwininfo to find the window id) >>> >> I have tried this, but could not get any idea if any event is going wrong. >> Here is the output of xev -id 0xe00021 (only for drag and drop event): >> >> LeaveNotify event, serial 13, synthetic NO, window 0xe00021, >> root 0x5a, subw 0xe00025, time 3560250, (87,65), root:(91,95), >> mode NotifyGrab, detail NotifyVirtual, same_screen YES, >> focus YES, state 256 >> >> FocusOut event, serial 13, synthetic NO, window 0xe00021, >> mode NotifyGrab, detail NotifyAncestor >> >> EnterNotify event, serial 13, synthetic NO, window 0xe00021, >> root 0x5a, subw 0xe00025, time 3565375, (212,48), root:(216,78), >> mode NotifyUngrab, detail NotifyVirtual, same_screen YES, >> focus YES, state 0 >> >> KeymapNotify event, serial 13, synthetic NO, window 0x0, >> keys: 90 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> >> FocusIn event, serial 13, synthetic NO, window 0xe00021, >> mode NotifyUngrab, detail NotifyAncestor >> >> KeymapNotify event, serial 13, synthetic NO, window 0x0, >> keys: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >> >> LeaveNotify event, serial 13, synthetic NO, window 0xe00021, >> root 0x5a, subw 0xe00025, time 3569046, (205,211), root:(209,241), >> mode NotifyNormal, detail NotifyNonlinearVirtual, same_screen YES, >> focus YES, state 0 >> >> Does the window 0x0 in two events in the log(above) signify anything >> misbehaving? >> Your reply is much awaited and appreciated. >> >> >>> -- >>> Jon TURNEY >>> Volunteer Cygwin/X X Server maintainer >>> >> > -- 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/ From jeanfrancois.simon@gmail.com Thu Dec 24 10:33:00 2009 From: jeanfrancois.simon@gmail.com (Simon Jean-Francois) Date: Thu, 24 Dec 2009 10:33:00 -0000 Subject: updating to cygwin 1.7.1: X not starting + font problem [SOLVED] Message-ID: <6661a2300912240233x5042095erbcbc237db3b3d50e@mail.gmail.com> Hello, I wanted to share some of my experiences when upgrading to cygwin 1.7.1: XWin would not start, /var/log/XWin.0.log reporting the following error: "(EE) Error compiling keymap (server-0)" After some time, I figured out the source of the problem: /bin/sh disappeared: this was fixed with " ln -s /bin/bash /bin/sh " Another problem related to fonts was fixed by " mkfontdir " Regards, Jfs -- 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/ From andy.koppe@gmail.com Thu Dec 24 10:55:00 2009 From: andy.koppe@gmail.com (Andy Koppe) Date: Thu, 24 Dec 2009 10:55:00 -0000 Subject: updating to cygwin 1.7.1: X not starting + font problem [SOLVED] In-Reply-To: <6661a2300912240233x5042095erbcbc237db3b3d50e@mail.gmail.com> References: <6661a2300912240233x5042095erbcbc237db3b3d50e@mail.gmail.com> Message-ID: <416096c60912240255j3dc5a5b5x673a938a726de89b@mail.gmail.com> 2009/12/24 Simon Jean-Francois: > I wanted to share some of my experiences when upgrading to cygwin 1.7.1: > XWin would not start, /var/log/XWin.0.log reporting the following error: > "(EE) Error compiling keymap (server-0)" > > After some time, I figured out the source of the problem: > /bin/sh disappeared: ?this was fixed with " ln -s /bin/bash /bin/sh " Hmm, /bin/sh should have been installed as part of the bash package. Did you have a message box about in-use processes during your update? Might be better to reinstall the bash package in case anything else wasn't set up correctly, but make sure you quit all Cygwin processes first. Andy -- 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/ From pficheux@prologue.fr Thu Dec 24 12:25:00 2009 From: pficheux@prologue.fr (patrick ficheux) Date: Thu, 24 Dec 2009 12:25:00 -0000 Subject: Why XWin expose multiple visuals with same depth/colormap ? Message-ID: <4B335DB3.9080804@prologue.fr> Hello, It seems that XWin exposes a lot of Visuals with same caracteristics (depth / colormap). xdpyinfo displays 33 visuals of 2 type : TrueColor / 24 bits DirectColor / 24 bits Is there a reason to expose 15 identical TrueColor visuals and 16 identical DirectColor visuals ? Regards -- 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/ From namux@mail.ru Fri Dec 25 19:20:00 2009 From: namux@mail.ru (=?windows-1251?Q?=C4=EC=E8=F2=F0=E8=E9_=D2=F0=E5=E1=E8=F7?=) Date: Fri, 25 Dec 2009 19:20:00 -0000 Subject: =?windows-1251?Q?1.7.1=3A_xterm_osc_52_copy/paste_bug=3F?= Message-ID: Hi! I just have installed 1.7.1 release and try xterm osc 52 copy/paste escape sequences - they have work in the beta release. The paste seq: echo -ne "\033]52;;?\033\\" works justr fine, but copy seq: echo -ne "\033]52;;cXdlcnR5\033\\" didn't works ("cXdlcnR5" is base64 encodig for "qwerty"). Any suggestions? It seems like or xterm bug, or I missing something in the configuration. Thank you dmitry -- 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/ From Michi_cc@gmx.net Sat Dec 26 17:00:00 2009 From: Michi_cc@gmx.net (Michael Lutz) Date: Sat, 26 Dec 2009 17:00:00 -0000 Subject: X server fails to start In-Reply-To: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> References: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> Message-ID: Am 17.12.2009 14:48 schrieb Csaba Raduly: > X used to work for quite a while but now it doesn't. The X icon > appears and disappears. > It seems to have developed a fixation with "another window manager", > according to the log. Not even a reboot helps. I have the same problem after upgrading to 1.7.1. Commenting the checkX call in startxwin.bat out and replacing it with 'sleep 5' makes it work for me. Michael Lutz -- PGP encrypted mails preferred. 4096/1024-bit DH/DSS key, ID 0x31DEFEF1, created 2001-03-02 FP: 5305 7CF5 09E9 EFF6 E12F D3D2 CD12 A090 31DE FEF1 -- 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/ From albert.xtheunknown0@gmail.com Sat Dec 26 21:46:00 2009 From: albert.xtheunknown0@gmail.com (xtheunknown0) Date: Sat, 26 Dec 2009 21:46:00 -0000 Subject: Setup for "basic" development Message-ID: <26930106.post@talk.nabble.com> Hi, I've used various distros of Linux *just* long enough to know commands like ls, cat, gcc something -o something, and cd. I was trying to setup Cygwin but when I got to the window with stacks of checkboxes to tick or not tick I got bewildered. What do I tick so that I can compile simple C programs, use basic Unix commands, have Vim, ie. use a Linux shell to replace Command Prompt? TIA Albert -- View this message in context: http://old.nabble.com/Setup-for-%22basic%22-development-tp26930106p26930106.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/ From cgf-use-the-mailinglist-please@cygwin.com Sat Dec 26 23:41:00 2009 From: cgf-use-the-mailinglist-please@cygwin.com (Christopher Faylor) Date: Sat, 26 Dec 2009 23:41:00 -0000 Subject: Setup for "basic" development In-Reply-To: <26930106.post@talk.nabble.com> References: <26930106.post@talk.nabble.com> Message-ID: <20091226234125.GC21254@ednor.casa.cgf.cx> On Sat, Dec 26, 2009 at 01:46:07PM -0800, xtheunknown0 wrote: > >Hi, I've used various distros of Linux *just* long enough to know commands >like ls, cat, gcc something -o something, and cd. I was trying to setup >Cygwin but when I got to the window with stacks of checkboxes to tick or not >tick I got bewildered. What do I tick so that I can compile simple C >programs, use basic Unix commands, have Vim, ie. use a Linux shell to >replace Command Prompt? This has nothing to do with Cygwin/X. Please check out the mailing lists at http://cygwin.com/lists.html and then decide to move to the cygwin mailing list. To answer your question, the basic Cygwin install will provide you with the bash shell. If you want 'vim', then check the 'vim' checkbox. If you want a compiler use 'gcc'. -- 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/ From venkatt123@yahoo.com Mon Dec 28 14:34:00 2009 From: venkatt123@yahoo.com (Venkatesan Ekambaram) Date: Mon, 28 Dec 2009 14:34:00 -0000 Subject: XWin Server Not Starting Message-ID: <442150.51612.qm@web57616.mail.re1.yahoo.com> Hello, ? ??????????????? When I am trying the to start Xwin server, I am getting the following exception in the log. ? ??????????????? /var/log/Xwin.0.log contents: ??????????????? Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.1.0 (10701000) Build Date: 2009-11-11 ? Contact: cygwin-xfree@cygwin.com ? XWin was started with the following command line: ? XWin -multiwindow -clipboard -silent-dup-error ? ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1024 h 768 winInitializeDefaultScreens - Returning 2009-12-25 02:28:37 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2009-12-25 02:28:37 _XSERVTransOpen: transport open failed for inet6/Gadag:0 2009-12-25 02:28:37 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2009-12-25 02:28:37 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-12-25 02:28:37 (II) xorg.conf is not supported 2009-12-25 02:28:37 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.htmlfor more information 2009-12-25 02:28:37 winPrefsLoadPreferences: /etc/X11/system.XWinrc 2009-12-25 02:28:37 LoadPreferences: Done parsing the configuration file... 2009-12-25 02:28:37 winGetDisplay: DISPLAY=:0.0 2009-12-25 02:28:37 winDetectSupportedEngines - Windows NT/2000/XP 2009-12-25 02:28:37 winDetectSupportedEngines - DirectDraw installed 2009-12-25 02:28:37 winDetectSupportedEngines - DirectDraw4 installed 2009-12-25 02:28:37 winDetectSupportedEngines - Returning, supported engines 00000007 2009-12-25 02:28:37 winSetEngine - Multi Window or Rootless => ShadowGDI 2009-12-25 02:28:37 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-12-25 02:28:37 winAllocateFBShadowGDI - Creating DIB with width: 1024 height: 768 depth: 32 2009-12-25 02:28:37 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff 2009-12-25 02:28:37 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 2009-12-25 02:28:37 null screen fn ReparentWindow 2009-12-25 02:28:37 null screen fn RestackWindow 2009-12-25 02:28:37 InitQueue - Calling pthread_mutex_init 2009-12-25 02:28:37 InitQueue - pthread_mutex_init returned 2009-12-25 02:28:37 InitQueue - Calling pthread_cond_init 2009-12-25 02:28:37 InitQueue - pthread_cond_init returned 2009-12-25 02:28:37 winInitMultiWindowWM - Hello 2009-12-25 02:28:37 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-12-25 02:28:37 Screen 0 added at XINERAMA coordinate (0,0). 2009-12-25 02:28:37 winMultiWindowXMsgProc - Hello 2009-12-25 02:28:37 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-12-25 02:28:37 MIT-SHM extension disabled due to lack of kernel support 2009-12-25 02:28:37 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-12-25 02:28:37 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-12-25 02:28:37 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-12-25 02:28:38 (EE) Error compiling keymap (server-0) 2009-12-25 02:28:38 (EE) XKB: Couldn't compile keymap 2009-12-25 02:28:38 XKB: Failed to compile keymap 2009-12-25 02:28:38 Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. 2009-12-25 02:28:38 Fatal server error: 2009-12-25 02:28:38 Failed to activate core devices. ? ??????????????? Can you please help me in getting Xwin server started. ? Thanks Venkat -- 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/ From freedai@hotmail.com Mon Dec 28 21:40:00 2009 From: freedai@hotmail.com (Feng Dai) Date: Mon, 28 Dec 2009 21:40:00 -0000 Subject: X server fails to start References: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> Message-ID: Michael Lutz gmx.net> writes: > > Am 17.12.2009 14:48 schrieb Csaba Raduly: > > X used to work for quite a while but now it doesn't. The X icon > > appears and disappears. > > It seems to have developed a fixation with "another window manager", > > according to the log. Not even a reboot helps. > > I have the same problem after upgrading to 1.7.1. Commenting the checkX > call in startxwin.bat out and replacing it with 'sleep 5' makes it work > for me. > > Michael Lutz The root cause is checkX doesn't work properly. It cause XWin failed on initClipboard and exit itself. The work around is either comment out checkX or have a "sleep 3" to let XWin server startup before checkX runs. Feng -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 04:17:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 04:17:00 -0000 Subject: [ANNOUNCEMENT] [1.7] Updated: libxcb-1.5-1, xcb-proto-1.6-1 Message-ID: The following packages have been updated for Cygwin 1.7: * libxcb1-1.5-1 * libxcb-composite-devel-1.5-1 * libxcb-composite0-1.5-1 * libxcb-damage-devel-1.5-1 * libxcb-damage0-1.5-1 * libxcb-devel-1.5-1 * libxcb-doc-1.5-1 * libxcb-dpms-devel-1.5-1 * libxcb-dpms0-1.5-1 * libxcb-glx-devel-1.5-1 * libxcb-glx0-1.5-1 * libxcb-randr-devel-1.5-1 + libxcb-randr0-1.5-1 * libxcb-record-devel-1.5-1 * libxcb-record0-1.5-1 * libxcb-render-devel-1.5-1 * libxcb-render0-1.5-1 * libxcb-res-devel-1.5-1 * libxcb-res0-1.5-1 * libxcb-screensaver-devel-1.5-1 * libxcb-screensaver0-1.5-1 * libxcb-shape-devel-1.5-1 * libxcb-shape0-1.5-1 * libxcb-shm-devel-1.5-1 * libxcb-shm0-1.5-1 * libxcb-sync-devel-1.5-1 * libxcb-sync0-1.5-1 * libxcb-xfixes-devel-1.5-1 * libxcb-xfixes0-1.5-1 * libxcb-xinerama-devel-1.5-1 * libxcb-xinerama0-1.5-1 * libxcb-xinput-devel-1.5-1 * libxcb-xinput0-1.5-1 * libxcb-xtest-devel-1.5-1 * libxcb-xtest0-1.5-1 * xcb-proto-1.6-1 libxcb provides an interface to the X Window System protocol, which replaces the current Xlib interface. This is an upstream bugfix release. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 04:17:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 04:17:00 -0000 Subject: [ANNOUNCEMENT] [1.7] Updated: xorg-server-1.7.3-1 Message-ID: The following package has been updated for Cygwin 1.7: * xorg-server-1.7.3-1 This package contains XWin and the other X.Org X11 servers. This is an update to the latest stable upstream release. Support for the Composite extension has been disabled as it has been broken since 1.7.1. We hope to re-enable it in a future release, once we have diagnosed and fixed the problem. The following patches has been added in this release: - Restore -nolock option. - Allow resizing of transient windows. - Avoid log spam from Fedora 12 wait cursor. - Avoid server termination when XDMCP kills internal clipboard manager. Clipboard integration will not be available but the session will continue. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 04:53:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 04:53:00 -0000 Subject: [ANNOUNCEMENT] New package: qt4-4.5.3-1 Message-ID: Qt4, the latest version of Trolltech's C++ application framework, has been added to the Cygwin distribution. Due to its size and dependencies, Qt4 has been broken up into over three dozen packages: * libQt*4: runtime libraries, one per API * libQt*4-devel: corresponding headers, link libraries, and tools * qt4-devel-tools: assistant, designer, linguist, etc. * qt4-doc: API documentation (viewable with assistant-qt4) * qt4-qtconfig: Qt configuration manager * qt4-qtdemo: example programs and source code If you have difficulty finding a particular file, please use the Cygwin package search page at http://cygwin.com/packages/ . Qt4 can be installed in parallel to the Qt3 packages. The tools which exist for both versions have a "-qt4" suffix in their /usr/bin symlinks; e.g. qmake-qt4, qtconfig-qt4, etc. Please note that the Phonon multimedia abstraction layer is not supported in this release, due to its additional dependencies which are not yet in the distro. Consequently, QtWebKit browsers such as Arora will not have support for HTML5 audio/video. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 04:56:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 04:56:00 -0000 Subject: [ANNOUNCEMENT] Updated: openbox-3.4.9-1 Message-ID: The following package has been updated for Cygwin 1.7: *** openbox-3.4.9-1 Openbox is a highly configurable, next generation window manager with extensive standards support. This is an update to the latest upstream release. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From cygwin@cwilson.fastmail.fm Tue Dec 29 07:01:00 2009 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Tue, 29 Dec 2009 07:01:00 -0000 Subject: X server fails to start In-Reply-To: References: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> Message-ID: <4B39A925.1050309@cwilson.fastmail.fm> Feng Dai wrote: > The root cause is checkX doesn't work properly. It cause XWin failed on > initClipboard and exit itself. The work around is either comment out checkX or > have a "sleep 3" to let XWin server startup before checkX runs. It's actually not checkX's fault that the Xserver dies. All checkX does is try to call XOpenDisplay(). However, in the current usage by the startup scripts, checkX will do so /repeatedly/ during the period when the Xserver is just getting started. XWin appears to be fragile at that stage in its execution. So, the latest version of checkX tries to be gentle with the Xserver when that Xserver is just launching. To try it out, you should make the relevant part of startxwin.bat look like this: ... %RUN% bash -l -c "XWin -multiwindow -clipboard -silent-dup-error" REM Make sure XWin is ready to accept connections before proceeding checkX -d %DISPLAY% -t 12 ... That is, don't use %RUN% to invoke checkX. -- Chuck -- 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/ From cygwin@cwilson.fastmail.fm Tue Dec 29 07:02:00 2009 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Tue, 29 Dec 2009 07:02:00 -0000 Subject: X server fails to start In-Reply-To: <4B39A925.1050309@cwilson.fastmail.fm> References: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> <4B39A925.1050309@cwilson.fastmail.fm> Message-ID: <4B39A951.6010203@cwilson.fastmail.fm> Charles Wilson wrote: > So, the latest version of checkX I guess I should be specific: that's checkX from the run2-0.4.0-1 package, which should begin hitting the mirrors soon. -- Chuck -- 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/ From freedai@hotmail.com Tue Dec 29 17:03:00 2009 From: freedai@hotmail.com (Feng Dai) Date: Tue, 29 Dec 2009 17:03:00 -0000 Subject: X server fails to start References: <1ef5a52f0912170548i3ccc5b65ia768141d7ba31cd8@mail.gmail.com> <4B39A925.1050309@cwilson.fastmail.fm> <4B39A951.6010203@cwilson.fastmail.fm> Message-ID: Charles Wilson cwilson.fastmail.fm> writes: > I guess I should be specific: that's checkX from the run2-0.4.0-1 > package, which should begin hitting the mirrors soon. > > -- > Chuck > I downloaded latest run2-0.4.0-1. One of machine is still failing. one Windows 7 and another XP work though. -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 20:58:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 20:58:00 -0000 Subject: [ANNOUNCEMENT] Updated: xinit-1.2.0-2 Message-ID: The following package has been updated in the Cygwin distribution: * xinit-1.2.0-2 This package includes the startx, startxdmcp.bat, and startxwin commands for launching the XWin server. IMPORTANT: THE startxwin.bat AND startxwin.sh SCRIPTS ARE NO LONGER SUPPORTED. This release replaces those scripts with a startxwin executable. By default, startxwin will launch an XWin server in multiwindow mode together with an xterm. A $HOME/.startxwinrc file can be created with a list of commands for startxwin to launch instead of an xterm. startxwin also accepts command line arguments to use a different DISPLAY number and add additional options to pass to the server. Please read the startxwin(1) manpage, which describes both the command-line arguments accepted by startxwin and the format of the $HOME/.startxwinrc file. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- 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/ From jjreisert@alum.mit.edu Tue Dec 29 22:15:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Tue, 29 Dec 2009 22:15:00 -0000 Subject: Updated: xinit-1.2.0-2 In-Reply-To: <4B3A6D32.9050606@users.sourceforge.net> References: <4B3A6D32.9050606@users.sourceforge.net> Message-ID: <806a89db0912291415i56b4372l44431b1062b9ac1a@mail.gmail.com> On Tue, Dec 29, 2009 at 1:57 PM, Yaakov (Cygwin/X) wrote: > This release replaces those scripts with a startxwin executable. Should we use "run" to launch startxwin.exe, or is it OK to just create a shortcut to startxwin.exe? - Jim -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From cygwin@cwilson.fastmail.fm Tue Dec 29 22:28:00 2009 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Tue, 29 Dec 2009 22:28:00 -0000 Subject: [ANNOUNCEMENT] Updated: xinit-1.2.0-2 In-Reply-To: References: Message-ID: <4B3A824F.2080509@cwilson.fastmail.fm> Yaakov (Cygwin/X) wrote: > IMPORTANT: THE startxwin.bat AND startxwin.sh SCRIPTS ARE NO LONGER > SUPPORTED. > > This release replaces those scripts with a startxwin executable. ! Sounds like a good idea, but I wish I'd known this was coming before wasting time on: 2009-12-29 run2-0.4.0 (release) ... * Improve checkX behavior when used as 'barrier' in startxwin. ... Oh, well. -- Chuck -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 23:08:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 23:08:00 -0000 Subject: Updated: xinit-1.2.0-2 In-Reply-To: <806a89db0912291415i56b4372l44431b1062b9ac1a@mail.gmail.com> References: <4B3A6D32.9050606@users.sourceforge.net> <806a89db0912291415i56b4372l44431b1062b9ac1a@mail.gmail.com> Message-ID: <4B3A8BD8.3030903@users.sourceforge.net> On 29/12/2009 16:15, Jim Reisert AD1C wrote: > Should we use "run" to launch startxwin.exe, or is it OK to just > create a shortcut to startxwin.exe? In general, you should be using run.exe in Windows shortcuts. The Start Menu shortcut created during postinstall goes a step further, running: \path\to\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe IOW startxwin is launched from within a login shell so that it knows where to find HOME (for .startxwinrc) and so that clients launched thereby inherit a complete user environment. Yaakov Cygwin/X -- 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/ From yselkowitz@users.sourceforge.net Tue Dec 29 23:32:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 29 Dec 2009 23:32:00 -0000 Subject: [ANNOUNCEMENT] Updated: xinit-1.2.0-2 In-Reply-To: <4B3A824F.2080509@cwilson.fastmail.fm> References: <4B3A824F.2080509@cwilson.fastmail.fm> Message-ID: <4B3A9187.8030806@users.sourceforge.net> On 29/12/2009 16:27, Charles Wilson wrote: > Sounds like a good idea, but I wish I'd known this was coming before > wasting time on: > > * Improve checkX behavior when used as 'barrier' in startxwin. Sorry about that, Chuck, but this was just the latest of a long string of issues involving these scripts. We've been talking about replacing them for a while, and the recent traffic on the list was enough of an impetus to make me finally stop bandaging the scripts and find a better solution. Plus, we gain argument handling and .startxwinrc, something the scripts would likely never do. Honestly, this wasn't even checkX's fault, so we weren't expecting you to "fix" it. The real problem here is a corner-case bug in the server; the race condition that checkX was causing was just the trigger. We still need to get to the bottom of that, but in the meantime we have a solution that completely avoids the problem and gives us new features to boot. Yaakov Cygwin/X -- 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/ From cygwin@cwilson.fastmail.fm Wed Dec 30 00:31:00 2009 From: cygwin@cwilson.fastmail.fm (Charles Wilson) Date: Wed, 30 Dec 2009 00:31:00 -0000 Subject: [ANNOUNCEMENT] Updated: xinit-1.2.0-2 In-Reply-To: <4B3A9187.8030806@users.sourceforge.net> References: <4B3A824F.2080509@cwilson.fastmail.fm> <4B3A9187.8030806@users.sourceforge.net> Message-ID: <4B3A9F4B.4070508@cwilson.fastmail.fm> Yaakov (Cygwin/X) wrote: > On 29/12/2009 16:27, Charles Wilson wrote: >> Sounds like a good idea, but I wish I'd known this was coming before >> wasting time on: >> >> * Improve checkX behavior when used as 'barrier' in startxwin. > > Sorry about that, Chuck, but this was just the latest of a long string > of issues involving these scripts. We've been talking about replacing > them for a while, and the recent traffic on the list was enough of an > impetus to make me finally stop bandaging the scripts and find a better > solution. Plus, we gain argument handling and .startxwinrc, something > the scripts would likely never do. Like I said, it sounds to me like a good idea; there's just so many issues that can go (and have gone) wrong in these scripts -- PLUS, whose idea was it to have TWO, one .sh and one .bat?!!? Yeeesh. We're well rid of them. > Honestly, this wasn't even checkX's fault, so we weren't expecting you > to "fix" it. The real problem here is a corner-case bug in the server; > the race condition that checkX was causing was just the trigger. We > still need to get to the bottom of that, but in the meantime we have a > solution that completely avoids the problem and gives us new features to > boot. Yes, it definitely seemed like some sort of race going on -- I even noticed sometimes that checkX would return success (e.g. was able to call XOpenDisplay()), but that the very next command in my startxwin.sh script would fail with a "can't open display" error. Err...what? So, yeah, I think startxwin.exe/.startxwinrc is a really excellent step forward. -- Chuck -- 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/ From jjreisert@alum.mit.edu Wed Dec 30 01:08:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Wed, 30 Dec 2009 01:08:00 -0000 Subject: What is correct way to start xterm from .XWinrc? In-Reply-To: <806a89db0910280917k187ee65fy40775ed371771563@mail.gmail.com> References: <806a89db0910280917k187ee65fy40775ed371771563@mail.gmail.com> Message-ID: <806a89db0912291708m75157077mde1cd2b1bd37b501@mail.gmail.com> On Wed, Oct 28, 2009 at 9:17 AM, Jim Reisert AD1C wrote: > My .XWinrc file has this menu line: > > ? ? ? ?"xterm" ? ? ?EXEC ?"xterm -e tcsh" > > Since my default shell in /etc/passwd is /bin/tcsh, why should I need > to specify it here also? ?If I don't specify it, a new xterm doesn't > execute my ~/.cshrc file. ?I do not have a ~/.login or ~/.profile > file. > > What is the right way to do this? Using the new startwin.exe in my Startup folder shortcut: C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe My .XWinrc now has simply: "xterm" EXEC "xterm" -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From ericmho@shaw.ca Wed Dec 30 05:23:00 2009 From: ericmho@shaw.ca (ERIC HO) Date: Wed, 30 Dec 2009 05:23:00 -0000 Subject: Cygwin 1.7 beta XWin Crashs from Ubuntun 9.10 after Firefox sessions (update) Message-ID: After I upgraded to xorg-server1.7.3-1, XWin does not crash anymore after I ssh to Ubuntun 9.10 invoking gnome-session. But it hangs intermittently after a few Firefox sessions and I need to terminate XWin. Hope the next xorg-server upgrade will improve this. -- 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/ From jjreisert@alum.mit.edu Wed Dec 30 17:07:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Wed, 30 Dec 2009 17:07:00 -0000 Subject: Can't start xterm from Cygwin/X icon in system tray Message-ID: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> I have a very strange situation. At work, I am running Win XP SP3. I installed all the latest Cygwin (1.7.1) + Xorg updates, including startxwin.exe. Everything works perfectly. At home, I am running Windows 7 Professional, 64-bit. I am unable to start an xterm from the Cygwin/X icon in the system tray (right-click, select xterm). Both setups have the same line in .XWinrc: "xterm" EXEC "xterm" I am starting the X server the same way: D:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I do not have a ~/.startxwinrc file. The xterm that is supposed to be created when the server starts doesn't start either. The symptom is that xterm.exe is shown running in the task manager, but there is no Xterm window on the desktop. As a work-around, I created a shortcut on my desktop to start an xterm: D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 That works perfectly, but is not an optimum solution (I try to have as few desktop icons as possible). There is nothing in the /var/log/Xwin log that indicates why an xterm would start but not open a window. Any ideas? -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From Brian.Timares@va.gov Wed Dec 30 17:53:00 2009 From: Brian.Timares@va.gov (Timares, Brian (Harris Corp.)) Date: Wed, 30 Dec 2009 17:53:00 -0000 Subject: xterm process exists but no window appears when XWin Server launched (current release) In-Reply-To: References: Message-ID: <270AA78168E41541833C52448F4F34AD1DF063E4@VHAISHMSGJ2.vha.med.va.gov> Summary: After a fresh install of 1.7 including the startxwin and run2 changes when I launch Cygwin-X an xterm process is running, but I see no window. cygcheck shows 2 potential conflicts (see bottom of email) Steps: I deleted all of cygwin, and installed fresh, getting the release of 1.7 (Cygwin/X X Server says 1.7.3). I updated this morning, Dec 30, restarted and didn't sign on to the VPN (essentially Cisco). McAfee Agent 4, BlackIce, and Pointsec whole-drive encryption are installed, Window Firewall is off. I launched Start > Programs > Cygwin-X > XWin Server, which is C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I got XWin.exe and xterm.exe as processes in the Task Manager but no window appeared. The X icon appeared in the icon tray (is that the right term? The lower right area next to the time). Selecting xterm from its right-click popup didn't work (no window, no additional process). I have enclosed the XWin.0.log renamed to XWin.0-bt20091230.log, I have marked off the lines that appeared after I force-quit the non-appearing xterm. I have also enclosed the results of cygcheck -s -v -r > cygcheck-bt20091230.out What did work was launching Start > Programs > Cygwin > Cygwin Bash Shell, and nohup xterm & (so I could close the bash shell), which is where I ran the cygcheck. Information: WinXP SP3, I installed every font I could find in Setup :), I didn't even think of changing anything after the install, I made sure I had the latest versions announced as of this morning. I checked the FAQ, looked over the XWin.0 log, looked over the cygcheck output which shows: Sonic Solutions burning software containing DLA component Detected: Named process. ZoneAlarm Personal Firewall Detected: HKLM Registry Key, Named file. I had rebooted since last I used the Sonic Solutions (I can remove it if it is worth trying), the ZoneAlarm I have no control over (nor the other security-related items). I hope this is enough and complete, but if not, let me know! Brian Timares -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0-bt20091230.log Type: application/octet-stream Size: 4540 bytes Desc: XWin.0-bt20091230.log URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck-bt20091230.out Type: application/octet-stream Size: 60371 bytes Desc: cygcheck-bt20091230.out URL: -------------- next part -------------- -- 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/ From ericmho@shaw.ca Wed Dec 30 19:57:00 2009 From: ericmho@shaw.ca (ERIC HO) Date: Wed, 30 Dec 2009 19:57:00 -0000 Subject: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1) Message-ID: Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up the x server and the xterm. I then entered exit on the xterm to terminate the xterm. I got Xwin Fatal error. The last few messages in Xwin.0.log are as follows: 2009-12-30 12:45:31 DetectUnicodeSupport - Windows NT/2000/XP 2009-12-30 12:45:31 winGetDisplay: DISPLAY=:0.0 2009-12-30 12:45:31 winClipboardProc - DISPLAY=:0.0 2009-12-30 12:45:31 winClipboardProc - XOpenDisplay () returned and successfully opened the display. 2009-12-30 12:45:37 winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. 2009-12-30 12:45:37 winClipboardProc - XDestroyWindow succeeded. 2009-12-30 12:45:37 Segmentation fault at address 0x268 2009-12-30 12:45:37 Fatal server error: 2009-12-30 12:45:37 Caught signal 11 (Segmentation fault). Server aborting Does anyone gets the similar messages? Thanks. -- 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/ From yselkowitz@users.sourceforge.net Wed Dec 30 22:13:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Wed, 30 Dec 2009 22:13:00 -0000 Subject: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1) In-Reply-To: References: Message-ID: <4B3BD098.3000708@users.sourceforge.net> On 30/12/2009 13:57, ERIC HO wrote: > Hi there, I'm running cygwin 1.7.1. I entered xinit and it brought up > the x server and the xterm. I then entered exit on the xterm to > terminate the xterm. I got Xwin Fatal error. > Problem reports: http://cygwin.com/problems.html ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Yaakov Cygwin/X -- 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/ From crawford.carl@csuptwo.com Thu Dec 31 03:20:00 2009 From: crawford.carl@csuptwo.com (Carl R. Crawford) Date: Thu, 31 Dec 2009 03:20:00 -0000 Subject: X11 assertion fails Message-ID: <18E20F2ADD5241F19C423AB5F71AEA33@carllt> I just upgraded to the latest version of X11. A program that previously worked fine now reports the following error: assertion "ret != inval_id" failed: file "/usr/src/ports/xorg/libX11/libX11-1.3.2-2/src/libX11-1.3.2/src/xcb_io.c", line 385, function: _XAllocID Aborted (core dumped) How do I fix this? Thanks, --Carl -- 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/ From ericmho@shaw.ca Thu Dec 31 04:10:00 2009 From: ericmho@shaw.ca (ERIC HO) Date: Thu, 31 Dec 2009 04:10:00 -0000 Subject: Fwd: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1) Message-ID: Please see the attahced files for problem doc. Thanks. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: cygcheck.out URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 3337 bytes Desc: not available URL: -------------- next part -------------- An embedded message was scrubbed... From: ERIC HO Subject: xinit-1.2.0-2 and Xwin Fatal error (xorg-server1.7.3-1) Date: Wed, 30 Dec 2009 12:57:36 -0700 Size: 1555 URL: -------------- next part -------------- -- 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/ From dahaiou@gmail.com Thu Dec 31 13:33:00 2009 From: dahaiou@gmail.com (dahaiou) Date: Thu, 31 Dec 2009 13:33:00 -0000 Subject: Can't start xterm from Cygwin/X icon in system tray In-Reply-To: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> References: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> Message-ID: <26977792.post@talk.nabble.com> Jim Reisert AD1C wrote: > > I am unable to start an xterm from the Cygwin/X icon in the system tray > (right-click, select xterm). Both setups have the same line in .XWinrc: > "xterm" EXEC "xterm" > As a work-around, I created a shortcut on my desktop to start an xterm: > D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 > That works perfectly, What exact command is mapped to the "xterm" label in the right-click tray menu? It's configured in an init file somewhere though I can't remember the filename right now. Can you check whether the DISPLAY variable is set in the xterm process started from the tray menu? If it isn't, that would explain it. -- View this message in context: http://old.nabble.com/Can%27t-start-xterm-from-Cygwin-X-icon-in-system-tray-tp26969798p26977792.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/ From jjreisert@alum.mit.edu Thu Dec 31 15:35:00 2009 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Thu, 31 Dec 2009 15:35:00 -0000 Subject: Can't start xterm from Cygwin/X icon in system tray In-Reply-To: <26977792.post@talk.nabble.com> References: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> <26977792.post@talk.nabble.com> Message-ID: <806a89db0912310735q20ecf0b4u2948e8d2ed3c6b4@mail.gmail.com> On Thu, Dec 31, 2009 at 6:33 AM, dahaiou wrote: > > > Jim Reisert AD1C wrote: >> >> I am unable to start an xterm from the Cygwin/X icon in the system tray >> (right-click, select xterm). ?Both setups have the same line in .XWinrc: >> ? ? ? ? "xterm" ? ? ?EXEC ?"xterm" >> As ?a work-around, I created a shortcut on my desktop to start an xterm: >> ? ? D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 >> That works perfectly, > > What exact command is mapped to the "xterm" label in the right-click tray > menu? It's configured in an init file somewhere though I can't remember the > filename right now. "which" points to /usr/bin/xterm > Can you check whether the DISPLAY variable is set in the xterm process > started from the tray menu? If it isn't, that would explain it. I tried this explicitly: "xterm" EXEC "xterm -display localhost:0" That didn't make a difference. One other piece of data: I modifed ~/.XWinrc and then clicked "Reload .xwinrc" from the menu in the system tray. This KILLED the X server! - Jim -- Jim Reisert AD1C, , http://www.ad1c.us -- 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/ From john@asyn.org Thu Dec 31 15:53:00 2009 From: john@asyn.org (john@asyn.org) Date: Thu, 31 Dec 2009 15:53:00 -0000 Subject: Can't start xterm from Cygwin/X icon in system tray In-Reply-To: <806a89db0912310735q20ecf0b4u2948e8d2ed3c6b4@mail.gmail.com> References: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> <26977792.post@talk.nabble.com> <806a89db0912310735q20ecf0b4u2948e8d2ed3c6b4@mail.gmail.com> Message-ID: I had this problem. It was happening because PATH was not being set. The problem went away when I used /startxwin.bat instead of /bin/startxwin.exe. On Thu, 31 Dec 2009, Jim Reisert AD1C wrote: > On Thu, Dec 31, 2009 at 6:33 AM, dahaiou wrote: > > > > > > Jim Reisert AD1C wrote: > >> > >> I am unable to start an xterm from the Cygwin/X icon in the system tray > >> (right-click, select xterm). ??Both setups have the same line in .XWinrc: > >> ?? ?? ?? ?? "xterm" ?? ?? ??EXEC ??"xterm" > >> As ??a work-around, I created a shortcut on my desktop to start an xterm: > >> ?? ?? D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 > >> That works perfectly, > > > > What exact command is mapped to the "xterm" label in the right-click tray > > menu? It's configured in an init file somewhere though I can't remember the > > filename right now. > > "which" points to /usr/bin/xterm > > > Can you check whether the DISPLAY variable is set in the xterm process > > started from the tray menu? If it isn't, that would explain it. > > I tried this explicitly: > > "xterm" EXEC "xterm -display localhost:0" > > That didn't make a difference. > > One other piece of data: I modifed ~/.XWinrc and then clicked "Reload > .xwinrc" from the menu in the system tray. This KILLED the X server! > > - Jim > > > -- Hendrik Groeneveld +1 (425) 327-4506 +1 (425) 645-8027 Fax hendrik@hg.com -------------- next part -------------- -- 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/ From kbrown@cornell.edu Thu Dec 31 16:28:00 2009 From: kbrown@cornell.edu (Ken Brown) Date: Thu, 31 Dec 2009 16:28:00 -0000 Subject: Can't start xterm from Cygwin/X icon in system tray In-Reply-To: References: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> <26977792.post@talk.nabble.com> <806a89db0912310735q20ecf0b4u2948e8d2ed3c6b4@mail.gmail.com> Message-ID: <4B3CD139.7070809@cornell.edu> On 12/31/2009 10:53 AM, john at asyn dot org wrote: > On Thu, 31 Dec 2009, Jim Reisert AD1C wrote: >>> Jim Reisert AD1C wrote: >>>> >>>> I am unable to start an xterm from the Cygwin/X icon in the system tray >>>> (right-click, select xterm). Both setups have the same line in .XWinrc: >>>> "xterm" EXEC "xterm" >>>> As a work-around, I created a shortcut on my desktop to start an xterm: >>>> D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 >>>> That works perfectly, [...] >> I tried this explicitly: >> >> "xterm" EXEC "xterm -display localhost:0" >> >> That didn't make a difference. >> >> One other piece of data: I modifed ~/.XWinrc and then clicked "Reload >> .xwinrc" from the menu in the system tray. This KILLED the X server! > > I had this problem. It was happening because PATH was not being set. > The problem went away when I used /startxwin.bat instead of > /bin/startxwin.exe. If PATH is not being set, then you're probably not running startxwin.exe from a login shell. See http://cygwin.com/ml/cygwin-xfree/2009-12/msg00117.html Ken -- 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/ From yselkowitz@users.sourceforge.net Thu Dec 31 18:34:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 31 Dec 2009 18:34:00 -0000 Subject: X11 assertion fails In-Reply-To: <18E20F2ADD5241F19C423AB5F71AEA33@carllt> References: <18E20F2ADD5241F19C423AB5F71AEA33@carllt> Message-ID: <4B3CEEC2.3030003@users.sourceforge.net> On 30/12/2009 21:20, Carl R. Crawford wrote: > I just upgraded to the latest version of X11. A program that previously > worked fine now reports the following error: > > assertion "ret != inval_id" failed: file > "/usr/src/ports/xorg/libX11/libX11-1.3.2-2/src/libX11-1.3.2/src/xcb_io.c", > line 385, function: _XAllocID > Aborted (core dumped) > > How do I fix this? Start here: > Problem reports: http://cygwin.com/problems.html Yaakov Cygwin/X -- 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/ From yselkowitz@users.sourceforge.net Thu Dec 31 19:20:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 31 Dec 2009 19:20:00 -0000 Subject: xterm process exists but no window appears when XWin Server launched (current release) In-Reply-To: <270AA78168E41541833C52448F4F34AD1DF063E4@VHAISHMSGJ2.vha.med.va.gov> References: <270AA78168E41541833C52448F4F34AD1DF063E4@VHAISHMSGJ2.vha.med.va.gov> Message-ID: <4B3CF977.3090504@users.sourceforge.net> On 30/12/2009 11:52, Timares, Brian (Harris Corp.) wrote: > I checked the FAQ, looked over the XWin.0 log, looked over the cygcheck > output which shows: > Sonic Solutions burning software containing DLA component > Detected: Named process. > > ZoneAlarm Personal Firewall > Detected: HKLM Registry Key, Named file. > > I had rebooted since last I used the Sonic Solutions (I can remove it if > it is worth trying), the ZoneAlarm I have no control over (nor the other > security-related items). BLODA often needs to be completely uninstalled, followed by a reboot, for it not to interfere. ZA is a known troublemaker wrt Cygwin, so if you can't remove it, then I'm not sure that we'll be able to help. Yaakov Cygwin/X -- 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/ From yselkowitz@users.sourceforge.net Thu Dec 31 20:43:00 2009 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 31 Dec 2009 20:43:00 -0000 Subject: Can't start xterm from Cygwin/X icon in system tray In-Reply-To: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> References: <806a89db0912300907g4dea8ed9ub32e8f942fb06710@mail.gmail.com> Message-ID: <4B3D0CFA.5060209@users.sourceforge.net> On 30/12/2009 11:07, Jim Reisert AD1C wrote: > I do not have a ~/.startxwinrc file. The xterm that is supposed to be > created when the server starts doesn't start either. > > The symptom is that xterm.exe is shown running in the task manager, > but there is no Xterm window on the desktop. This sounds like it has nothing to do with startxwin. I can't reproduce this, but do any of the following help: 1) creating a ~/.startxwinrc containing just "xterm &"? 2) changing that .startxwinrc to "run xterm"? 3) setting LANG=en_US.ISO-8859-1 ? 4) installing the font-daewoo-misc, font-isas-misc, and font-jis-misc packages? Yaakov Cygwin/X -- 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/ From barltrop@pacbell.net Thu Dec 31 21:00:00 2009 From: barltrop@pacbell.net (Kevin Barltrop) Date: Thu, 31 Dec 2009 21:00:00 -0000 Subject: Keymap problem with XWin Server after upgrading to 1.7.3.0 Message-ID: <4B3D1129.7060709@pacbell.net> After upgrading to 1.7.3.0, I get a fatal error dialog box, which says to look at /var/log/XWin.0.log. I did a reinstall of the xkeyboard-config package, but that hasn't helped. the log is shown below. Help! Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.7.3.0 (10703000) Build Date: 2009-12-22 Contact: cygwin-xfree@cygwin.com XWin was started with the following command line: X :0 -multiwindow ddxProcessArgument - Initializing default screens winInitializeDefaultScreens - w 1280 h 1024 winInitializeDefaultScreens - Returning 2009-12-31 12:39:36 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 2009-12-31 12:39:36 _XSERVTransOpen: transport open failed for inet6/OfficeComputer:0 2009-12-31 12:39:36 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 2009-12-31 12:39:37 winValidateArgs - g_iNumScreens: 1 iMaxConsecutiveScreen: 1 2009-12-31 12:39:37 (II) xorg.conf is not supported 2009-12-31 12:39:37 (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information 2009-12-31 12:39:37 winPrefsLoadPreferences: /etc/X11/system.XWinrc 2009-12-31 12:39:37 LoadPreferences: Done parsing the configuration file... 2009-12-31 12:39:37 winGetDisplay: DISPLAY=:0.0 2009-12-31 12:39:37 winDetectSupportedEngines - Windows NT/2000/XP 2009-12-31 12:39:37 winDetectSupportedEngines - DirectDraw installed 2009-12-31 12:39:37 winDetectSupportedEngines - DirectDraw4 installed 2009-12-31 12:39:37 winDetectSupportedEngines - Returning, supported engines 00000007 2009-12-31 12:39:37 winSetEngine - Multi Window or Rootless => ShadowGDI 2009-12-31 12:39:37 winAdjustVideoModeShadowGDI - Using Windows display depth of 32 bits per pixel 2009-12-31 12:39:37 winAllocateFBShadowGDI - Creating DIB with width: 1280 height: 1024 depth: 32 2009-12-31 12:39:37 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff 2009-12-31 12:39:37 winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 2009-12-31 12:39:37 null screen fn ReparentWindow 2009-12-31 12:39:37 null screen fn RestackWindow 2009-12-31 12:39:37 InitQueue - Calling pthread_mutex_init 2009-12-31 12:39:37 InitQueue - pthread_mutex_init returned 2009-12-31 12:39:37 InitQueue - Calling pthread_cond_init 2009-12-31 12:39:37 InitQueue - pthread_cond_init returned 2009-12-31 12:39:37 winInitMultiWindowWM - Hello 2009-12-31 12:39:37 winInitMultiWindowWM - Calling pthread_mutex_lock () 2009-12-31 12:39:37 winMultiWindowXMsgProc - Hello 2009-12-31 12:39:37 winMultiWindowXMsgProc - Calling pthread_mutex_lock () 2009-12-31 12:39:37 Screen 0 added at XINERAMA coordinate (0,0). 2009-12-31 12:39:37 MIT-SHM extension disabled due to lack of kernel support 2009-12-31 12:39:37 XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel 2009-12-31 12:39:37 (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so 2009-12-31 12:39:37 (II) GLX: Initialized DRISWRAST GL provider for screen 0 2009-12-31 12:39:37 [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! 2009-12-31 12:39:37 [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! 2009-12-31 12:39:37 [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! 2009-12-31 12:39:37 (EE) Error compiling keymap (server-0) 2009-12-31 12:39:37 (EE) XKB: Couldn't compile keymap 2009-12-31 12:39:37 XKB: Failed to compile keymap 2009-12-31 12:39:37 Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. 2009-12-31 12:39:37 Fatal server error: 2009-12-31 12:39:37 Failed to activate core devices. -- 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/