From ajay050@gmail.com Mon Nov 1 04:59:00 2010 From: ajay050@gmail.com (Ajay Jain) Date: Mon, 01 Nov 2010 04:59:00 -0000 Subject: Xterm Title Message-ID: Hi, I want my Xterm to display a constant title say mercury. So I use: Xterm -T mercury. Further, I have placed the following line in my .Xresources: xterm*allowTitleOps: 0. From my .vnc/xstartup, I also do: xrdb -merge ~/.Xresources. Even then my Xterm title changes to logname@hostname:pwd. I want to avoid it and replace this with a fixed title. Could you suggest something? After all, what is it that is going wrong? I am also trying to set PROMT_COMMAND, without any success. Regards, Ajay. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From rcsaba@gmail.com Tue Nov 2 08:23:00 2010 From: rcsaba@gmail.com (Csaba Raduly) Date: Tue, 02 Nov 2010 08:23:00 -0000 Subject: Xterm Title In-Reply-To: References: Message-ID: Hi Ajay, On Mon, Nov 1, 2010 at 5:59 AM, Ajay Jain wrote: > Hi, > > I want my Xterm to display a constant title say mercury. So I use: > Xterm -T mercury. Further, I have placed the following line in my > .Xresources: xterm*allowTitleOps: 0. From my .vnc/xstartup, I also do: > xrdb -merge ~/.Xresources. Even then my Xterm title changes to > logname@hostname:pwd. I want to avoid it and replace this with a fixed > title. Could you suggest something? After all, what is it that is > going wrong? I am also trying to set PROMT_COMMAND, without any > success. Check your prompt ($PS1) for xterm title escape sequences (http://www.faqs.org/docs/Linux-mini/Xterm-Title.html), like \[\e]0; ... stuff ... \a\] -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ Life is complex, with real and imaginary parts. "Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds "People disagree with me. I just ignore them." -- Linus Torvalds -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From aaron@1buiz.com Tue Nov 2 11:00:00 2010 From: aaron@1buiz.com (Aaron Tyler) Date: Tue, 02 Nov 2010 11:00:00 -0000 Subject: Quick Question About GDI Message-ID: Hello, I was searching online to find more info about GDI and I came across your information. Can you tell me, are you still involved with GDI? If you are, how are things going for you? Please let me know. Sincerely, Aaron Tyler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From aaron@1buiz.com Tue Nov 2 11:00:00 2010 From: aaron@1buiz.com (Aaron Tyler) Date: Tue, 02 Nov 2010 11:00:00 -0000 Subject: Quick Question About GDI Message-ID: Hello, I was searching online to find more info about GDI and I came across your information. Can you tell me, are you still involved with GDI? If you are, how are things going for you? Please let me know. Sincerely, Aaron Tyler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From aaron@1buiz.com Tue Nov 2 11:30:00 2010 From: aaron@1buiz.com (Aaron Tyler) Date: Tue, 02 Nov 2010 11:30:00 -0000 Subject: Quick Question About GDI Message-ID: Hello, I was searching online to find more info about GDI and I came across your information. Can you tell me, are you still involved with GDI? If you are, how are things going for you? Please let me know. Sincerely, Aaron Tyler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From aaron@1buiz.com Tue Nov 2 12:00:00 2010 From: aaron@1buiz.com (Aaron Tyler) Date: Tue, 02 Nov 2010 12:00:00 -0000 Subject: Quick Question About GDI Message-ID: Hello, I was searching online to find more info about GDI and I came across your information. Can you tell me, are you still involved with GDI? If you are, how are things going for you? Please let me know. Sincerely, Aaron Tyler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From aaron@1buiz.com Tue Nov 2 12:00:00 2010 From: aaron@1buiz.com (Aaron Tyler) Date: Tue, 02 Nov 2010 12:00:00 -0000 Subject: Quick Question About GDI Message-ID: Hello, I was searching online to find more info about GDI and I came across your information. Can you tell me, are you still involved with GDI? If you are, how are things going for you? Please let me know. Sincerely, Aaron Tyler -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Wed Nov 3 23:41:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 03 Nov 2010 23:41:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.9.2-1 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.9.2-1 *** xorg-server-dmx-1.9.2-1 These packages contain XWin and the other X.Org X11 servers. In addition to upstream fixes, this contains the following cygwin-specific changes since 1.9.0-2: * Rewrite of the way clipboard thread is started, which should improve clipboard robustness in XDMCP session (thanks to Michel Hummel) * Fix clipboard interaction with nxproxy (and possibly other X clients) (thanks to Roland Cassard) * Fix WM_DISPLAYCHANGE handling in windowed mode to not resize the X screen * Don't write list email address into log * Fix random DPI after resize * Implement WGL AIGLX for non-toplevel X windows WGL AIGLX ========= The experimental WGL AIGLX mode (activated by the XWin command line option '-wgl') which enables hardware accelerated OpenGL rendering in the X server using the native WGL OpenGL interface, should now be working well enough to be useful. I'd very much like to hear reports of success or failure with specific OpenGL applications. For remote clients, you must 'export LIBGL_ALWAYS_INDIRECT=1' before starting the client application to force indirect rendering. For local clients, the recent update of libGL1 to 7.8.2-1 makes indirect rendering the default, so no special steps are needed. Please ensure you are using the latest display drivers for your graphics hardware before reporting any visual issues with WGL. Known problems: - OpenGL windows with static contents aren't re-drawn when occluded by a native Window and then exposed. Workaround: force the window to redraw, e.g. by resizing it. - When an OpenGL window is behind a native application window which uses layered windows for translucency e.g mintty, the OpenGL rendering is drawn over the top, flickering. Apparently, if we want to avoid this, we need to do the OpenGL rendering offscreen, then transfer it our window, so this becomes most of the 'use native compositing in multiwindow mode' todo list item. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From b.weeber@viastore.com Thu Nov 4 14:49:00 2010 From: b.weeber@viastore.com (Weeber, Burkhard) Date: Thu, 04 Nov 2010 14:49:00 -0000 Subject: 1.9.2.0: Xwin SIGSEGV when font server should be queried Message-ID: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> Hello, I updated my Cygwin with the latest available from the "setup.exe". Now XWin.exe gets a Signal 11 (Segmentation violation) when a font switch (-fn) is on the command line. Command: $ ssh -Y myaix "aixterm -fullcursor -geometry 81x30-125+93 -e /usr/local/bin/max.pl" Is OK. $ ssh -Y myaix "aixterm -fullcursor -geometry 81x30-125+93 -fn 6x10 -e /usr/local/bin/max.pl" Fails. I have a font server running on AIX6.1 and before the start this font server is added by xset command. This worked well until the update. Also the xlsfonts command of cygwin distribution causes XWin to SIGSEGV. Also when specifying "-fp tcp/myfontserver:7100" on the XWin start line any X-Program will cause a SIGSEGV. Regards Burkhard Burkhard Weeber Systemspezialist UNIX und Netze Specialist UNIX systems and networks viastore systems GmbH Magirusstra?e 13 D-70469 Stuttgart Tel.: +49 (0)711 98 18 277 Fax: +49 (0)711 98 18 180 mail: B.Weeber@viastore.com http://www.viastore.com Content of XWin.0.log after starting xlsfonts: 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: XWin -multiwindow -clipboard -silent-dup-error -xkbvariant nodeadkeys ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeDefaultScreens - native DPI x 96 y 96 [102623.744] winInitializeScreens - 1 [102623.744] winInitializeScreen - 0 [102623.744] (II) xorg.conf is not supported [102623.744] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [102623.744] LoadPreferences: Loading /cygdrive/c/Users/wee/.XWinrc [102623.744] LoadPreferences: Done parsing the configuration file... [102623.744] winGetDisplay: DISPLAY=:0.0 [102623.744] winDetectSupportedEngines - Windows NT/2000/XP [102623.791] winDetectSupportedEngines - DirectDraw installed [102623.791] winDetectSupportedEngines - Allowing PrimaryDD [102623.791] winDetectSupportedEngines - DirectDraw4 installed [102623.791] winDetectSupportedEngines - Returning, supported engines 0000001f [102623.791] winSetEngine - Multi Window or Rootless => ShadowGDI [102623.791] winScreenInit - Using Windows display depth of 32 bits per pixel [102623.822] winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 [102623.822] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [102623.822] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [102623.822] null screen fn ReparentWindow [102623.822] null screen fn RestackWindow [102623.822] InitQueue - Calling pthread_mutex_init [102623.822] InitQueue - pthread_mutex_init returned [102623.822] InitQueue - Calling pthread_cond_init [102623.822] InitQueue - pthread_cond_init returned [102623.822] winInitMultiWindowWM - Hello [102623.822] winInitMultiWindowWM - Calling pthread_mutex_lock () [102623.822] Screen 0 added at virtual desktop coordinate (0,0). [102623.822] winMultiWindowXMsgProc - Hello [102623.822] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [102623.978] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [102623.978] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [102623.978] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [102623.978] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [102624.742] winPointerWarpCursor - Discarding first warp: 840 525 [102624.742] (--) 3 mouse buttons found [102624.742] (--) Setting autorepeat to delay=500, rate=31 [102624.742] (--) Windows keyboard layout: "00000407" (00000407) "German", type 4 [102624.742] (--) Found matching XKB configuration "German (Germany)" [102624.742] (--) Model = "pc105" Layout = "de" Variant = "none" Options = "none" [102624.742] (++) XKB: variant: "nodeadkeys" [102624.742] Rules = "base" Model = "pc105" Layout = "de" Variant = "nodeadkeys" Options = "none" [102625.398] winInitMultiWindowWM - pthread_mutex_lock () returned. [102625.398] winInitMultiWindowWM - pthread_mutex_unlock () returned. [102625.398] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [102625.398] winGetDisplay: DISPLAY=:0.0 [102625.398] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [102625.398] winInitMultiWindowWM - DISPLAY=:0.0 [102625.398] winGetDisplay: DISPLAY=:0.0 [102625.398] winMultiWindowXMsgProc - DISPLAY=:0.0 [102625.413] winProcEstablishConnection - Hello [102625.413] winInitClipboard () [102625.413] winProcEstablishConnection - winInitClipboard returned. [102625.413] winClipboardProc - Hello [102625.413] DetectUnicodeSupport - Windows NT/2000/XP [102625.413] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [102625.413] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [102625.413] winGetDisplay: DISPLAY=:0.0 [102625.413] winClipboardProc - DISPLAY=:0.0 [102625.429] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [102638.471] Segmentation fault at address 0x14 [102638.471] Fatal server error: [102638.471] Caught signal 11 (Segmentation fault). Server aborting [102638.471] _________________________________________________________________________________________ Geschaeftsfuehrer/Managing Directors: Christoph Hahn-Woernle, Frank Apel HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart) St.-Nr. 99064/06051, USt-IdNr./VAT Reg.No.: DE 203036780 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Fri Nov 5 19:52:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 05 Nov 2010 19:52:00 -0000 Subject: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> Message-ID: <4CD46065.4080501@dronecode.org.uk> Thanks for reporting this issue. On 04/11/2010 14:49, Weeber, Burkhard wrote: > I updated my Cygwin with the latest available from the "setup.exe". Do you know which version of Xserver that worked you updated from? Examining /var/log/setup.log and/or using setup to revert to the previous version should tell you. > Now XWin.exe gets a Signal 11 (Segmentation violation) when a font switch (-fn) is on the command line. > > Command: > $ ssh -Y myaix "aixterm -fullcursor -geometry 81x30-125+93 -e /usr/local/bin/max.pl" > Is OK. > > $ ssh -Y myaix "aixterm -fullcursor -geometry 81x30-125+93 -fn 6x10 -e /usr/local/bin/max.pl" > Fails. > > I have a font server running on AIX6.1 and before the start this font server is added by xset command. > This worked well until the update. > > Also the xlsfonts command of cygwin distribution causes XWin to SIGSEGV. > > Also when specifying "-fp tcp/myfontserver:7100" on the XWin start line any X-Program will cause a SIGSEGV. I'm afraid I'm not able to reproduce this (testing using an xfs running on Solaris, I don't have access to AIX). Can you please obtain a backtrace as follows: 1) Install gdb (for gdb) and sysvinit (for pidof) packages 2) Start XWin using your normal method 3) In a non-X terminal window, run gdb --pid=`pidof /usr/bin/XWin` 4) Type 'c' at the '(gdb)' prompt 5) Reproduce your crash 6) Type 'bt full' at the '(gdb)' prompt. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From b.weeber@viastore.com Mon Nov 8 10:21:00 2010 From: b.weeber@viastore.com (Weeber, Burkhard) Date: Mon, 08 Nov 2010 10:21:00 -0000 Subject: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <4CD46065.4080501@dronecode.org.uk> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> <4CD46065.4080501@dronecode.org.uk> Message-ID: <578A937A9A719E4CB564C5A9013A6012032EA5B2@MAILD.viastore.de> The previous version, that was stable for xorg-server was 1.8.2-1, according to setup.log. The gdb stack trace is not very talkative: ... Loaded symbols for /usr/bin/cygXrender-1.dll [Switching to thread 8788.0x2740] (gdb) c Continuing. (no debugging symbols found) Program received signal SIGSEGV, Segmentation fault. [Switching to thread 8788.0x1178] 0x005508b5 in ?? () (gdb) bt full #0 0x005508b5 in ?? () No symbol table info available. #1 0x0000000c in ?? () No symbol table info available. #2 0x005fa120 in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. I will download current source and compile it with -g . Something funny about it: I had the "xset fp+ tcp/mystique:7100" commented out in the .startxwinrc. Then I started XWin, attached the gdb and issued the xset command from within a AIX aixterm shell. Then I started a window that has to use a font server font and it worked. Then I activated the xset command in the .startxwinrc again and the XWin crashed again. I keep on researching. Burkhard _________________________________________________________________________________________ Geschaeftsfuehrer/Managing Directors: Christoph Hahn-Woernle, Frank Apel HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart) St.-Nr. 99064/06051, USt-IdNr./VAT Reg.No.: DE 203036780 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From fergus@bonhard.uklinux.net Mon Nov 8 11:51:00 2010 From: fergus@bonhard.uklinux.net (Fergus) Date: Mon, 08 Nov 2010 11:51:00 -0000 Subject: Updated: xorg-server-1.9.2-1 Message-ID: <4CD7E3A7.3060704@bonhard.uklinux.net> Dear Jon, Since the update I have been unable to start XWin under [1.7]. Following my usual sequence at a bash prompt: mount n:/tmp /tmp # drive n: is NTFS as required run XWin -multiwindow & Normally these two would be followed by a command line for xterm, but I am not getting that far! The second line repeatedly generates a Cygwin/X error message box, where the reason given is very familiar: Can't read lock file /tmp/.X0-lock I used to get this when /tmp was FAT32 but as you see from line 1 I am making an explicit mount to a NTFS drive, and in the recent past this step has been all that is necessary to make progress. When I open /var/log/xwin/XWin.0.log for more information I read ~> cat /var/log/xwin/XWin.0.log 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 -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1280 h 1024 winInitializeDefaultScreens - native DPI x 96 y 96 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/mandible:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 Fatal server error: Can't read lock file /tmp/.X0-lock [1]+ Done run XWin -multiwindow Can anything be determined from the 3 lines in this file beginning _XSERV ("Unable" .. "failed" .. "failed")? Do I need to change my command sequence? BTW it's interesting (is it?) that the error message refers to 1.9.2.0 not 1.9.2-1. I'm surprised that there are no other anguished reports to you following the update, but I guess that's because the fault/ problem/ difficulty is mine rather than general. ?? Any insights much appreciated. Thank you, Fergus PS It kills me not to copy this to cygwin at cygwin dot com which I feel will have a much wider readership and skill set amongst that readership, but anybody sinning in this regard is always referred straight to Cygwin-X. A strange separation of reporting. Not that I am doubting your specific capability, just the potential for "Me Too" amongst readers. (Or even "Not Me, but I Know What's Going Wrong".) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Mon Nov 8 13:48:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 08 Nov 2010 13:48:00 -0000 Subject: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <578A937A9A719E4CB564C5A9013A6012032EA5B2@MAILD.viastore.de> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> <4CD46065.4080501@dronecode.org.uk> <578A937A9A719E4CB564C5A9013A6012032EA5B2@MAILD.viastore.de> Message-ID: <4CD7FFC2.3090004@dronecode.org.uk> On 08/11/2010 10:21, Weeber, Burkhard wrote: > The previous version, that was stable for xorg-server was 1.8.2-1, > according to setup.log. > > The gdb stack trace is not very talkative: > ... > Loaded symbols for /usr/bin/cygXrender-1.dll > [Switching to thread 8788.0x2740] > (gdb) c > Continuing. > (no debugging symbols found) > > Program received signal SIGSEGV, Segmentation fault. > [Switching to thread 8788.0x1178] > 0x005508b5 in ?? () > (gdb) bt full > #0 0x005508b5 in ?? () > No symbol table info available. > #1 0x0000000c in ?? () > No symbol table info available. > #2 0x005fa120 in ?? () > No symbol table info available. > #3 0x00000000 in ?? () > No symbol table info available. > > I will download current source and compile it with -g . Sorry, I forgot that it was stripped. To save you a bit of time, I've uploaded an unstripped build at [1] [1] ftp://cygwin.com/pub/cygwinx/XWin.20101108-git-eb4deaf9bfbab023.exe.bz2 > Something funny about it: > I had the "xset fp+ tcp/mystique:7100" commented out in the > .startxwinrc. > Then I started XWin, attached the gdb and issued the xset command from > within a AIX aixterm shell. > Then I started a window that has to use a font server font and it > worked. > > Then I activated the xset command in the .startxwinrc again and the XWin > crashed again. > I keep on researching. Thanks. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Mon Nov 8 14:06:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 08 Nov 2010 14:06:00 -0000 Subject: Updated: xorg-server-1.9.2-1 In-Reply-To: <4CD7E3A7.3060704@bonhard.uklinux.net> References: <4CD7E3A7.3060704@bonhard.uklinux.net> Message-ID: <4CD803CD.60603@dronecode.org.uk> On 08/11/2010 11:48, Fergus wrote: > Since the update I have been unable to start XWin under [1.7]. > Following my usual sequence at a bash prompt: > > mount n:/tmp /tmp # drive n: is NTFS as required > run XWin -multiwindow & > > Normally these two would be followed by a command line for xterm, but I am not > getting that far! The second line repeatedly generates a Cygwin/X error > message box, where the reason given is very familiar: > > Can't read lock file /tmp/.X0-lock > > I used to get this when /tmp was FAT32 but as you see from line 1 I am making > an explicit mount to a NTFS drive, and in the recent past this step has been > all that is necessary to make progress. When I open /var/log/xwin/XWin.0.log > for more information I read > > ~> cat /var/log/xwin/XWin.0.log > 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 -multiwindow > > ddxProcessArgument - Initializing default screens > winInitializeScreenDefaults - primary monitor w 1280 h 1024 > winInitializeDefaultScreens - native DPI x 96 y 96 > _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 > _XSERVTransOpen: transport open failed for inet6/mandible:0 > _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 > > Fatal server error: > Can't read lock file /tmp/.X0-lock I don't think there have been any significant changes in the lockfile code since the previous version, so this is mysterious. Does /tmp/.X0-lock exists? Is it readable by you? ('ls -al /tmp/.X0-lock' ) Are you sure /tmp is getting mounted successfully where you expect it to be? Have you tried '-nolock', as suggested by [1] > Can anything be determined from the 3 lines in this file beginning _XSERV > ("Unable" .. "failed" .. "failed")? Do I need to change my command sequence? The lines about inet6 are expected if you don't have IPv6 installed. If they have just started appearing with 1.9.2, that would be odd. > BTW it's interesting (is it?) that the error message refers to 1.9.2.0 not > 1.9.2-1. XWin only reports the upstream version (1.9.2.0), not our packaging version (the -1), for various uninteresting reasons. > I'm surprised that there are no other anguished reports to you following the > update, but I guess that's because the fault/ problem/ difficulty is mine > rather than general. ?? Any insights much appreciated. Either that or you are the only person who uses XWin :-) I never hear from anyone saying it just works fine, so I assume they don't exist :-) [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-cant-read-lock-file -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From b.weeber@viastore.com Mon Nov 8 14:11:00 2010 From: b.weeber@viastore.com (Weeber, Burkhard) Date: Mon, 08 Nov 2010 14:11:00 -0000 Subject: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <4CD46065.4080501@dronecode.org.uk> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> <4CD46065.4080501@dronecode.org.uk> Message-ID: <578A937A9A719E4CB564C5A9013A6012032EA7B0@MAILD.viastore.de> I did a bit of further reseach. It looks like it does not have anything to do with the way the font server is queried, but rather the way the startup is done. When I have the font server added during the XWin startup - either in the startxwin.bat, or a bash-script I call from there, the XWin SIGSEGVs. When I let the XWin come up with a few of my fav screens, and I then add the font server either from a cygwin shell or from a client shell the font server is subsequently queried correctly and the SIGSEGV does not appear. Strange. Anyway. Thanks for the exe to create a full stack trace. Here it is: (gdb) bt full #0 0x005b56a2 in doListFontsWithInfo (client=0x10981dc8, c=0x108693f0) at dixfonts.c:920 fpe = (FontPathElementPtr) 0x109816a0 err = 85 name = 0x5b3f36 "\203E?\001?h?e" namelen = 2280120 numFonts = 1628938183 fontInfo = {firstCol = 51800, lastCol = 34, firstRow = 1, lastRow = 0, defaultCh = 1, noOverlap = 0, terminalFont = 0, constantMetrics = 0, constantWidth = 0, inkInside = 0, inkMetrics = 0, allExist = 0, drawDirection = 0, cachable = 0, anamorphic = 0, maxOverlap = 0, pad = 0, maxbounds = {leftSideBearing = 0, rightSideBearing = 0, characterWidth = 0, ascent = 0, descent = 5840, attributes = 4248}, minbounds = {leftSideBearing = 16384, rightSideBearing = 0, characterWidth = 0, ascent = 0, descent = 100, attributes = 0}, ink_maxbounds = {leftSideBearing = -24633, rightSideBearing = 24855, characterWidth = 12266, ascent = 4168, descent = -29488, attributes = 65}, ink_minbounds = { leftSideBearing = -13640, rightSideBearing = 34, characterWidth = -29439, ascent = 65, descent = -13668, attributes = 34}, fontAscent = 0, fontDescent = 0, nprops = 0, props = 0x0, isStringProp = 0x1
} pFontInfo = (FontInfoRec *) 0x1097d4d8 reply = (xListFontsWithInfoReply *) 0x0 ---Type to continue, or q to quit--- length = 0 pFP = (xFontProp *) 0x1 i = 278402720 aliascount = 0 finalReply = {type = 0 '\0', nameLength = 0 '\0', sequenceNumber = 0, length = 0, minBounds = {leftSideBearing = 0, rightSideBearing = 0, characterWidth = -10208, ascent = 4207, descent = 24928, attributes = 102}, walign1 = 0, maxBounds = {leftSideBearing = -16392, rightSideBearing = 24843, characterWidth = 0, ascent = 0, descent = 0, attributes = 0}, walign2 = 0, minCharOrByte2 = 0, maxCharOrByte2 = 0, defaultChar = 0, nFontProps = 0, drawDirection = 0 '\0', minByte1 = 0 '\0', maxByte1 = 0 '\0', allCharsExist = 0 '\0', fontAscent = 0, fontDescent = 0, nReplies = 0} #1 0x00579a0f in ProcessWorkQueue () at dixutils.c:527 q = (WorkQueuePtr) 0x108698a8 p = (WorkQueuePtr *) 0x665de4 #2 0x005eb4f5 in WaitForSomething (pClientsReady=0x106d0ff8) at WaitFor.c:169 i = 1 waittime = {tv_sec = 30, tv_usec = 0} wt = (struct timeval *) 0x22cba0 timeout = 570906 clientsReadable = {fds_bits = {0, 0, 0, 0, 0, 0, 0, 0}} clientsWritable = {fds_bits = {277256200, 277256384, 0, 2280408, 6197569, 278385880, 2280328, 1}} ---Type to continue, or q to quit--- curclient = 292 selecterr = 0 nready = 0 devicesReadable = {fds_bits = {0, 0, 0, 0, 0, 0, 0, 0}} now = 447551595 someReady = 0 #3 0x0057093e in Dispatch () at dispatch.c:369 clientReady = (int *) 0x106d0ff8 result = 0 client = (ClientPtr) 0x10981dc8 nready = -1 icheck = (HWEventQueuePtr *) 0x665aa0 start_tick = 0 #4 0x0056af00 in main (argc=8, argv=0x10482fa8, envp=0x104480e0) at main.c:298 i = 1 alwaysCheckForInput = {0, 1} (gdb) Thanks for your help Burkhard _________________________________________________________________________________________ Geschaeftsfuehrer/Managing Directors: Christoph Hahn-Woernle, Frank Apel HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart) St.-Nr. 99064/06051, USt-IdNr./VAT Reg.No.: DE 203036780 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From reply-to-list-only-lh-x@cygwin.com Mon Nov 8 17:34:00 2010 From: reply-to-list-only-lh-x@cygwin.com (Larry Hall (Cygwin X)) Date: Mon, 08 Nov 2010 17:34:00 -0000 Subject: Updated: xorg-server-1.9.2-1 In-Reply-To: <4CD7E3A7.3060704@bonhard.uklinux.net> References: <4CD7E3A7.3060704@bonhard.uklinux.net> Message-ID: <4CD83482.2040209@cygwin.com> On 11/8/2010 6:48 AM, Fergus wrote: > PS It kills me not to copy this to cygwin at cygwin dot com which I feel will > have a much wider readership and skill set amongst that readership, but > anybody sinning in this regard is always referred straight to Cygwin-X. Because this is where those interested in Cygwin-X will be "hanging out" and looking for answers. For issues that are clearly X-related (or suspected to be so), it makes sense to query the list that supports that functionality, even if the readership is smaller than the main list. From the perspective of those with a problem, I would think there would be a preference for quality (of responses from this list) vs quantity (of eyes on some other list). And I'm sure those on the main list who aren't interested in X issues much prefer the lack of X traffic (and vice-versa). If you look in the email archives for discussions about merging the lists, you'll see these two points were well represented in the feedback, if my memory serves. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From b.weeber@viastore.com Tue Nov 9 08:45:00 2010 From: b.weeber@viastore.com (Weeber, Burkhard) Date: Tue, 09 Nov 2010 08:45:00 -0000 Subject: AW: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <4CD7FFC2.3090004@dronecode.org.uk> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> <4CD46065.4080501@dronecode.org.uk> <578A937A9A719E4CB564C5A9013A6012032EA5B2@MAILD.viastore.de> <4CD7FFC2.3090004@dronecode.org.uk> Message-ID: <578A937A9A719E4CB564C5A9013A6012032EAA31@MAILD.viastore.de> I managed to work around it. In the startup of XWin I start a few windows. In one of them I add the font server after a bit of sleep to settle down XWin. Now the XWin does not SIGSEGV any more why so ever. Here are the scripts I use to start up my X environment Burkhard Startxwin.bat: @echo off SET DISPLAY=127.0.0.1:0.0 REM REM The path in the CYGWIN_ROOT environment variable assignment assume REM that Cygwin is installed in a directory called 'cygwin' in the root REM directory of the current drive. You will only need to modify REM CYGWIN_ROOT if you have installed Cygwin in another directory. For REM example, if you installed Cygwin in \foo\bar\baz\cygwin, you will need REM to change \cygwin to \foo\bar\baz\cygwin. REM REM This batch file will almost always be run from the same drive (and REM directory) as the drive that contains Cygwin/X, therefore you will REM not need to add a drive letter to CYGWIN_ROOT. For example, you do REM not need to change \cygwin to c:\cygwin if you are running this REM batch file from the C drive. REM SET CYGWIN_ROOT=\cygwin SET RUN=%CYGWIN_ROOT%\bin\run -p /usr/bin SET PATH=.;%CYGWIN_ROOT%\bin;%PATH% SET XAPPLRESDIR= SET XCMSDB= SET XKEYSYMDB= SET XNLSPATH= REM Shared Memory support SET CYGWIN=server REM REM Cleanup after last run. REM if not exist %CYGWIN_ROOT%\tmp\.X11-unix\X0 goto CLEANUP-FINISH attrib -s %CYGWIN_ROOT%\tmp\.X11-unix\X0 del %CYGWIN_ROOT%\tmp\.X11-unix\X0 :CLEANUP-FINISH if exist %CYGWIN_ROOT%\tmp\.X11-unix rmdir %CYGWIN_ROOT%\tmp\.X11-unix REM REM The error "Fatal server error: could not open default font 'fixed'" is REM caused by using a DOS mode mount for the mount that the Cygwin/X REM fonts are accessed through. See the Cygwin/X FAQ for more REM information: REM http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-error-font-eof REM if "%OS%" == "Windows_NT" goto OS_NT REM Windows 95/98/Me echo startxwin.bat - Starting on Windows 95/98/Me goto STARTUP :OS_NT REM Windows NT/2000/XP/2003 echo startxwin.bat - Starting on Windows NT/2000/XP/2003 :STARTUP REM Description of XWin-specific options is in XWin(1) manpage. REM REM Startup the programs REM REM Startup the X Server with the integrated Windows-based window manager. REM WARNING: Do not use 'xwinclip' in conjunction with the ``-clipboard'' REM command-line parameter for XWin. Doing so would start two clipboard REM managers, which is never supposed to happen. %RUN% XWin -multiwindow -clipboard -silent-dup-error -xkbvariant nodeadkeys -logverbose 3 REM add my favorites %RUN% bash ~/.startxwinrc ~/startxwinrc: sleep 3 xrdb -all -load ~/.Xdefaults 2>>/tmp/startxwin.log # add WEE's favorites ssh -Y as1 "aixterm -fullcursor -geometry 81x30-125+93 -T \"ROUTERS-LOG\" -fn 6x10 -e /usr/local/bin/max.pl" & ssh -Y as1 "aixterm -ls -fullcursor -geometry 81x25+711+1 -bg magenta -fg snow -T \"Mail-LOG\" -fn 6x10 -e ~/bin/maillog.sh" & ssh -Y as1 "~/bin/termtk.pl" & #now add font server ; terminal closes upon script end ssh -Y as1 "aixterm -ls -fullcursor -geometry 81x25+37+208 -e ~/.xsetwee" ssh -Y as1 "aixterm -ls -fullcursor -geometry 81x25+37+208" & ssh -Y as1 "aixterm -ls -fullcursor -geometry 81x25+88+217" & .xsetwee: echo "Sleeping 10 seconds" sleep 10 xset fp+ tcp/mystique:7100 xset q echo "Sleeping 10 seconds until close" sleep 10 exit _________________________________________________________________________________________ Geschaeftsfuehrer/Managing Directors: Christoph Hahn-Woernle, Frank Apel HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart) St.-Nr. 99064/06051, USt-IdNr./VAT Reg.No.: DE 203036780 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From fergus@bonhard.uklinux.net Tue Nov 9 09:12:00 2010 From: fergus@bonhard.uklinux.net (Fergus) Date: Tue, 09 Nov 2010 09:12:00 -0000 Subject: Updated: xorg-server-1.9.2-1 In-Reply-To: <4CD803CD.60603@dronecode.org.uk> References: <4CD7E3A7.3060704@bonhard.uklinux.net> <4CD803CD.60603@dronecode.org.uk> Message-ID: <4CD90E42.5000308@bonhard.uklinux.net> >> Fatal server error: >> Can't read lock file /tmp/.X0-lock > Does /tmp/.X0-lock exists? Is it readable by you? Yes. > Are you sure /tmp is getting mounted successfully > where you expect it to be? Yes. > Have you tried '-nolock', as suggested by [1] I hadn't then. But I have now and as a consequence everything is working perfectly. Thank you. (Over time I have occasionally had to moderate the syntax of both "XWin" and "xterm" command lines to go from working to failing and back again to working. This is just another example. On an earlier occasion, the recommended use of -nolock failed. I am just happy when the current usage works. Thanks again.) Fergus -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From b.weeber@viastore.com Tue Nov 9 09:52:00 2010 From: b.weeber@viastore.com (Weeber, Burkhard) Date: Tue, 09 Nov 2010 09:52:00 -0000 Subject: AW: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <4CD7FFC2.3090004@dronecode.org.uk> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> <4CD46065.4080501@dronecode.org.uk> <578A937A9A719E4CB564C5A9013A6012032EA5B2@MAILD.viastore.de> <4CD7FFC2.3090004@dronecode.org.uk> Message-ID: <578A937A9A719E4CB564C5A9013A6012032EAAC8@MAILD.viastore.de> Rejoiced too early. When I start an application that uses a font that is not on the font server XWin crashes again with the same stack trace I already sent you. Burkhard _________________________________________________________________________________________ Geschaeftsfuehrer/Managing Directors: Christoph Hahn-Woernle, Frank Apel HRB 17335, Amtsgericht Stuttgart (Commercial Register District Court Stuttgart) St.-Nr. 99064/06051, USt-IdNr./VAT Reg.No.: DE 203036780 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From rodmedina@cantv.net Wed Nov 10 02:52:00 2010 From: rodmedina@cantv.net (Rodrigo Medina) Date: Wed, 10 Nov 2010 02:52:00 -0000 Subject: Does gvim functions correctly for any body? Message-ID: <380-22010113102529827@cantv.net> Hi, Some time ago I have reported a problem with gvim, it stops because it receives a SEGV signal when the OPEN menu-item is selected. I have installed the new XWin server, but the problem persists. Does gvim functions correctly for any body? Thanks in advance for any replay RM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ezedtheamerican@gmail.com Wed Nov 10 09:20:00 2010 From: ezedtheamerican@gmail.com (ed) Date: Wed, 10 Nov 2010 09:20:00 -0000 Subject: X server does not start from bash nor start menu Message-ID: Hello, I have a newly installed windows XP pro virtual machine that I was using to test out x/cygwin with empathy and kdenlive, but unfortunatly I have run into a problem. The X server will not start. I have tried to startxwin.exe from the bash shell and I get the following error : $startxwin giving up. startxwin: No such file or directory (errno 2): unable to connect to X server. startxwin: No such Process (errno 3): Server error. $ I have looked for an error log in /var/log, but there is nothing to view only a sub-directory named xwin with a zero byte file named ".keep-xorg-server" Also, I have changed the PATH environment variable in Windows to include C:\cygwin\bin and this also has no affect on the ability to start the X server. When I choose to use the start menu entry "XWin Server" I get a couple of processes named bash.exe and startxwin.exe, but then they disappear after a few seconds. I have also added a CYGWIN variable to the environment variables in the advanced tab of "my computer" properties, but giving the value of "tty notitle noglob" doesn't resolve the issue either. Now I am back with a fresh install of windows XP and a minimal install of cygwin that includes the cygwin default packages and three additional packages ( xinit, xorg-server, and X-start-menu-icons), which should give me a minimal install of an X server with the ability to run at least xterm. I am Administrator on the Windows machine, and the bash shell works fine ( I installed midnight commander and nano ), Any help appreciated. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Wed Nov 10 16:12:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 10 Nov 2010 16:12:00 -0000 Subject: AW: 1.9.2.0: Xwin SIGSEGV when font server should be queried In-Reply-To: <578A937A9A719E4CB564C5A9013A6012032EA7B0@MAILD.viastore.de> References: <578A937A9A719E4CB564C5A9013A6012032E9D75@MAILD.viastore.de> <4CD46065.4080501@dronecode.org.uk> <578A937A9A719E4CB564C5A9013A6012032EA7B0@MAILD.viastore.de> Message-ID: <4CDAC486.6030106@dronecode.org.uk> On 08/11/2010 14:11, Weeber, Burkhard wrote: > I did a bit of further reseach. > > It looks like it does not have anything to do with the way the font server is queried, > but rather the way the startup is done. > > When I have the font server added during the XWin startup - either in the startxwin.bat, or a bash-script I call from there, the XWin SIGSEGVs. > > When I let the XWin come up with a few of my fav screens, and I then add the font server either from a cygwin shell or from a client shell the font server is subsequently queried correctly and the SIGSEGV does not appear. > > Strange. > > Anyway. > Thanks for the exe to create a full stack trace. > Here it is: > (gdb) bt full > #0 0x005b56a2 in doListFontsWithInfo (client=0x10981dc8, c=0x108693f0) Thanks for obtaining this backtrace. With this and the startup script you posted, I have managed to reproduce the problem. It looks like this has been caused by the changes in Xserver 1.9 to fix a different bug with xfs [1]. The problem is a use-after-free, so that probably explains why it sometimes works if you do things in a different order. I noticed that setup is only offering a choice of 1.9.0-2 or 1.9.2-1, which isn't a very smart thing to do, so I've rearranged things so now 1.8.2-1 should be offered as the previous version. [1] https://bugs.freedesktop.org/show_bug.cgi?id=3040 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Wed Nov 10 16:25:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 10 Nov 2010 16:25:00 -0000 Subject: Updated: xorg-server-1.9.2-1 In-Reply-To: <4CD90E42.5000308@bonhard.uklinux.net> References: <4CD7E3A7.3060704@bonhard.uklinux.net> <4CD803CD.60603@dronecode.org.uk> <4CD90E42.5000308@bonhard.uklinux.net> Message-ID: <4CDAC78F.1010402@dronecode.org.uk> On 09/11/2010 09:02, Fergus wrote: >>> Fatal server error: >>> Can't read lock file /tmp/.X0-lock > >> Does /tmp/.X0-lock exists? Is it readable by you? > > Yes. Hmm. It's strange that the Xserver should choose to lie about that, then. The code in question really does just say... lfd = open(LockFile, O_RDONLY); if (lfd < 0) { unlink(tmp); FatalError("Can't read lock file %s\n", LockFile); } ... so I can't see much room for unpredictability. It would be helpful if you could strace XWin to see why it gets this wrong. Have you tried manually removing the lock file /tmp/.X0-lock? >> Are you sure /tmp is getting mounted successfully >> where you expect it to be? > > Yes. > >> Have you tried '-nolock', as suggested by [1] > > I hadn't then. > But I have now and as a consequence everything is working perfectly. > Thank you. > > (Over time I have occasionally had to moderate the syntax of both "XWin" and > "xterm" command lines to go from working to failing and back again to working. > This is just another example. On an earlier occasion, the recommended use of > -nolock failed. I am just happy when the current usage works. Thanks again.) Well, I can't deny this might be your experience, but that's not how things are supposed to work :-) -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Wed Nov 10 16:33:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 10 Nov 2010 16:33:00 -0000 Subject: X server does not start from bash nor start menu In-Reply-To: References: Message-ID: <4CDAC966.2080608@dronecode.org.uk> On 10/11/2010 09:19, ed wrote: > I have a newly installed windows XP pro virtual machine that I was > using to test out x/cygwin with empathy and kdenlive, but unfortunatly > I have run into a problem. > The X server will not start. I have tried to startxwin.exe from > the bash shell and I get the following error : > $startxwin > giving up. > startxwin: No such file or directory (errno 2): unable to connect > to X server. > startxwin: No such Process (errno 3): Server error. > $ > I have looked for an error log in /var/log, but there is nothing > to view only a sub-directory named xwin with a zero byte file named > ".keep-xorg-server" > Also, I have changed the PATH environment variable in Windows to > include C:\cygwin\bin and this also has no affect on the ability to > start the X server. > When I choose to use the start menu entry "XWin Server" I get a > couple of processes named bash.exe and startxwin.exe, but then they > disappear after a few seconds. > I have also added a CYGWIN variable to the environment variables > in the advanced tab of "my computer" properties, but giving the value > of "tty notitle noglob" doesn't resolve the issue either. I don't know where you've found this suggestion, but don't add 'tty' to CYGWIN if you want to start it via the start menu item. This doesn't work due to some problem with run.exe [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-startxwin-no-windows > Now I am back with a fresh install of windows XP and a minimal > install of cygwin that includes the cygwin default packages and three > additional packages ( xinit, xorg-server, and X-start-menu-icons), > which should give me a minimal install of an X server with the ability > to run at least xterm. > I am Administrator on the Windows machine, and the bash shell > works fine ( I installed midnight commander and nano ), Can you start the X server by typing 'XWin' into a bash shell? Does that produce any output? If not, does 'cygcheck XWin' identify any problems? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ezedtheamerican@gmail.com Wed Nov 10 17:38:00 2010 From: ezedtheamerican@gmail.com (ed) Date: Wed, 10 Nov 2010 17:38:00 -0000 Subject: X server does not start from bash nor start menu In-Reply-To: <4CDAC966.2080608@dronecode.org.uk> References: <4CDAC966.2080608@dronecode.org.uk> Message-ID: >On Wed, Nov 10, 2010 at 9:33 AM, Jon TURNEY wrote: > > Can you start the X server by typing 'XWin' into a bash shell? ?Does that > produce any output? ?If not, does 'cygcheck XWin' identify any problems? in a command shell (not a bash shell) xwin.exe gave me the error report that I needed "cygcrypto-0.9.8.dll" I don't know exactly why the file didn't install by default, but I found a 3rd party site that had the file. I really don't trust the file I installed, but the X server starts with it installed. I don't know which package would install "cygcrypto-0.9.8.dll" thank you for you assistance it is greatly appreciated. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From reply-to-list-only-lh-x@cygwin.com Wed Nov 10 17:50:00 2010 From: reply-to-list-only-lh-x@cygwin.com (Larry Hall (Cygwin X)) Date: Wed, 10 Nov 2010 17:50:00 -0000 Subject: X server does not start from bash nor start menu In-Reply-To: References: <4CDAC966.2080608@dronecode.org.uk> Message-ID: <4CDADB6F.3060808@cygwin.com> On 11/10/2010 12:38 PM, ed wrote: >> On Wed, Nov 10, 2010 at 9:33 AM, Jon TURNEY wrote: ^^^^^^^^^^^^^^ >> >> Can you start the X server by typing 'XWin' into a bash shell? Does that >> produce any output? If not, does 'cygcheck XWin' identify any problems? > in a command shell (not a bash shell) xwin.exe gave me the error > report that I needed "cygcrypto-0.9.8.dll" > I don't know exactly why the file didn't install by default, but I > found a 3rd party site that had the file. > I really don't trust the file I installed, but the X server starts > with it installed. > I don't know which package would install "cygcrypto-0.9.8.dll" > thank you for you assistance it is greatly appreciated. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ezedtheamerican@gmail.com Wed Nov 10 17:57:00 2010 From: ezedtheamerican@gmail.com (ed) Date: Wed, 10 Nov 2010 17:57:00 -0000 Subject: X server does not start from bash nor start menu In-Reply-To: <4CDADB6F.3060808@cygwin.com> References: <4CDAC966.2080608@dronecode.org.uk> <4CDADB6F.3060808@cygwin.com> Message-ID: On Wed, Nov 10, 2010 at 10:50 AM, Larry Hall (Cygwin X) > Yes, my apologies I did not notice that email included... > > thank you for the link. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From mruyc@cgkoswae.com Sat Nov 13 21:15:00 2010 From: mruyc@cgkoswae.com (Impt) Date: Sat, 13 Nov 2010 21:15:00 -0000 Subject: Mgk Message-ID: A non-text attachment was scrubbed... Name: Korx8307.rar Type: application/octet-stream Size: 428 bytes Desc: not available URL: From jjreisert@alum.mit.edu Tue Nov 16 20:37:00 2010 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Tue, 16 Nov 2010 20:37:00 -0000 Subject: X server with multiple Windows desktops Message-ID: I'm running this program to give myself multiple Windows (7) desktops: http://technet.microsoft.com/en-us/sysinternals/cc817881.aspx Desktops 1.01 Copyright (c) 2006-2010 Mark Russinovich and Bryce Cogswell Sysinternals - www.sysinternals.com I started the Cygwin X server on the 1st desktop, but then tried to open a new Xterm from the 2nd desktop. It of course landed on the first one. Is there any way for the X server to recognize these as four different desktops, so I could, for example, open an Xterm explicitly on a given desktop, for example: xterm -display localhost:0.1 - Jim -- Jim Reisert AD1C, , http://www.ad1c.us -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From polfam19@msn.com Thu Nov 18 12:33:00 2010 From: polfam19@msn.com (Frederick Hansen) Date: Thu, 18 Nov 2010 12:33:00 -0000 Subject: xorg-server-1.9.2-1 Fullscreen Issue Message-ID: Greetings, Just FYI, after upgrading to xorg-server 1.9.2, any attempt to run in fullscreen results in an error.? Downgrading to version 1.8.2 seems to correct the issue.? Running either version in multiwindow also works. The contents of Xwin.log are shown below: 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 -fullscreen -depth 8 -clipboard -silent-dup-error ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1920 h 1080 winInitializeDefaultScreens - native DPI x 96 y 96 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/HCU-47R4ZN1:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 [ 30090.218] winInitializeScreens - 1 [ 30090.218] winInitializeScreen - 0 [ 30090.234] (II) xorg.conf is not supported [ 30090.234] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 30090.265] LoadPreferences: /home/200007557/.XWinrc not found [ 30090.265] LoadPreferences: Loading /etc/X11/system.XWinrc [ 30090.265] LoadPreferences: Done parsing the configuration file... [ 30090.265] winGetDisplay: DISPLAY=:0.0 [ 30090.265] winDetectSupportedEngines - Windows NT/2000/XP [ 30090.265] winDetectSupportedEngines - DirectDraw installed [ 30090.265] winDetectSupportedEngines - Allowing PrimaryDD [ 30090.265] winDetectSupportedEngines - DirectDraw4 installed [ 30090.265] winDetectSupportedEngines - Returning, supported engines 0000001f [ 30090.265] winSetEngine - Using Shadow DirectDraw NonLocking [ 30090.265] winScreenInit - Using command line depth of 8 bpp [ 30090.734] winFinishScreenInitFB - Masks: 00000000 00000000 00000000 [ 30090.781] Screen 0 added at virtual desktop coordinate (0,0). [ 30090.781] MIT-SHM extension disabled due to lack of kernel support [ 30090.796] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 30091.140] (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so [ 30091.140] (II) GLX: Initialized DRISWRAST GL provider for screen 0 [ 30091.171] [dix] Could not init font path element /usr/share/fonts/TTF/, removing from list! [ 30091.171] [dix] Could not init font path element /usr/share/fonts/OTF/, removing from list! [ 30091.171] [dix] Could not init font path element /usr/share/fonts/Type1/, removing from list! [ 30091.406] (EE) XKB: Could not invoke xkbcomp [ 30091.406] (EE) XKB: Couldn't compile keymap [ 30091.406] XKB: Failed to compile keymap [ 30091.406] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. [ 30091.406] Fatal server error: [ 30091.406] Failed to activate core devices. Thanks for your time, Fred -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Fri Nov 19 13:26:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 19 Nov 2010 13:26:00 -0000 Subject: Does gvim functions correctly for any body? In-Reply-To: <380-22010113102529827@cantv.net> References: <380-22010113102529827@cantv.net> Message-ID: <4CE67B06.8070804@dronecode.org.uk> On 10/11/2010 02:52, Rodrigo Medina wrote: > Some time ago I have reported a problem with gvim, > it stops because it receives a SEGV signal when the > OPEN menu-item is selected. I have installed the new > XWin server, but the problem persists. > Does gvim functions correctly for any body? Probably not, it crashes in the same way for me. This is very like a problem in gvim or one of the GNOME libraries it depends upon, which can't be fixed in the X server. Interestingly 'gdb --args gvim -f' doesn't show the problem (so gvim -f might be a work around). Attaching to a running gvim with gdb --pid= and then provoking the crash gives the following backtrace > (gdb) bt > #0 0x76bf1ef4 in ?? () > #1 0x6ff41795 in g_module_symbol () from /usr/bin/cyggmodule-2.0-0.dll > #2 0x6ff41d64 in g_module_open () from /usr/bin/cyggmodule-2.0-0.dll > #3 0x68169cd5 in g_io_modules_scan_all_in_directory () from /usr/bin/cyggio-2.0-0.dll > #4 0x6e5a3db6 in g_type_module_use () from /usr/bin/cyggobject-2.0-0.dll > #5 0x68169902 in g_io_modules_scan_all_in_directory () from /usr/bin/cyggio-2.0-0.dll > #6 0x68169b7e in g_io_modules_scan_all_in_directory () from /usr/bin/cyggio-2.0-0.dll > #7 0x68180e2b in g_vfs_is_active () from /usr/bin/cyggio-2.0-0.dll > #8 0x6aa8cdde in g_once_impl () from /usr/bin/cygglib-2.0-0.dll > #9 0x68180a72 in g_vfs_get_default () from /usr/bin/cyggio-2.0-0.dll > #10 0x68150893 in g_file_new_for_path () from /usr/bin/cyggio-2.0-0.dll > #11 0x6af6044f in gtk_recent_manager_get_for_screen () from /usr/bin/cyggtk-x11-2.0-0.dll > #12 0x6e588cd6 in g_object_freeze_notify () from /usr/bin/cyggobject-2.0-0.dll > #13 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll > #14 0x6e58a8f0 in g_object_new () from /usr/bin/cyggobject-2.0-0.dll > #15 0x6af5ff1b in gtk_recent_manager_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #16 0x6af5ff3c in gtk_recent_manager_get_default () from /usr/bin/cyggtk-x11-2.0-0.dll > #17 0x6aebb649 in gtk_file_chooser_button_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #18 0x6e5a2dd3 in g_type_create_instance () from /usr/bin/cyggobject-2.0-0.dll > #19 0x6e588bca in g_object_freeze_notify () from /usr/bin/cyggobject-2.0-0.dll > #20 0x6aebb7c5 in gtk_file_chooser_button_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #21 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll > #22 0x6e58a8f0 in g_object_new () from /usr/bin/cyggobject-2.0-0.dll > #23 0x6aebcf1b in gtk_file_chooser_button_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #24 0x6aec1873 in gtk_file_chooser_widget_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #25 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll > #26 0x6e58a8f0 in g_object_new () from /usr/bin/cyggobject-2.0-0.dll > #27 0x6aebd565 in gtk_file_chooser_dialog_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #28 0x6e58a246 in g_object_newv () from /usr/bin/cyggobject-2.0-0.dll > #29 0x6e58a7a9 in g_object_new_valist () from /usr/bin/cyggobject-2.0-0.dll > #30 0x6e58a8ce in g_object_new () from /usr/bin/cyggobject-2.0-0.dll > #31 0x6aebd160 in gtk_file_chooser_dialog_get_type () from /usr/bin/cyggtk-x11-2.0-0.dll > #32 0x6aebd209 in gtk_file_chooser_dialog_new () from /usr/bin/cyggtk-x11-2.0-0.dll > #33 0x0055a46a in ?? () > #34 0x0057ff09 in ?? () > #35 0x0071d000 in ?? () > #36 0x00000000 in ?? () You might try reverting to previous versions of gvim or GNOME libraries to try to narrow down where the problem was introduced. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Fri Nov 19 13:31:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 19 Nov 2010 13:31:00 -0000 Subject: X server with multiple Windows desktops In-Reply-To: References: Message-ID: <4CE67BFB.2020303@dronecode.org.uk> On 16/11/2010 20:37, Jim Reisert AD1C wrote: > I'm running this program to give myself multiple Windows (7) desktops: > > http://technet.microsoft.com/en-us/sysinternals/cc817881.aspx > Desktops 1.01 > Copyright (c) 2006-2010 Mark Russinovich and Bryce Cogswell > Sysinternals - www.sysinternals.com > > I started the Cygwin X server on the 1st desktop, but then tried to > open a new Xterm from the 2nd desktop. It of course landed on the > first one. > > Is there any way for the X server to recognize these as four different > desktops, so I could, for example, open an Xterm explicitly on a given > desktop, for example: > > xterm -display localhost:0.1 >From reading the description of how that works, I would guess you should be able to start an instance of the X server with a different display number in each virtual desktop. e.g. in your 2nd desktop, start X (however you do that) with :1, and then use xterm -display :1 to connect to 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/ From jon.turney@dronecode.org.uk Fri Nov 19 13:37:00 2010 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 19 Nov 2010 13:37:00 -0000 Subject: xorg-server-1.9.2-1 Fullscreen Issue In-Reply-To: References: Message-ID: <4CE67D81.7080203@dronecode.org.uk> On 18/11/2010 12:33, Frederick Hansen wrote: > Just FYI, after upgrading to xorg-server 1.9.2, any attempt to run in fullscreen results in an error. Downgrading to version 1.8.2 seems to correct the issue. Running either version in multiwindow also works. > > The contents of Xwin.log are shown below: > > > 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 -fullscreen -depth 8 -clipboard -silent-dup-error > [snip] > [ 30091.406] (EE) XKB: Could not invoke xkbcomp > [ 30091.406] (EE) XKB: Couldn't compile keymap > [ 30091.406] XKB: Failed to compile keymap > [ 30091.406] Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. > [ 30091.406] > Fatal server error: > [ 30091.406] Failed to activate core devices. Interesting. I can start X in fullscreen without problems using the same options. Are you sure that removing -fullscreen allows the X server to start properly? This kind of failure (invoking xkbcomp) is usually caused by BLODA or rebase problems preventing xkbcomp from being spawned. It would be unusual for that to only occur with certain options, but I guess it is possible. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From csylvain@electro-technica.com Fri Nov 19 15:04:00 2010 From: csylvain@electro-technica.com (Claude Sylvain) Date: Fri, 19 Nov 2010 15:04:00 -0000 Subject: Does gvim functions correctly for any body? In-Reply-To: <380-22010113102529827@cantv.net> References: <380-22010113102529827@cantv.net> Message-ID: <4CE691E2.6010606@electro-technica.com> On 09/11/2010 21:52, Rodrigo Medina wrote: > > Hi, > Some time ago I have reported a problem with gvim, > it stops because it receives a SEGV signal when the > OPEN menu-item is selected. I have installed the new > XWin server, but the problem persists. > Does gvim functions correctly for any body? > Thanks in advance for any replay > - I have the same problem here, on 2 Cygwin v1.7.x / Windows XP prof. computer. - I reverted back to vim-7.2/gvim-7.2 to avoid that problem. P.S.: Hope that this problem will be resolved one day. Claude. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 01:30:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 01:30:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 01:45:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 01:45:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 01:45:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 01:45:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 01:45:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 01:45:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 02:00:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 02:00:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 02:00:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 02:00:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From leonard@increaseyourprofits.net Wed Nov 24 02:15:00 2010 From: leonard@increaseyourprofits.net (Leonard) Date: Wed, 24 Nov 2010 02:15:00 -0000 Subject: I have a question about GDI Message-ID: Hello, ?? I was searching online to find more info about GDI and I came across your information. ?? Can you tell me, are you still involved with GDI? If you are, how are things going for you? ?? Please let me know. ?? Sincerely, Leonard -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From joe.joeoptions@gmail.com Wed Nov 24 03:59:00 2010 From: joe.joeoptions@gmail.com (Joe) Date: Wed, 24 Nov 2010 03:59:00 -0000 Subject: =?utf-8?Q?Your_Rental_Property_Listing?= Message-ID: <4cec8a932c97f@gmail.com> Hi! I noticed your property website online and I thought you might be interested in my new rental website called JoeOptions: http://www.joeoptions.com/ Here's how JoeOptions benefits you: * FREE listings through December 31, 2011 for properties created on JoeOptions. * UNLIMITED pictures/videos/links to help promote and better represent your Property and the Destination. * HomeAway Connect integration eliminating the need to manage multiple calendars * Unique property management tool allowing Renters to find your property based on Date, Price and Location in one step. * Meet People Where They Are: Social Media integration with Facebook, Twitter, YouTube, etc. Check out this video that explains why JoeOptions: http://www.youtube.com/watch?v=kohBjcuPMhE We look forward to you joining us at JoeOptions! Best Regards, Joe We've sent you this email because we think you'll enjoy using JoeOptions. If you'd rather not receive any more emails from us, please email unsubscribe@joeoptions.com, and we'll take you off our list. To remove your email from the "20101123" mailing list, click here: http://cs.joeoptions.com/index.php?ACT=5&id=gLeYWMPm0Y -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From kdo@cosmos.phy.tufts.edu Mon Nov 29 00:27:00 2010 From: kdo@cosmos.phy.tufts.edu (Ken Olum) Date: Mon, 29 Nov 2010 00:27:00 -0000 Subject: Server segmentation fault at address 0x306 using ParaView Message-ID: Running paraview 3.8.1 (see http://paraview.org) on a Linux client (Mandriva 2010.0 or Red Hat Enterprise Server 5.5) causes a crash of my Cygwin/X (release 1.9.2.0) with "Segmentation fault at address 0x306". Any ideas? Paraview uses OpenGL. Perhaps that is related. Thanks. Ken -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ofrijole@hotmail.com Mon Nov 29 05:44:00 2010 From: ofrijole@hotmail.com (Oly) Date: Mon, 29 Nov 2010 05:44:00 -0000 Subject: cygwin 1.7 startxwin failing due to "winMultiWindowXMsgProc - another window manager is running. Exiting." Message-ID: <4CF33DB3.2020805@hotmail.com> Not sure when this started happening ... but sometime recently, starting the xserver became a hit/miss proposition (mostly miss). I'm running Windows XP Pro Service Pack 3 with the cygwin 1.7.7-1 and xorg-server 1.9.2-1 (as reported by the setup wizard). I am using the installed x server start shortcut which executes the following command: C:\cygwin17\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe The failure to start seems always to coincide with a log like the attached. The interesting symptom is (from the bottom of the log): [214595.953] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [214595.953] winMultiWindowXMsgProc - another window manager is running. Exiting. [214595.953] winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. [214595.953] winClipboardProc - XDestroyWindow succeeded. [214595.953] winClipboardProc - Clipboard disabled - Exit from server [214596.015] winDeinitMultiWindowWM - Noting shutdown in progress I've seen a nearly identical report on the forum about a year ago ... back in the startxwin.bat days. The closest thing I found to a possible resolution was the suggestion of inserting a sleep in the batch file. Not sure what might be the trick now. For what it is worth, I notice consistent failure when I create an empty .startxwinrc (to avoid the xterm opening - which I'd really like but could live with closing it if the server started every single time). When I don't have an empty .startxwinrc in my home directory ... failure is frequent, but doesn't occur on every single start attempt. Failed 1 out of 2 tries tonight. I deleted the log after stopping the server (right clicked the task tray icon and chose exit) and the second start attempt failed. But sometimes it is the first try. How could I figure out what is making the startup think some other window manager is running? I don't think this is true - the failure occurs after a clean reboot (and I don't have any auto-start stuff) ... but I also saw in that previous thread something about a restart attempt (which may be borne out by what I see in the attached log) ... maybe there *are* two managers due to some race condition or something? -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: XWin.0.log URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/