From yselkowitz@users.sourceforge.net Sun Jan 1 06:01:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Sun, 01 Jan 2012 06:01:00 -0000 Subject: [ANNOUNCEMENT] Updated: GNOME 3.2 bugfixes Message-ID: I just uploaded a number of fixes for the GNOME libraries: * pango1.0 1.29.4-2 restores the postinstall/preremove scripts to manage the /etc/pango/pango.modules file, even though its empty now, to quiet the warning messages reported on the list. * gtk3 3.2.3-1 should fix issues with apps sometimes not responding to mouse input in multiwindow mode. * Various updates to audiofile, gdk-pixbuf2.0, libgsf, python-gi, shared-mime-info, and vala. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From oschmidt-mailinglists@gmx.de Sun Jan 8 15:23:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Sun, 08 Jan 2012 15:23:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4E4A8D56.6010704@gmx.de> References: <4E4A8D56.6010704@gmx.de> Message-ID: <4F09B4D4.4070905@gmx.de> Hi, On 8/16/2011 5:31 PM, Oliver Schmidt wrote: > I had the problem, that the state of the modifier keys was lost when a > window is created (or raised). > I send a patch to fix this problem with this email: I just extended the I just merged the current official source from xorg-server-1.11.3-1 into my local development source and discovered, that my patch for the problem "lost modifier key after a new window is created" has not been applied. Is there a chance, that this patch could be applied to a future version or that another solution could be provided to fix this problem? I'm also attaching a newer version of the patch with this email. Best regards, Oliver -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch.txt URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From talbright@brigadoonsoftware.com Mon Jan 9 06:37:00 2012 From: talbright@brigadoonsoftware.com (Tim Albright) Date: Mon, 09 Jan 2012 06:37:00 -0000 Subject: Laptop Theft at All Time High - Don't be a victim! - Software Tracks & Recovers Lost & Stolen Computers Message-ID: Greetings, Our award PC PhoneHome and MacPhoneHome is the NUMBER ONE stand-alone computer tracking and recovery software in the world to both the Windows and Mac communities! We are currently protecting over 1,500,000 computers worldwide. Unlike OTHER computer tracking products, PC PhoneHome and MacPhoneHome contain NO SPYWARE to invade your privacy... Every time a PC PhoneHome or MacPhoneHome protected computer makes an Internet connection, it sends a stealth email message containing its exact location to a pre-determined email address of the user's choice and to our Worldwide Command Center. In the event your computer goes missing, all you need to do is make a police report and contact us. We do the rest. Your missing computer is returned to you with the help of our recovery agents, local police services and global ISPs. Our lost & stolen computer recovery rate is over 99% worldwide! The SINGLE COPY version of PC PhoneHome and MacPhoneHome normally retail for $29.95 each. Our new Family/Household license which costs a one time fee of $79.95 USD allows the user to install PC PhoneHome and/or MacPhoneHome on as many computers in the household as is necessary, even the ones your kids may have away at college! You have 5-8-12 computers? No Problem! Our Family Household license protects them all! Only $79.95! No yearly monitoring fees. No hidden costs. No additional charges! We still provide full location and recovery service. This is the BEST deal in the industry! Our 2011 Special Bundle Deals will save you a BUNDLE of money! You can mix any combination of PC PhoneHome and/or MacPhoneHome in your deal! Please visit: http://www.brigadoonsoftware.com/purchase.html today to purchase and download your copy of PC PhoneHome/MacPhoneHome. Ask for a price quote on our CUSTOM BLANKET ENTERPRISE LICENSE for LARGE SCALE DEPLOYMENT to HUNDREDS or THOUSANDS of computers! Whether you're trying to protect one hundred computers or twenty thousand we have the right license plan for you. We will soon be releasing PhoneHome protection for iPods, iPhones and the NEW iPad... Version 4.0 will offer our users multi-lingual installation and documentation in English, Spanish, Portuguese, Italian, French and German language. Version 4.0 will OPTIONALLY snap the picture of whoever is sitting at the computer and send you a picture of the thief if your computer is lost or stolen as well as offer PhoneHome protection for your iPod, iPhone and iPad! Reseller Inquires are Invited! Information on our product line is available for download directly from our web site at: http://www.brigadoonsoftware.com If you are interested in finding out more or have any additional questions about our single copy, bundle deal or Enterprise license program, please feel free to contact me personally at 1-845-624-0909. Best Regards, Tim Albright VP - Sales Brigadoon Software, Inc. 119 Rockland Center Suite 250 Nanuet, New York 10954 USA Tel: +1-845-624-0909 Fax: +1-845-624-0990 Email: talbright@brigadoonsoftware.com Web: http://www.brigadoonsoftware.com To be excluded from future emails, please type "Remove" in the subject line and reply to this message. Please include all email aliases you are using. -- Unsubscribe info: http://cygwin.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 Jan 9 14:06:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 09 Jan 2012 14:06:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F09B4D4.4070905@gmx.de> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> Message-ID: <4F0AF463.5050707@dronecode.org.uk> On 08/01/2012 15:23, Oliver Schmidt wrote: > On 8/16/2011 5:31 PM, Oliver Schmidt wrote: >> I had the problem, that the state of the modifier keys was lost when a >> window is created (or raised). >> I send a patch to fix this problem with this email: I just extended the > > I just merged the current official source from xorg-server-1.11.3-1 into > my local development source and discovered, that my patch for the > problem "lost modifier key after a new window is created" has not been > applied. > > Is there a chance, that this patch could be applied to a future version > or that another solution could be provided to fix this problem? I'm also > attaching a newer version of the patch with this email. Thanks very much for the updated patch, and for following up on this, and apologies for overlooking it. I have a few questions and comments below: > Example: in window A Ctrl + some key opens a window B, then in window B > Ctrl + some other key triggers the next action. However after the opening > of window B the Ctrl key has to be released and pressed again. If the user > keeps the Ctrl key holding when the window B is opened, the next key press > X will be interpreted as X and not as Ctrl+X. Can you give an example of an application where this causes a problem, so I can test your patch? > I send a patch to fix this problem with this email: I just extended the > function winRestoreModeKeyStates in winkeybd.c to consider not only the > mode switch key but also the modifiers Ctrl, Shift, Alt/AltGr by using the > Windows function GetAsyncKeyState. After your patch, the X server is releasing all keys on WM_KILLFOCUS, then pressing again some subset of them on WM_SETFOCUS. The code would seem to end up simpler (which is an important consideration) if we were to modify winKeybdReleaseKeys() not to release modifier keys. Some archaeology is probably required to determine if releasing the modifier keys in winKeybdReleaseKeys() is necessary to avoid some other undesirable behaviour? This also begs the question why is it only necessary to press some some subset of the down keys on WM_SETFOCUS? Does the X server behave correctly if a non-modifier key is held down while focus moves from one X server window to another, or from one X server window to a native window an back? > diff --git a/cygwin/hw/xwin/winkeybd.c b/cygwin/hw/xwin/winkeybd.c > index 278342f..a2ac4d0 100644 > --- a/cygwin/hw/xwin/winkeybd.c > +++ b/cygwin/hw/xwin/winkeybd.c > @@ -283,6 +283,29 @@ winRestoreModeKeyStates (void) > * have a logical XOR operator, so we use a macro instead. > */ > > + { > + /* consider modifer keys */ > + > + BOOL ctrl = (GetAsyncKeyState (VK_CONTROL) < 0); > + BOOL shift = (GetAsyncKeyState (VK_SHIFT) < 0); > + BOOL alt = (GetAsyncKeyState (VK_LMENU) < 0); > + BOOL altgr = (GetAsyncKeyState (VK_RMENU) < 0); Why is is correct to use GetAsyncKeyState() here and not GetKeyState()? If we use GetAsyncKeyState() there may be a message pending (See the remarks on GetKeyState() in MSDN) to change to the key state, so we might conceivably double the key press? > + > + if (ctrl && altgr) ctrl = FALSE; > + > + if (WIN_XOR (internalKeyStates & ControlMask, ctrl)) > + winSendKeyEvent (KEY_LCtrl, ctrl); This maps VK_CONTROL to KEY_LCtrl. Why not use VK_LCONTROL and VK_RCONTROL, so the generated key-press is for the correct key? > + > + if (WIN_XOR (internalKeyStates & ShiftMask, shift)) > + winSendKeyEvent (KEY_ShiftL, shift); Ditto for VK_LSHIFT and VK_RSHIFT > + > + if (WIN_XOR (internalKeyStates & Mod1Mask, alt)) > + winSendKeyEvent (KEY_Alt, alt); > + > + if (WIN_XOR (internalKeyStates & Mod5Mask, altgr)) > + winSendKeyEvent (KEY_AltLang, altgr); > + } > + > /* Has the key state changed? */ > dwKeyState = GetKeyState (VK_NUMLOCK) & 0x0001; > if (WIN_XOR (internalKeyStates & NumLockMask, dwKeyState)) > @@ -328,7 +351,7 @@ winIsFakeCtrl_L (UINT message, WPARAM wParam, LPARAM lParam) > MSG msgNext; > LONG lTime; > Bool fReturn; > - > + > static Bool lastWasControlL = FALSE; > static UINT lastMessage; > static LONG lastTime; -- Unsubscribe info: http://cygwin.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 oschmidt-mailinglists@gmx.de Mon Jan 9 18:11:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Mon, 09 Jan 2012 18:11:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F0AF463.5050707@dronecode.org.uk> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> <4F0AF463.5050707@dronecode.org.uk> Message-ID: <4F0B2DC8.9030706@gmx.de> Hi Jon, On 09.01.2012 15:06, Jon TURNEY wrote: > I have a few questions and comments below: > >> Example: in window A Ctrl + some key opens a window B, then in window B >> Ctrl + some other key triggers the next action. However after the opening >> of window B the Ctrl key has to be released and pressed again. If the user >> keeps the Ctrl key holding when the window B is opened, the next key press >> X will be interpreted as X and not as Ctrl+X. > > Can you give an example of an application where this causes a problem, so I > can test your patch? because current cygwin x-server is not able to raise windows, you could only test the case, that a new window is created. Any X11 program that can create windows and has keyboard shortcuts will do it, e.g. take NEdit, press Ctrl+N for a new window, hold the Ctrl key and press S (i.e. Ctrl+S) for saving. > The code would seem to end up simpler (which is an important consideration) if > we were to modify winKeybdReleaseKeys() not to release modifier keys. Some > archaeology is probably required to determine if releasing the modifier keys > in winKeybdReleaseKeys() is necessary to avoid some other undesirable behaviour? I don't know anything about the cygwin X server history, I can only guess why the current code is as it is: Perhaps the modifier keys are released afer loosing a window's focus because if another Non-cygwin window gains the focus, no more modifier change events will arrive to the cygwin x server. > This also begs the question why is it only necessary to press some some subset > of the down keys on WM_SETFOCUS? Does the X server behave correctly if a > non-modifier key is held down while focus moves from one X server window to > another, or from one X server window to a native window an back? My code simply updates the xserver's internal state about the modifier keys after gaining the window focus. Other keys behave correctly, because the xserver doesn't have an internal state for them. > Why is is correct to use GetAsyncKeyState() here and not GetKeyState()? If we > use GetAsyncKeyState() there may be a message pending (See the remarks on > GetKeyState() in MSDN) to change to the key state, so we might conceivably > double the key press? I will try using GetKeyState tomorrow. I just wanted to be sure to get the current key state when the window gets the focus. > This maps VK_CONTROL to KEY_LCtrl. Why not use VK_LCONTROL and VK_RCONTROL, > so the generated key-press is for the correct key? > Ditto for VK_LSHIFT and VK_RSHIFT Perhaps this might improve the patch, however the internal modifier state of the xserver has only ShiftMask, LockMask, ControlMask, Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, and Mod5Mask. So the internal state does not distinguish betweem left or right shift key. Best regards, Oliver -- Unsubscribe info: http://cygwin.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 geary@acm.org Mon Jan 9 18:32:00 2012 From: geary@acm.org (Mark Geary) Date: Mon, 09 Jan 2012 18:32:00 -0000 Subject: Why doesn't M-C-s work for me? In-Reply-To: <1326036218.19662.ezmlm@cygwin.com> References: <1326036218.19662.ezmlm@cygwin.com> Message-ID: --s (will abbreviate as M-C-s from here-on) does nothing for me. Does anyone have any thoughts on why it might not be working? More info: I get no action in either an xterm or an emacs window. If I use right Alt, or right Control, or both, I get the expected action. In emacs, describe-key can see C-s, M-s, C-M-a but cannot see C-M-s, it does not react at all. Likewise, in an Xterm, cat -v can see control a: ^A control s: ^S meta control a: ^[^A but shows nothing for meta control s. xev shows the expected events for everything mentioned above except that pressing "s" while "Control_L" and "Meta_L" are down produces no event. My current setup: Dell Optiplex 780 Win XP sp3 $ uname -srvmo CYGWIN_NT-5.1 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.5.3.0 (20090222) I have the left control and the caps lock keys swapped with a registry edit: [HKEY_CURRENT_USER\Keyboard Layout] "Scancode Map"=hex:00,00,00,00,00,00,00,00,03,00,00,00,1d,00,3a,00,3a,00,1d,00,00,00,00,00 -- Don't forget to stop and eat the roses. -- Unsubscribe info: http://cygwin.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 oschmidt-mailinglists@gmx.de Mon Jan 9 18:58:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Mon, 09 Jan 2012 18:58:00 -0000 Subject: Why doesn't M-C-s work for me? In-Reply-To: References: <1326036218.19662.ezmlm@cygwin.com> Message-ID: <4F0B38D0.8000300@gmx.de> Hi Mark, On 09.01.2012 19:32, Mark Geary wrote: > --s (will abbreviate as M-C-s from here-on) does > nothing for me. Does anyone have any thoughts on why it might not be working? > I have the left control and the caps lock keys swapped with a > registry edit: does this problem also occur with normal windows programs? I have also made the caps lock key to a ctrl key and I cannot press ctrl+shift+s when using the "caps lock" key as ctrl key. So it seems for me that on some keyboards some key combinations of more than two keys at the same time are not possible (perhaps due to technical implementation details?) Best regards, Oliver -- Unsubscribe info: http://cygwin.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 Jan 9 19:31:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 09 Jan 2012 19:31:00 -0000 Subject: Built XWin on mingw - with patches In-Reply-To: References: <4EB2E8FE.6020305@dronecode.org.uk> <4EB81EF8.5060107@dronecode.org.uk> Message-ID: <4F0B406B.2010001@dronecode.org.uk> On 10/11/2011 16:50, Ryan Pavlik wrote: > On Mon, Nov 7, 2011 at 12:10 PM, Jon TURNEY wrote: >> 0009-os-utils.c-Use-winxp-or-better-for-Winsock-API.patch >> >> I am a bit unclear why this is needed, surely the winsock API predates XP? >> It might be better to add this define to CFLAGS rather than to start >> sprinkling it around source files as needed? > > Yes, but one of the calls in that file uses a part of the winsock API > introduced in XP - getaddrinfo and freeaddrinfo. > http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/w32api/include/ws2tcpip.h?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=src In my build testing, this only seems to be a problem if you explicitly ./configure the X server with --enable-ipv6, and in that case other build problems exist as well (No inet_pton/inet_ntop, inclusion of ws2tcpip.h is needed) (Ideally, if you were to ./configure with CFLAGS=-D_WIN32_WINNT=0x0501, IPv6 should be auto-detected by ./configure and build successfully. But this auto-detection doesn't work, because AC_CHECK_FUNC(getaddrinfo) fails because the test program generated doesn't prototype getaddrinfo, so it doesn't look for it with stdcall mangling...) So it seems there are a couple of generic problems here, so I'm not sure fixing it like this is the right thing to do. >> 0027-dix-registry.c-Free-old-memory-upon-realloc-failure.patch >> >> Interesting. >> >> It would probably be useful to quote the language from the appropriate >> standard which describes the behavior of realloc() in this error case in the >> comment. >> >> I don't think this change is fully correct however. If the realloc'ed size >> is 0, realloc() may return NULL, but the previously allocated memory has >> been freed. Perhaps you need to check if errno has been set by realloc to >> distinguish these two cases? >> >> Did you notice this by inspection or actually have a problem caused by this >> code? Have you audited the rest of the xserver code for this class of error? > > Good point. I found this with cppcheck - a static analysis tool that, > despite its name, is useful for C code as well. There were other > issues it mentioned in the xserver code, but I didn't get to any of > the others yet. In any case, it's a completely orthogonal patch. Might > be useful for someone more familiar with the code to run cppcheck and > address the issues. Since it's outside my area of expertise to do a good review, I'd suggest you post this patch (when you have it in a correct form) directly to xorg-devel. >> 0041-configure.ac-mingw-doesn-t-have-setuid-either.patch >> >> Use whitespace consistently with the context, please > > Oops - will correct. Looking at this again, I'm a bit puzzled by the comment "Fixes having to pass this flag for a successful MinGW build" I can understand adding MinGW to the set of targets which don't have setuid binaries, but I'm not sure how the MinGW build can fail if this flag isn't supplied: INSTALL_SETUID appears to only apply to installing the Xorg DDX. Is the real bug here that the test immediately below this assumes that we are not cross-compiling? Should the test check for cross-compiling and assume setuid binaries are possible unless it's on the list of excluded targets? -- 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 Jan 9 19:51:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 09 Jan 2012 19:51:00 -0000 Subject: Why doesn't M-C-s work for me? In-Reply-To: References: <1326036218.19662.ezmlm@cygwin.com> Message-ID: <4F0B453B.6080001@dronecode.org.uk> On 09/01/2012 18:32, Mark Geary wrote: > --s (will abbreviate as M-C-s from here-on) does > nothing for me. Does anyone have any thoughts on why it might not be working? This seems to work correctly for me: KeyPress event, serial 27, synthetic NO, window 0x1000001, root 0x206, subw 0x0, time 22102718, (105,96), root:(2137,224), state 0x1c, keycode 39 (keysym 0x73, s), same_screen YES, XLookupString gives 1 bytes: (13) "" XmbLookupString gives 1 bytes: (13) "" XFilterEvent returns: False It might be the case that M-C-s has been made a Windows shell shortcut key, in which case the Windows shell will process it before X server gets a chance to see it. You might wish to try the -keyhook X server option to see if that changes anything. > I have the left control and the caps lock keys swapped with a registry edit: > > [HKEY_CURRENT_USER\Keyboard Layout] > "Scancode > Map"=hex:00,00,00,00,00,00,00,00,03,00,00,00,1d,00,3a,00,3a,00,1d,00,00,00,00,00 > You might want to try with that reverted, both to eliminate it and possible mechanical limitations of your keyboard's caps lock key as a cause. > Welcome to the XWin X Server > Vendor: The Cygwin/X Project > Release: 1.5.3.0 (20090222) I know this is the last X server release for Cygwin 1.5, but it is quite old now. While I can't think of any change made which might fix this, I can't rule that out. If this is a bug in the X server, a fixed X server will only be made available for Cygwin 1.7 -- 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 rodmedina@cantv.net Tue Jan 10 04:01:00 2012 From: rodmedina@cantv.net (rodmedina@cantv.net) Date: Tue, 10 Jan 2012 04:01:00 -0000 Subject: XWIN-1.11.3.0 crashes when some client programs terminate. Message-ID: <1868438265.1264161.1326168096787.JavaMail.gess@webmail-01.datacenter.cha.cantv.net> Hi, With the last release of Xwin (1.11.3.0) I have found the following problem. The termination of some programs that otherwise work correctly, produces a crash of Xwin. With some client programs the problem allways appears, with others it happens only occationally. I am attaching the sources of a simple program that consistently produces the crash of the server. RM. -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 109131 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 3880 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bug.tar Type: application/octet-stream Size: 112640 bytes Desc: not available URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From oschmidt-mailinglists@gmx.de Tue Jan 10 09:47:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Tue, 10 Jan 2012 09:47:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F0B2DC8.9030706@gmx.de> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> <4F0AF463.5050707@dronecode.org.uk> <4F0B2DC8.9030706@gmx.de> Message-ID: <4F0C0934.7010708@gmx.de> Hi, On 1/9/2012 7:11 PM, Oliver Schmidt wrote: > NEdit, press Ctrl+N for a new window, hold the Ctrl key and press S > (i.e. Ctrl+S) for saving. For the above NEdit example you have to disable the entry "Preferences / Default Settings / Tabbed Editing / Open File In New Tab" from NEdit's menu bar. Otherwise Ctrl+N will not open a new window. Of course every keyboard driven program that opens new windows with keyboard shortcuts will have problems with lost modifier key state. Moreover, if using my patch for "programmatically raising top level windows" ( http://cygwin.com/ml/cygwin-xfree/2011-08/msg00034.html ) the problem also occurs if a application raises windows by keyboard shortcuts. > I will try using GetKeyState tomorrow. I just wanted to be sure to get > the current key state when the window gets the focus. Ok, I tried using "GetKeyState" instead of "GetAsyncKeyState" and it also works. So it seems to be a good idea to switch to "GetKeyState". Best regards, Oliver -- Unsubscribe info: http://cygwin.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 oschmidt-mailinglists@gmx.de Tue Jan 10 10:15:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Tue, 10 Jan 2012 10:15:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F0C0934.7010708@gmx.de> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> <4F0AF463.5050707@dronecode.org.uk> <4F0B2DC8.9030706@gmx.de> <4F0C0934.7010708@gmx.de> Message-ID: <4F0C0F9B.5010704@gmx.de> It's me again ;-) On 1/10/2012 10:47 AM, Oliver Schmidt wrote: > Ok, I tried using "GetKeyState" instead of "GetAsyncKeyState" and it > also works. So it seems to be a good idea to switch to "GetKeyState". My answer was too fast: unfortunately I got problems using "GetKeyState" instead of "GetAsyncKeyState": I had hanging Alt-Keys if switching into a x11 window using alt+tab when the mouse was already in the window before the alt+tab keypress. So I switched back to using "GetAsyncKeyState" and everything now works again as it should. So after my experience we should use "GetAsyncKeyState": this works for me without any problems since August 2011 and I'm using this 8 hours every day, doing a lot of keyboard stuff and opening, raising and closing X11 windows frequently using the keyboard. Best regards, Oliver -- Unsubscribe info: http://cygwin.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 oschmidt-mailinglists@gmx.de Tue Jan 10 10:29:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Tue, 10 Jan 2012 10:29:00 -0000 Subject: XWIN-1.11.3.0 crashes when some client programs terminate. In-Reply-To: <1868438265.1264161.1326168096787.JavaMail.gess@webmail-01.datacenter.cha.cantv.net> References: <1868438265.1264161.1326168096787.JavaMail.gess@webmail-01.datacenter.cha.cantv.net> Message-ID: <4F0C130D.6040601@gmx.de> Hi, On 1/10/2012 5:01 AM, rodmedina@cantv.net wrote: > I am attaching the sources of a > simple program that consistently produces the crash of the server. I compiled your program using the commandline: gcc -I. paneltest.c xbutton.c xinitapp.c xinline.c \ xinpanel.c xwinutil.c -lx11 in the src directory of your expanded archive. How can the crash be reproduced? If I leave the program by closing the window no crash occurs. > With the last release of Xwin (1.11.3.0) I have found the following > problem. I'm using the current cygwin xorg-server version 1.11.3-1, perhaps the problem has been fixed? Best regards, Oliver -- Unsubscribe info: http://cygwin.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 Jan 11 13:16:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 11 Jan 2012 13:16:00 -0000 Subject: XWIN-1.11.3.0 crashes when some client programs terminate. In-Reply-To: <1868438265.1264161.1326168096787.JavaMail.gess@webmail-01.datacenter.cha.cantv.net> References: <1868438265.1264161.1326168096787.JavaMail.gess@webmail-01.datacenter.cha.cantv.net> Message-ID: <4F0D8BC6.5040109@dronecode.org.uk> On 10/01/2012 04:01, rodmedina@cantv.net wrote: > With the last release of Xwin (1.11.3.0) I have found the following problem. > The termination of some programs that otherwise work correctly, produces > a crash of Xwin. With some client programs the problem allways appears, > with others it happens only occationally. I am attaching the sources of a > simple program that consistently produces the crash of the server. I tried your test program, but couldn't reproduce the crash. Perhaps you can follow the instructions at [1] and produce a backtrace? Thanks for attaching the cygcheck.out and XWin.0.log files. I notice one odd thing in the XWin.0.log: [ 9863.906] setlocale failed. According to your cygcheck.out, you have LANG = 'es_VE.ISO-8859-1', which should be valid, and I can't reproduce this either, so there is something I don't understand going on here. Does this error disappear when you revert to a previous version also? [1] http://x.cygwin.com/devel/backtrace.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Wed Jan 11 17:16:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Wed, 11 Jan 2012 17:16:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F0B2DC8.9030706@gmx.de> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> <4F0AF463.5050707@dronecode.org.uk> <4F0B2DC8.9030706@gmx.de> Message-ID: <4F0DC3DF.8000802@dronecode.org.uk> On 09/01/2012 18:11, Oliver Schmidt wrote: > On 09.01.2012 15:06, Jon TURNEY wrote: >> The code would seem to end up simpler (which is an important consideration) if >> we were to modify winKeybdReleaseKeys() not to release modifier keys. Some >> archaeology is probably required to determine if releasing the modifier keys >> in winKeybdReleaseKeys() is necessary to avoid some other undesirable behaviour? > > I don't know anything about the cygwin X server history, I can only > guess why the current code is as it is: Perhaps the modifier keys are > released afer loosing a window's focus because if another Non-cygwin > window gains the focus, no more modifier change events will arrive to > the cygwin x server. Then you know as much as I do. I didn't write this code. Fortunately, the history of the code is preserved both in the VCS, and in discussions on this mailing list. I think it is useful to consider this history when reviewing a patch, as there are a couple of dangers this avoids: Are we going in circles? Are we fixing one bug just to re-introduce another bug which has already been fixed? Are we doing in the wrong direction? Adding special case on top of special case, increasing the complexity of the code, is often a sign that something is wrong with the approach taken. Anyhow, in a brief look at some mailing list discussions from 2002 or so, it seems that: i) We must release modifier keys when focus leaves the X server, as modifier keys may be part of a Windows shell shortcut which moves the focus elsewhere, e.g. alt-tab) so the key-release isn't received by the X server. ii) We must release non-modifier keys when focus leaves the X server, or they continue to auto-repeat in the X server (specifically a problem when a key-press closes a window (such as typing ctrl-d or exit into an Xterm), as the key-release goes to the next window to receive focus, which may not be an X window) After your change we will have: iii) We must press held modifier keys when focus enters the X server (toggling latching ones as appropriate), so that the future key-presses have the correct modifiers. So I guess we should also consider: iv) What should we do about held non-modifier keys when focus enters the X server? It looks like these should be pressed as well for strict correctness. If we hold down a non-modifier key so it auto-repeats, and move the focus between X and native windows, the native windows receive repeats, but the the X windows do not. I doubt many people care about this behaviour, though :-) Staring at the code some more, this means that winInitializeModeKeyStates() is possibly wrong: It should do the same work as winRestoreModeKeyStates(). If it's possible to launch the X server with a key held down, that key won't be noticed until it's pressed and released :-) >> This maps VK_CONTROL to KEY_LCtrl. Why not use VK_LCONTROL and VK_RCONTROL, >> so the generated key-press is for the correct key? >> Ditto for VK_LSHIFT and VK_RSHIFT > > Perhaps this might improve the patch, however the internal modifier > state of the xserver has only ShiftMask, LockMask, ControlMask, > Mod1Mask, Mod2Mask, Mod3Mask, Mod4Mask, and Mod5Mask. So the internal > state does not distinguish betweem left or right shift key. Hm... on looking at this again, isn't that code you are adding checking the internal state of non-latching modifiers bogus? If we release all keys on WM_KILLFOCUS, then the non-latching modifiers will always be clear when the WM_SETFOCUS occurs, so we will always generate the keypress for the modifier. (This is different to the existing code below for the latching modifiers, where we generate a keypress and release if necessary to toggle the state of the latching modifier in the X server to match the actual state) -- 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 servvt38165@onlinevt-globalpayments.com Wed Jan 11 18:33:00 2012 From: servvt38165@onlinevt-globalpayments.com (servvt38165@onlinevt-globalpayments.com) Date: Wed, 11 Jan 2012 18:33:00 -0000 Subject: Update your account Message-ID: An embedded and charset-unspecified text was scrubbed... Name: not available URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: servvtM75GF40U.html URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From oschmidt-mailinglists@gmx.de Thu Jan 12 12:19:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Thu, 12 Jan 2012 12:19:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F0DC3DF.8000802@dronecode.org.uk> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> <4F0AF463.5050707@dronecode.org.uk> <4F0B2DC8.9030706@gmx.de> <4F0DC3DF.8000802@dronecode.org.uk> Message-ID: <4F0ECFC5.7090903@gmx.de> Hi Jon, On 1/11/2012 6:16 PM, Jon TURNEY wrote: > I think it is useful to consider this history when reviewing a patch, > Are we going in circles? Are we doing in the wrong direction? I appreciate your carefulness und thoroughness. It's of course always better to understand what is going on, especially in a large code base with a long history. > Anyhow, in a brief look at some mailing list discussions from 2002 or so, it > seems that: > i) We must release modifier keys when focus leaves the X server, as modifier > keys may be part of a Windows shell shortcut which moves the focus elsewhere, > e.g. alt-tab) so the key-release isn't received by the X server. Ah ok, so my guess was in the right direction ;-) > ii) We must release non-modifier keys when focus leaves the X server, or they > continue to auto-repeat in the X server (specifically a problem when a > key-press closes a window (such as typing ctrl-d or exit into an Xterm), as > the key-release goes to the next window to receive focus, which may not be an > X window) Interesting, I didn't know this. Thank you for figuring this out from the malinglists archives. > iv) What should we do about held non-modifier keys when focus enters the X server? > > It looks like these should be pressed as well for strict correctness. If we > hold down a non-modifier key so it auto-repeats, and move the focus between X > and native windows, the native windows receive repeats, but the the X windows > do not. I doubt many people care about this behaviour, though :-) Yes, you are right: I can reproduce this phenomenon by holding down Ctrl+N for opening windows and the key is not autorepeated (so only one window is opened, whereas under Linux xserver many windows are opened). In my daily usage I didn't discover this phenomenon. My patch only addresses the problem, that the modifier keys are not right after keyboard driven focus change, disrupting my workflow. So I agree that there might not many people caring about this behaviour. > Hm... on looking at this again, isn't that code you are adding checking the > internal state of non-latching modifiers bogus? If we release all keys on > WM_KILLFOCUS, then the non-latching modifiers will always be clear when the > WM_SETFOCUS occurs, so we will always generate the keypress for the modifier. Yes, my patch also generates key release events for modifiers despite the fact, that all modifier have been released after the xserver looses the window focus. When writing the patch, I wasn't sure if this is always the case, so I made the code a little bit more "robust" in the sense that it tries to correct the modifier keys in any case (so it will always work, even if something goes wrong in other code locations). Best regards, Oliver -- Unsubscribe info: http://cygwin.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 oschmidt-mailinglists@gmx.de Thu Jan 12 12:38:00 2012 From: oschmidt-mailinglists@gmx.de (Oliver Schmidt) Date: Thu, 12 Jan 2012 12:38:00 -0000 Subject: considering modifier keys after gaining focus In-Reply-To: <4F0ECFC5.7090903@gmx.de> References: <4E4A8D56.6010704@gmx.de> <4F09B4D4.4070905@gmx.de> <4F0AF463.5050707@dronecode.org.uk> <4F0B2DC8.9030706@gmx.de> <4F0DC3DF.8000802@dronecode.org.uk> <4F0ECFC5.7090903@gmx.de> Message-ID: <4F0ED443.7020403@gmx.de> On 1/12/2012 1:19 PM, Oliver Schmidt wrote: > On 1/11/2012 6:16 PM, Jon TURNEY wrote: >> Hm... on looking at this again, isn't that code you are adding checking the >> internal state of non-latching modifiers bogus? If we release all keys on >> WM_KILLFOCUS, then the non-latching modifiers will always be clear when the >> WM_SETFOCUS occurs, so we will always generate the keypress for the modifier. > > Yes, my patch also generates key release events for modifiers despite > the fact, that all modifier have been released after the xserver looses > the window focus. When writing the patch, I wasn't sure if this is > always the case, so I made the code a little bit more "robust" in the > sense that it tries to correct the modifier keys in any case (so it will > always work, even if something goes wrong in other code locations). My answer is perhaps a little bit unexact. To be more precise: + BOOL ctrl = (GetAsyncKeyState (VK_CONTROL) < 0); + if (WIN_XOR (internalKeyStates & ControlMask, ctrl)) + winSendKeyEvent (KEY_LCtrl, ctrl); The above code fragment will send a key press event for the ctrl key, if the current "real" ctrl modifier state is pressed and differs from the xserver's internal key state for ControlMask. It will send a key release event for the ctrl key, if the current "real" ctrl modifier state is "not pressed" and differs from the xserver's internal key state for ControlMask. Best regards, Oliver -- Unsubscribe info: http://cygwin.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 ajodidio@niksun.com Thu Jan 12 16:31:00 2012 From: ajodidio@niksun.com (Alex Jodidio) Date: Thu, 12 Jan 2012 16:31:00 -0000 Subject: Shift Function Key not working because of a bug in xkeyboard-config-2.4.1 Message-ID: Please be aware that Shift Function Key (e.g., Shift + F3) is not working with xkeyboard-config-2.4.1-1. You can verify that by running xev. This problem is known in X11 community and apparently a fix is on its way and may already be available in 2.4.1-r2 - see http://forums.funtoo.org/viewtopic.php?id=817. In the meantime you can avoid this problem by going back to xkeyboard-config-2.3-1. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@users.sourceforge.net Mon Jan 16 22:35:00 2012 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Mon, 16 Jan 2012 22:35:00 -0000 Subject: [ANNOUNCEMENT] Updated: xterm-277-1 Message-ID: The following package has been updated for the Cygwin distribution: *** xterm-277-1 The xterm program is a terminal emulator for the X Window System. It provides DEC VT102 and Tektronix 4014 compatible terminals for programs that can't use the window system directly. This is an update to the latest upstream release. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From mathog@caltech.edu Tue Jan 17 19:07:00 2012 From: mathog@caltech.edu (mathog) Date: Tue, 17 Jan 2012 19:07:00 -0000 Subject: font question, xfs locally on =?UTF-8?Q?cygwin=3F?= Message-ID: Short version: Can somebody please point me to instructions for setting up xfs on Cygwin/X? I especially need to know how to set this up so that Courier fonts work properly for sizes for which there is no corresponding pcf file. Is xfs really needed, or is putting in the right libfreetype bits and pieces enough? The files that go in /usr/share/fonts/default/Type1 on Mandriva, for instance? Long version: Two machines both running Xorg, one is an old Mandriva 2008.0 machine with Xorg 7.2 on the console, and the other is a Cygwin machine using whatever Xorg version is current on Cygwin/X. In nedit they handle the following font differently: -*-courier-medium-r-normal--17-120-*-*-*-iso8859-1 That works fine on the Mandriva machine X11 server, but uses some other font on the Cygwin X11 server (in both cases the Nedit client is on the Mandriva machine). I don't know what font is actually being used, but it isn't fixed (no error messages relating to this show up in the X.0.log file). I looked through the fonts on the Mandriva machine and it does not actually have a 17 point Courier font in the 75dpi directory, so it is coming up with that size on the fly, presumably through xfs, which is running there. Change to 14 pt (for which a pcf font file exists) then it is fixed width. Unfortunately that font is much too small on the monitor in question. Seems like font use on the Mandriva server is through xfs, but Cygwin/X client cannot use it, and isn't running its own copy. The main server has in /usr/share/fonts: 100dpi/ 75dpi/ cyrillic/ default/ fluxbox-artwiz-fonts/ misc/ OTF/ Speedo/ ttf/ TTF/ Type1/ whereas the Cygwin variant has only the first two, and only the 75dpi has any fonts in it. Presumably the Cygwin X11 server could be aimed at the Mandriva xfs, but for reasons I don't want to go into here it would be much better if the Cygwin machine ran its own xfs. How is this done? (Pointer to instructions?) Also, which part of xfs is coming up with the nice 17 point courier? What else, if anything, needs to be added to get that functionality? Or is xfs irrelevant and this is done through libfreetype? The Mandriva machine definitely loads that, and the Cygwin does not. Moreover on the Mandriva machine there is a /usr/share/fonts/default/Type1/adobestd35/ directory with a .dir file that does include a Courier entry. Thank you, David Mathog mathog@caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -- Unsubscribe info: http://cygwin.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 mathog@caltech.edu Tue Jan 17 19:58:00 2012 From: mathog@caltech.edu (mathog) Date: Tue, 17 Jan 2012 19:58:00 -0000 Subject: font question, xfs locally on =?UTF-8?Q?cygwin=3F?= In-Reply-To: References: Message-ID: On 17-Jan-2012 11:07, mathog wrote: > Is > xfs really needed, or is putting in the right libfreetype bits and > pieces enough? The files that go in > /usr/share/fonts/default/Type1 on Mandriva, for instance? So I tried copying the files from Mandriva over and dropping them into the Cygwin distro. That actually worked, in that the fonts then appeared and they looked good on the screen. Looks like xfs isn't needed. However, there was a problem with the naming conventions. This one works on the Mandriva X11 server -*-courier-medium-r-normal--17-120-*-*-*-iso8859-1 but it doesn't work on the Cygwin X11 server. The file name there must be -*-courier-medium-r-normal--17-120-*-*-*-*-iso8859-13 The problem seems to be that the font naming convention is slightly different. There are 3 fields between 120 and iso8859 on the Mandriva machine, but 4 on Cygwin/X. Change in the font naming conventions between different Xorg versions??? Which Cygwin package would install /usr/share/fonts/Type1 properly? Thanks, David Mathog mathog@caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -- Unsubscribe info: http://cygwin.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 Thu Jan 19 14:58:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 19 Jan 2012 14:58:00 -0000 Subject: font question, xfs locally on cygwin? In-Reply-To: References: Message-ID: <4F182FA1.6040309@dronecode.org.uk> On 17/01/2012 19:58, mathog wrote: > On 17-Jan-2012 11:07, mathog wrote: >> Is >> xfs really needed, or is putting in the right libfreetype bits and >> pieces enough? The files that go in >> /usr/share/fonts/default/Type1 on Mandriva, for instance? To address some of the questions from your previous email: xfs doesn't magically make fonts scalable, or know how to read types of font that the X server itself doesn't (now). So there is no reason whatsoever to use a local xfs. The same result can be achieved (better), simply by adding the same directories to the X server's fontpath. There are also some technical difficulties in building xfs for cygwin, due to libXfont's widespread use of weak symbols. Furthermore, core (server) fonts are a legacy feature. All modern toolkits use Xft (client) fonts. (See [1]) For all of these reasons, we don't provide an xfs. > So I tried copying the files from Mandriva over and dropping them into the > Cygwin distro. That actually worked, in that the fonts then appeared and they > looked > good on the screen. Looks like xfs isn't needed. However, there was a > problem with the naming conventions. > This one works on the Mandriva X11 server > > -*-courier-medium-r-normal--17-120-*-*-*-iso8859-1 > > but it doesn't work on the Cygwin X11 server. The file name there must be > > -*-courier-medium-r-normal--17-120-*-*-*-*-iso8859-13 > The problem seems to be that the font naming convention is slightly > different. There > are 3 fields between 120 and iso8859 on the Mandriva machine, but 4 on > Cygwin/X. Change in > the font naming conventions between different Xorg versions??? These names should be XLFDs (X logical font descriptions [1]). The first one doesn't look well-formed as it only has 13 fields. > Which Cygwin package would install /usr/share/fonts/Type1 properly? I think the fonts we talking about are the so-called 'URW fonts', donated by the URW foundry to ghostscript. These are packaged with ghostscript on cygwin, but it doesn't install them in a place where they can be shared with other uses. All other things being equal, it would be nice to have these fonts available to X, although I don't know if it would be better to pick a some other fonts to be aliased as scalable versions of courier etc. Also, some investigation would be needed to discover if we should adjust the ghostscript-fonts-std package, or make a separate package for these fonts for the X server. We would also need to make or obtain a suitable fonts.alias to map the font names to the standard postscript font names (e.g. so URW nimbus mono l can be accessed by the name courier) [1] http://www.x.org/releases/X11R7.6/doc/xorg-docs/fonts/fonts.html [2] http://www.x.org/releases/X11R7.6/doc/xorg-docs/specs/XLFD/xlfd.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/ From mathog@caltech.edu Thu Jan 19 16:37:00 2012 From: mathog@caltech.edu (mathog) Date: Thu, 19 Jan 2012 16:37:00 -0000 Subject: font question, xfs locally on =?UTF-8?Q?cygwin=3F?= In-Reply-To: <4F182FA1.6040309@dronecode.org.uk> References: <4F182FA1.6040309@dronecode.org.uk> Message-ID: <55348c7723bc5887ce2317d67bd66577@saf.bio.caltech.edu> On 19-Jan-2012 06:58, Jon TURNEY wrote: > On 17/01/2012 19:58, mathog wrote: >> This one works on the Mandriva X11 server >> >> -*-courier-medium-r-normal--17-120-*-*-*-iso8859-1 >> >> but it doesn't work on the Cygwin X11 server. The file name there >> must be >> >> -*-courier-medium-r-normal--17-120-*-*-*-*-iso8859-13 >> The problem seems to be that the font naming convention is slightly >> different. There >> are 3 fields between 120 and iso8859 on the Mandriva machine, but 4 >> on >> Cygwin/X. Change in >> the font naming conventions between different Xorg versions??? > > These names should be XLFDs (X logical font descriptions [1]). > > The first one doesn't look well-formed as it only has 13 fields. Right. Oddly it has been like that for, I don't know, 20 years? Searched for new fonts and it came back with 13 fields. Sent you a set of fonts.dir/fonts.scale for urw font names in a direct email. (Didn't have an actual fonts.alias, but should be easy to make one from these files.) Thanks, David Mathog mathog@caltech.edu Manager, Sequence Analysis Facility, Biology Division, Caltech -- Unsubscribe info: http://cygwin.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 Sun Jan 22 00:43:00 2012 From: rodmedina@cantv.net (rodmedina@cantv.net) Date: Sun, 22 Jan 2012 00:43:00 -0000 Subject: XWIN-1.11.3.0 crashes when some client programs terminate. Message-ID: <585051184.1267390.1327193019361.JavaMail.gess@webmail-05.datacenter.cha.cantv.net> Hi folks. I was on vacation so I couldn't replay. 3 days ago I tried to reproduce the crash, but it did not happen! I have not installed new software since the previous crash, niether cygwin nor Windows. I do not understand how that can be. The only difference I can think of is that when the crashes happened 2 weeks ago I had ben working for a long time with the machine. Three days ago I just booted the machine and tried to reproduce the crash. Today I tried again and the crash was back again (my wife had been using the machine all day). I have made the backtrace as suggested. It is attached together with the XWin.0.log. In order to have the crash you have to interact for a while with the test program and then close the window. About the locale non working, I start the X server with a windows batch script that makes the following sets before running XWin: SET DISPLAY=127.0.0.1:0.0 SET XAPPLRESDIR=/etc/X11/app-defaults SET XCMSDB=/usr/lib/X11/Xcms.txt SET XKEYSYMDB=/usr/share/X11/XKeysymDB SET XNLSPATH=/usr/share/X11/locale SET XLIB_SKIP_ARGB_VISUALS=1 SET LC_ALL=es_VEN.ISO-8859-1 Hope that this can be useful RM -------------- next part -------------- $ gdb --pid=4020 GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special) Copyright (C) 2011 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later 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-cygwin". For bug reporting instructions, please see: . Attaching to process 4020 [New Thread 4020.0x644] [New Thread 4020.0x6f4] [New Thread 4020.0x8dc] [New Thread 4020.0xab0] [New Thread 4020.0xfe4] [New Thread 4020.0x7d0] [New Thread 4020.0xcd8] [New Thread 4020.0xac] [New Thread 4020.0xb90] [New Thread 4020.0x720] [New Thread 4020.0x948] [New Thread 4020.0x35c] [New Thread 4020.0xc84] Reading symbols from /usr/bin/XWin...done. (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 4020.0x644] 0x0058bf47 in DeleteWindowFromAnyEvents (pWin=0x0, freeResources=0) at events.c:5624 5624 events.c: No such file or directory. in events.c (gdb) bt full #0 0x0058bf47 in DeleteWindowFromAnyEvents (pWin=0x0, freeResources=0) at events.c:5624 parent = 0xf8 mouse = 0x0 keybd = 0x126d4d0 focus = 0x12ac748 oc = 0x19560a60 passive = 0x7e3a941e grab = 0x0 #1 0x00425be4 in winTopLevelWindowProc@16 (hwnd=0x220370, message=8, wParam=0, lParam=0) at winmultiwindowwndproc.c:719 ptMouse = {x = 2279540, y = 3} hdcUpdate = 0x1c ps = {hdc = 0x1c, fErase = 0, rcPaint = {left = 3744, top = 0, right = 2117700569, bottom = 2118062216}, fRestore = 3, fIncUpdate = 2279588, rgbReserved = "?\215:~\213\215:~p\005V\031\034\000\000\000?\003\020\000\000\000\000\000\001\000\000\000\000\000\000"} pWin = 0x0 pWinPriv = 0x0 s_pScreen = 0x0 s_pScreenPriv = 0x0 s_pScreenInfo = 0x0 ---Type to continue, or q to quit--- hwndScreen = 0x0 pDraw = 0x0 wmMsg = {dwID = 0, msg = 2279472, iWindow = 6363488, hwndWindow = 0x11637b0, iX = 2281060, iY = 2279516, iWidth = 2117766617, iHeight = 1049548} fWMMsgInitialized = 0 s_fTracking = 0 needRestack = 0 ret = 0 hasEnteredSizeMove = 0 #2 0x7e398734 in USER32!GetDC () from /cygdrive/c/WINDOWS/system32/USER32.dll No symbol table info available. #3 0x00220370 in ?? () No symbol table info available. #4 0x7e398816 in USER32!GetDC () from /cygdrive/c/WINDOWS/system32/USER32.dll No symbol table info available. #5 0x00424e77 in winStartMousePolling (s_pScreenPriv=0x8) at winmultiwindowwndproc.c:299 No locals. #6 0x00220370 in ?? () No symbol table info available. #7 0x7e3a8ea0 in USER32!DefWindowProcW () from /cygdrive/c/WINDOWS/system32/USER32.dll ---Type to continue, or q to quit--- No symbol table info available. #8 0x00000000 in ?? () No symbol table info available. (gdb) -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 24915 bytes Desc: not available URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Sun Jan 22 22:04:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sun, 22 Jan 2012 22:04:00 -0000 Subject: XWIN-1.11.3.0 crashes when some client programs terminate. In-Reply-To: <585051184.1267390.1327193019361.JavaMail.gess@webmail-05.datacenter.cha.cantv.net> References: <585051184.1267390.1327193019361.JavaMail.gess@webmail-05.datacenter.cha.cantv.net> Message-ID: <4F1C87DB.6000007@dronecode.org.uk> On 22/01/2012 00:43, rodmedina wrote: > I was on vacation so I couldn't replay. 3 days ago I tried to reproduce the crash, > but it did not happen! I have not installed new software since the previous crash, > niether cygwin nor Windows. I do not understand how that can be. The only > difference I can think of is that when the crashes happened 2 weeks ago I had ben working > for a long time with the machine. Three days ago I just booted the machine and tried to > reproduce the crash. Today I tried again and the crash was back again (my wife had been > using the machine all day). I have made the backtrace as suggested. It is attached > together with the XWin.0.log. > In order to have the crash you have to interact for a while with the test program > and then close the window. Thanks very much for the backtrace. This helps a great deal, and I can see what I think is causing this problem. It looks like there is a race condition during window destruction, if we process a WM_KILLFOCUS message just as we are deleting the window, which could cause this crash. I've applied a couple of fixes to address this, both by removing the race condition, and avoiding the particular crash occurring in your case, so hopefully this works better now. I've uploaded a snapshot at [1]. Perhaps you could try that out and see if that makes a difference? > About the locale non working, I start the X server with a windows batch script that makes > the following sets before running XWin: > SET LC_ALL=es_VEN.ISO-8859-1 I don't think this is valid as we are expecting a 2-character ISO 3166 code here, which for Venezuela is VE. This doesn't match what's reported in your cygcheck.out, so I don't know if you've made a typo somewhere. [1] ftp://cygwin.com/pub/cygwinx/XWin.20120122-git-e8802abd6e2953e0.exe.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: 0001-Avoid-WIN_WINDOW_PROP-races-during-Windows-window-de.patch URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From svn-user@web.de Sun Jan 22 23:11:00 2012 From: svn-user@web.de (Paul Maier) Date: Sun, 22 Jan 2012 23:11:00 -0000 Subject: Levovo trackpoint come delayed (reproducable with xev) Message-ID: <000301ccd95b$09e07ca0$1da175e0$@de> Hi there, Lenovo trackpoint scrolling events get buffered somewhere until I release the button: then I get hundreds of scrolling events all at once. I can clearly see these events in xev. Result is that I don't really experience scrolling, rather jumping up and down with a random-like distance. With trackpoint I mean that red button in the middle of a Lenovo laptop. (Mouse wheel scrolling works perfect, in contrast.) Thanks & regards, Paul -- Unsubscribe info: http://cygwin.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 Jan 23 13:18:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 23 Jan 2012 13:18:00 -0000 Subject: Levovo trackpoint come delayed (reproducable with xev) In-Reply-To: <000301ccd95b$09e07ca0$1da175e0$@de> References: <000301ccd95b$09e07ca0$1da175e0$@de> Message-ID: <4F1D5E08.5020803@dronecode.org.uk> On 22/01/2012 23:10, Paul Maier wrote: > Lenovo trackpoint scrolling events get buffered somewhere until I release the button: > then I get hundreds of scrolling events all at once. > > I can clearly see these events in xev. > > Result is that I don't really experience scrolling, rather jumping up and down > with a random-like distance. > > With trackpoint I mean that red button in the middle of a Lenovo laptop. > > (Mouse wheel scrolling works perfect, in contrast.) Have you tried the workaround given in [1] ? According to the internet, the trackpoint driver tries to be too clever and doesn't send WM_MOUSEWHEEL messages, but tries to fiddle with the Windows scrollbars directly itself, which obviously isn't going to work well for an X window :S [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trackpoint -- 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 rodmedina@cantv.net Mon Jan 23 15:05:00 2012 From: rodmedina@cantv.net (rodmedina@cantv.net) Date: Mon, 23 Jan 2012 15:05:00 -0000 Subject: XWIN-1.11.3.0 crashes when some client programs terminate. Message-ID: <236499353.1262579.1327331129929.JavaMail.gess@webmail-02.datacenter.cha.cantv.net> Hi, Jon TURNEY wrote: >you've made a typo somewhere. It was indeed a typo! Thanks a lot 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 svn-user@web.de Mon Jan 23 21:57:00 2012 From: svn-user@web.de (Paul Maier) Date: Mon, 23 Jan 2012 21:57:00 -0000 Subject: AW: Levovo trackpoint come delayed (reproducable with xev) In-Reply-To: <4F1D5E08.5020803@dronecode.org.uk> References: <000301ccd95b$09e07ca0$1da175e0$@de> <4F1D5E08.5020803@dronecode.org.uk> Message-ID: <000701ccda19$ddd393d0$997abb70$@de> > On 22/01/2012 23:10, Paul Maier wrote: > > Lenovo trackpoint scrolling events get buffered somewhere until I release the button: > > then I get hundreds of scrolling events all at once. > > > > I can clearly see these events in xev. > > > > Result is that I don't really experience scrolling, rather jumping up and down > > with a random-like distance. > > > > With trackpoint I mean that red button in the middle of a Lenovo laptop. > > > > (Mouse wheel scrolling works perfect, in contrast.) > > Have you tried the workaround given in [1] ? > > According to the internet, the trackpoint driver tries to be too clever and > doesn't send WM_MOUSEWHEEL messages, but tries to fiddle with the Windows > scrollbars directly itself, which obviously isn't going to work well for an X > window :S > > [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trackpoint > Hi Jon, I can't find any of the files tp4*.dat on my PC (I'm running Windows 7) - see console output below. And I do get the trackpoint events, they are just delayed until I release that button; on release I get hundreds of correct events scrolling my window to somewhere. How many events I get depends on how long or how intense I pressed the track point (sounds reasonable to me). Paul. C:\Windows\System32>dir tp*.dat Datentr?ger in Laufwerk C: ist Systemplatte Verzeichnis von C:\Windows\System32 Datei nicht gefunden C:\Windows\System32>dir *.dat Datentr?ger in Laufwerk C: ist Systemplatte Verzeichnis von C:\Windows\System32 10.06.2009 22.34 215.943 dssec.dat 14.10.2011 14.31 369.104 FNTCACHE.DAT 10.06.2009 22.13 3.698.584 ieapfltr.dat 10.06.2009 22.26 673.088 mlang.dat 10.06.2009 22.32 741 NOISE.DAT 29.12.2011 07.53 152.404 perfc007.dat 29.12.2011 07.53 125.350 perfc009.dat 14.07.2009 09.49 38.104 perfd007.dat 14.07.2009 01.34 31.548 perfd009.dat 29.12.2011 07.53 711.580 perfh007.dat 29.12.2011 07.53 665.164 perfh009.dat 14.07.2009 09.49 295.922 perfi007.dat 14.07.2009 01.34 291.294 perfi009.dat 13 Datei(en), 7.268.826 Bytes 0 Verzeichnis(se), 54.902.112.256 Bytes frei -- Unsubscribe info: http://cygwin.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 gpion@lfdj.com Tue Jan 24 11:40:00 2012 From: gpion@lfdj.com (Gilles Pion) Date: Tue, 24 Jan 2012 11:40:00 -0000 Subject: upgraded cygwin and Xfree to latest releases "Alt-r" sequence doesn't work anymore Message-ID: (I've used XEV to investigate) Pressing alt key alone works normally (xev able to see "keypress" and "keyrelease" event for "Alt_L" key) Pressing "r" key alone is also ok (ditto) But when pressing in sequence, the "r" up and down events are missing (I have no problem with other alphabetic keys) Any idea? -- Unsubscribe info: http://cygwin.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 gpion@lfdj.com Tue Jan 24 12:05:00 2012 From: gpion@lfdj.com (Gilles Pion) Date: Tue, 24 Jan 2012 12:05:00 -0000 Subject: upgraded cygwin and Xfree to latest releases "Alt-r" sequence doesn't work anymore References: Message-ID: Please ignore my previous post: problem has been fixed by rebooting -- Unsubscribe info: http://cygwin.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 Tue Jan 24 13:17:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 24 Jan 2012 13:17:00 -0000 Subject: AW: Levovo trackpoint come delayed (reproducable with xev) In-Reply-To: <000701ccda19$ddd393d0$997abb70$@de> References: <000301ccd95b$09e07ca0$1da175e0$@de> <4F1D5E08.5020803@dronecode.org.uk> <000701ccda19$ddd393d0$997abb70$@de> Message-ID: <4F1EAF7D.5030602@dronecode.org.uk> On 23/01/2012 21:56, Paul Maier wrote: >> On 22/01/2012 23:10, Paul Maier wrote: >>> Lenovo trackpoint scrolling events get buffered somewhere until I release the button: >>> then I get hundreds of scrolling events all at once. >>> >>> I can clearly see these events in xev. >>> >>> Result is that I don't really experience scrolling, rather jumping up and down >>> with a random-like distance. >>> >>> With trackpoint I mean that red button in the middle of a Lenovo laptop. >>> >>> (Mouse wheel scrolling works perfect, in contrast.) >> >> Have you tried the workaround given in [1] ? >> >> According to the internet, the trackpoint driver tries to be too clever and >> doesn't send WM_MOUSEWHEEL messages, but tries to fiddle with the Windows >> scrollbars directly itself, which obviously isn't going to work well for an X >> window :S >> >> [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trackpoint > > I can't find any of the files tp4*.dat on my PC (I'm running Windows 7) - see console output below. It seems that FAQ might need a little updating, that file might found under %PROGRAMFILES% now, C:\Program Files\Synaptics\SynTP\TP4table.dat or C:\Program Files\Lenovo\Trackpoint\tp4table.dat for example. > And I do get the trackpoint events, they are just delayed until I release that button; > on release I get hundreds of correct events scrolling my window to somewhere. > How many events I get depends on how long or how intense I pressed the track point (sounds reasonable to me). So, if you can't try the workaround, perhaps you could do a bit of investigation? Download the latest snapshot built with debugging enabled from [1] Run it using 'WIN_DEBUG_MESSAGES=1 ./XWin -logverbose 3 ' Open up an xterm You should then be able to see WM_MOUSEWHEEL messages being delivered in the debug output from XWin when you use the trackpoint scrolling. Are they being delivered on time, or only when you release the the button? -- Unsubscribe info: http://cygwin.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 ryan.johnson@cs.utoronto.ca Tue Jan 24 13:52:00 2012 From: ryan.johnson@cs.utoronto.ca (Ryan Johnson) Date: Tue, 24 Jan 2012 13:52:00 -0000 Subject: AW: Levovo trackpoint come delayed (reproducable with xev) In-Reply-To: <4F1EAF7D.5030602@dronecode.org.uk> References: <000301ccd95b$09e07ca0$1da175e0$@de> <4F1D5E08.5020803@dronecode.org.uk> <000701ccda19$ddd393d0$997abb70$@de> <4F1EAF7D.5030602@dronecode.org.uk> Message-ID: <4F1EB781.1040304@cs.utoronto.ca> On 24/01/2012 8:17 AM, Jon TURNEY wrote: > On 23/01/2012 21:56, Paul Maier wrote: >>> On 22/01/2012 23:10, Paul Maier wrote: >>>> Lenovo trackpoint scrolling events get buffered somewhere until I release the button: >>>> then I get hundreds of scrolling events all at once. >>>> >>>> I can clearly see these events in xev. >>>> >>>> Result is that I don't really experience scrolling, rather jumping up and down >>>> with a random-like distance. >>>> >>>> With trackpoint I mean that red button in the middle of a Lenovo laptop. >>>> >>>> (Mouse wheel scrolling works perfect, in contrast.) >>> Have you tried the workaround given in [1] ? >>> >>> According to the internet, the trackpoint driver tries to be too clever and >>> doesn't send WM_MOUSEWHEEL messages, but tries to fiddle with the Windows >>> scrollbars directly itself, which obviously isn't going to work well for an X >>> window :S >>> >>> [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-trackpoint >> I can't find any of the files tp4*.dat on my PC (I'm running Windows 7) - see console output below. > It seems that FAQ might need a little updating, that file might found under > %PROGRAMFILES% now, C:\Program Files\Synaptics\SynTP\TP4table.dat or > C:\Program Files\Lenovo\Trackpoint\tp4table.dat for example. I've done this with mintty on my machine as follows: > --- TP4scrol-orig.dat 2011-12-11 16:33:22.742741700 -0500 > +++ TP4scrol.dat 2011-12-30 00:59:46.793965200 -0500 > @@ -24,6 +24,9 @@ > ; Pass 0 rules (These rules run first) > ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;; > > +; mintty > +*,*,mintty.exe,*,*,*,WheelStd,0,9 > + > ; Windows IE3 patch for 2 button systems > *,*,iexplore.exe,*,Shell DocObject View,HTML_Internet > Explorer,Standard,0,5 I assume the line for X apps would be the similar. Note that you have to put the same line in TP4table.dat, then kill and restart all the TP* processes. One of them (sorry, can't remember which) is the "parent" process and will start the others if it sees they're missing. Good luck! Ryan -- Unsubscribe info: http://cygwin.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 sonja.abe@web.de Mon Jan 30 12:20:00 2012 From: sonja.abe@web.de (Sonja Abe) Date: Mon, 30 Jan 2012 12:20:00 -0000 Subject: Errormessage Message-ID: <1715036956.1132871.1327926043893.JavaMail.fmail@mwmweb071> Hello, I have installed cygwinx and now when I will start the programm and entering startxwin, I got allways this error-message: startxwin: Another X server instance is running on DISPLAY :0 . Resource temprarily unavailable Can you help me and write me, what I can do to run this program. Thank you very much Sonja Ab? ___________________________________________________________ SMS schreiben mit WEB.DE FreeMail - einfach, schnell und kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192 -- Unsubscribe info: http://cygwin.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 Jan 30 16:56:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Mon, 30 Jan 2012 16:56:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.11.4-1 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.11.4-1 *** xorg-server-dmx-1.11.4-1 These packages contain XWin and the other X.Org X11 servers. IMPORTANT NOTE: This release changes the default settings so that the -resize and -wgl options are turned on by default. If that causes issues, please let us know, and either revert to the previous version, or turn off those features using the -noresize and -nowgl options. (See [2] for help on how to do that) In addition to upstream fixes [1], this contains the following cygwin-specific changes since 1.11.4-1: * Enable RANDR resize (option -resize) by default * Enable AIGLX (option -wgl) by default * Ignore bogus WM_DISPLAYCHANGE messages that have 0 bpp (Thanks to Colin Harrison for patch) * Avoid WIN_WINDOW_PROP races which could cause a crash during Windows window destruction (Reported by Rodrigo Medina) * Restore modifier key state when an X window gains focus (Thanks to Oliver Schmidt for patch) * RANDR resize didn't occur, in windowed mode, with option -resize, when the window was maximized or restored. (Thanks to Colin Harrison for patch) * Fix rrScreenSetSize function pointer mismatch (Thanks to Ryan Pavlik for patch) * Add Windows 8 to the list of Windows versions we know the name of aec6d0bf84b96a4586dc5e8dc77ffe2f *xorg-server-1.11.4-1.tar.bz2 21423d8221c934e25c1aa5e1a0bddc2d *xorg-server-dmx-1.11.4-1.tar.bz2 6bd74a8c9677daf1f9087c54e78751f6 *xorg-server-1.11.4-1-src.tar.bz2 [1] http://lists.x.org/archives/xorg-announce/2012-January/001805.html [2] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-command-line-args -- 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 cht74@yahoo.de Tue Jan 31 08:43:00 2012 From: cht74@yahoo.de (Christian Tuma) Date: Tue, 31 Jan 2012 08:43:00 -0000 Subject: xwin.exe 1.11.4-1 segmentation fault on startup (-wgl -multiwindow) Message-ID: <1327999414.12334.YahooMailNeo@web25702.mail.ukl.yahoo.com> Hello, when I invoke xwin.exe for hardware accelerated OpenGL (AIGLX) $ xwin -wgl -multiwindow a segmentation fault occurs. This happens with the latest version (1.11.4-1), but I already had the same problem with my first installation of the X server (1.11.3-1). Attached please find cygcheck.out (sensitive data deleted) and XWin.0.log for further details. Somebody with an idea what is going wrong here? Thank you. - Christian -------------- next part -------------- A non-text attachment was scrubbed... Name: cygcheck.out Type: application/octet-stream Size: 34168 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 2378 bytes Desc: not available URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From kare.edvardsen@uit.no Tue Jan 31 12:48:00 2012 From: kare.edvardsen@uit.no (=?utf-8?B?RWR2YXJkc2VuIEvDpXJl?=) Date: Tue, 31 Jan 2012 12:48:00 -0000 Subject: X-win server will not start after upgrade Message-ID: <1328014016.18556.92.camel@kare-desktop> I've reinstalled cygwin and cygwin-X from setup ver 2.763, and now X-server won't start. Logfile attaced. Cheers, K?re -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: text/x-log Size: 2380 bytes Desc: 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/ From jon.turney@dronecode.org.uk Tue Jan 31 14:45:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 31 Jan 2012 14:45:00 -0000 Subject: xwin.exe 1.11.4-1 segmentation fault on startup (-wgl -multiwindow) In-Reply-To: <1327999414.12334.YahooMailNeo@web25702.mail.ukl.yahoo.com> References: <1327999414.12334.YahooMailNeo@web25702.mail.ukl.yahoo.com> Message-ID: <4F27FE74.9030803@dronecode.org.uk> On 31/01/2012 08:43, Christian Tuma wrote: > when I invoke xwin.exe for hardware accelerated OpenGL (AIGLX) > > $ xwin -wgl -multiwindow > > a segmentation fault occurs. This happens with the latest version > (1.11.4-1), but I already had the same problem with my first installation > of the X server (1.11.3-1). > > Attached please find cygcheck.out (sensitive data deleted) and XWin.0.log > for further details. > [ 3248.876] GL_VERSION: 1.1.0 > [ 3248.876] GL_VENDOR: Microsoft Corporation > [ 3248.876] GL_RENDERER: GDI Generic > [ 3248.876] GL_EXTENSIONS: GL_WIN_swap_hint GL_EXT_bgra GL_EXT_paletted_texture > [ 3248.876] wglwrap: Can't resolve "wglGetExtensionsStringARB" > [ 3248.876] WGL_EXTENSIONS: (null)Segmentation fault at address 0x0 > [ 3248.876] Fatal server error: > [ 3248.876] Caught signal 11 (Segmentation fault). Server aborting > [ 3248.876] Server terminated with error (1). Closing log file. Thanks for reporting this issue. I've uploaded a 1.11.4-2 which should contain a fix. When it reaches the mirrors, perhaps you could try it and see if it fixes things for you? You don't appear to be using a graphics card driver with OpenGL acceleration though, I'd be interested to which one? -- 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 Tue Jan 31 14:50:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 31 Jan 2012 14:50:00 -0000 Subject: Errormessage In-Reply-To: <1715036956.1132871.1327926043893.JavaMail.fmail@mwmweb071> References: <1715036956.1132871.1327926043893.JavaMail.fmail@mwmweb071> Message-ID: <4F27FFAF.9020405@dronecode.org.uk> On 30/01/2012 12:20, Sonja Abe wrote: > I have installed cygwinx and now when I will start the programm and entering startxwin, I got allways this error-message: > > startxwin: Another X server instance is running on DISPLAY :0 > . Resource temprarily unavailable > > Can you help me and write me, what I can do to run this program. > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html There's probably more detail about why it thinks another X server is already running in /var/log/xwin/XWin.0.log, which is why we ask people to attach it to their problem reports in the page linked above. > Documentation: http://x.cygwin.com/docs/ > FAQ: http://x.cygwin.com/docs/faq/ -- 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 Tue Jan 31 15:53:00 2012 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 31 Jan 2012 15:53:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.11.4-2 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-1.11.4-2 *** xorg-server-dmx-1.11.4-2 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.11.4-1: * Fix a crash in -wgl mode when the WGL_ARB_extensions_string extension is not supported e.g with the 'GDI Generic' GL renderer 5f374cd95e0f67ffe39a095369b32bae *xorg-server-1.11.4-2.tar.bz2 4cef79e875d6d3d2cf038024307a513e *xorg-server-dmx-1.11.4-2.tar.bz2 4c52d3d92bb07d85b2d87675cf50b556 *xorg-server-1.11.4-2-src.tar.bz2 -- 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 angelo.graziosi@alice.it Tue Jan 31 22:03:00 2012 From: angelo.graziosi@alice.it (Angelo Graziosi) Date: Tue, 31 Jan 2012 22:03:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.11.4-2 Message-ID: <4F286512.6090408@alice.it> I notice a problem moving the mouse pointer. Usually I start XWin with a link on the desktop whose target is C:\cygwin-2\bin\run.exe bash -l -c 'rm -rf /tmp/.X11-unix; XWin -multiwindow -clipboard -silent-dup-error 2>/dev/null &' it produces the XWin.0.log-with_wgl attached via the tar-ball. Both with xorg-server-1.11.4-1 and xorg-server-1.11.4-2, the mouse pointer moves in slow motion, in "steps", with a delay.. one has difficulty to move finely... If I switch-off wgl, C:\cygwin-2\bin\run.exe bash -l -c 'rm -rf /tmp/.X11-unix; XWin -multiwindow -nowgl -clipboard -silent-dup-error 2>/dev/null &' it moves just fine! I have attached XWin.0.log-nowgl for this case and the check.out (all in the tar-ball). Ciao, Angelo. -------------- next part -------------- A non-text attachment was scrubbed... Name: logs_checkout.tar.xz Type: application/octet-stream Size: 20832 bytes Desc: not available URL: -------------- next part -------------- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/