hi cygwin
Salutations cygwin nirvanaspace.in/calculator.php?quiet=1v88gpcc0zwh0h J W -- 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/
hi cygwin
Sup cygwin http://marketingtervezes.com/dozen.php?send=13cyaqq7u00nr ggvrsn -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why?
On 02/12/2015 00:16, John J Ottusch wrote: Makes sense that it could be run.exe behavior. However, the version of run.exe from [2] (which is 220K in size vs. 68K for the original version ?!?) does not seem to do anything. Running it from a CMD window with urxvtermX.bat as the argument does not produce an error message, a urxvt term, nothing. It's larger because it doesn't have debug information stripped. BTW, I made an effort to give both versions of run.exe (I renamed the new one runX.exe) the same ownership and permissions, but to no avail. Am I missing something essential? Just chmod +x should be sufficient. I've probably done something wrong, although I have re-tested this run.exe and it seems to work for me. Perhaps you could try 'strace ./run XWin', that might shed some light on what's going wrong? -- 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/
Re: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why?
> I think this is not a problem with the X server, but with the Cygwin run > utility, which is supposed to run the .bat file with a hidden console. > See [1] a previous discussion of this problem. > I've built an x86_64 run.exe with that patch applied and uploaded it at > [2]. Perhaps you could try that and see if it improves things. > [1] http://cygwin.com/ml/cygwin-xfree/2012-08/msg0.html > [2] ftp://cygwin.com/pub/cygwinx/x86_64/run.exe -- Makes sense that it could be run.exe behavior. However, the version of run.exe from [2] (which is 220K in size vs. 68K for the original version ?!?) does not seem to do anything. Running it from a CMD window with urxvtermX.bat as the argument does not produce an error message, a urxvt term, nothing. BTW, I made an effort to give both versions of run.exe (I renamed the new one runX.exe) the same ownership and permissions, but to no avail. Am I missing something essential? jjo P.S. My apologies if this message is not properly threaded. I see how one can post an original message from 'http://post.gmane.org/post.php? group=gmane.os.cygwin.xfree', but not how one goes about replying to a previously posted message. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why?
On 29/11/2015 02:56, John J Ottusch wrote: I use CYGWIN a lot with 64-bit Windows 7 and have been transitioning from 32-bit CYGWIN to 64-bit CYGWIN primarily in hopes of avoiding repeated STATUS_ACCESS_VIOLATION errors. If I could set up 64-bit CYGWIN (= C64) to behave exactly the same way as my 32-bit CYGWIN (= C32) set up I would, but the applications don't match up exactly and they don't behave exactly the same way. One difference I notice is that opening a urxvt in C64 creates a separate button associated with the Cygwin/X server process in the taskbar, whereas opening an rxvt in C32 does not. (rxvt is not available as a C64 application, but I would expect urxvt to operate similarly). In Yes, please use rxvt-unicode (urxvt). rxvt has been dead upstream for a decade. both cases an icon for the Cygwin/X server process shows up in the notification area. Both are started from a Windows shortcut: C32 target: C:\win32app\cygwin\bin\run.exe C:\win32app\cygwin\rxvtermX.bat C64 target: C:\win64app\cygwin\bin\run.exe C:\win64app\cygwin\urxvtermX.bat The batch files that run are similar. Both start 'XWin' if it is not already running, then run 'rxvt/urxvt'. [...] I prefer NOT to have the taskbar button for the Cygwin/X server process show up. Having an icon show up in the notification area is cleaner. Why are they behaving differently? Is there a way to make the urxvt version (C64) behave like the rxvt version (C32)? I think this is not a problem with the X server, but with the Cygwin run utility, which is supposed to run the .bat file with a hidden console. See [1] a previous discussion of this problem. I've built an x86_64 run.exe with that patch applied and uploaded it at [2]. Perhaps you could try that and see if it improves things. [1] http://cygwin.com/ml/cygwin-xfree/2012-08/msg0.html [2] ftp://cygwin.com/pub/cygwinx/x86_64/run.exe -- 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/
Persistent CYGWIN/X server taskbar button with urxvt in CYGWIN-64, not rxvt in CYGWIN-32. Why?
I use CYGWIN a lot with 64-bit Windows 7 and have been transitioning from 32-bit CYGWIN to 64-bit CYGWIN primarily in hopes of avoiding repeated STATUS_ACCESS_VIOLATION errors. If I could set up 64-bit CYGWIN (= C64) to behave exactly the same way as my 32-bit CYGWIN (= C32) set up I would, but the applications don't match up exactly and they don't behave exactly the same way. One difference I notice is that opening a urxvt in C64 creates a separate button associated with the Cygwin/X server process in the taskbar, whereas opening an rxvt in C32 does not. (rxvt is not available as a C64 application, but I would expect urxvt to operate similarly). In both cases an icon for the Cygwin/X server process shows up in the notification area. Both are started from a Windows shortcut: C32 target: C:\win32app\cygwin\bin\run.exe C:\win32app\cygwin\rxvtermX.bat C64 target: C:\win64app\cygwin\bin\run.exe C:\win64app\cygwin\urxvtermX.bat The batch files that run are similar. Both start 'XWin' if it is not already running, then run 'rxvt/urxvt'. Contents of 'rxvterm.bat' (C32): = @echo off C: chdir C:\win32app\cygwin\bin ps -ef | grep /usr/bin/XWin > nul if ERRORLEVEL 1 ( start /DC:\win32app\cygwin\bin /B XWin -multiwindow ) set DISPLAY=localhost:0.0 rxvt -fn 10x20 -sl 1 +sr -fg yellow -bg navyblue -title "RXVTerm w/X" -e /usr/bin/bash --login -i Contents of 'urxvterm.bat' (C64): = @echo off C: chdir C:\win64app\cygwin\bin ps -ef | grep /usr/bin/XWin > nul if ERRORLEVEL 1 ( start /DC:\win64app\cygwin\bin /B XWin -multiwindow ) set DISPLAY=localhost:0.0 urxvt -fn 10x20 -sl 1 +sr -fg yellow -bg navyblue -title "URXVTerm w/X" -e /usr/bin/bash --login -i I prefer NOT to have the taskbar button for the Cygwin/X server process show up. Having an icon show up in the notification area is cleaner. Why are they behaving differently? Is there a way to make the urxvt version (C64) behave like the rxvt version (C32)? John Ottusch -- 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/
Cygwin Users List
Hi, Greeting for the day, Would you be interested in reaching out “Cygwin Users List” with opt-in verified contact information? We also have data for Microsoft Users Lists, Windows Users List, Nortel Users List, Avaya Users List, Citrix Users, IBM Users, McKesson Horizon Users, Oracle List, SAP Users List and many more… Each record in the list contains Company Name, Contact First Name, Last Name, Title, HQ Phone, Direct No, Email, Address1, Address2, City, State, Zip, Country, Industry, Revenue, Fiscal Year End, Employees, IT Budget, IT Employees, Website, Technology, Company HQ Address1, Company HQ Address2, Company HQ City, Company HQ State, Company HQ Zip, Company HQ Country and LinkedIn link. Hit reply and send in the target criteria accordingly. I can provide you with counts and a few demo samples to prove the accuracy of our data. Look forward to your prompt response. Thanks and Regards, Chris Dillie We respect your privacy, if you do not wish to receive any further emails from our end, please reply with a subject “Leave Out”. -- 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/
Problems with cygwin in Windows 10
Having problems with the X interface in Windows 10 (currently build 10240). /bin/startxwin fails with the symptoms in the attached file xwin.txt. The output from cygcheck -cv is also attached. What am I missing? $ startxwin Could not load crashreporter dll Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.1.0 OS: CYGWIN_NT-10.0 WIN-xx 2.0.4(0.287/5/3) 2015-06-09 12:22 x86_64 OS: Windows 10 [Windows NT 10.0 build 10130] (Win64) Package: version 1.17.1-5 built 2015-06-02 XWin was started with the following command line: /usr/bin/XWin :2 -multiwindow -auth /home/granp/.serverauth.5032 (EE) Fatal server error: (EE) Could not create lock file in /tmp/.tX2-lock waiting for X server to begin accepting connections . .. .. .. .. .. .. .. ..winDeinitMultiWindowWM - Noting shutdown in progress xinit: giving up xinit: unable to connect to X server: Connection refused xinit: server error granp@WIN-xx ~ $ cd / granp@WIN-xx / $ ls -la total 1303 drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 May 21 15:33 . drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 May 21 15:33 .. drwxrwx---+ 1 Unknown+User Unknown+Group 0 Apr 1 2014 .cache lrwxrwxrwx 1 Unknown+User Unknown+Group 21 Jan 1 2014 30cm - /cygdrive/f/rods/30cm lrwxrwxrwx 1 Unknown+User Unknown+Group 21 Jan 1 2014 60cm - /cygdrive/f/rods/60cm drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 Jul 11 01:15 bin dr-xr-xr-x 1 granpgranp 0 Jul 11 01:19 cygdrive -rwxrwxrwx+ 1 Unknown+User Unknown+Group 59 Jul 7 21:58 Cygwin.bat -rwxrwxrwx+ 1 Unknown+User Unknown+Group 59 Aug 8 2013 Cygwin.bat~ -rwxrwxrwx+ 1 Unknown+User Unknown+Group 157097 Aug 8 2013 Cygwin.ico -rwxrwxrwx+ 1 Unknown+User Unknown+Group 53342 Aug 8 2013 Cygwin-Terminal.ico -rwxrwxrwx+ 1 Unknown+User Unknown+Group 132014 Apr 26 11:40 cygwin-ug-net-nochunks.html drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 Oct 10 2013 dev drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 Jul 11 01:15 etc lrwxrwxrwx 1 Unknown+User Unknown+Group 11 Sep 7 2013 f - /cygdrive/f drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 Jul 7 21:58 home lrwxrwxrwx 1 Unknown+User Unknown+Group 11 Sep 7 2013 j - /cygdrive/j drwxr-xr-x+ 1 Unknown+User Unknown+Group 0 Jul 11 01:14 lib lrwxrwxrwx 1 Unknown+User Unknown+Group 26 Sep 7 2013 MCNP_DATA - /cygdrive/d/MCNP/mcnp_data drwx---r-x+ 1 Unknown+User Unknown+Group 0 May 31 21:27 mnt drwx---r-x+ 1 Unknown+User Unknown+Group 0 Apr 26 21:26 opt dr-xr-xr-x 9 granpgranp 0 Jul 11 01:19 proc drwxr--r-t+ 1 Unknown+User Unknown+Group 0 Apr 27 21:12 run drwxrwxr-x+ 1 Unknown+User Unknown+Group 0 Apr 25 15:47 sbin drwxrwxr-t+ 1 Unknown+User Unknown+Group 0 Jun 2 10:52 tmp drwxrwxrwx+ 1 Unknown+User Unknown+Group 0 Jul 11 01:08 usr drwxr-xr-x+ 1 Unknown+User Unknown+Group 0 Oct 3 2014 var $ startxwin Could not load crashreporter dll Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.1.0 OS: CYGWIN_NT-10.0 WIN-xx 2.0.4(0.287/5/3) 2015-06-09 12:22 x86_64 OS: Windows 10 [Windows NT 10.0 build 10240] (Win64) Package: version 1.17.1-5 built 2015-06-02 XWin was started with the following command line: /usr/bin/XWin :2 -multiwindow -auth /home/granp/.serverauth.5124 Could not load crashreporter dll (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /home/granp/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0005 winSetEngine - Multi Window or Rootless = ShadowGDI winScreenInit - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1400 height: 1050 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' (II) AIGLX: Testing pixelFormatIndex 2 GL_VERSION: 1.1.0 GL_VENDOR: Microsoft Corporation GL_RENDERER:GDI Generic wglwrap: Can't resolve wglGetExtensionsStringARB (EE) AIGLX: Won't use the generic native renderer as it is not accelerated glWinSelectGLimplementation: Loaded 'cygGL-1.dll' (II) AIGLX: enabled GLX_EXT_texture_from_pixmap (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 700 525 (--) 5 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) Windows keyboard layout: 0409 (0409) US, type 7 (--) Found matching XKB configuration English
Re: Problems with cygwin in Windows 10
Hi, On Tue, Jul 21, 2015 at 12:52 AM, Robert McBroom mcfo...@bellsouth.net wrote: Having problems with the X interface in Windows 10 (currently build 10240). /bin/startxwin fails with the symptoms in the attached file xwin.txt. The output from cygcheck -cv is also attached. What am I missing? I have been using Cygwin/X on Windows 10 64-bit without issue, across numerous builds (currently 10240 also.) The 2nd time you ran startxwin, It looks like Cygwin thinks you lack 3D acceleration. Try this command: $ startxwin -- -extension GLX -multiwindow Also, the UnknownGroup might be an issue that prevented you from writing the lock file to /tmp/. Someone else would know better than me though. -Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin XWin 1.17.1 crash at startup
On 31/03/2015 19:36, Michel Poirier wrote: Since last X-Cygwin update several of my X-Win applications are not working properly. Googling cygwin xorg 1.17 crash gave many posts reporting probably similar issues but I couldn't find a fix for the error. I also looked at the Cygwin-FAQ and mailing list without real success. The issue appeared using a long-time tested DOS script launching xmgrace which failed with a message telling A fatal error has occurred and Cygwin/X will now exit. And other XWin programs were not working properly. So I tried to make a fresh install of X-Cygwin (32 bits) on another computer and went through the procedure explained on page Can you be a bit more specific than not working properly, please? I made a brief test with xmgrace, and I wasn't able to observe any problems. Is there some specific option or action in xmgrace which causes this crash? http://x.cygwin.com/devel/backtrace.html Would it be possible for you to try the a backtrace when some specific action is making the X server crash method on the machine which shows the crash? which produced the debug info attached as backtrace for X server crashing at startup.txt. The X Server crashed when the r command was launched and a copy of the Windows error message is provided at Capture of Windows error message.txt. I checked that no other X Server was then running and clicked Ok button to finish the procedure. Thanks for attempting this. Unfortunately, this looks like the server refusing to start as one is already running. If there really isn't one running, this looks like a different problem. -- 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/
Cygwin XWin 1.17.1 crash at startup
Dear Cygwin maintainer Since last X-Cygwin update several of my X-Win applications are not working properly. Googling cygwin xorg 1.17 crash gave many posts reporting probably similar issues but I couldn't find a fix for the error. I also looked at the Cygwin-FAQ and mailing list without real success. The issue appeared using a long-time tested DOS script launching xmgrace which failed with a message telling A fatal error has occurred and Cygwin/X will now exit. And other XWin programs were not working properly. So I tried to make a fresh install of X-Cygwin (32 bits) on another computer and went through the procedure explained on page http://x.cygwin.com/devel/backtrace.html which produced the debug info attached as backtrace for X server crashing at startup.txt. The X Server crashed when the r command was launched and a copy of the Windows error message is provided at Capture of Windows error message.txt. I checked that no other X Server was then running and clicked Ok button to finish the procedure. The content of the file /var/log/xwin/XWin.0.log is listed at the end of the first attached file. I also tried to install the most recent xlaunch program as suggested here https://www.cygwin.com/ml/cygwin-xfree/2015-02/msg00089.html but it did not solve the issue. Sorry for asking something that might be FAQ but as I told I could not find a clear answer elsewhere and indeed xlaunch reproduced the error consistently. Thanking you in advance for your assistance, and of course for providing this invaluable software that is cygwin. Regards -- Michel Poirier CEA, IRAMIS Laboratoire Interactions, Dynamique et Lasers Centre d'Études de Saclay, bât. 522 F91191 Gif/Yvette (France) Tél. : +33 1 69 08 46 29 FAX : +33 1 69 08 87 07 e-mail: michel.poir...@cea.fr IRAM-FA-004439+admin-local@IRAM-FA-004439 ~ $ gdb --args /usr/bin/XWin -multiwindow GNU gdb (GDB) 7.8 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i686-pc-cygwin. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from /usr/bin/XWin...Reading symbols from /usr/lib/debug//usr/bi n/XWin.exe.dbg...Can't read data for section '.debug_frame' in file '/usr/lib/de bug/usr/bin/XWin.exe.dbg' (gdb) handle SIGSYS nostop SignalStop Print Pass to program Description SIGSYSNoYes Yes Bad system call (gdb) r Starting program: /usr/bin/XWin -multiwindow [New Thread 5852.0xc88] [New Thread 5852.0x1a0c] [New Thread 5852.0xcec] [New Thread 5852.0x1548] [New Thread 5852.0x50c] [New Thread 5852.0x4e0] [Thread 5852.0x4e0 exited with code 1] [Thread 5852.0x1a0c exited with code 1] [Thread 5852.0x50c exited with code 1] [Thread 5852.0xcec exited with code 1] [Inferior 1 (process 5852) exited with code 01] (gdb) bt full No stack. (gdb) q IRAM-FA-004439+admin-local@IRAM-FA-004439 ~ $ cat /var/log/xwin/XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.1.0 OS: CYGWIN_NT-6.1-WOW IRAM-FA-004439 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.17.1-2 built 2015-02-23 XWin was started with the following command line: /usr/bin/XWin -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1200 winInitializeScreenDefaults - native DPI x 96 y 96 _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running (EE) Fatal server error: (EE) Cannot establish any listening sockets - Make sure an X server isn't alread y running(EE) [ 17451.691] (EE) Server terminated with error (1). Closing log file.A fatal error has occurred and Cygwin/X will now exit. Cannot establish any listening sockets - Make sure an X server isn't already running Please open /var/log/xwin/XWin.0.log for more information. Vendor: The Cygwin/X Project Release: 1.17.1.0 Contact: cygwin-xfree@cygwin.com Package: version 1.17.1-2 built 2015-02-23 XWin was started with the following command-line: /usr/bin/XWin -multiwindow -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin XWin 1.17.1 crash at startup
On 3/31/2015 8:36 PM, Michel Poirier wrote: Dear Cygwin maintainer Since last X-Cygwin update several of my X-Win applications are not working properly. Googling cygwin xorg 1.17 crash gave many posts reporting probably similar issues but I couldn't find a fix for the error. I also looked at the Cygwin-FAQ and mailing list without real success. can you just run startxwin from mintty and report the outcome ? There were several changes in the default https://www.cygwin.com/ml/cygwin-xfree-announce/2015-02/msg0.html https://www.cygwin.com/ml/cygwin-xfree-announce/2015-02/msg00014.html may be you are hitting one of them. Regards Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X : display error with latest x-related packages
xflr6 xflr6 at orange.fr writes: Dear Cygwin/X users and developpers, I recently experienced a problem with a program using the X window system. With the latest Cygwin release, the latter is not able to open the display, whereas with previous versions of cygwin (+ the x-window machinery, i.e the Cygwin/X installation as described in the installation notes, with xlaunch, xinit, xorg-server etc.) (prior to mid-February 2015), it was working correctly. Other programs using the X window system, such as ghostview for example, is working correctly on my installation. I have seen on the Cygwin/X news that X server and X.Org X11 packages have been upgraded to newer versions, and I was wondering if there was a known loss of backward compatibility with these fresh versions (even a simple change, like in the DISPLAY variable or something like that) ? Best regards, xflr6 -- 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/ seeing similar behavior here after upgrading to: $ uname -a CYGWIN_NT-6.1-WOW xxx 1.7.35(0.287/5/3) 2015-03-04 12:07 i686 Cygwin It seems that the server is not opening the tcp/6000 port for remote connections. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X : display error with latest x-related packages
Ceuso ceuso writes: Yes, I got it: https://www.cygwin.com/ml/cygwin-xfree-announce/2015-02/msg00014.html NOTEWORTHY CHANGES IN 1.17 == '-nolisten tcp' is now the default, so the server only accepts local connections on a unix domain socket. A '-listen' option has been added which can be used to restore the previous behaviour. -- 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/
Cygwin/X : display error with latest x-related packages
Dear Cygwin/X users and developpers, I recently experienced a problem with a program using the X window system. With the latest Cygwin release, the latter is not able to open the display, whereas with previous versions of cygwin (+ the x-window machinery, i.e the Cygwin/X installation as described in the installation notes, with xlaunch, xinit, xorg-server etc.) (prior to mid-February 2015), it was working correctly. Other programs using the X window system, such as ghostview for example, is working correctly on my installation. I have seen on the Cygwin/X news that X server and X.Org X11 packages have been upgraded to newer versions, and I was wondering if there was a known loss of backward compatibility with these fresh versions (even a simple change, like in the DISPLAY variable or something like that) ? Best regards, xflr6 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X : display error with latest x-related packages
On Mar 12 13:44, xflr6 wrote: Dear Cygwin/X users and developpers, Please note that the cygwin-xfree list has been deprecated. Use the cygwin AT cygwin DOT com list instead. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat pgpWZJoQn3SlG.pgp Description: PGP signature
[ANNOUNCEMENT] cygwin-xfree list deprecation
Dear Internet, It no longer makes much sense to have a separate list for Cygwin X related traffic, so the cygwin-xfree list is now officially deprecated. Reasons for this decision include: - the level of traffic on the cygwin-xfree list is low - splitting the traffic in this way currently serves no useful purpose - the distinction between what is and is not an X issue is artificial, vague, and often ignored The cygwin-xfree list will continue to operate, but I suggest and encourage you to use the main cygwin list for all your cygwin X server and X application related questions, bug reports, moans, gripes, whines and patches ;-). The Cygwin X website and documentation will be updated to point to the main cygwin list. Mail delivery for the cygwin-xfree list may be turned off at some future date, but even if that happens, the list archives will continue to be available. Live Long and Prosper, Jon -- 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/
[ANNOUNCEMENT] Merge of cygwin-xfree-announce into cygwin-announce
Hi folks, it's becoming awkward having to split package announcements between two mailing lists. In fact, there's neither a good reason having to decide where to send an announcement, nor having to subscribe to two lists for Cygwin package announcements. Therefore, effectiv immediately, we're going to give up the cygwin-xfree-announce mailing list in favor of only the cygwin-announce mailing list. === In future, new Cygwin packages and package updates will be announced on cygwin-announce only. === If you're not subscribed to cygwin-announce, only to cygwin-xfree-announce, I'll suggest to subscribe to cygwin-announce instead. For reference and archeological diggings, the cygwin-xfree-announce archives will stay available. Peace, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer 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/
Re: Cygwin/X XDMCP Issue
On Sun, Feb 22, 2015 at 4:38 PM, Maarten Hoes hoes.maar...@gmail.com wrote: On 22-2-2015 22:09, Maarten Hoes wrote: 28 1.690209 192.168.0.21 - 192.168.178.20 TCP 74 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6862378 TSecr=0 WS=128 Wait, what ? send to 192.168.178.20 instead of 192.168.0.20 ? i changed the ip address range of my home network. thats whats wrong, now i guess i need to figure out where i forgot to update that ip range / address. Oh, well. I can think of 2 possible issues/solutions: With XDMCP under VcXsrv or Cygwin XWin, you often need to use this argument to, usually when you have multiple (virtual) network adapters: -from 192.168.0.20 XDMCP involves a forward-confirmed reverse DNS lookup. So if you have incorrect DNS records like the following: PTR: 192.168.0.20 - windows-pc A: windows-pc - 192.168.178.20 Then this problem will happen. -Mike -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
On 23-2-2015 16:33, Maarten Hoes wrote: On 23-2-2015 16:11, Maarten Hoes wrote: I suspect something strange is going on under the covers of my ISP supplied FRITZ!Box 7390, but I cant figure out what... Looks like I managed to seriously mess up my network settings, alright. From another Linux host on the same subnet (192.168.0.31), I get these ICMP messages when I try to start an X/XDMCP session to it: 4 0.000292 192.168.0.31 - 192.168.0.20 ICMP 77 Destination unreachable (Host administratively prohibited) 7 1.989470 192.168.0.31 - 192.168.0.20 ICMP 77 Destination unreachable (Host administratively prohibited) 12 5.989469 192.168.0.31 - 192.168.0.20 ICMP 77 Destination unreachable (Host administratively prohibited) Oh wait, thats just the default iptables ruleset on Fedora (phew). Well I changed the range back to 192.168.178.0/255.255.255.0, and now it works again. Guess ill do some digging around later looking for root causes when I have more time, but for now it's good enough for me. ;) Thanks for the help, - Maarten 1 0.0 192.168.178.20 - 192.168.178.21 XDMCP 49 Query 2 0.038915000 192.168.178.21 - 192.168.178.20 XDMCP 99 Willing 3 0.213517000 192.168.178.20 - 192.168.178.21 XDMCP 352 Request 4 0.213793000 192.168.178.21 - 192.168.178.20 XDMCP 94 Accept 5 0.213875000 192.168.178.20 - 192.168.178.21 XDMCP 71 Manage 6 0.221893000 192.168.178.21 - 192.168.178.20 TCP 74 42824â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=4294947644 TSecr=0 WS=128 7 0.221999000 192.168.178.20 - 192.168.178.21 TCP 74 6000â+'42824 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=35608 TSecr=4294947644 8 0.222094000 192.168.178.21 - 192.168.178.20 TCP 66 42824â+'6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=4294947644 TSecr=35608 9 0.33000 192.168.178.21 - 192.168.178.20 X11 114 Initial connection request 10 0.222453000 192.168.178.20 - 192.168.178.21 TCP 74 [TCP segment of a reassembled PDU] 11 0.222515000 192.168.178.20 - 192.168.178.21 TCP 1514 [TCP segment of a reassembled PDU] 12 0.222529000 192.168.178.20 - 192.168.178.21 TCP 1514 [TCP segment of a reassembled PDU] 13 0.222536000 192.168.178.21 - 192.168.178.20 TCP 66 42824â+'6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=4294947645 TSecr=35608 14 0.222539000 192.168.178.20 - 192.168.178.21 X11 254 Initial connection reply 15 0.222602000 192.168.178.21 - 192.168.178.20 TCP 66 42824â+'6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=4294947645 TSecr=35608 16 0.222715000 192.168.178.21 - 192.168.178.20 X11 86 Requests: QueryExtension 17 0.22282 192.168.178.20 - 192.168.178.21 X11 98 Reply: QueryExtension 18 0.222908000 192.168.178.21 - 192.168.178.20 X11 70 Requests: BIG-REQUESTS 19 0.223006000 192.168.178.20 - 192.168.178.21 X11 98 Reply: BIG-REQUESTS 20 0.223102000 192.168.178.21 - 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 21 0.223186000 192.168.178.20 - 192.168.178.21 X11 98 Reply: GetProperty 22 0.22329 192.168.178.21 - 192.168.178.20 X11 86 Requests: QueryExtension 23 0.22347 192.168.178.20 - 192.168.178.21 X11 98 Reply: QueryExtension 24 0.22357 192.168.178.21 - 192.168.178.20 X11 74 Requests: XKEYBOARD 25 0.223659000 192.168.178.20 - 192.168.178.21 X11 98 Reply: XKEYBOARD 26 0.224025000 192.168.178.21 - 192.168.178.20 X11 102 Requests: OpenFont, QueryExtension 27 0.224145000 192.168.178.20 - 192.168.178.21 X11 98 Reply: QueryExtension 28 0.224244000 192.168.178.21 - 192.168.178.20 X11 82 Requests: RENDER, RENDER 29 0.224331000 192.168.178.20 - 192.168.178.21 X11 98 Reply: RENDER -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
On 20/02/2015 18:36, Maarten Hoes wrote: I am (again) experiencing some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startxwin' works as expected. But when I try to connect to my remote Linux system with the command 'xwin -query 192.168.0.21' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. Things used to work, but apparently something broke my setup. Im running the latest Cygwin/X, and applied all current updates on my Fedora 21 Linux system. Im running KDM. Any and all ideas are more than welcome, as I have no idea whats going on here. Package: version 1.16.3-1 built 2014-12-30 xwin -query 192.168.0.21 -logverbose 3 1 0.00 192.168.0.20 - 192.168.0.21 XDMCP 49 Query 2 0.013254 192.168.0.21 - 192.168.0.20 XDMCP 100 Willing 3 0.227426 192.168.0.20 - 192.168.0.21 XDMCP 360 Request 4 0.227831 192.168.0.21 - 192.168.0.20 XDMCP 94 Accept 5 0.227968 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage Assuming your wireshark filter includes X11, you should be seeing a X11 connection request from 192.168.0.21 to the X server here. Since the same X server version was working for you before (to a different IP address), I can only suggest you examine what else has changed. You might want to check your firewall/network configuration. 6 2.225721 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage 7 6.229538 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage 8 14.230544 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage 9 30.228625 192.168.0.20 - 192.168.0.21 XDMCP 71 Manage -- 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/
Re: Cygwin/X XDMCP Issue
Hi, On 22-2-2015 14:55, Jon TURNEY wrote: Assuming your wireshark filter includes X11, you should be seeing a X11 connection request from 192.168.0.21 to the X server here. Hrm. wireshark (running in promisc mode on my desktop that runs cygwin) does show TCP sessions for port 6000 (that's X11, right ?). But somehow that doesnt seem to get through correctly. I tried opening up that range on my desktop firewall (Norton Internet Security), but that doesnt seem to change anything. - Maarten. 28 1.690209 192.168.0.21 - 192.168.178.20 TCP 74 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6862378 TSecr=0 WS=128 30 2.692531 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6863380 TSecr=0 WS=128 32 4.696609 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6865384 TSecr=0 WS=128 45 8.704426 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6869392 TSecr=0 WS=128 69 16.719818 192.168.0.21 - 192.168.178.20 TCP 74 [TCP Retransmission] 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6877408 TSecr=0 WS=128 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
On 22-2-2015 22:09, Maarten Hoes wrote: 28 1.690209 192.168.0.21 - 192.168.178.20 TCP 74 60221â+'6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=6862378 TSecr=0 WS=128 Wait, what ? send to 192.168.178.20 instead of 192.168.0.20 ? i changed the ip address range of my home network. thats whats wrong, now i guess i need to figure out where i forgot to update that ip range / address. Oh, well. - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
On 20-2-2015 19:36, Maarten Hoes wrote: ( I tried to included my XWin.log and a wireshark tracefile to this message, but the mail server keeps bouncing my messages). Perhaps this works: Xwin.log: http://ur1.ca/jrrmb wireshark tracefile (txt): http://ur1.ca/jrrmh - Maarten -- 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/
Cygwin/X XDMCP Issue
Hi, I am (again) experiencing some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startxwin' works as expected. But when I try to connect to my remote Linux system with the command 'xwin -query 192.168.0.21' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. Things used to work, but apparently something broke my setup. Im running the latest Cygwin/X, and applied all current updates on my Fedora 21 Linux system. Im running KDM. Any and all ideas are more than welcome, as I have no idea whats going on here. ( I tried to included my XWin.log and a wireshark tracefile to this message, but the mail server keeps bouncing my messages). - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
On 13/02/2015 07:24, Maarten Hoes wrote: On 2-2-2015 16:20, Jon TURNEY wrote: If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. I was wondering if you managed to reproduce the issue ? Yes, I can reproduce it. It seems that the XRANDR data which XWin returns isn't quite complete, which tickles a bug in Gnome [1] primaryMonitor is undefined, which prevents the login greeter from being displayed. I've been testing a fix for that issue in XWin. This gets you the greeter login screen. Unfortunately there seem to be other bugs, which prevent login from working. These also occur when starting an XDMCP session from linux, so I don't think these are XWin issues. [1] https://bugzilla.gnome.org/show_bug.cgi?id=736054 -- 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/
Re: Cygwin/X XDMCP Issue
Hi, On 2-2-2015 16:20, Jon TURNEY wrote: If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. I was wondering if you managed to reproduce the issue ? - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Launching Cygwin/X in background with no clients
On 2/2/2015 9:12 PM, Jim Garrison wrote: On 2/2/2015 5:21 PM, Yaakov Selkowitz wrote: On Mon, 2015-02-02 at 16:52 -0800, Jim Garrison wrote: I updated Cygwin (which pulled in a bunch of Cygwin-X updates) and now startxwin no longer works. According to the log (below) it starts the XServer successfully but then shuts down. My .startxwinrc is an empty (zero-length) file to prevent automatic launching of the default clients, which I don't need. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit Thanks. I want to start an X server in the background, with no visible clients, if it's not already running, whenever I launch a mintty session. X should continue to run even if the mintty session that started it is closed. Currently I have the following in my .bash_profile ps -ef|grep -q XWin || nohup setsid startxwin 2startxwin.log This now works again after adding exec sleep infinity in .startxwinrc, but I can't help feel my whole approach is a bad hack. Both nohup and setsid seem to be required. Without setsid the mintty will hang if I attempt to close it with exit or ^D, and without nohup the X server terminates whenever the first mintty session is closed. Is there a cleaner way to accomplish this objective? Are you willing to have the X Server launch when you log into windows and just keep it running? This is what I do and I find it very useful. I launch the X server when I log in using a shortcut with the following target: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons 100 -multiwindow -clipboard -swcursor I then place this shortcut into the Startup folder of my Start menu. I hope this helps. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin, Python Anaconda 32-bit, Google Cloud SDK: Issues with Python functionality inside of Cygwi
On 03/02/15 03:43, mjmv wrote: When I went to install Cygwin, I did not see an option for Python 2.7, which is what the GC SDK requires (more specifically, 2.7 32-bit). 32-bit Cygwin has python 2.7.8, which should work with Google Cloud SDK. You can select this by searching for 'python' on the package selection page of the Cygwin installer - or you can find it by expanding the 'Python' group on the same page. According to the Google Cloud SDK docs [1], you will also require openssh and curl. Hope this helps, Dave. [1] - https://cloud.google.com/sdk/ - See 'Alternative methods' tab. -- 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/
Launching Cygwin/X in background with no clients
On 2/2/2015 5:21 PM, Yaakov Selkowitz wrote: On Mon, 2015-02-02 at 16:52 -0800, Jim Garrison wrote: I updated Cygwin (which pulled in a bunch of Cygwin-X updates) and now startxwin no longer works. According to the log (below) it starts the XServer successfully but then shuts down. My .startxwinrc is an empty (zero-length) file to prevent automatic launching of the default clients, which I don't need. http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwinrc-exit Thanks. I want to start an X server in the background, with no visible clients, if it's not already running, whenever I launch a mintty session. X should continue to run even if the mintty session that started it is closed. Currently I have the following in my .bash_profile ps -ef|grep -q XWin || nohup setsid startxwin 2startxwin.log This now works again after adding exec sleep infinity in .startxwinrc, but I can't help feel my whole approach is a bad hack. Both nohup and setsid seem to be required. Without setsid the mintty will hang if I attempt to close it with exit or ^D, and without nohup the X server terminates whenever the first mintty session is closed. Is there a cleaner way to accomplish this objective? -- Jim Garrison -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
On 22/01/2015 07:46, Maarten Hoes wrote: Well I changed from GDM to KDM, and now everything is working as expected. Just one last question: are there any known issues with XDMCP and Gnome GDM ? Or is that combination supposed to just work ? Yes, XDMCP is supposed to work with GDM. No, there are no known issues, but we don't know about issues until someone reports them. :) If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. -- 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/
Re: Cygwin/X XDMCP Issue
Hi, On 2-2-2015 16:20, Jon TURNEY wrote: If you can provide the details of the linux distribution and release you are using on your remote host, I can see if I can try to reproduce the problem. I can reproduce the behavior with GDM on both Fedora 21 and Ubuntu 14.04. So im not too sure that it is distribution specific. Of course, it could just be a configuration error on my side that I made on both distributions thinking it was 'the right thing to do'. ;) Thanks for looking, - Maarten -- 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/
Cygwin, Python Anaconda 32-bit, Google Cloud SDK: Issues with Python functionality inside of Cygwi
Hello, I am new to Cygwin, and am not sure what to make of my current issue regarding Python and, ultimately, Google Cloud's SDK and bdutl package, required for me to deploy a Hortonworks platform Hadoop/Apache toolkit NoSQL db et al. When I went to install Cygwin, I did not see an option for Python 2.7, which is what the GC SDK requires (more specifically, 2.7 32-bit). As such, I installed an Anaconda distro version. After fighting with Cygwin to use this install as my Python of choice for Cygwin applications (I ended up actually having to delete from my environmental variables reference to the native 64-bit version I usually use, as modifications to the $PATH did not change anything), I am left with a half-functional version of Python, and non-functional GC SDK. Pasted below are snippets from my terminal sessions. If anyone can make sense of this, and point me in the direction of resolving the issue(s), I will be very greatful. Mersee --FIRST, MAKE SURE PYTHONPATH IS CORRECT MJ@Speed_rAcer ~ $ which python /cygdrive/c/Users/MJ/Anaconda/python --NEXT SHOW THAT I AM IN THE CYGWIN HOME DIR MJ@Speed_rAcer ~ $ pwd /cygdrive/c/Users/MJ/home --NEXT TEST A PYTHON SCRIPT MJ@Speed_rAcer ~ $ python test.py this is a test i am inside the home directory for cygwin --NEXT, UPDATE CONDA (should work since Cygwin is using the conda Python...but doesn't) MJ@Speed_rAcer ~ $ conda update conda -bash: conda: command not found ***---NEXT, SEE IF GOOGLE CLOUD SDK WORKING---*** --INSIDE FOLDER WITH PYTHON SCRIPTS MJ@Speed_rAcer ~/google-cloud-sdk/bin/bootstrapping $ ls __init__.pybq.py install.py setup.py bootstrapping.py gcutil.py prerun.py setup.pyc bootstrapping.pyc gsutil.py print_env_info.py --RUNS PYTHON SCRIPT (install.py). HOWEVER, DIDN'T LET ME PICK Y OR N BUT SAYS IT'S CONFIGURED MJ@Speed_rAcer ~/google-cloud-sdk/bin/bootstrapping $ python install.py Do you want to help improve the Google Cloud SDK (Y/n)? All components are up to date. Update %PATH% to include Cloud SDK binaries? (Y/n)? The Google Cloud SDK is currently in developer preview. To help improve the quality of this product, we collect anonymized data on how the SDK is used. You may choose to opt out of this collection now (by choosing 'N' at the below prompt), or at any time in the future by running the following command: gcloud config set --scope=user disable_usage_reporting true This will install all the core command line tools necessary for working with the Google Cloud Platform. The following directory has been added to your PATH. C:\Users\MJ\home\google-cloud-sdk\bin Create a new command shell for the changes to take effect. For more information on how to get started, please visit: insert URL that keeps my messages from being posted ***---NEW SHELL---*** --SHOWING COMMANDS I SHOULD BE ABLE TO RUN (first is gcloud. cmd) MJ@Speed_rAcer ~/google-cloud-sdk/bin $ ls bootstrapping gcloud - Copy.cmd gcutil.cmd gsutil.cmd bq.cmd gcloud.cmd git-credential-gcloud.cmd sdk --TRY ONE TO EXECUTE COMMAND $ ./gcloud auth login -bash: ./gcloud: No such file or directory --TRY TWO TO EXECUTE COMMAND MJ@Speed_rAcer ~/google-cloud-sdk/bin $ gcloud auth login -bash: gcloud: command not found -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
Hi, Well I changed from GDM to KDM, and now everything is working as expected. Just one last question: are there any known issues with XDMCP and Gnome GDM ? Or is that combination supposed to just work ? Just for the record, here is the XWin.0.log of a working KDM session. - Maarten XWin.0.log Description: Binary data -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Cygwin/X XDMCP Issue
Hi, Sorry, I forgot to include it in my previous posts: please find the contents of 'cygcheck -s -v -r' attached in 'cygcheck.out' - Maarten Cygwin Configuration Diagnostics Current System Time: Sun Jan 18 08:54:47 2015 Windows 8.1 Ver 6.3 Build 9600 Path: C:\cygwin64\usr\local\bin C:\cygwin64\bin C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common C:\PROGRAM FILES (X86)\INTEL\ICLS CLIENT C:\PROGRAM FILES\INTEL\ICLS CLIENT C:\Windows\SYSTEM32 C:\Windows C:\Windows\SYSTEM32\WBEM C:\Windows\SYSTEM32\WINDOWSPOWERSHELL\V1.0 C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT D:\Progra~1\Java\jre7\bin C:\MinGW\bin D:\Program Files\Calibre2 C:\MinGW\bin C:\MinGW\mingw32\bin C:\MinGW\msys\1.0\bin C:\GnuWin32\bin C:\Program Files (x86)\QuickTime\QTSystem Output from C:\cygwin64\bin\id.exe UID: 1001(Maarten) GID: 513(Geen) 513(Geen) 545(Gebruikers) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'Maarten' PWD = '/home/Maarten' HOME = '/home/Maarten' USERDOMAIN_ROAMINGPROFILE = 'DUSTY123' HOMEPATH = '\Users\Maarten' APPDATA = 'C:\Users\Maarten\AppData\Roaming' ProgramW6432 = 'C:\Program Files' HOSTNAME = 'DUSTY123' SHELL = '/bin/bash' TERM = 'xterm' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' PROFILEREAD = 'true' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/cygdrive/d/Users/Maarten/Desktop' ORIGINAL_PATH = '/cygdrive/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/cygdrive/c/PROGRAM FILES (X86)/INTEL/ICLS CLIENT:/cygdrive/c/PROGRAM FILES/INTEL/ICLS CLIENT:/cygdrive/c/Windows/SYSTEM32:/cygdrive/c/Windows:/cygdrive/c/Windows/SYSTEM32/WBEM:/cygdrive/c/Windows/SYSTEM32/WINDOWSPOWERSHELL/V1.0:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/d/Progra~1/Java/jre7/bin:/cygdrive/c/MinGW/bin:/cygdrive/d/Program Files/Calibre2:/cygdrive/c/MinGW/bin:/cygdrive/c/MinGW/mingw32/bin:/cygdrive/c/MinGW/msys/1.0/bin:/cygdrive/c/GnuWin32/bin:/cygdrive/c/Program Files (x86)/QuickTime/QTSystem' USERDOMAIN = 'DUSTY123' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/tmp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'Maarten' PROCESSOR_LEVEL = '6' ProgramFiles(x86) = 'C:\Program Files (x86)' PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' JAVA_HOME = 'D:\Progra~1\Java\jre7' LANG = 'en_US.UTF-8' USERPROFILE = 'C:\Users\Maarten' TZ = 'Europe/Amsterdam' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\DUSTY123' CommonProgramW6432 = 'C:\Program Files\Common Files' PROCESSOR_ARCHITECTURE = 'AMD64' LOCALAPPDATA = 'C:\Users\Maarten\AppData\Local' ProgramData = 'C:\ProgramData' EXECIGNORE = '*.dll' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/tmp' SYSTEMROOT = 'C:\Windows' PRINTER = 'HP Photosmart C5200 series' PROCESSOR_REVISION = '3c03' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '8' asl.log = 'Destination=file' SESSIONNAME = 'Console' COMPUTERNAME = 'DUSTY123' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Installations (default) = '\??\C:\cygwin64' c5e39b7a9d22bafb = '\??\C:\cygwin' HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\DefaultIcon (default) = 'C:\cygwin64\bin\xlaunch.exe,1' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit\command (default) = 'C:\cygwin64\bin\run C:\cygwin64\bin\bash -l -c xlaunch -load \%1\' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open\command (default) = 'C:\cygwin64\bin\run C:\cygwin64\bin\bash -l -c xlaunch -run \%1\' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C
Re: Cygwin/X XDMCP Issue
Hi, Also, when I run wireshark/tshark, I seem to be watching a regular/successful XDCMP/X11 session ? : - Maarten 1 0.00 192.168.178.20 - 192.168.178.22 XDMCP 49 Query 2 0.013070 192.168.178.22 - 192.168.178.20 XDMCP 106 Willing 3 0.178469 192.168.178.20 - 192.168.178.22 XDMCP 312 Request 4 0.183798 192.168.178.22 - 192.168.178.20 XDMCP 94 Accept 5 0.183901 192.168.178.20 - 192.168.178.22 XDMCP 71 Manage 6 0.687156 192.168.178.22 - 192.168.178.20 TCP 74 49008→6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=8283439 TSecr=0 WS=128 7 0.687297 192.168.178.20 - 192.168.178.22 TCP 74 6000→49008 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=1056917 TSecr=8283439 8 0.687462 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=8283439 TSecr=1056917 9 0.687695 192.168.178.22 - 192.168.178.20 X11 114 Initial connection request 10 0.687992 192.168.178.20 - 192.168.178.22 TCP 74 [TCP segment of a reassembled PDU] 11 0.688064 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 12 0.688086 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 13 0.688104 192.168.178.20 - 192.168.178.22 X11 254 Initial connection reply 14 0.688127 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=8283440 TSecr=1056917 15 0.688225 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=8283440 TSecr=1056917 16 0.688451 192.168.178.22 - 192.168.178.20 X11 86 Requests: QueryExtension 17 0.688654 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 18 0.688823 192.168.178.22 - 192.168.178.20 X11 70 Requests: BIG-REQUESTS 19 0.688958 192.168.178.20 - 192.168.178.22 X11 98 Reply: BIG-REQUESTS 20 0.689164 192.168.178.22 - 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 21 0.689567 192.168.178.20 - 192.168.178.22 X11 98 Reply: GetProperty 22 0.689752 192.168.178.22 - 192.168.178.20 X11 86 Requests: QueryExtension 23 0.690102 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 24 0.690259 192.168.178.22 - 192.168.178.20 X11 74 Requests: XKEYBOARD 25 0.690419 192.168.178.20 - 192.168.178.22 X11 98 Reply: XKEYBOARD 26 0.692905 192.168.178.22 - 192.168.178.20 X11 82 Requests: QueryExtension 27 0.693104 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 28 0.693326 192.168.178.22 - 192.168.178.20 X11 98 Requests: QueryExtension 29 0.693477 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 30 0.693627 192.168.178.22 - 192.168.178.20 X11 74 Requests: Generic Event Extension 31 0.693881 192.168.178.20 - 192.168.178.22 X11 98 Reply: Generic Event Extension 32 0.694061 192.168.178.22 - 192.168.178.20 X11 78 Requests: RANDR 33 0.694183 192.168.178.20 - 192.168.178.22 X11 98 Reply: RANDR 34 0.694334 192.168.178.22 - 192.168.178.20 X11 74 Requests: RANDR 35 0.694481 192.168.178.20 - 192.168.178.22 X11 98 Reply: RANDR 36 0.694628 192.168.178.22 - 192.168.178.20 X11 74 Requests: RANDR 37 0.694759 192.168.178.20 - 192.168.178.22 X11 98 Reply: RANDR 38 0.734457 192.168.178.22 - 192.168.178.20 TCP 66 49008→6000 [ACK] Seq=229 Ack=3445 Win=35456 Len=0 TSval=8283487 TSecr=1056918 39 0.774514 192.168.178.22 - 192.168.178.20 TCP 74 49009→6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=8283526 TSecr=0 WS=128 40 0.774620 192.168.178.20 - 192.168.178.22 TCP 74 6000→49009 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=1056926 TSecr=8283526 41 0.774780 192.168.178.22 - 192.168.178.20 TCP 66 49009→6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=8283527 TSecr=1056926 42 0.774978 192.168.178.22 - 192.168.178.20 X11 114 Initial connection request 43 0.775254 192.168.178.20 - 192.168.178.22 TCP 74 [TCP segment of a reassembled PDU] 44 0.775304 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 45 0.775327 192.168.178.20 - 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 46 0.775336 192.168.178.20 - 192.168.178.22 X11 254 Initial connection reply 47 0.775382 192.168.178.22 - 192.168.178.20 TCP 66 49009→6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=8283527 TSecr=1056926 48 0.775458 192.168.178.22 - 192.168.178.20 TCP 66 49009→6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=8283527 TSecr=1056926 49 0.775580 192.168.178.22 - 192.168.178.20 X11 86 Requests: QueryExtension 50 0.775697 192.168.178.20 - 192.168.178.22 X11 98 Reply: QueryExtension 51 0.775818 192.168.178.22 - 192.168.178.20 X11 70 Requests: BIG-REQUESTS 52 0.775916 192.168.178.20 - 192.168.178.22 X11 98 Reply: BIG-REQUESTS 53 0.776069 192.168.178.22 - 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 54 0.776186 192.168.178.20 - 192.168.178.22 X11 98 Reply:
Cygwin/X XDMCP Issue
Hi, Im having some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startx' works as expected. When I try to connect to my remote Linux system with the command 'xwin -query 192.168.178.22' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. I get the impression that I do get an connection, but that there is a display problem. When I try to close the blacked out Window, I get the message 'Exiting will close all screens on this display. There are currently 6 clients connected. Proceed with the shutdown of this display/server ?' When i specify 'xwin -retro -query 192.168.178.22', the cursor appears and the screen gets gray-ish, but mouse clicking has no effect. Setting 'xwin -engine 16 -query 192.168.178.22' results in a blue background and an error: 'Failed asserion key - size == 0 at line 147 of file /qip/cygport-git/x-org-server/x-org-server-1.16.3-1.x86_64/src/xserver-cygwin-1.16.3-1/include/privates.h in function dixSetPrivate' and a core dump. Any and all ideas are more than welcome, as I have no idea whats going on here. This is the output of the 'xwin -query 192.168.178.22' command : $ xwin -query 192.168.178.22 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.3.0 OS: CYGWIN_NT-6.3 DUSTY123 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 OS: Windows 8.1 [Windows NT 6.3 build 9600] (Win64) Package: version 1.16.3-1 built 2014-12-30 XWin was started with the following command line: xwin -query 192.168.178.22 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /home/Maarten/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0015 winSetEngine - Using Shadow DirectDraw NonLocking winScreenInit - Using Windows display depth of 32 bits per pixel winWindowProc - WM_SIZE - new client area w: 1424 h: 821 winFinishScreenInitFB - Masks: 00ff ff00 00ff 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 (EE) AIGLX: No native OpenGL in modes with a root window (II) AIGLX: enabled GLX_EXT_texture_from_pixmap (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 712 410 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) Windows keyboard layout: 0409 (0409) US, type 4 (--) Found matching XKB configuration English (USA) (--) Model = pc105 Layout = us Variant = none Options = none Rules = base Model = pc105 Layout = us Variant = none Options = none winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 OS maintains clipboard viewer chain: yes winClipboardProc - XOpenDisplay () returned and successfully opened the display. winWindowProc - WM_*KEYDOWN - Closekey hit, quitting winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress (EE) Server terminated successfully (0). Closing log file. Regards, - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwin emacs failing siletnly
Thanks for all of the advice on fc-cache, but it doesn't help my emacs run. Does anyone else have any ideas why the fonts are causing emacs to blow up? Thanks Gulliver On Mon, Oct 13, 2014 at 8:18 PM, Gulliver Smith gulliver.m.sm...@gmail.com wrote: Follow up: It is only emacs for X-windows that fails silently. emacs-nox works perfectly. As I said, the silent failure has no core dump and no log messages anywhere. Nothing is displayed in the shell window. Thanks Gulliver -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwin emacs failing siletnly
On 11/25/2014 8:54 PM, Gulliver Smith wrote: Thanks for all of the advice on fc-cache, but it doesn't help my emacs run. Does anyone else have any ideas why the fonts are causing emacs to blow up? You said in one of your messages of October 13 that fc-cache is failing. emacs-X11 is not going to be able to find any fonts if there's something wrong with your fontconfig setup. You might try running fc-cache under strace to see if that gives any clues. 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/
cygwin setup program questions
I have some elementary questions regarding the cygwin setup program. I ran the latest version 2.852 (64 bit). the options are install / re-install / un-install / default my understanding is as follows; choosing install creates a new installation of the selected cygwin components choosing re-install uninstalls the selected cygwin components, then creates a new installation choosing un-install uninstalls the selected cygwin components choosing default updates the selected cygwin components so if I wish to update my local installation to the latest release, I would choose default, as per the following screen capture; http://www.cpm86.com/default.jpg What is the function of the keep / cur / exp radio buttons? Please confirm my understanding of these four options. 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/
Re: cygwin emacs failing siletnly
On Sun, Nov 9, 2014 at 10:10 AM, Gulliver Smith wrote: My emacs (x) is still not running at all on my windows XP virtual machine. cygcheck output from both machines attached. Have you tried this yet? https://cygwin.com/ml/cygwin/2013-12/msg00248.html -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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/
Re: FW: Cygwin start menu / mirrors
webpage; http://cygwinports.org/ says to issue the command;cygstart -- /path/to/setup-x86.exe -K http://cygwinports.org/ports.gpg so I issued; cygstart -- e:/setup-x86_64.exe -K http://cygwinports.org/ports.gpg at first this command worked. Now it doesn't. It throws up an error message unable to get setup.ini from http://cygwinports.org/ports.gpg; help, please?
Re: FW: Cygwin start menu / mirrors
On 10/21/2014 04:59 PM, t s wrote: webpage; http://cygwinports.org/ says to issue the command; cygstart -- /path/to/setup-x86.exe -K http://cygwinports.org/ports.gpg so I issued; cygstart -- e:/setup-x86_64.exe -K http://cygwinports.org/ports.gpg at first this command worked. Now it doesn't. It throws up an error message unable to get setup.ini from http://cygwinports.org/ports.gpg; help, please? Looks like it's a temporary glitch, as it works fine for me when I tried it just now. Two other things to note though: 1. cygwinports.org is not cygwin.com so asking questions about it on cygwin.com mailing lists is really off-topic. cygwinports.org has its own mailing list if you have further questions about the packages and services it provides. 2. This list is reserved for Cygwin-X-specific issues. So if you have questions in the future related to Cygwin-X, this is the right mailing list. Otherwise, if it's a more general Cygwin issue, the main list (cygwin at cygwin dot com) is the right place. -- Larry _ 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/
Re: cygwin emacs failing siletnly
On Mon, Oct 13, 2014 at 7:16 PM, Gulliver Smith wrote: Thanks for the pointer to fc-cache. On which machine should this be run? a) the machine hosting the X-Server b) the machine on which emacs is running I don't have a client/server configuration, so I don't know how to answer that, sorry. -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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/
problems with cygwin/x
On 04/10/2014 18:16, t s wrote: first of all, regarding the Cygwin setup program; the options are install / re-install / un-install / default is it correct that to install only the latest updates, I would choose the option 'default' ? I'm not sure what text you are looking at. The options for an individual package which is already installed are 'reinstall', 'uninstall', 'keep' and specific versions other than the currently installed one (if any). I can't see default anywhere. If you mean the default version, then yes, when curr is selected at the top, all packages which have updates, will be updated. The current version of the setup program, 2.850 (64 bit), on the select packages screen, features a default option. Please see; http://cpm86.com/default.jpg The four options are; Install; Reinstall; Uninstall; Default I just want to be sure; to install only the latest updates, I would choose 'Default' ? next question : if I delete the start menu option Cygwin/x and run the setup program for option default, it doesn't re-create the start menu option Cygwin/x is this 'feature' acknowledged, and is it being addressed? The start menu link for for the X server is owned by the package xinit. If you reinstall that package, it should be recreated. That's the answer I was looking for. Thank you. I have a further question. Choosing menu item Cygwin-X / X Win Server boots X windows. If you right click on the 'X' icon in the lower right side of the screen, it features applications xterm / emacs / notepad / xload. Is it possible to tailor the list of applications referenced above? to include say xclock, xeyes And yet another question; I note the presence of a number of files in \usr\bin which start with 'gnome'. Does Cygwin/x feature gnome or kde as user interfaces? or does it only allow compilation of apps which use features of those interfaces? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: FW: Cygwin start menu / mirrors
On 08/10/2014 23:40, t s wrote: On 04/10/2014 18:16, t s wrote: first of all, regarding the Cygwin setup program; the options are install / re-install / un-install / default is it correct that to install only the latest updates, I would choose the option 'default' ? I'm not sure what text you are looking at. The options for an individual package which is already installed are 'reinstall', 'uninstall', 'keep' and specific versions other than the currently installed one (if any). I can't see default anywhere. If you mean the default version, then yes, when curr is selected at the top, all packages which have updates, will be updated. The current version of the setup program, 2.850 (64 bit), on the select packages screen, features a default option. Please see; http://cpm86.com/default.jpg The four options are; Install; Reinstall; Uninstall; Default I just want to be sure; to install only the latest updates, I would choose 'Default' ? Oh yes, on the category view, you have that option next to each category, which does what you expect. I have a further question. Choosing menu item Cygwin-X / X Win Server boots X windows. If you right click on the 'X' icon in the lower right side of the screen, it features applications xterm / emacs / notepad / xload. Is it possible to tailor the list of applications referenced above? to include say xclock, xeyes Yes. See http://x.cygwin.com/docs/ug/configure-cygwin-xwinrc.html And yet another question; I note the presence of a number of files in \usr\bin which start with 'gnome'. Does Cygwin/x feature gnome or kde as user interfaces? or does it only allow compilation of apps which use features of those interfaces? I don't think KDE or GNOME desktop environments are available. -- 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/
Re: problems with cygwin/x
On 14/10/2014 17:19, t s wrote: [duplicate email] Please don't spam the list with the same mail. If you get no answer, it is because no-one has an answer for you (yet). -- 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/
Re: FW: Cygwin start menu / mirrors
On 14/10/14 20:35, Jon TURNEY wrote: On 08/10/2014 23:40, t s wrote: And yet another question; I note the presence of a number of files in \usr\bin which start with 'gnome'. Does Cygwin/x feature gnome or kde as user interfaces? or does it only allow compilation of apps which use features of those interfaces? I don't think KDE or GNOME desktop environments are available. I think both are available in CygwinPorts. http://cygwinports.org/ Dave. -- 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/
cygwin macs failing siltently
With recent upgrade of cygwin, emacs is always crashing. Windows XP VirtualBox virtual machines (don't ask) setup.exe version 2.8.50 (32 bit) tried both emacs 24.3.93-1 and 24.3-2 X-server is cygin 64 bit on windows 7. It was working last week. Now silent crash, no log entries. Occassionally a core dump? More information - I had an older computer with an older version of cygwin 32 bit running an x-server and an older version of cygwin emacs 32 bit installed on a virtual machine. a) setting the DISPLAY to the new computer with the latest version doesn't help - the older emacs crashes with an illegal system call. However, there are no problems running xterm. b) after setting the DISPLAY to the old computer's cygwin x server, emacs runs fine on the old vm. Does anyone have suggestions? Thanks Gulliver -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwin emacs failing siletnly
Follow up: It is only emacs for X-windows that fails silently. emacs-nox works perfectly. As I said, the silent failure has no core dump and no log messages anywhere. Nothing is displayed in the shell window. Thanks Gulliver -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwin emacs failing siletnly
Try re-setting your fonts. See this post: https://cygwin.com/ml/cygwin/2013-12/msg00248.html -- Jim Reisert AD1C, jjreis...@alum.mit.edu, 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/
Re: cygwin emacs failing siletnly
Thanks for the pointer to fc-cache. On which machine should this be run? a) the machine hosting the X-Server b) the machine on which emacs is running fc-cache ran successfully on a - the machine hosting the x-server but fails silently on the virtual machine hosting emacs and xterm. Thanks Gulliver -- 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/
Issues since last update of cygwin - clipboard, crashing
Windows 7 Professional, I updated cygwin on the weekend of Oct 4 and am now having issues with cygwin X, mostly with the clipboard. I am running with no root window (XWin.exe) I have two different systems (home and work), one running cygwin 64 bit and the other cygwin 32 bit. Both have these issues. 1) frequent clipboard timeouts when querying the x-selection for something in the Windows clipboard 2) After an hour or two, the X-selection no longer appears in the windows clipboard, so I have to restart everything 3) cygwin X freezes - all windows are light grey and not responding 4) cygwin x has crashed a few times. These are all new symptoms since Oct 4. I have been using this set up for years with few problems. Is this a known problem that is being fixed? Thanks Gulliver -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: FW: Cygwin start menu / mirrors
On 04/10/2014 18:16, t s wrote: first of all, regarding the Cygwin setup program; the options are install / re-install / un-install / default is it correct that to install only the latest updates, I would choose the option 'default' ? I'm not sure what text you are looking at. The options for an individual package which is already installed are 'reinstall', 'uninstall', 'keep' and specific versions other than the currently installed one (if any). I can't see default anywhere. If you mean the default version, then yes, when curr is selected at the top, all packages which have updates, will be updated. The current version of the setup program, 2.850 (64 bit), on the select packages screen, features a default option. Please see; http://cpm86.com/default.jpg The four options are; Install; Reinstall; Uninstall; Default I just want to be sure; to install only the latest updates, I would choose 'Default' ? next question : if I delete the start menu option Cygwin/x and run the setup program for option default, it doesn't re-create the start menu option Cygwin/x is this 'feature' acknowledged, and is it being addressed? The start menu link for for the X server is owned by the package xinit. If you reinstall that package, it should be recreated. That's the answer I was looking for. Thank you. I have a further question. Choosing menu item Cygwin-X / X Win Server boots X windows. If you right click on the 'X' icon in the lower right side of the screen, it features applications xterm / emacs / notepad / xload. Is it possible to tailor the list of applications referenced above? to include say xclock, xeyes And yet another question; I note the presence of a number of files in \usr\bin which start with 'gnome'. Does Cygwin/x feature gnome or kde as user interfaces? or does it only allow compilation of apps which use features of those interfaces?
Re: Subject: Re: FW: Cygwin start menu / mirrors
On 04/10/2014 18:16, t s wrote: first of all, regarding the Cygwin setup program; the options are install / re-install / un-install / default is it correct that to install only the latest updates, I would choose the option 'default' ? I'm not sure what text you are looking at. The options for an individual package which is already installed are 'reinstall', 'uninstall', 'keep' and specific versions other than the currently installed one (if any). I can't see default anywhere. If you mean the default version, then yes, when curr is selected at the top, all packages which have updates, will be updated. next question : if I delete the start menu option Cygwin/x and run the setup program for option default, it doesn't re-create the start menu option Cygwin/x is this 'feature' acknowledged, and is it being addressed? The start menu link for for the X server is owned by the package xinit. If you reinstall that package, it should be recreated. I'm not sure what you are asking for here. If you were (for example) to delete /usr/bin/XWin.exe, are you expecting setup to reinstall that file, even though the package which owns it has no updates? While setup has many, many infelicities, I'm not sure this is one of them. Patches are always thoughtfully considered. -- 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/
Subject: Re: FW: Cygwin start menu / mirrors
first of all, regarding the Cygwin setup program; the options are install / re-install / un-install / default is it correct that to install only the latest updates, I would choose the option 'default' ? next question : if I delete the start menu option Cygwin/x and run the setup program for option default, it doesn't re-create the start menu option Cygwin/x is this 'feature' acknowledged, and is it being addressed? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem with Cygwin/X from remote Linux
On 03/10/2014 05:19, Chris Carlson wrote: I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. [...] I thought the two logs that you requested were a bit large for this e-mail, so I put them on my web site. You can access them as: Thanks. So, this is the set visuals that the X server supports. GL_VERSION: 3.1.0 - Build 8.15.10.2455 GL_VENDOR: Intel GL_RENDERER:Intel(R) HD Graphics Family [...] pxf vis fb render Ste aux accumMSdrawable Group/ idx ID ID VisualType Depth Lvl RGB CI DB Swap reo R G B A Z S buf AR AG AB AA bufs num W P Pb Float Trans Caveat - 1 51 42 TrueColor32 0 y . . . 8 8 8 8 0 0 0 0 0 0 000 y . y . . 2 2 52 43 TrueColor32 0 y . y xchg . 8 8 8 8 0 0 0 16 16 16 1600 y . y . . 2 3 53 44 TrueColor32 0 y . . . 8 8 8 8 24 8 0 0 0 0 000 y . y . . 2 4 21 45 TrueColor32 0 y . y xchg . 8 8 8 8 24 8 0 16 16 16 1600 y . y . . 2 5 54 46 TrueColor32 0 y . . . 8 8 8 8 16 0 0 0 0 0 000 y . y . . 2 6 55 47 TrueColor32 0 y . y xchg . 8 8 8 8 16 0 0 16 16 16 1600 y . y . . 2 7 56 48 TrueColor32 0 y . y copy . 8 8 8 8 0 0 0 16 16 16 1600 y . y . . 2 8 57 49 TrueColor32 0 y . y copy . 8 8 8 8 16 0 0 16 16 16 1600 y . y . . 2 9 41 4a TrueColor32 0 y . y copy . 8 8 8 8 24 8 0 16 16 16 1600 y . y . . 2 10 58 4b TrueColor32 0 y . . . 8 8 8 8 0 0 0 0 0 0 014 y . y . . 2 11 59 4c TrueColor32 0 y . y xchg . 8 8 8 8 0 0 0 16 16 16 1614 y . y . . 2 12 5a 4d TrueColor32 0 y . . . 8 8 8 8 16 0 0 0 0 0 014 y . y . . 2 13 5b 4e TrueColor32 0 y . y xchg . 8 8 8 8 16 0 0 16 16 16 1614 y . y . . 2 14 5c 4f TrueColor32 0 y . . . 8 8 8 8 24 8 0 0 0 0 014 y . y . . 2 15 5d 50 TrueColor32 0 y . y xchg . 8 8 8 8 24 8 0 16 16 16 1614 y . y . . 2 The mesa software renderer on the remote host constructs the set of visuals the client gets offered by picking the visuals from the server's set of visuals which match one of it's visuals OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 0x300) OpenGL version string: 2.1 Mesa 8.0.4 [...] visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat 0x051 24 tc 0 32 0 r . . 8 8 8 8 . . 0 0 0 0 0 0 0 0 0 None 0x053 24 tc 0 32 0 r . . 8 8 8 8 . . 0 24 8 0 0 0 0 0 0 None Unfortunately this set is small, and indeed doesn't contain any double-buffered visuals. Workarounds are to use either start Cygwin X server with -nowgl (so it too uses the software renderer and will offer a set of visual which is probably exactly the same), or to run the client with the LIBGL_ALWAYS_INDIRECT env var set (so that indirect rendering is used and the remote client has access to the actual set of visuals the server supports) I think the real fix to this is to fix the remote libGL, either so it matches visuals less precisely, or so it offers more visuals which can match, but this is not simple. Believe it or not, I just so happen to have an XWin.0.log from my old, old, old version of Cygwin. It was: Package: version 1.15.1-2 built 2014-05-06 Now I can reproduce this, it seems that this can be an unfortunate side-effect of the Improve visual matching with a remote libGL by not reporting pbuffer size limits change in 1.15.1-3 [1], which was intended to have the opposite effect, if previously no visuals at all were matching, so the software renderer was disabled, and we were falling back to indirect rendering. [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-06/msg2.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/
FW: Cygwin start menu / mirrors
fwd From: furrine...@hotmail.com To: cygwin-xfree@cygwin.com; jon.tur...@dronecode.org.uk Subject: Cygwin start menu / mirrors Date: Thu, 2 Oct 2014 06:05:10 -0400 Do these updates solve the problem with the start menu? I usually download updates from; ftp://mirrors.kernel.org/sourceware/cygwin/ Today it says; One or more mirrors you have selected is/are not on the list of official Cygwin mirrors any more. They may be out of date or missing some packages. if you experience installation problems consider trying official mirrors only when I click Yes, it goes to a download screen for setup.bz2.sig and it stalls which server should I be using? surely mirrors.kernel.org should be trustworthy? On 19:59, Jon TURNEY wrote: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.16.1-1 These packages contain XWin and the other X.Org X11 servers. In addition to upstream fixes [1][2], this contains the following cygwin-specific changes since 1.16.0-2: * Also automatically activate the -nolock option if /tmp is on an exFAT filesystem (Reported by 't s') * Log owning HWND when OpenClipboard fails * Log name of format atom when conversion of X clipboard to a format is refused * Also use _NET_WM_NAME for window titles in multiwindow mode * Downgrade some uninformative, always-emitted log output to debug * Check TEMP and TMP directories for accessibility before using for xkbcomp temporary file * Log filename when xkbcomp temporary file cannot be opened * Don't add an extra null character at the end of the text on the Windows clipboard (Thanks to Colin Harrison for patch) x86: 6b72d0bdaba1e89e90430a751eef61a9 *xorg-server-1.16.1-1-src.tar.xz 7b63f2b0e424292b62ceead452802f80 *xorg-server-1.16.1-1.tar.xz 9ca33a0326e50c5583730c495940903d *xorg-server-common-1.16.1-1.tar.xz 90c76a195c62251322883b31709817da *xorg-server-debuginfo-1.16.1-1.tar.xz ab4dfe97c97d333bb1cfb30f9ebee8b7 *xorg-server-devel-1.16.1-1.tar.xz da75032daeaf0e4664ed85c1d333657e *xorg-server-dmx-1.16.1-1.tar.xz 0eb18d9a456f6f37a403febc49080c9c *xorg-server-extra-1.16.1-1.tar.xz c1478d018c9be5781d85b8ee040398b8 *xwinclip-1.16.1-1.tar.xz x86_64: 46e54c368dd214df58810a6c703680b4 *xorg-server-1.16.1-1-src.tar.xz b90e45d736c3f79261518a4c9c9aa9c5 *xorg-server-1.16.1-1.tar.xz ed7dae27a5430a584b44265996b21a15 *xorg-server-common-1.16.1-1.tar.xz 763fd8a59ac318549bf9f5ee963e593a *xorg-server-debuginfo-1.16.1-1.tar.xz 12a2cc29adc45533bfcda7c33392deaf *xorg-server-devel-1.16.1-1.tar.xz 7dcfedb1a26176345f56c2c3d9058fbe *xorg-server-dmx-1.16.1-1.tar.xz 973da9ca3368b4356dc8e5b89880fc40 *xorg-server-extra-1.16.1-1.tar.xz 9e222444d273c7989631343557e878b3 *xwinclip-1.16.1-1.tar.xz [1] http://lists.x.org/archives/xorg-announce/2014-September/002478.html [2] http://lists.x.org/archives/xorg-announce/2014-September/002480.html -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: FW: Cygwin start menu / mirrors
On 02.10.2014 12:07, t s wrote: fwd Subject: Cygwin start menu / mirrors Date: Thu, 2 Oct 2014 06:05:10 -0400 Do these updates solve the problem with the start menu? I usually download updates from; ftp://mirrors.kernel.org/sourceware/cygwin/ Today it says; One or more mirrors you have selected is/are not on the list of official Cygwin mirrors any more. They may be out of date or missing some packages. if you experience installation problems consider trying official mirrors only when I click Yes, it goes to a download screen for setup.bz2.sig and it stalls which server should I be using? surely mirrors.kernel.org should be trustworthy? the ftp portion of mirrors.kernel.org was a bit unresponsive in the latest days. Try using the http://mirrors.kernel.org -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem with Cygwin/X from remote Linux
On 02/10/2014 04:53, Chris Carlson wrote: I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. [...] Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. Thanks for reporting this problem. Unfortunately, I can't reproduce it. Please can you attach the output of 'X -multiwindow -logverbose 3', so I can see what visuals the server thinks should be available, and the output of running 'glxinfo' on your remote system. Can you give the version of Fedora you are using, and the version of the libGL package you have? I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? No, this is not intentional. I guess this is an unintended consequence of a change. It would be useful in tracking down that change if you could identify the last X server release which worked correctly. The release announce mails are a hopefully accurate summary of intended changes (e.g [1]) [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-09/msg4.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/
Re: FW: Cygwin start menu / mirrors
Firstly, please do not send me personal email. Please read http://cygwin.com/problems.html#personal-email, particularly the section starting Shouldn't I just send email to straight to a Cygwin developer or package maintainer? On 02/10/2014 11:07, t s wrote: Do these updates solve the problem with the start menu? No, they solve the problems that they say they solve. If you are uncertain, you could always test it yourself. In addition to upstream fixes [1][2], this contains the following cygwin-specific changes since 1.16.0-2: * Also automatically activate the -nolock option if /tmp is on an exFAT filesystem (Reported by 't s') * Log owning HWND when OpenClipboard fails * Log name of format atom when conversion of X clipboard to a format is refused * Also use _NET_WM_NAME for window titles in multiwindow mode * Downgrade some uninformative, always-emitted log output to debug * Check TEMP and TMP directories for accessibility before using for xkbcomp temporary file * Log filename when xkbcomp temporary file cannot be opened * Don't add an extra null character at the end of the text on the Windows clipboard (Thanks to Colin Harrison for patch) -- 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/
Re: Problem with Cygwin/X from remote Linux
Hello, Jon. The version of Fedora I'm running is: Linux rolf 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux I thought the two logs that you requested were a bit large for this e-mail, so I put them on my web site. You can access them as: http://beachware.org/Cygwin/glxinfo.cygwin http://beachware.org/Cygwin/X.log Believe it or not, I just so happen to have an XWin.0.log from my old, old, old version of Cygwin. It was: Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 grover 1.7.30(0.272/5/3) 2014-05-23 10:36 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601](Win64) Package: version 1.15.1-2 built 2014-05-06 XWin was started with the following command line: X :0 -multiwindow Let me know if there's anything else I can provide. Chris Carlson On 10/2/2014 5:05 AM, Jon TURNEY wrote: On 02/10/2014 04:53, Chris Carlson wrote: I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. [...] Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. Thanks for reporting this problem. Unfortunately, I can't reproduce it. Please can you attach the output of 'X -multiwindow -logverbose 3', so I can see what visuals the server thinks should be available, and the output of running 'glxinfo' on your remote system. Can you give the version of Fedora you are using, and the version of the libGL package you have? I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? No, this is not intentional. I guess this is an unintended consequence of a change. It would be useful in tracking down that change if you could identify the last X server release which worked correctly. The release announce mails are a hopefully accurate summary of intended changes (e.g [1]) [1] https://cygwin.com/ml/cygwin-xfree-announce/2014-09/msg4.html -- 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/
Problem with Cygwin/X from remote Linux
I've been using Cygwin on a Windows 7 laptop for a few years as an X server from my Fedora Linux system. I ssh -X to my Linux system and run various X programs (thunderbird, chrome, nautilus, etc.) with very few issues. Every now and then, I will upgrade Cygwin_64 just to get the latest changes. I hope that the few issues I have will be cleared up. I believe the one issue I have with Thunderbird may be Thunderbird, not Cygwin/X. Anyway, over the past weekend, I upgraded again. The upgrade seemed to go well. No surprises until... One of the things I've been doing is learning OpenGL. I'm converting a sample program that I acquired while working at SGI to OpenGL (it was written in gl, the original SGI graphics language). For the past few months, all of my OpenGL programs have worked fine over the network. Suddenly, with the latest version of Cygwin/X, it doesn't. Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.1.0 OS: CYGWIN_NT-6.1 grover 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.16.1-1 built 2014-09-29 XWin was started with the following command line: X :0 -multiwindow I discovered there are no visuals available to remote X connections that support OpenGL double buffering. There used to be, but no longer. There are visuals available to direct connections, but not for remote. I tried looking through the FAQ for answers, but I didn't see anything. Is this something that has intentionally changed? Where would I find it if it is (for future reference so I don't bug you)? Thanks, Chris Carlson -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: problems running Cygwin/x
On 21/09/2014 17:56, t s wrote: I successfully installed Cygwin/x on an NTFS drive unfortunately the menu items are limited to; one item for Cygwin (cygwin64 terminal) five items for cygwinx (GNOME openbox, KDE openbox, openbox, xlaunch, xwin server) if I try GNOME Openbox, or KDE Openbox, or Openbox; it appears to start, but I cannot run xclock and there is no X server icon in the lower right icon panel [...] essentially I want to be sure Cygwin/x has installed correctly; particularly the three Openbox options do not seem to do anything; should they be bringing up some sort of GNOME or KDE desktop? It seems that the open start menu links don't work correctly anymore. It seems that shortcut targets like 'C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startx /usr/bin/openbox-session' need the new --quote option in run-1.3.3 to work correctly. Thanks for drawing this problem to my attention. -- 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/
RE: problems running Cygwin/x
When you make the changes to run-1.3.3, can you email me and say when I should re-install the appropriate packages please? my email is furrine...@hotmail.com thank you Date: Fri, 26 Sep 2014 16:00:20 +0100 From: jon.tur...@dronecode.org.uk To: cygwin-xfree@cygwin.com CC: furrine...@hotmail.com Subject: Re: problems running Cygwin/x On 21/09/2014 17:56, t s wrote: I successfully installed Cygwin/x on an NTFS drive unfortunately the menu items are limited to; one item for Cygwin (cygwin64 terminal) five items for cygwinx (GNOME openbox, KDE openbox, openbox, xlaunch, xwin server) if I try GNOME Openbox, or KDE Openbox, or Openbox; it appears to start, but I cannot run xclock and there is no X server icon in the lower right icon panel [...] essentially I want to be sure Cygwin/x has installed correctly; particularly the three Openbox options do not seem to do anything; should they be bringing up some sort of GNOME or KDE desktop? It seems that the open start menu links don't work correctly anymore. It seems that shortcut targets like 'C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startx /usr/bin/openbox-session' need the new --quote option in run-1.3.3 to work correctly. Thanks for drawing this problem to my attention. -- 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/
problems running Cygwin/x
I successfully installed Cygwin/x on an NTFS drive unfortunately the menu items are limited to; one item for Cygwin (cygwin64 terminal) five items for cygwinx (GNOME openbox, KDE openbox, openbox, xlaunch, xwin server) please see graphic at; http://cpm86.com/menu.jpg if I try GNOME Openbox, or KDE Openbox, or Openbox; it appears to start, but I cannot run xclock and there is no X server icon in the lower right icon panel if I try xlaunch, it shows a dialog select display settings, then select how to start clients, then extra settings; then it shows an 'X' icon in the lower RH panel; and when I right-mouse-click the X icon, choose applications/xterm, it brings up a terminal window where I can run xclock etc if I try xwin server it doesn't bring up the xlaunch dialogs, instead it immediately opens a terminal window where I can start xclock etc essentially I want to be sure Cygwin/x has installed correctly; particularly the three Openbox options do not seem to do anything; should they be bringing up some sort of GNOME or KDE desktop? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: problems installing Cygwin/x
On 04/09/2014 18:46, Marco Atzeri wrote: On 04/09/2014 19:33, t s wrote: I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened. (EE) Fatal server error: (EE) Can't read lock file /tmp/.X0-lock This is covered in the FAQ [1]. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file Start the server with the -nolock option. This option is turned on automatically when you have a FAT filesystem, but it seems this doesn't happen for exFAT filesystems. Thanks for reporting this problem. -- 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/
FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
sorry to bug you ; do you know of any utility which can convert a volume from EXFAT to NTFS? if not then no worries, but please email me and say so thank you From: furrine...@hotmail.com To: marco.atz...@gmail.com Subject: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Thu, 11 Sep 2014 16:18:05 -0400 I tried CONVERT from the NT command line it says C:\Users\Tadeusz Szocikconvert /? Converts a FAT volume to NTFS. CONVERT volume /FS:NTFS [/V] [/CvtArea:filename] [/NoSecurity] [/X] volume Specifies the drive letter (followed by a colon), mount point, or volume name. /FS:NTFS Specifies that the volume will be converted to NTFS. /V Specifies that Convert will be run in verbose mode. /CvtArea:filename Specifies a contiguous file in the root directory that will be the place holder for NTFS system files. /NoSecurity Specifies that the security settings on the converted files and directories allow access by all users. /X Forces the volume to dismount first if necessary. All open handles to the volume will not be valid. C:\Users\Tadeusz Szocikconvert e: /fs:ntfs /nosecurity /x CONVERT is not available for EXFAT drives. C:\Users\Tadeusz Szocik do you know of any other utility or do I have to reformat? thank you From: furrine...@hotmail.com To: marco.atz...@gmail.com Subject: RE: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Thu, 11 Sep 2014 16:08:51 -0400 hi, I'd like to convert to NTFS. It says; You should really consider converting the drive to NTFS with CONVERT.EXE. where is CONVERT.EXE? is this a Cygwin component or do I find it elsewhere? thank you Date: Thu, 11 Sep 2014 13:31:44 +0200 From: marco.atz...@gmail.com To: furrine...@hotmail.com; cygwin-xfree@cygwin.com Subject: Re: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 On 11/09/2014 11:51, t s wrote: From: furriner67 (at) hotmail.com To: cygwin-xfree (at) cygwin.com; marco.atzeri (at) gmail.com Subject: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Thu, 11 Sep 2014 05:49:53 -0400 fwd please see file; cpm86.com/cygcheck.out why are my posts to cygwin-xfree@cygwin.com not going through? thank you this passed ;-) as your disk is formatted as exFat and not as NTFS e: fd exFAT 122038Mb 81% CP UN CYGWIN I suggest this two readings: https://cygwin.com/faq.html#faq.using.chmod https://cygwin.com/cygwin-ug-net/ntsec.html Regards MArco -- 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/
FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
From: furrine...@hotmail.com To: cygwin-xfree@cygwin.com; marco.atz...@gmail.com Subject: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Thu, 11 Sep 2014 05:49:53 -0400 fwd please see file; cpm86.com/cygcheck.out why are my posts to cygwin-xfree@cygwin.com not going through? thank you From: furrine...@hotmail.com To: cygwin-xfree@cygwin.com Subject: RE: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Fri, 5 Sep 2014 19:04:34 -0400 cpm86.com/cygcheck.out thanks From: furrine...@hotmail.com To: cygwin-xfree@cygwin.com Subject: RE: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Fri, 5 Sep 2014 19:01:01 -0400 Can you also please also follow Run cygcheck -s -v -r cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a straight text file so that it can be easily viewed. done Date: Fri, 5 Sep 2014 16:55:49 + From: cygwin-xfree-digest-h...@cygwin.com To: cygwin-xfree@cygwin.com Subject: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Topics (messages 31775 through 31777): problems installing Cygwin/xþþ 31775 by: t s 31776 by: Marco Atzeri Possible X11 server bug 31777 by: mathog Administrivia: To subscribe to the digest, e-mail: cygwin-xfree-digest-subscr...@cygwin.com To unsubscribe from the digest, e-mail: cygwin-xfree-digest-unsubscr...@cygwin.com To post to the list, e-mail: cygwin-xfree@cygwin.com -- --Forwarded Message Attachment-- From: furrine...@hotmail.com To: cygwin-xfree@cygwin.com Subject: problems installing Cygwin/x Date: Thu, 4 Sep 2014 13:33:20 -0400 I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened. $ Xwin :0 -multiwindow -clipboard -wgl Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 SONYZ 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.15.1-4 built 2014-07-18 XWin was started with the following command line: Xwin :0 -multiwindow -clipboard -wgl _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 _XSERVTransmkdir: this may cause subsequent errors (EE) Fatal server error: (EE) Can't read lock file /tmp/.X0-lock (EE) Server terminated with error (1). Closing log file. winDeinitMultiWindowWM - Noting shutdown in progress $ Help, please? My post to this mailing list of two weeks ago was deleted. It's impolite to delete a post without giving a reason. Please allow this post. Thank you. --Forwarded Message Attachment-- Date: Thu, 4 Sep 2014 19:46:26 +0200 From: marco.atz...@gmail.com To: cygwin-xfree@cygwin.com Subject: Re: problems installing Cygwin/x On 04/09/2014 19:33, t s wrote: I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened. $ Xwin :0 -multiwindow -clipboard -wgl Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 SONYZ 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.15.1-4 built 2014-07-18 XWin was started with the following command line: Xwin :0 -multiwindow -clipboard -wgl _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 _XSERVTransmkdir: this may cause subsequent errors (EE) Fatal server error: (EE) Can't read lock file /tmp/.X0-lock (EE) Server terminated with error (1). Closing log file. winDeinitMultiWindowWM - Noting shutdown in progress $ Help, please? My post to this mailing list of two weeks ago was deleted. It's impolite to delete a post without giving a reason. Please allow this post. Thank you. Hi TS your mail was probably rejected by the SPAM filter. possibly as there as something looking as a raw email address. Can you also please also follow Run cygcheck -s -v -r cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a straight text file so that it can be easily viewed. as reported https://cygwin.com/problems.html Regards Marco --Forwarded Message Attachment-- To: cygwin-xfree@cygwin.com Subject: Possible X11 server bug Date: Fri, 5 Sep 2014 09:55:44 -0700 From: mat...@caltech.edu I have run into an issue which _may_ indicate a bug in the cygwin X11 server. The issue is documented here: https://bugs.launchpad.net/inkscape/+bug/1365153 In brief, for certain test files viewed in Inkscape (current trunk at least) over a putty ssh tunnel from an Ubuntu 12.04lts system to the cygwin 1.14.1.0 X11 server there are glitches in the image when it is zoomed in and out. This does not occur
Re: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 -0000 Issue 3554
On 11/09/2014 11:51, t s wrote: From: furriner67 (at) hotmail.com To: cygwin-xfree (at) cygwin.com; marco.atzeri (at) gmail.com Subject: FW: cygwin-xfree Digest 5 Sep 2014 16:55:49 - Issue 3554 Date: Thu, 11 Sep 2014 05:49:53 -0400 fwd please see file; cpm86.com/cygcheck.out why are my posts to cygwin-xfree@cygwin.com not going through? thank you this passed ;-) as your disk is formatted as exFat and not as NTFS e: fd exFAT 122038Mb 81% CPUN CYGWIN I suggest this two readings: https://cygwin.com/faq.html#faq.using.chmod https://cygwin.com/cygwin-ug-net/ntsec.html Regards MArco -- 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/
problems installing Cygwin/x
I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened. $ Xwin :0 -multiwindow -clipboard -wgl Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 SONYZ 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.15.1-4 built 2014-07-18 XWin was started with the following command line: Xwin :0 -multiwindow -clipboard -wgl _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 _XSERVTransmkdir: this may cause subsequent errors (EE) Fatal server error: (EE) Can't read lock file /tmp/.X0-lock (EE) Server terminated with error (1). Closing log file. winDeinitMultiWindowWM - Noting shutdown in progress $ Help, please? My post to this mailing list of two weeks ago was deleted. It's impolite to delete a post without giving a reason. Please allow this post. Thank you.
Re: problems installing Cygwin/x
On 04/09/2014 19:33, t s wrote: I can't get cygwin/x to run. I downloaded the latest revision. Here is what happened. $ Xwin :0 -multiwindow -clipboard -wgl Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-6.1 SONYZ 1.7.32(0.274/5/3) 2014-08-13 23:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (Win64) Package: version 1.15.1-4 built 2014-07-18 XWin was started with the following command line: Xwin :0 -multiwindow -clipboard -wgl _XSERVTransmkdir: Mode of /tmp/.X11-unix should be set to 1777 _XSERVTransmkdir: this may cause subsequent errors (EE) Fatal server error: (EE) Can't read lock file /tmp/.X0-lock (EE) Server terminated with error (1). Closing log file. winDeinitMultiWindowWM - Noting shutdown in progress $ Help, please? My post to this mailing list of two weeks ago was deleted. It's impolite to delete a post without giving a reason. Please allow this post. Thank you. Hi TS your mail was probably rejected by the SPAM filter. possibly as there as something looking as a raw email address. Can you also please also follow Run cygcheck -s -v -r cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a straight text file so that it can be easily viewed. as reported https://cygwin.com/problems.html Regards Marco -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 open gl c++ code does not compile with new cygwin download
On 01/09/2014 20:42, Tony wrote: For the X11 GL/glu.h, you need to install libGLU-devel and its dependencies. How do you install libGLU-devel and its dependencies (on Windows 8.1)? Thanks. You use the cygwin setup program to install the libGLU-devel package. See https://cygwin.com/install.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/
Re: X11 open gl c++ code does not compile with new cygwin download
For the X11 GL/glu.h, you need to install libGLU-devel and its dependencies. How do you install libGLU-devel and its dependencies (on Windows 8.1)? 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/
Re: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
On 26/05/2014 16:55, Ralf Oltmanns wrote: I updated to 1.15.1-2 and placed the crash-reporter into cygwin64/bin. A crash report has been submitted to your server. The same problem still persists. Thanks very much. Could you please also install the xorg-server-debuginfo package, remove xorg_cygwin_crash_reporter_gui and show the log you get then? On 05/26/2014 03:32 PM, Jon TURNEY wrote: On 26/05/2014 14:18, Ralf Oltmanns wrote: I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) My installation is as follows: Release: 1.15.0.0 Package: version 1.15.0-2 built 2014-01-11 Thanks for the bug report. The current XWin version is 1.15.1-2. Perhaps you could try again with that? If that doesn't resolve your problem, I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Could you then install the xorg-server-debuginfo package, which enables a more useful backtrace to be generated in the log, and try again? With 1.15.1, I also enabled a tool I have been working to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe -- 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/
Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
To whom it may concern, I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) My installation is as follows: Release: 1.15.0.0 Package: version 1.15.0-2 built 2014-01-11 XWin was started with the following command-line: X :0 -multiwindow Please find attached the XWin.0.log. Kind regards Ralf Oltmanns Systems Adminstrator financial.com AG Munich Head Office/Hauptsitz München: Georg-Muche-Straße 3 | 80807 Munich | Germany | Tel. +49 89 318528-0 | Google Maps: http://goo.gl/maps/UHwj9 Frankfurt Branch Office/Niederlassung Frankfurt: Messeturm | Friedrich-Ebert-Anlage 49 | 60327 Frankfurt am Main | Germany | Google Maps: http://goo.gl/maps/oSGjR Management Board/Vorstand: Dr. Steffen Boehnert | Dr. Alexis Eisenhofer | Dr. Yann Samson Supervisory Board/Aufsichtsrat: Rolf Richter (Chairman/Vorsitzender) Register Court/Handelsregister: Munich – HRB 128972 | Sales Tax ID Number/St.Nr.: DE205370553 XWin.0.log Description: XWin.0.log -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Fatal error when starting Cygwin/X v1.15.0-2 built 2014-01-11
On 26/05/2014 14:18, Ralf Oltmanns wrote: I just installed cygwin/X on a freshly installed Windows 7 Professional (64bit). When trying to start XWin Server, it crashes with signal 11 (Segmentation fault) My installation is as follows: Release: 1.15.0.0 Package: version 1.15.0-2 built 2014-01-11 Thanks for the bug report. The current XWin version is 1.15.1-2. Perhaps you could try again with that? If that doesn't resolve your problem, I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Could you then install the xorg-server-debuginfo package, which enables a more useful backtrace to be generated in the log, and try again? With 1.15.1, I also enabled a tool I have been working to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe -- 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/
Re: running openGL application remotely using ssh -X and cygwin/x ,extension NV-GLX missing on display localhost:10.0
On 28/04/2014 22:02, Linda Walsh wrote: Jon TURNEY wrote: Yes, this should work. *But*, I'm pretty sure it doesn't anymore since the Xgl extension that was used to transport the openGL commands between client/server was removed from xorg's Xserver. You seem to be confusing Xgl (an X server implementation) and GLX (an X protocol extension). While they do contain the same letters in a different order, they are very different things. AIGLX doesn't work with client's native openGL drives when the DISPLAY isn't local. Instead, it sends full-frame-buffer updates to simulate what would be happening -- something that appears to work correctly for small OpenGL windows. But is entirely 'faked' (not really remote openGL that used the Server's acceleration Hardware. Which would give you unaccelerated frame-buffer updates to simulate the effect. Not quite what used to be available. This is also totally wrong. You are (more or less) describing how mesa's direct software rendering works (which is usually the default path for remote displays) which is completely different to AIGLX (where GL commands are sent via the GLX protocol to the X server and rendered using acceleration there) So, again, please stop spreading misinformation. I'm sure there are bugs in and limitations with OpenGL and the XWin server, but if you have a problem, please don't hijack someone else's thread, but report it in sufficient detail for me to try to reproduce it. -- 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/
Re: running openGL application remotely using ssh -X and cygwin/x ,extension NV-GLX missing on display localhost:10.0
Jon TURNEY wrote: Yes, this should work. *But*, I'm pretty sure it doesn't anymore since the Xgl extension that was used to transport the openGL commands between client/server was removed from xorg's Xserver. From wikipedia: Xgl was a display server implementation supporting the X Window System protocol designed to take advantage of modern graphics cards via their OpenGL drivers, layered on top of OpenGL via glitz. It supported hardware acceleration of all X, OpenGL and XVideo applications and graphical effects by a compositing window manager such as Compiz or Beryl. The project was started by David Reveman of Novell and first released on January 2, 2006. It was removed[1] from the X.org server in favor of AIGLX on June 12, 2008. --- AIGLX doesn't work with client's native openGL drives when the DISPLAY isn't local. Instead, it sends full-frame-buffer updates to simulate what would be happening -- something that appears to work correctly for small OpenGL windows. But is entirely 'faked' (not really remote openGL that used the Server's acceleration Hardware. I'm not entirely clear if the 'extension �NV-GLX� missing' message is a warning or an error, but according to the internet it seems to be due to having a Nvidia libGL installed on the remote machine, so if all else fails you might look at uninstalling the Nvidia proprietary driver and libGL, and using mesa instead. Which would give you unaccelerated frame-buffer updates to simulate the effect. Not quite what used to be available. Note: this isn't a cygwin specific problem. i.e. people running xorg's server on a linux box have the same problem -- accelerated+remote 3D graphics seems to be dead. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: running openGL application remotely using ssh -X and cygwin/x ,extension NV-GLX missing on display localhost:10.0
I know for a fact that when I ssh from my Ubuntu partition to the remote machine the application works without crashing. However, when I use windows 8 and Cygwin X the crash occurs for the same application. I will install the debugging tools and report my findings to you. Thanks for looking into this! -Octavian On Sat, Apr 26, 2014 at 7:52 AM, Jon TURNEY jon.tur...@dronecode.org.uk wrote: On 24/04/2014 23:45, Biris, Octavian wrote: I am attempting to run an opengl application remptely to a ubuntu linux machine from my windows 8 machine. To do so I start the cygwin console, call startxwin. Running glxinfo | grep OpenGL returns the vendor of my graphics card, NVIDIA. glxinfo |grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 580/PCIe/SSE2 OpenGL version string: 1.4 (4.4.0) OpenGL extensions: Then I ssh on the ubuntu machine using -X -C as the parameters. When attempting to start the application the console reads extension NV-GLX missing on display localhost:10.0. Afterwards, the cygwin/X server crashes and I have to restart it.I attached the log from /var/log/Xwin/XWin.0.log Thanks for the bug report. I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Can you install the xorg-server-debuginfo package and try again? I also have been working on a tool to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe Does cygwin/x support running OpenGL applications remotely? Am I missing something? Do I have to install the mesa-utils libraries on the remote machine? Yes, this should work. I'm not entirely clear if the 'extension NV-GLX missing' message is a warning or an error, but according to the internet it seems to be due to having a Nvidia libGL installed on the remote machine, so if all else fails you might look at uninstalling the Nvidia proprietary driver and libGL, and using mesa instead. -- 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/
Re: running openGL application remotely using ssh -X and cygwin/x ,extension NV-GLX missing on display localhost:10.0
On 24/04/2014 23:45, Biris, Octavian wrote: I am attempting to run an opengl application remptely to a ubuntu linux machine from my windows 8 machine. To do so I start the cygwin console, call startxwin. Running glxinfo | grep OpenGL returns the vendor of my graphics card, NVIDIA. glxinfo |grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 580/PCIe/SSE2 OpenGL version string: 1.4 (4.4.0) OpenGL extensions: Then I ssh on the ubuntu machine using -X -C as the parameters. When attempting to start the application the console reads extension NV-GLX missing on display localhost:10.0. Afterwards, the cygwin/X server crashes and I have to restart it.I attached the log from /var/log/Xwin/XWin.0.log Thanks for the bug report. I'm afraid that the log doesn't contain enough information for me to identify the cause of the crash. Can you install the xorg-server-debuginfo package and try again? I also have been working on a tool to automate sending better crash information using minidumps. If you would like to try that, download it from [1] (anonymous ftp) and put it into /usr/bin and reproduce your crash again. [1] ftp://cygwin.com/pub/cygwinx/x86_64/xorg_cygwin_crash_reporter_gui.exe Does cygwin/x support running OpenGL applications remotely? Am I missing something? Do I have to install the mesa-utils libraries on the remote machine? Yes, this should work. I'm not entirely clear if the 'extension “NV-GLX” missing' message is a warning or an error, but according to the internet it seems to be due to having a Nvidia libGL installed on the remote machine, so if all else fails you might look at uninstalling the Nvidia proprietary driver and libGL, and using mesa instead. -- 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/
running openGL application remotely using ssh -X and cygwin/x ,extension NV-GLX missing on display localhost:10.0
Hello there! I am attempting to run an opengl application remptely to a ubuntu linux machine from my windows 8 machine. To do so I start the cygwin console, call startxwin. Running glxinfo | grep OpenGL returns the vendor of my graphics card, NVIDIA. glxinfo |grep OpenGL OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 580/PCIe/SSE2 OpenGL version string: 1.4 (4.4.0) OpenGL extensions: Then I ssh on the ubuntu machine using -X -C as the parameters. When attempting to start the application the console reads extension NV-GLX missing on display localhost:10.0. Afterwards, the cygwin/X server crashes and I have to restart it.I attached the log from /var/log/Xwin/XWin.0.log Does cygwin/x support running OpenGL applications remotely? Am I missing something? Do I have to install the mesa-utils libraries on the remote machine? Thanks so much! -Octavian XWin.0.log Description: Binary data -- 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/
windows 7 cygwin/XWin session dies
Hello, I run my cygwin/XWin.exe session on Windows 7 Professional and this session dies when I iconify it during some time (let'say 20 min). I think the problem is not to iconify it but more to not do anything. It is very uncomfortable because I have to relaunch it every time I do something else (emails, internet,...) more than about 20 minutes... I do not understand why the X session crashes... Could anyone help me ? It seems there is something with : XDM: Alive response indicates session dead, declaring session dead but I do not know which parameter I have to change to modify this behaviour... Here is the log file of the session : Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.9.2.0 (10902000) Build Date: 2010-11-03 XWin was started with the following command line: /usr/bin/XWin -query asterix ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1200 winInitializeDefaultScreens - native DPI x 96 y 96 [ 5918.085] winInitializeScreens - 1 [ 5918.085] winInitializeScreen - 0 [ 5918.085] (II) xorg.conf is not supported [ 5918.085] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 5918.085] LoadPreferences: /home/caubel/.XWinrc not found [ 5918.085] LoadPreferences: Loading /etc/X11/system.XWinrc [ 5918.085] LoadPreferences: Done parsing the configuration file... [ 5918.085] winGetDisplay: DISPLAY=:0.0 [ 5918.085] winDetectSupportedEngines - Windows NT/2000/XP [ 5918.116] winDetectSupportedEngines - DirectDraw installed [ 5918.116] winDetectSupportedEngines - Allowing PrimaryDD [ 5918.116] winDetectSupportedEngines - DirectDraw4 installed [ 5918.116] winDetectSupportedEngines - Returning, supported engines 001f [ 5918.131] winSetEngine - Using Shadow DirectDraw NonLocking [ 5918.131] winScreenInit - Using Windows display depth of 32 bits per pixel [ 5918.147] winFinishScreenInitFB - Masks: 00ff ff00 00ff [ 5918.147] Screen 0 added at virtual desktop coordinate (0,0). [ 5918.147] MIT-SHM extension disabled due to lack of kernel support [ 5918.163] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 5918.194] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [ 5918.194] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 5918.506] winPointerWarpCursor - Discarding first warp: 957 566 [ 5918.506] (--) 8 mouse buttons found [ 5918.506] (--) Setting autorepeat to delay=500, rate=31 [ 5918.506] (--) Windows keyboard layout: 040C (040c) French, type 4 [ 5918.506] (--) Found matching XKB configuration French (Standard) [ 5918.506] (--) Model = pc105 Layout = fr Variant = none Options = none [ 5918.506] Rules = base Model = pc105 Layout = fr Variant = none Options = none [ 5919.286] winProcEstablishConnection - Hello [ 5919.286] winInitClipboard () [ 5919.286] winProcEstablishConnection - winInitClipboard returned. [ 5919.286] winClipboardProc - Hello [ 5919.286] DetectUnicodeSupport - Windows NT/2000/XP [ 5919.301] winGetDisplay: DISPLAY=:0.0 [ 5919.301] winClipboardProc - DISPLAY=:0.0 [ 5919.301] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 6240.102] XDM: Alive response indicates session dead, declaring session dead [ 6240.102] winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. [ 6240.102] winClipboardProc - XDestroyWindow succeeded. [ 6240.102] winClipboardProc - Clipboard disabled - Exit from server [ 6240.149] winDeinitMultiWindowWM - Noting shutdown in progress Thanks a lot in advance ! Best regards, Arnaud -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: windows 7 cygwin/XWin session dies
On 22/04/2014 11:00, Arnaud Caubel wrote: I run my cygwin/XWin.exe session on Windows 7 Professional and this session dies when I iconify it during some time (let'say 20 min). I think the problem is not to iconify it but more to not do anything. It is very uncomfortable because I have to relaunch it every time I do something else (emails, internet,...) more than about 20 minutes... I do not understand why the X session crashes... Could anyone help me ? It seems there is something with : XDM: Alive response indicates session dead, declaring session dead but I do not know which parameter I have to change to modify this behaviour... Release: 1.9.2.0 (10902000) Build Date: 2010-11-03 This is quite an old version. While I am not aware of any fixes in this area, you might like to try with the current version. [ 6240.102] XDM: Alive response indicates session dead, declaring session dead This means I sent an XDMCP keepalive for the current session to the XDM server, but it's response said that the session wasn't alive. One question I have is if your machine running XWin is idle, and going into a sleep state before this problem occurs? If that is the case, that may be the problem, as XDM will, by default, periodically test if it can contact the display and declare the session dead if that fails. If your display manager is XDM, that can be turned off by setting the DisplayManager.DISPLAY.pingInterval resource to 0. Other display managers may have similar settings. Alternatively, you could arrange for sleeping to be suspended while the X server is running (It seems on Win7 or later you can use powercfg -requestsoverride to prevent sleep while a specified program is running, or there are several simple utilities available which prevent suspend while they are running) If that is not the case, the XDM logs on the XDM host might be informative, if you have access to them. Failing that, you could use wireshark or similar to monitor the XDMCP protocol interactions. -- 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/
Re: problem with opengl (glxgears) running on cygwin ....
On 2014-03-25 09:05, Jon TURNEY wrote: On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. This should be fixed in mesa-demos-8.1.0-2. 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/
remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....)
Yaakov (Cygwin/X) wrote: On 2014-03-25 09:05, Jon TURNEY wrote: On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. This should be fixed in mesa-demos-8.1.0-2. FWIW, I tried another X server...VcXsrv?... Same with that program. I tried several, got some that worked, most didn't. Of the few that worked 'well' remotely, they were variations on the glgears... got about 400-500 FPS -- and about low 300's MB/s in bandwidth consumed... that sounds about right... but I think there are other problem in trying to get a remote desktop to work now... everything wants to connect to the session bus -- and many progs won't start if they can't. So if I can't figure out a way to get that to work, remote usage is left at a fairly primitive level despite the high frame rates on a 3x4 window... ;-) One of the demo progs said it required opengl 2.1 .. my card has V4.something. well above 2.1, so that seems like another latent problem. Will look for the fixed version ... thanks for the news... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: problem with opengl (glxgears) running on cygwin ....
On 20/03/2014 08:41, Linda Walsh wrote: When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Same effect happens when I try remotely. Window comes up with gears displayed, but no motion. Fraps also shows 30 FPS. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. Since [1], glxgears turns at a constant 70 degrees per second. glxSwapBuffers does not block when used with indirect rendering, which means that lots of frames can be rendered almost instantly, with no apparent rotation, since the elapsed time between frames is very small. glxgears is a very basic test that GLX is functioning, and definitely not a benchmark. Real GLX clients should have a better mechanism for ensuring their animation rate doesn't outrun the vsync frequency. If you have any problems with real GLX clients, I would be interested to hear them. [1] http://cgit.freedesktop.org/mesa/demos/commit/src/xdemos/glxgears.c?id=0b19fb0a5c6299baf28e26625e39773846f815b2 When I try remote display, the above is pretty much the same except I get an error on the client system that it can't load the 3d swrast.so driver on the other end. There is some problem with loading the swrast_dri.so renderer on the remote system, so it is falling back to indirect rendering. What is the OS of the remote system? But it sees pretty much the same capabilities -- FWIW, there is next to zilch network traffic happening when I try this.. I mean while it is happening. Before and after ~ 200-400KB/s (xosview), during, all my X windows become very slow and no longer refresh steadily. Network throughput registers a drop to 1-80KB/s. Despite that -- xwin pegs a cpu @100% and stays that way until I exit glxgears. I think this is because glxgears will send frames as fast as it can, and can saturate the X server. -- 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/
Re: problem with opengl (glxgears) running on cygwin ....
Jon TURNEY wrote: Since [1], glxgears turns at a constant 70 degrees per second. --- 70 degress/s? How is that important? glxSwapBuffers does not block when used with indirect rendering, which means that lots of frames can be rendered almost instantly, with no apparent rotation, since the elapsed time between frames is very small. According to the text in the starting window it is rendering at 30FPS. -- I.e. it is sync'ed with my monitor's refresh rate (except for the 1st iteration when it acted unsynced) ... I.e. in starting window this was displayed: Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 45623 frames in 6.4 seconds = 7166.903 FPS 834 frames in 27.4 seconds = 30.428 FPS 822 frames in 28.8 seconds = 28.542 FPS With all X-window response degraded (Xserver process was peg'ed@100%cpu), virtually no network traffic -- dropped from a norm of 200-400KB/s down to between 1KB-80KB/s. glxgears is a very basic test that GLX is functioning, and definitely not a benchmark. Real GLX clients should have a better mechanism for ensuring their animation rate doesn't outrun the vsync frequency. I thought it was the most basic. It claims (except for the 1st iteration) that it is not outruning my monitor's refresh rate. If you have any problems with real GLX clients, I would be interested to hear them. I'd be interested in finding any that work and proves that it works locally. While my initial use was to try remote GLX, I reverted to trying it localling -- just to verify it worked as it used to. Thats what brought this on. What is the OS of the remote system? --- linux (opensuse 13.1). No one else on that list was able to see normal response... some got really sluggish response, others saw no movement or nothing. It was only after I ran glxgears locally that I figured I might also have a problem in Cygwin's X, in addition to any other problem I have w/remote display. I think this is because glxgears will send frames as fast as it can, and can saturate the X server. The demo claims to sync at the same rate the monitor is refreshing. i.e -- 30 FPS. -- 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/
problem with opengl (glxgears) running on cygwin ....
th cl r g b a ns b eat 0x021 24 tc 0 32 0 r y . 8 8 8 8 . . 4 24 8 16 16 16 16 0 0 None a bunch of lines 323 GLXFBConfigs: visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat 0x042 24 tc 0 32 0 r . . 8 8 8 0 . . 4 24 0 16 16 16 16 0 0 None ...a bunch more lines... - When I try remote display, the above is pretty much the same except I get an error on the client system that it can't load the 3d swrast.so driver on the other end. But it sees pretty much the same capabilities -- FWIW, there is next to zilch network traffic happening when I try this.. I mean while it is happening. Before and after ~ 200-400KB/s (xosview), during, all my X windows become very slow and no longer refresh steadily. Network throughput registers a drop to 1-80KB/s. Despite that -- xwin pegs a cpu @100% and stays that way until I exit glxgears. xwin log is below... Any ideas? more /var/log/xwin/XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.0.0 OS: CYGWIN_NT-6.1 Athenae 1.7.28(0.271/5/3) 2014-02-09 21:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601](Win64) Package: version 1.15.0-3 built 2014-02-25 XWin was started with the following command line: /usr/bin/XWin -dpi 120 -nomultimonitors -clipboard -ac -unixkill -nowinkill +bs -fp /windows/fonts,built-ins,/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/100dpi -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 2560 h 1600 winInitializeScreenDefaults - native DPI x 120 y 120 [ 86222.282] Initializing built-in extension Generic Event Extension [ 86222.282] Initializing built-in extension SHAPE [ 86222.282] Initializing built-in extension MIT-SHM [ 86222.282] Initializing built-in extension XInputExtension [ 86222.282] Initializing built-in extension XTEST [ 86222.282] Initializing built-in extension BIG-REQUESTS [ 86222.282] Initializing built-in extension SYNC [ 86222.282] Initializing built-in extension XKEYBOARD [ 86222.282] Initializing built-in extension XC-MISC [ 86222.282] Initializing built-in extension XINERAMA [ 86222.282] Initializing built-in extension XFIXES [ 86222.282] Initializing built-in extension XFree86-Bigfont [ 86222.282] Initializing built-in extension RENDER [ 86222.282] Initializing built-in extension RANDR [ 86222.282] Initializing built-in extension COMPOSITE [ 86222.282] Initializing built-in extension DAMAGE [ 86222.282] Initializing built-in extension MIT-SCREEN-SAVER [ 86222.282] Initializing built-in extension DOUBLE-BUFFER [ 86222.282] Initializing built-in extension RECORD [ 86222.282] Initializing built-in extension DPMS [ 86222.282] Initializing built-in extension Present [ 86222.282] Initializing built-in extension X-Resource [ 86222.282] Initializing built-in extension GLX [ 86222.282] (II) xorg.conf is not supported [ 86222.282] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 86222.282] (++) FontPath set to /windows/fonts,built-ins,/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/100dpi [ 86222.282] LoadPreferences: Loading /Users/law.Bliss/.XWinrc [ 86222.282] LoadPreferences: Done parsing the configuration file... [ 86222.329] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD[ 86222.329] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [ 86222.329] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 86222.345] winDetectSupportedEngines - Returning, supported engines 001f [ 86222.345] winSetEngine - Multi Window or Rootless = ShadowGDI [ 86222.345] winScreenInit - Using Windows display depth of 32 bits per pixel [ 86222.345] winAllocateFBShadowGDI - Creating DIB with width: 2560 height: 1600 depth: 32 [ 86222.345] winFinishScreenInitFB - Masks: 00ff ff00 00ff [ 86222.345] winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 [ 86222.345] winInitMultiWindowWM - Calling pthread_mutex_lock () [ 86222.345] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 86222.360] MIT-SHM extension disabled due to lack of kernel support [ 86222.360] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 86222.376] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' [ 86222.532] GL_VERSION: 4.4.0 [ 86222.532] GL_VENDOR: NVIDIA Corporation [ 86222.532] GL_RENDERER:GeForce GTX 590/PCIe/SSE2 [ 86222.532] (II) AIGLX: enabled GLX_SGI_make_current_read [ 86222.532] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 86222.532] (II) AIGLX: enabled GLX_SGI_swap_control
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 11:57 AM, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. I just installed the 64-bit version of Cygwin to another 64-bit Windows 7 PC, and it did not have this problem. After the installation was finished, my user was configured in the /etc/passwd file and did not have the mkgroup group. Instead, it was set to 513 (None), which I guess is okay - at least I don't get the error when launching a shell. I don't think I did anything different during the installation other than just getting a later version (I downloaded the software on 3/15/2014). FYI -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem launching XTerm on new Cygwin installation
On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. (I don't know about this one) Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303 (from yesterday) I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I'd try putting -e before the /bin/zsh, which moves it away from the bug noted. (actually, the trailing -l doesn't look right either) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 11:57 AM, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I've searched for this XTERM_SHELL error, but can't find anything. Can anybody help me? Thanks, Well, I did the following two things: 1. I changed the group id for my entry in the /etc/passwd file from 10530 (or whatever that value was) to 545 (Users) and the first error went away. 2. I changed the shortcut I use to launch the XTerms and removed the shell name at the end, so it now looks like this: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls and now the XTerm is started without any errors. I guess it's working now, but I'm curious why these problems happened on the laptop installation and not on the desktop installation. Especially why the XTerm launch command had to change. The one I showed first I've been using for years without problems. I don't remember how I came up with it now, but I remember spending a lot of time putting that together. Also, that original launch command is working on my other PC (the desktop) as well as my other machines running the 32-bit version of Cygwin. Thanks for any feedback/clarification. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 1:49 PM, Thomas Dickey wrote: On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote: I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently mkgroup. This indicates that neither your gid nor your pgsid is in /etc/group. (I don't know about this one) Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303 (from yesterday) I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I'd try putting -e before the /bin/zsh, which moves it away from the bug noted. (actually, the trailing -l doesn't look right either) Thanks. I think the -l was to cause a login shell, but I see now that is what the -ls argument does. Since I removed the shell argument (/bin/zsh -l) it is now working. I'm getting the shell I want, I suspect, because that is the shell mentioned in the /etc/passwd file for my user. As a result, it is working so I'll leave it alone. fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? Thanks for your help! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem launching XTerm on new Cygwin installation
On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote: As a result, it is working so I'll leave it alone. :-) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? yes - I finished #302 at the beginning of the week. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 2:12 PM, Thomas Dickey wrote: On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote: As a result, it is working so I'll leave it alone. :-) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? yes - I finished #302 at the beginning of the week. Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the /bin/zsh -l from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. I'm confused... FYI. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Problem launching XTerm on new Cygwin installation
On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote: Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the /bin/zsh -l from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. xterm handles these three cases differently: xterm xterm /bin/zsh xterm -e /bin/zsh The bug that I mentioned is in the second case - not in the other two. -- Thomas E. Dickey dic...@invisible-island.net http://invisible-island.net ftp://invisible-island.net signature.asc Description: Digital signature
Re: Problem launching XTerm on new Cygwin installation
On 3/7/2014 4:36 PM, Thomas Dickey wrote: On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote: Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the /bin/zsh -l from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. xterm handles these three cases differently: xterm xterm /bin/zsh xterm -e /bin/zsh The bug that I mentioned is in the second case - not in the other two. Thanks. That was the bug I hit on my laptop. However, my desktop PC was working fine with xterm ... /bin/zsh -l and then suddenly, it started getting the same error. I made the same change to it as I did on my laptop PC and it worked, so I'm not stopped - I'm just wondering how my desktop PC was working then suddenly stopped working without altering any of the Cygwin software or settings. -- 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/
Restricting Port 6000 access in Cygwin/X
My company recently sent an audit finding requesting for our Cygwin/X users with a finding of the following; The remote host is running an X11 server. X11 is a client-server protocol that can be used to display graphical applications running on a given host on a remote client. Since the X11 traffic is not ciphered, it is possible for an attacker to eavesdrop on the connection. The suggested solution was; Restrict access to this port. If the X11 client/server facility is not used, disable TCP support in X11 entirely (-nolisten tcp). My problem is that I haven't found any information that would help me accomplish this task. I've only recently taken over support of our Cygwin users and am not well versed in the software. Can this be done without breaking the functionality of the the software? If so, can you please advise on the steps to take to accomplish this? Current version being used is 1.7.11-1. Thanks, Kevin E. Brown Soli Deo Gloria! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: Restricting Port 6000 access in Cygwin/X
On 09/12/2013 14:37, Kevin Brown wrote: My company recently sent an audit finding requesting for our Cygwin/X users with a finding of the following; The remote host is running an X11 server. X11 is a client-server protocol that can be used to display graphical applications running on a given host on a remote client. Since the X11 traffic is not ciphered, it is possible for an attacker to eavesdrop on the connection. The suggested solution was; Restrict access to this port. If the X11 client/server facility is not used, disable TCP support in X11 entirely (-nolisten tcp). My problem is that I haven't found any information that would help me accomplish this task. I've only recently taken over support of our Cygwin users and am not well versed in the software. Can this be done without breaking the functionality of the the software? If so, can you please advise on the steps to take to accomplish this? The usual caveat applies: if you have an actual need for security, a random person on the internet is not where you should be getting your information. As suggested, if you start the X server with the option '-nolisten tcp' (see 'man Xserver'), then it will not accept remote connections. There's probably something to be said for this being the default configuration and requiring an explicit '-listen', but historically it's been this way. If you then need to connect to remote clients, use ssh forwarding, see [1]. [1] http://x.cygwin.com/docs/ug/using-remote-apps.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/
Re: Problem trying to build Cygwin X server from source
Jon TURNEY jon.tur...@dronecode.org.uk writes: This looks like [1], a mis-match in TLS-ness between XWin and libglapi. If you are building using the .cygport file it should have ./configure'ed with --disable-glx-tls? [1] http://www.cygwin.com/ml/cygwin-xfree/2011-10/msg00065.html Ah! I had indeed screwed up the configuration -- I was manually building in src using autogen.sh rather than in build and thus had lost the configuration set up by cygport. When I blew everything away and did the cygport stuff again, cd /usr/src/ cygport xorg-server.cygport prep cd /usr/src/ cygport xorg-server.cygport compile things built fine. Thank you for all your help! (To be clear, this didn't work before the 2 patches you had me make.) - Mark -- 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/
