From yselkowitz@users.sourceforge.net Tue Mar 4 02:39:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Tue, 04 Mar 2014 02:39:00 -0000 Subject: [ANNOUNCEMENT] Updated: xterm-302-1 Message-ID: The following package has been updated in the Cygwin distribution: *** xterm-302-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 jjreisert@alum.mit.edu Thu Mar 6 01:28:00 2014 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Thu, 06 Mar 2014 01:28:00 -0000 Subject: Emacs just stopped working for no reason Message-ID: I was away on vacation for a week. Cygwin / X / GNU Emacs 24.3.1 were all working normally when I left. I left the computer powered on while I was away. No software was updated on the computer during that time, though I am running the BOINC software for World Community Grid. Computer is running Windows 7 Pro 64-bit. I left a couple of xterm windows open before I left, because there was some work I wanted to be reminded of when I got home. Upon arriving home last night, I tried to fire up Emacs, but now it's not working. It either says "memory exhausted" or just hangs. I rebooted, nothing changed. I started "ash" and ran "rebaseall -v". Still, nothing changed. This is not the first time that Emacs has died. The only way to fix the problem is to completely re-install Cygwin from scratch. Is there *any* way to try to figure out what is causing this? -- 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 kbrown@cornell.edu Thu Mar 6 03:10:00 2014 From: kbrown@cornell.edu (Ken Brown) Date: Thu, 06 Mar 2014 03:10:00 -0000 Subject: Emacs just stopped working for no reason In-Reply-To: References: Message-ID: <5317E6F9.9040506@cornell.edu> On 3/5/2014 8:28 PM, Jim Reisert AD1C wrote: > I was away on vacation for a week. Cygwin / X / GNU Emacs 24.3.1 were > all working normally when I left. I left the computer powered on > while I was away. No software was updated on the computer during that > time, though I am running the BOINC software for World Community Grid. > Computer is running Windows 7 Pro 64-bit. > > I left a couple of xterm windows open before I left, because there was > some work I wanted to be reminded of when I got home. > > Upon arriving home last night, I tried to fire up Emacs, but now it's > not working. It either says "memory exhausted" or just hangs. > > I rebooted, nothing changed. > > I started "ash" and ran "rebaseall -v". Still, nothing changed. > > This is not the first time that Emacs has died. The only way to fix > the problem is to completely re-install Cygwin from scratch. > > Is there *any* way to try to figure out what is causing this? You might check to see if this is the fontconfig problem that others have reported (see http://cygwin.com/ml/cygwin/2013-12/msg00248.html): Try running "fc-cache -fsv". 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 jjreisert@alum.mit.edu Thu Mar 6 05:03:00 2014 From: jjreisert@alum.mit.edu (Jim Reisert AD1C) Date: Thu, 06 Mar 2014 05:03:00 -0000 Subject: Emacs just stopped working for no reason In-Reply-To: <5317E6F9.9040506@cornell.edu> References: <5317E6F9.9040506@cornell.edu> Message-ID: On Wed, Mar 5, 2014 at 8:09 PM, Ken Brown wrote: > You might check to see if this is the fontconfig problem that others have > reported (see http://cygwin.com/ml/cygwin/2013-12/msg00248.html): Try > running "fc-cache -fsv". That was exactly the problem! You just saved me a boatload of time. I'll bookmark that link for next time. - 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 david.cutler@hp.com Thu Mar 6 22:26:00 2014 From: david.cutler@hp.com (Cutler, David (NonStop)) Date: Thu, 06 Mar 2014 22:26:00 -0000 Subject: Problem with Multi-Key Sequences... They Seem To Be Filtered Out By XWin Message-ID: Hello, I downloaded a new copy of Cygwin in the last 5 days (effectively started from scratch) and am trying to use XWin on a Windows 7 virtual machine running an old proprietary X program (it's called x6530 which is a terminal emulator for a proprietary terminal built originally by Tandem Computers and now owned by Hewlett Packard.) I start up the server and window manager using the following command: /usr/bin/setsid \ /usr/bin/XWin \ -mwextwm \ -multimonitors \ -internalwm \ -nowinkill \ & I'm trying to use multi-key sequences like Control_L-Alt_L-F6, Shift_L-Control_L-F6, etc.? I do see that xev recognizes these sequences but the Control_L and Alt_L keys seem to be filtered out when I run x6530. All it seems to get is F6 or Shift_L-F6. I've tried different window managers, run /usr/bin/XWin directly, used the right-hand modification keys like Control_R, etc. and no matter what I try, I see the same filtering behavior in x6530. I have recently used exceed (formally owned by Hummingbird) with x6530 and the Control_L and Alt_L keys are passed to x6530 as expected so my suspicion is that XWin is responsible for the unwanted behavior of filtering out the keys like Control_L and Alt_L keys. Is this the case?? Is there a way to get these sequences "unfiltered". If there is additional information I can provide, please let me know. Thanks for any information you can provide. -David Cutler -- Unsubscribe info: http://cygwin.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 Mar 7 13:45:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 07 Mar 2014 13:45:00 -0000 Subject: Problem with Multi-Key Sequences... They Seem To Be Filtered Out By XWin In-Reply-To: References: Message-ID: <5319CD73.2080804@dronecode.org.uk> On 06/03/2014 22:25, Cutler, David (NonStop) wrote: > I downloaded a new copy of Cygwin in the last 5 days (effectively started > from scratch) and am trying to use XWin on a Windows 7 virtual machine > running an old proprietary X program (it's called x6530 which is a terminal > emulator for a proprietary terminal built originally by Tandem Computers > and now owned by Hewlett Packard.) > > I start up the server and window manager using the following command: > /usr/bin/setsid \ /usr/bin/XWin \ -mwextwm \ -multimonitors \ -internalwm > \ -nowinkill \ & While probably not the cause of your problems, -mwextwm is an experimental option and -internalwm is undocumented. I think you should get the same effect with just '-multiwindow -nowinkill' > I'm trying to use multi-key sequences like Control_L-Alt_L-F6, > Shift_L-Control_L-F6, etc. I do see that xev recognizes these sequences > but the Control_L and Alt_L keys seem to be filtered out when I run x6530. > All it seems to get is F6 or Shift_L-F6. > > I've tried different window managers, run /usr/bin/XWin directly, used the > right-hand modification keys like Control_R, etc. and no matter what I > try, I see the same filtering behavior in x6530. I have recently used > exceed (formally owned by Hummingbird) with x6530 and the Control_L and > Alt_L keys are passed to x6530 as expected so my suspicion is that XWin is > responsible for the unwanted behavior of filtering out the keys like > Control_L and Alt_L keys. > > Is this the case? Is there a way to get these sequences "unfiltered". The evidence doesn't really support your conclusion: If one X client (xev) gets these key events, why would the X server not send them to a different X client (x6530)? However, it's perfectly possibly that they aren't sent in the expected form, or some other problem. I guess that x6530 is running on a remote host, so the details of that remote host might be pertinent. FAQ 5.1.8 [1] and the linked email thread may be relevant. If you still have access to the working setup, you might want to compare the xev output for these keys to see if there any differences. You might also consider using wireshark, xmon or xscope to examine the protocol interactions between client and server to see if there is any difference there. > If there is additional information I can provide, please let me know. It would be nice to see /var/log/xwin/XWin.0.log just to see what keyboard configuration is being used by the X server etc. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#alt-gr-with-old-x -- 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 meh@winfirst.com Fri Mar 7 19:57:00 2014 From: meh@winfirst.com (Mark Hansen) Date: Fri, 07 Mar 2014 19:57:00 -0000 Subject: Problem launching XTerm on new Cygwin installation Message-ID: <531A24A0.7010400@winfirst.com> I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. On the desktop, everything worked as expected without problems. On the laptop, I have the following problems: When I launch a shell window, I get the following error: Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid is in /etc/group. Also, when I try to launch an XTerm, I get the following message in the XTerm window for just a few seconds and then the window goes away: /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory I'm starting the XWin Server using a shortcut with the following: C:\Apps\cygwin\bin\run.exe /usr/bin/bash.exe -l -c "/usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor" I'm starting the XTerm using a shortcut with the following: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I've searched for this XTERM_SHELL error, but can't find anything. Can anybody help me? Thanks, -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dickey@his.com Fri Mar 7 21:50:00 2014 From: dickey@his.com (Thomas Dickey) Date: Fri, 07 Mar 2014 21:50:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <531A24A0.7010400@winfirst.com> References: <531A24A0.7010400@winfirst.com> Message-ID: <20140307214954.GA4187@aerie.jexium-island.net> On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote: > I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. > On the desktop, everything worked as expected without problems. On the laptop, I > have the following problems: > > When I launch a shell window, I get the following error: > > Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid is in /etc/group. (I don't know about this one) > Also, when I try to launch an XTerm, I get the following message in the XTerm window for > just a few seconds and then the window goes away: > > /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303 (from yesterday) > I'm starting the XWin Server using a shortcut with the following: > > C:\Apps\cygwin\bin\run.exe > /usr/bin/bash.exe -l -c > "/usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor" > > I'm starting the XTerm using a shortcut with the following: > > C:\Apps\cygwin\bin\run.exe > -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l I'd try putting "-e" before the "/bin/zsh", which moves it away from the bug noted. (actually, the trailing "-l" doesn't look right either) fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. However, I was able to analyze it on Linux with valgrind... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From meh@winfirst.com Fri Mar 7 22:00:00 2014 From: meh@winfirst.com (Mark Hansen) Date: Fri, 07 Mar 2014 22:00:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <531A24A0.7010400@winfirst.com> References: <531A24A0.7010400@winfirst.com> Message-ID: <531A4180.9070509@winfirst.com> On 3/7/2014 11:57 AM, Mark Hansen wrote: > I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. > On the desktop, everything worked as expected without problems. On the laptop, I > have the following problems: > > When I launch a shell window, I get the following error: > > Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid is in /etc/group. > > Also, when I try to launch an XTerm, I get the following message in the XTerm window for > just a few seconds and then the window goes away: > > /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory > > I'm starting the XWin Server using a shortcut with the following: > > C:\Apps\cygwin\bin\run.exe > /usr/bin/bash.exe -l -c > "/usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor" > > I'm starting the XTerm using a shortcut with the following: > > C:\Apps\cygwin\bin\run.exe > -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l > > I've searched for this XTERM_SHELL error, but can't find anything. Can anybody help me? > > Thanks, Well, I did the following two things: 1. I changed the group id for my entry in the /etc/passwd file from 10530 (or whatever that value was) to 545 (Users) and the first error went away. 2. I changed the shortcut I use to launch the XTerms and removed the shell name at the end, so it now looks like this: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls and now the XTerm is started without any errors. I guess it's working now, but I'm curious why these problems happened on the laptop installation and not on the desktop installation. Especially why the XTerm launch command had to change. The one I showed first I've been using for years without problems. I don't remember how I came up with it now, but I remember spending a lot of time putting that together. Also, that original launch command is working on my other PC (the desktop) as well as my other machines running the 32-bit version of Cygwin. Thanks for any feedback/clarification. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From meh@winfirst.com Fri Mar 7 22:04:00 2014 From: meh@winfirst.com (Mark Hansen) Date: Fri, 07 Mar 2014 22:04:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <20140307214954.GA4187@aerie.jexium-island.net> References: <531A24A0.7010400@winfirst.com> <20140307214954.GA4187@aerie.jexium-island.net> Message-ID: <531A424D.5000204@winfirst.com> On 3/7/2014 1:49 PM, Thomas Dickey wrote: > On Fri, Mar 07, 2014 at 11:57:20AM -0800, Mark Hansen wrote: >> I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. >> On the desktop, everything worked as expected without problems. On the laptop, I >> have the following problems: >> >> When I launch a shell window, I get the following error: >> >> Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid is in /etc/group. > > (I don't know about this one) > >> Also, when I try to launch an XTerm, I get the following message in the XTerm window for >> just a few seconds and then the window goes away: >> >> /cygdrive/c/Apps/cygwin/bin/xterm: Could not exec XTERM_SHELL=XTERM_SHELL=: No such file or directory > > yes, that's a bug which surfaced in #301, thought it was gone in #302, and _should_ be gone in #303 > (from yesterday) > >> I'm starting the XWin Server using a shortcut with the following: >> >> C:\Apps\cygwin\bin\run.exe >> /usr/bin/bash.exe -l -c >> "/usr/bin/startxwin.exe -- -emulate3buttons -multiwindow -clipboard -swcursor" >> >> I'm starting the XTerm using a shortcut with the following: >> >> C:\Apps\cygwin\bin\run.exe >> -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls /bin/zsh -l > > I'd try putting "-e" before the "/bin/zsh", which moves it away from the bug noted. > (actually, the trailing "-l" doesn't look right either) Thanks. I think the -l was to cause a login shell, but I see now that is what the -ls argument does. Since I removed the shell argument ("/bin/zsh -l") it is now working. I'm getting the shell I want, I suspect, because that is the shell mentioned in the /etc/passwd file for my user. As a result, it is working so I'll leave it alone. > > fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. > However, I was able to analyze it on Linux with valgrind... Well, I downloaded the Cygwin installation for my desktop last week, and downloaded the Cygwin for my laptop yesterday. I guess the bug could have been introduced between those times? Thanks for your help! -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dickey@his.com Fri Mar 7 22:12:00 2014 From: dickey@his.com (Thomas Dickey) Date: Fri, 07 Mar 2014 22:12:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <531A424D.5000204@winfirst.com> References: <531A24A0.7010400@winfirst.com> <20140307214954.GA4187@aerie.jexium-island.net> <531A424D.5000204@winfirst.com> Message-ID: <20140307221219.GA5538@aerie.jexium-island.net> On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote: > As a result, it is working so I'll leave it alone. :-) > >fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. > >However, I was able to analyze it on Linux with valgrind... > > Well, I downloaded the Cygwin installation for my desktop last week, and downloaded > the Cygwin for my laptop yesterday. I guess the bug could have been introduced between > those times? yes - I finished #302 at the beginning of the week. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From meh@winfirst.com Fri Mar 7 23:37:00 2014 From: meh@winfirst.com (Mark Hansen) Date: Fri, 07 Mar 2014 23:37:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <20140307221219.GA5538@aerie.jexium-island.net> References: <531A24A0.7010400@winfirst.com> <20140307214954.GA4187@aerie.jexium-island.net> <531A424D.5000204@winfirst.com> <20140307221219.GA5538@aerie.jexium-island.net> Message-ID: <531A5840.605@winfirst.com> On 3/7/2014 2:12 PM, Thomas Dickey wrote: > On Fri, Mar 07, 2014 at 02:03:57PM -0800, Mark Hansen wrote: >> As a result, it is working so I'll leave it alone. > > :-) > >> >fwiw, when I compile #301, #302 and #303 for Cygwin, I don't see the bug. >> >However, I was able to analyze it on Linux with valgrind... >> >> Well, I downloaded the Cygwin installation for my desktop last week, and downloaded >> the Cygwin for my laptop yesterday. I guess the bug could have been introduced between >> those times? > > yes - I finished #302 at the beginning of the week. > Okay, this is very strange. As I said before, I have had no problems launching XTerms on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). I edited the launcher shortcut to remove the "/bin/zsh -l" from the end of the command and it started working again. I didn't do anything to update the Cygwin product on my desktop during this time. I'm confused... FYI. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dickey@his.com Sat Mar 8 00:36:00 2014 From: dickey@his.com (Thomas Dickey) Date: Sat, 08 Mar 2014 00:36:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <531A5840.605@winfirst.com> References: <531A24A0.7010400@winfirst.com> <20140307214954.GA4187@aerie.jexium-island.net> <531A424D.5000204@winfirst.com> <20140307221219.GA5538@aerie.jexium-island.net> <531A5840.605@winfirst.com> Message-ID: <20140308003615.GA8989@aerie.jexium-island.net> On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote: > > Okay, this is very strange. As I said before, I have had no problems launching XTerms > on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems > ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began > having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). > > I edited the launcher shortcut to remove the "/bin/zsh -l" from the end of the command > and it started working again. > > I didn't do anything to update the Cygwin product on my desktop during this time. xterm handles these three cases differently: xterm xterm /bin/zsh xterm -e /bin/zsh The bug that I mentioned is in the second case - not in the other two. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From meh@Winfirst.Com Sat Mar 8 00:43:00 2014 From: meh@Winfirst.Com (Mark Hansen) Date: Sat, 08 Mar 2014 00:43:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <20140308003615.GA8989@aerie.jexium-island.net> References: <531A24A0.7010400@winfirst.com> <20140307214954.GA4187@aerie.jexium-island.net> <531A424D.5000204@winfirst.com> <20140307221219.GA5538@aerie.jexium-island.net> <531A5840.605@winfirst.com> <20140308003615.GA8989@aerie.jexium-island.net> Message-ID: <531A67C6.9000502@Winfirst.Com> On 3/7/2014 4:36 PM, Thomas Dickey wrote: > On Fri, Mar 07, 2014 at 03:37:36PM -0800, Mark Hansen wrote: >> >> Okay, this is very strange. As I said before, I have had no problems launching XTerms >> on my desktop running 64-bit Cygwin. I've launched several XTerms today with no problems >> ... until a few minutes ago. I went to launch an XTerm on my desktop PC and it began >> having the same problem I saw on the laptop (the error having to do with XTERM_SHELL). >> >> I edited the launcher shortcut to remove the "/bin/zsh -l" from the end of the command >> and it started working again. >> >> I didn't do anything to update the Cygwin product on my desktop during this time. > > xterm handles these three cases differently: > > xterm > xterm /bin/zsh > xterm -e /bin/zsh > > The bug that I mentioned is in the second case - not in the other two. Thanks. That was the bug I hit on my laptop. However, my desktop PC was working fine with "xterm ... /bin/zsh -l" and then suddenly, it started getting the same error. I made the same change to it as I did on my laptop PC and it worked, so I'm not stopped - I'm just wondering how my desktop PC was working then suddenly stopped working without altering any of the Cygwin software or settings. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From meh@Winfirst.Com Sun Mar 16 18:48:00 2014 From: meh@Winfirst.Com (Mark Hansen) Date: Sun, 16 Mar 2014 18:48:00 -0000 Subject: Problem launching XTerm on new Cygwin installation In-Reply-To: <531A24A0.7010400@winfirst.com> References: <531A24A0.7010400@winfirst.com> Message-ID: <5325F1F9.4050409@Winfirst.Com> On 3/7/2014 11:57 AM, Mark Hansen wrote: > I just installed the 64-bit version of Cygwin on both a desktop PC and a laptop PC. > On the desktop, everything worked as expected without problems. On the laptop, I > have the following problems: > > When I launch a shell window, I get the following error: > > Your group is currently "mkgroup". This indicates that neither your gid nor your pgsid is in /etc/group. > I just installed the 64-bit version of Cygwin to another 64-bit Windows 7 PC, and it did not have this problem. After the installation was finished, my user was configured in the /etc/passwd file and did not have the "mkgroup" group. Instead, it was set to 513 (None), which I guess is okay - at least I don't get the error when launching a shell. I don't think I did anything different during the installation other than just getting a later version (I downloaded the software on 3/15/2014). FYI -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From c00jsh00@nchc.narl.org.tw Wed Mar 19 22:25:00 2014 From: c00jsh00@nchc.narl.org.tw (Jyhshyong) Date: Wed, 19 Mar 2014 22:25:00 -0000 Subject: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64 Message-ID: Hi I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that the Xterm in the system tray icon is no longer working. The Xwin server system tray icon has the following target C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe It works fine as the 32-bit version, click on the icon, I can start X server and open a small Xterm window. However, the Xterm system tray icon with the target defined as C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' failed to open an xterm window. The 32 bit version of the Xterm short icon with the target defined as C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' is still working, but only open to the 32-bit Cygwin environment. Any idea on solving this problem? Thanks for any suggestion. Jyhshyong -- Unsubscribe info: http://cygwin.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 meh@Winfirst.Com Wed Mar 19 23:25:00 2014 From: meh@Winfirst.Com (Mark Hansen) Date: Wed, 19 Mar 2014 23:25:00 -0000 Subject: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64 In-Reply-To: References: Message-ID: <532A2778.8030606@Winfirst.Com> On 3/19/2014 3:21 PM, Jyhshyong wrote: > Hi > > I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that > the Xterm in the system tray icon is no longer working. > > The Xwin server system tray icon has the following target > > C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe > > It works fine as the 32-bit version, click on the icon, I can start X > server and open a small Xterm window. > > However, the Xterm system tray icon with the target defined as > > C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - > geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* > -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' > > failed to open an xterm window. > > The 32 bit version of the Xterm short icon with the target defined as > > C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - > geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* > -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' > > is still working, but only open to the 32-bit Cygwin environment. > > Any idea on solving this problem? > > Thanks for any suggestion. > > Jyhshyong > I would start by removing arguments and trying to determine which are causing the problem. Note that (I believe) what shows up in the system try is not the XTerm, but the XServer (XWin). While the XServer is running, you can run a client, like XTerm and it will display on the XServer display. Here is the shortcut I'm using to launch an XTerm under 64-bit cygwin: C:\Apps\cygwin\bin\run.exe -p /usr/X11R6/bin xterm +tb -sb -sl 5000 -display 127.0.0.1:0.0 -ls This is working fine for me. You can also check the /var/log/xwin/XWin.log file to see if there are any errors being written there when you try to launch the XTerm. Good luck. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dickey@his.com Thu Mar 20 00:44:00 2014 From: dickey@his.com (Thomas Dickey) Date: Thu, 20 Mar 2014 00:44:00 -0000 Subject: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64 In-Reply-To: <532A2778.8030606@Winfirst.Com> References: <532A2778.8030606@Winfirst.Com> Message-ID: <20140320004429.GA21301@aerie.jexium-island.net> On Wed, Mar 19, 2014 at 04:25:44PM -0700, Mark Hansen wrote: > On 3/19/2014 3:21 PM, Jyhshyong wrote: > > Hi > > > > I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that > > the Xterm in the system tray icon is no longer working. > > > > The Xwin server system tray icon has the following target > > > > C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe > > > > It works fine as the 32-bit version, click on the icon, I can start X > > server and open a small Xterm window. > > > > However, the Xterm system tray icon with the target defined as > > > > C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - > > geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* > > -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' I don't see anything wrong with the command-line, but it's been a while since I updated Cygwin packages (and I'm not in the middle of a release cycle), so I'll do that to see if it breaks for me. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From cygwin@tlinx.org Thu Mar 20 08:41:00 2014 From: cygwin@tlinx.org (Linda Walsh) Date: Thu, 20 Mar 2014 08:41:00 -0000 Subject: problem with opengl (glxgears) running on cygwin .... Message-ID: <532AA9AD.4070306@tlinx.org> When I try to run glxgears locally, it displays the initial gears, but now they are just frozen. It doesn't work remotely, either, which was what I tried initially. It *used* to work -- remotely at 20-30 frames/second (as measured by fraps). Interestingly enough, I get a glx window, -- fraps will display 30 (the right number for my screen refresh rate), in the right corner of the glxgears window... but the gears don't move. Same effect happens when I try remotely. Window comes up with gears displayed, but no motion. Fraps also shows 30 FPS. When I do glxinfo (with LIBGL_DEBUG=verbose), I get (more below): name of display: :0 display: :0 screen: 0 direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose) server glx vendor string: SGI server glx version string: 1.4 server glx extensions: GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read, GLX_SGI_swap_control client glx vendor string: Mesa Project and SGI client glx version string: 1.4 client glx extensions: GLX_ARB_create_context, GLX_ARB_create_context_profile, GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_create_context_es2_profile, GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_make_current_read, GLX_SGI_swap_control, GLX_SGI_video_sync GLX version: 1.4 GLX extensions: GLX_ARB_get_proc_address, GLX_ARB_multisample, GLX_EXT_import_context, GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_MESA_copy_sub_buffer, GLX_MESA_multithread_makecurrent, GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer, GLX_SGI_make_current_read, GLX_SGI_swap_control OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 590/PCIe/SSE2 OpenGL version string: 1.4 (4.4.0) OpenGL extensions: GL_ARB_depth_texture, GL_ARB_draw_buffers, GL_ARB_fragment_program, GL_ARB_fragment_program_shadow, GL_ARB_framebuffer_object, GL_ARB_imaging, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_point_parameters, GL_ARB_point_sprite, GL_ARB_shadow, GL_ARB_texture_border_clamp, GL_ARB_texture_compression, GL_ARB_texture_cube_map, GL_ARB_texture_env_add, GL_ARB_texture_env_combine, GL_ARB_texture_env_crossbar, GL_ARB_texture_env_dot3, GL_ARB_texture_mirrored_repeat, GL_ARB_texture_non_power_of_two, GL_ARB_texture_rectangle, GL_ARB_texture_rg, GL_ARB_transpose_matrix, GL_ARB_vertex_program, GL_ARB_window_pos, GL_ATI_draw_buffers, GL_ATI_texture_float, GL_ATI_texture_mirror_once, GL_EXT_abgr, GL_EXT_bgra, GL_EXT_blend_color, GL_EXT_blend_equation_separate, GL_EXT_blend_func_separate, GL_EXT_blend_minmax, GL_EXT_blend_subtract, GL_EXT_draw_range_elements, GL_EXT_fog_coord, GL_EXT_framebuffer_blit, GL_EXT_framebuffer_multisample, GL_EXT_framebuffer_object, GL_EXT_framebuffer_sRGB, GL_EXT_multi_draw_arrays, GL_EXT_packed_depth_stencil, GL_EXT_packed_pixels, GL_EXT_point_parameters, GL_EXT_rescale_normal, GL_EXT_secondary_color, GL_EXT_separate_specular_color, GL_EXT_shadow_funcs, GL_EXT_stencil_two_side, GL_EXT_stencil_wrap, GL_EXT_texture3D, GL_EXT_texture_compression_dxt1, GL_EXT_texture_compression_s3tc, GL_EXT_texture_edge_clamp, GL_EXT_texture_env_add, GL_EXT_texture_env_combine, GL_EXT_texture_env_dot3, GL_EXT_texture_filter_anisotropic, GL_EXT_texture_lod, GL_EXT_texture_lod_bias, GL_EXT_texture_mirror_clamp, GL_EXT_texture_object, GL_EXT_texture_rectangle, GL_EXT_vertex_array, GL_IBM_rasterpos_clip, GL_IBM_texture_mirrored_repeat, GL_INGR_blend_func_separate, GL_NV_blend_square, GL_NV_copy_depth_to_color, GL_NV_depth_clamp, GL_NV_fog_distance, GL_NV_fragment_program, GL_NV_fragment_program2, GL_NV_fragment_program_option, GL_NV_light_max_exponent, GL_NV_multisample_filter_hint, GL_NV_packed_depth_stencil, GL_NV_point_sprite, GL_NV_texgen_reflection, GL_NV_texture_compression_vtc, GL_NV_texture_env_combine4, GL_NV_texture_rectangle, GL_NV_vertex_program, GL_NV_vertex_program1_1, GL_NV_vertex_program2, GL_NV_vertex_program2_option, GL_NV_vertex_program3, GL_SGIS_generate_mipmap, GL_SGIS_texture_border_clamp, GL_SGIS_texture_edge_clamp, GL_SGIS_texture_lod, GL_SGIX_depth_texture, GL_SGIX_shadow, GL_SUN_multi_draw_arrays, GL_SUN_slice_accum 98 GLX Visuals visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x021 24 tc 0 32 0 r y . 8 8 8 8 . . 4 24 8 16 16 16 16 0 0 None ....a bunch of lines.... 323 GLXFBConfigs: visual x bf lv rg d st colorbuffer sr ax dp st accumbuffer ms cav id dep cl sp sz l ci b ro r g b a F gb bf th cl r g b a ns b eat ---------------------------------------------------------------------------- 0x042 24 tc 0 32 0 r . . 8 8 8 0 . . 4 24 0 16 16 16 16 0 0 None ...a bunch more lines... ------------------------------------- When I try remote display, the above is pretty much the same except I get an error on the client system that it can't load the 3d swrast.so driver on the other end. But it sees pretty much the same capabilities -- FWIW, there is next to zilch network traffic happening when I try this.. I mean while it is happening. Before and after ~ 200-400KB/s (xosview), during, all my X windows become very slow and no longer refresh steadily. Network throughput registers a drop to 1-80KB/s. Despite that -- xwin pegs a cpu @100% and stays that way until I exit glxgears. xwin log is below... Any ideas? > more /var/log/xwin/XWin.0.log Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.0.0 OS: CYGWIN_NT-6.1 Athenae 1.7.28(0.271/5/3) 2014-02-09 21:06 x86_64 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601](Win64) Package: version 1.15.0-3 built 2014-02-25 XWin was started with the following command line: /usr/bin/XWin -dpi 120 -nomultimonitors -clipboard -ac -unixkill -nowinkill +bs -fp /windows/fonts,built-ins,/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/100dpi -multiwindow ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 2560 h 1600 winInitializeScreenDefaults - native DPI x 120 y 120 [ 86222.282] Initializing built-in extension Generic Event Extension [ 86222.282] Initializing built-in extension SHAPE [ 86222.282] Initializing built-in extension MIT-SHM [ 86222.282] Initializing built-in extension XInputExtension [ 86222.282] Initializing built-in extension XTEST [ 86222.282] Initializing built-in extension BIG-REQUESTS [ 86222.282] Initializing built-in extension SYNC [ 86222.282] Initializing built-in extension XKEYBOARD [ 86222.282] Initializing built-in extension XC-MISC [ 86222.282] Initializing built-in extension XINERAMA [ 86222.282] Initializing built-in extension XFIXES [ 86222.282] Initializing built-in extension XFree86-Bigfont [ 86222.282] Initializing built-in extension RENDER [ 86222.282] Initializing built-in extension RANDR [ 86222.282] Initializing built-in extension COMPOSITE [ 86222.282] Initializing built-in extension DAMAGE [ 86222.282] Initializing built-in extension MIT-SCREEN-SAVER [ 86222.282] Initializing built-in extension DOUBLE-BUFFER [ 86222.282] Initializing built-in extension RECORD [ 86222.282] Initializing built-in extension DPMS [ 86222.282] Initializing built-in extension Present [ 86222.282] Initializing built-in extension X-Resource [ 86222.282] Initializing built-in extension GLX [ 86222.282] (II) xorg.conf is not supported [ 86222.282] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 86222.282] (++) FontPath set to "/windows/fonts,built-ins,/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/100dpi" [ 86222.282] LoadPreferences: Loading /Users/law.Bliss/.XWinrc [ 86222.282] LoadPreferences: Done parsing the configuration file... [ 86222.329] winDetectSupportedEngines - DirectDraw installed, allowing ShadowDD[ 86222.329] winDetectSupportedEngines - Windows NT, allowing PrimaryDD [ 86222.329] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 86222.345] winDetectSupportedEngines - Returning, supported engines 0000001f [ 86222.345] winSetEngine - Multi Window or Rootless => ShadowGDI [ 86222.345] winScreenInit - Using Windows display depth of 32 bits per pixel [ 86222.345] winAllocateFBShadowGDI - Creating DIB with width: 2560 height: 1600 depth: 32 [ 86222.345] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [ 86222.345] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [ 86222.345] winInitMultiWindowWM - Calling pthread_mutex_lock () [ 86222.345] winMultiWindowXMsgProc - Calling pthread_mutex_lock () [ 86222.360] MIT-SHM extension disabled due to lack of kernel support [ 86222.360] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 86222.376] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' [ 86222.532] GL_VERSION: 4.4.0 [ 86222.532] GL_VENDOR: NVIDIA Corporation [ 86222.532] GL_RENDERER: GeForce GTX 590/PCIe/SSE2 [ 86222.532] (II) AIGLX: enabled GLX_SGI_make_current_read [ 86222.532] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 86222.532] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 86222.532] (II) AIGLX: enabled GLX_SGIX_pbuffer [ 86222.532] (II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample [ 86222.532] (II) 482 pixel formats reported by wglGetPixelFormatAttribivARB [ 86222.548] (II) AIGLX: Set GLX version to 1.4 [ 86222.548] (II) 323 fbConfigs [ 86222.548] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 86222.548] [dix] Could not init font path element /windows/fonts, removing from list! [ 86222.641] winPointerWarpCursor - Discarding first warp: 1280 800 [ 86222.641] (--) 5 mouse buttons found [ 86222.641] (--) Setting autorepeat to delay=250, rate=31 [ 86222.641] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [ 86222.641] (--) Found matching XKB configuration "English (USA)" [ 86222.641] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 86222.641] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 86222.641] winBlockHandler - pthread_mutex_unlock() [ 86222.641] winInitMultiWindowWM - pthread_mutex_lock () returned. [ 86222.641] winInitMultiWindowWM - pthread_mutex_unlock () returned. [ 86222.641] winMultiWindowXMsgProc - pthread_mutex_lock () returned. [ 86222.641] winInitMultiWindowWM - DISPLAY=:0.0 [ 86222.641] winMultiWindowXMsgProc - pthread_mutex_unlock () returned. [ 86222.641] winMultiWindowXMsgProc - DISPLAY=:0.0 [ 86222.641] winProcEstablishConnection - winInitClipboard returned. [ 86222.641] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [ 86222.641] winClipboardThreadProc - DISPLAY=:0.0 [ 86222.641] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [ 86222.657] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 86226.307] winXCursorToHCURSOR - Windows requires 32x32 cursor but X requires 48x48 [105011.433] winGetWindowInfo: forcing window to exist [105060.901] winGetWindowInfo: forcing window to exist [105079.449] winGetWindowInfo: forcing window to exist [105120.322] winGetWindowInfo: forcing window to exist [105130.040] winGetWindowInfo: forcing window to exist [105136.608] winGetWindowInfo: forcing window to exist [105264.201] winGetWindowInfo: forcing window to exist [105296.509] winGetWindowInfo: forcing window to exist [105312.671] winGetWindowInfo: forcing window to exist -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From dickey@his.com Thu Mar 20 23:22:00 2014 From: dickey@his.com (Thomas Dickey) Date: Thu, 20 Mar 2014 23:22:00 -0000 Subject: Problem of Starting Xterm using the System Tray Icon for Xterm for Cygwin64 In-Reply-To: <20140320004429.GA21301@aerie.jexium-island.net> References: <532A2778.8030606@Winfirst.Com> <20140320004429.GA21301@aerie.jexium-island.net> Message-ID: <20140320232047.GA4326@aerie.jexium-island.net> On Wed, Mar 19, 2014 at 08:44:29PM -0400, Thomas Dickey wrote: > On Wed, Mar 19, 2014 at 04:25:44PM -0700, Mark Hansen wrote: > > On 3/19/2014 3:21 PM, Jyhshyong wrote: > > > Hi > > > > > > I just installed Cygwin 64 on my 64-bit Cygein 64 PC, and found that > > > the Xterm in the system tray icon is no longer working. > > > > > > The Xwin server system tray icon has the following target > > > > > > C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe > > > > > > It works fine as the 32-bit version, click on the icon, I can start X > > > server and open a small Xterm window. > > > > > > However, the Xterm system tray icon with the target defined as > > > > > > C:\cygwin64\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/xterm -sl 1000 - > > > geometry 120x40 -fn -adobe-courier-bold-r-normal-*-18-*-*-*-*-*-iso8859-* > > > -sb -rightbar -fg black -bg white -display 127.0.0.1:0.0' > > I don't see anything wrong with the command-line, but it's been a while > since I updated Cygwin packages (and I'm not in the middle of a release > cycle), so I'll do that to see if it breaks for me. hmm: a) I'm uncertain how to configure the system tray to match the reported configuration (a sample .XWinrc might help). b) the latest xterm I find from mirrors is still #302 (should not be a problem with the given command-line). c) xterm comes up on my machine (which is 64-bits). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From info@link-king.org Mon Mar 24 19:17:00 2014 From: info@link-king.org (Kerry Stevens) Date: Mon, 24 Mar 2014 19:17:00 -0000 Subject: Reduce the carbon footprint at your company Message-ID: <20140324191712.D152FD7B692@link-king.org> Hi, Carbon emissions have been the buzz words now for years, but until very recently, very little has happened. Companies use more energy and have a larger carbon footprint than many households put together. We aim to lower the footprint of the human race as a whole. This means that we have to start with the biggest culprits. We want to see a 40% reduction in all types of ?energy wastage? within the UK?s industry. If we don?t do something soon, it will simply be too late. We need you to help. Never print an email unless it?s completely crucial. It starts with your desk, spreads to your office, spills to the company then changes the world. One person can make a difference. Regards Kerry Stevens. -- Unsubscribe info: http://cygwin.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 Mar 25 14:05:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Tue, 25 Mar 2014 14:05:00 -0000 Subject: problem with opengl (glxgears) running on cygwin .... In-Reply-To: <532AA9AD.4070306@tlinx.org> References: <532AA9AD.4070306@tlinx.org> Message-ID: <53318D38.5050409@dronecode.org.uk> On 20/03/2014 08:41, Linda Walsh wrote: > When I try to run glxgears locally, it displays the initial gears, > but now they are just frozen. It doesn't work remotely, either, > which was what I tried initially. It *used* to work -- remotely > at 20-30 frames/second (as measured by fraps). > > Interestingly enough, I get a glx window, -- fraps will display > 30 (the right number for my screen refresh rate), in the right corner > of the glxgears window... but the gears don't move. > > Same effect happens when I try remotely. Window comes up with gears > displayed, but no motion. Fraps also shows 30 FPS. Thanks for pointing out this issue. I think that currently glxgears doesn't work very well with the combination of indirect rendering and vsync-limited buffer swapping, so you are getting 30 fps, but they aren't useful frames. Since [1], glxgears turns at a constant 70 degrees per second. glxSwapBuffers does not block when used with indirect rendering, which means that lots of frames can be rendered almost instantly, with no apparent rotation, since the elapsed time between frames is very small. glxgears is a very basic test that GLX is functioning, and definitely not a benchmark. Real GLX clients should have a better mechanism for ensuring their animation rate doesn't outrun the vsync frequency. If you have any problems with real GLX clients, I would be interested to hear them. [1] http://cgit.freedesktop.org/mesa/demos/commit/src/xdemos/glxgears.c?id=0b19fb0a5c6299baf28e26625e39773846f815b2 > When I try remote display, the above is pretty much the same except > I get an error on the client system that it can't load the 3d swrast.so > driver on the other end. There is some problem with loading the swrast_dri.so renderer on the remote system, so it is falling back to indirect rendering. What is the OS of the remote system? > But it sees pretty much the same capabilities -- FWIW, there is next to zilch > network traffic happening when I try this.. I mean while it is happening. > > Before and after ~ 200-400KB/s (xosview), during, all my X windows become > very slow and no longer refresh steadily. Network throughput registers a drop > to 1-80KB/s. Despite that -- xwin pegs a cpu @100% and stays that way > until I exit glxgears. I think this is because glxgears will send frames as fast as it can, and can saturate the X server. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From cygwin@tlinx.org Tue Mar 25 15:59:00 2014 From: cygwin@tlinx.org (Linda Walsh) Date: Tue, 25 Mar 2014 15:59:00 -0000 Subject: problem with opengl (glxgears) running on cygwin .... In-Reply-To: <53318D38.5050409@dronecode.org.uk> References: <532AA9AD.4070306@tlinx.org> <53318D38.5050409@dronecode.org.uk> Message-ID: <5331A7C7.6020100@tlinx.org> Jon TURNEY wrote: > Since [1], glxgears turns at a constant 70 degrees per second. --- 70 degress/s? How is that important? > > glxSwapBuffers does not block when used with indirect rendering, which means > that lots of frames can be rendered almost instantly, with no apparent > rotation, since the elapsed time between frames is very small. ---- According to the text in the starting window it is rendering at 30FPS. -- I.e. it is sync'ed with my monitor's refresh rate (except for the 1st iteration when it acted unsynced).... ... I.e. in starting window this was displayed: Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh rate. 45623 frames in 6.4 seconds = 7166.903 FPS 834 frames in 27.4 seconds = 30.428 FPS 822 frames in 28.8 seconds = 28.542 FPS ---- With all X-window response degraded (Xserver process was peg'ed@100%cpu), virtually no network traffic -- dropped from a norm of 200-400KB/s down to between 1KB-80KB/s. > glxgears is a very basic test that GLX is functioning, and definitely not a > benchmark. Real GLX clients should have a better mechanism for ensuring their > animation rate doesn't outrun the vsync frequency. ---- I thought it was the most basic. It claims (except for the 1st iteration) that it is not outruning my monitor's refresh rate. > > If you have any problems with real GLX clients, I would be interested to hear > them. ---- I'd be interested in finding any that work and proves that it works locally. While my initial use was to try remote GLX, I reverted to trying it localling -- just to verify it worked as it used to. Thats what brought this on. > What is the OS of the remote system? --- linux (opensuse 13.1). No one else on that list was able to see normal response... some got really sluggish response, others saw no movement or nothing. It was only after I ran glxgears locally that I figured I might also have a problem in Cygwin's X, in addition to any other problem I have w/remote display. > I think this is because glxgears will send frames as fast as it can, and can > saturate the X server. ---- The demo claims to sync at the same rate the monitor is refreshing. i.e -- 30 FPS. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@users.sourceforge.net Thu Mar 27 06:28:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 27 Mar 2014 06:28:00 -0000 Subject: problem with opengl (glxgears) running on cygwin .... In-Reply-To: <53318D38.5050409@dronecode.org.uk> References: <532AA9AD.4070306@tlinx.org> <53318D38.5050409@dronecode.org.uk> Message-ID: <5333C52C.1040602@users.sourceforge.net> On 2014-03-25 09:05, Jon TURNEY wrote: > On 20/03/2014 08:41, Linda Walsh wrote: >> When I try to run glxgears locally, it displays the initial gears, >> but now they are just frozen. It doesn't work remotely, either, >> which was what I tried initially. It *used* to work -- remotely >> at 20-30 frames/second (as measured by fraps). >> >> Interestingly enough, I get a glx window, -- fraps will display >> 30 (the right number for my screen refresh rate), in the right corner >> of the glxgears window... but the gears don't move. > > Thanks for pointing out this issue. > > I think that currently glxgears doesn't work very well with the combination of > indirect rendering and vsync-limited buffer swapping, so you are getting 30 > fps, but they aren't useful frames. This should be fixed in mesa-demos-8.1.0-2. Yaakov Cygwin/X -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@users.sourceforge.net Thu Mar 27 06:29:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 27 Mar 2014 06:29:00 -0000 Subject: [ANNOUNCEMENT] GNOME 3.10 updates Message-ID: The following packages (and their subpackages) have been updated for both arches: * appdata-tools-0.1.7-1 (NEW) * at-spi2-atk-2.10.2-1 * at-spi2-core-2.10.2-1 * atk1.0-2.10.0-1 * cairo-1.12.16-1 * dconf-0.18.0-1 * gcr-3.10.1-1 * gdk-pixbuf2.0-2.30.4-1 * glib2.0-2.38.2-1 * glib2.0-networking-2.38.2-1 * gnome-common-3.10.0-1 * gnome-icon-theme-3.10.0-1 * gnome-keyring-3.10.1-1 * gnome-themes-standard-3.10.0-1 * gobject-introspection-1.38.0-1 * gsettings-desktop-schemas-3.10.1-1 * gstreamer1.0-1.2.3-1 * gstreamer1.0-plugins-base-1.2.3-1 * gstreamer1.0-plugins-good-1.2.3-1 * gtk-doc-1.19-2 * gtk3-3.10.7-1 * gvfs-1.18.3-1 * libgnome-keyring-3.10.1-1 * libgsf-1.14.30-1 * librsvg2-2.40.1-1 * libsecret1-0.16-1 * libsoup2.4-2.44.2-1 * pango1.0-1.36.3-1 * python-gi-3.10.2-1 * vala-0.22.1-1 * yelp-tools-3.10.0-1 * yelp-xsl-3.10.1-1 -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@users.sourceforge.net Thu Mar 27 06:31:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Thu, 27 Mar 2014 06:31:00 -0000 Subject: [ANNOUNCEMENT] Updated: shared-mime-info-1.2-1 Message-ID: The following package has been updated for the Cygwin distribution: *** shared-mime-info-1.2-1 This package provides the FreeDesktop.org MIME type database. This release is an update to the latest upstream version, with a few patches: * do not offer to open a ODF file with an archive program (e.g. ark/engrampa/file-roller). * the default action of EXEs is now "Run" (execute as a native binary) instead of "Open With..." -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From cygwin@tlinx.org Thu Mar 27 07:33:00 2014 From: cygwin@tlinx.org (Linda Walsh) Date: Thu, 27 Mar 2014 07:33:00 -0000 Subject: remote desktop /session bus woes...(was Re: problem with opengl (glxgears) running on cygwin ....) In-Reply-To: <5333C52C.1040602@users.sourceforge.net> References: <532AA9AD.4070306@tlinx.org> <53318D38.5050409@dronecode.org.uk> <5333C52C.1040602@users.sourceforge.net> Message-ID: <5333D453.2060409@tlinx.org> Yaakov (Cygwin/X) wrote: > On 2014-03-25 09:05, Jon TURNEY wrote: >> On 20/03/2014 08:41, Linda Walsh wrote: >>> When I try to run glxgears locally, it displays the initial gears, >>> but now they are just frozen. It doesn't work remotely, either, >>> which was what I tried initially. It *used* to work -- remotely >>> at 20-30 frames/second (as measured by fraps). >>> >>> Interestingly enough, I get a glx window, -- fraps will display >>> 30 (the right number for my screen refresh rate), in the right corner >>> of the glxgears window... but the gears don't move. >> >> Thanks for pointing out this issue. >> >> I think that currently glxgears doesn't work very well with the >> combination of >> indirect rendering and vsync-limited buffer swapping, so you are >> getting 30 >> fps, but they aren't useful frames. > > This should be fixed in mesa-demos-8.1.0-2. ---- FWIW, I tried another X server...VcXsrv?... Same with that program. I tried several, got some that worked, most didn't. Of the few that worked 'well' remotely, they were variations on the glgears... got about 400-500 FPS -- and about low 300's MB/s in bandwidth consumed... that sounds about right... but I think there are other problem in trying to get a remote desktop to work now... everything wants to connect to the session bus -- and many progs won't start if they can't. So if I can't figure out a way to get that to work, remote usage is left at a fairly primitive level despite the high frame rates on a 3"x4" window... ;-) One of the demo progs said it required opengl 2.1 .. my card has V4.something. well above 2.1, so that seems like another latent problem. Will look for the fixed version ... thanks for the news... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Thu Mar 27 21:52:00 2014 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Thu, 27 Mar 2014 21:52:00 -0000 Subject: [ANNOUNCEMENT] Updated: xorg-server-1.15.0-4 Message-ID: The following packages have been updated in the Cygwin distribution: *** xorg-server-*1.15.0-4 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.15.0-3: * Improve mapping of no-decoration MOTIF hint to remove system menu controls (This avoids a problem with fbpanel fighting the WM if it is minimized, causing it to spin) * Remove decorations and system menu controls from _NET_WM_WINDOW_TYPE_SPLASH type windows (e.g. GIMP splash screen) * Fix a regression introduced in 1.15.0-1 with Xephyr initial window sizing (fd.o bug #74849) x86: e605c0fb8d88d5b9a487ae6a1cf00237 *xorg-server-1.15.0-4-src.tar.xz d12e033678dcafde281f79b7501e587a *xorg-server-1.15.0-4.tar.xz d99e85f5cc4eaeb85c5480344d1c442b *xorg-server-common-1.15.0-4.tar.xz 2c334080fb5096ef4dd35fd75b996fe8 *xorg-server-debuginfo-1.15.0-4.tar.xz 3c7aed02c28caff4a537a95833b77836 *xorg-server-devel-1.15.0-4.tar.xz 84aeffd498d851dc8d1e4aad5dbeaa81 *xorg-server-dmx-1.15.0-4.tar.xz 1d19e543c3c0300d5cbb2e9d8031519b *xorg-server-extra-1.15.0-4.tar.xz 7824e7c0c493466804402658bbee0c63 *xwinclip-1.15.0-4.tar.xz x86_64: a5263742d75b2a09193a6eb184b63fe0 *xorg-server-1.15.0-4-src.tar.xz e5cad2b04a1156b65049ded9b968f1f5 *xorg-server-1.15.0-4.tar.xz 20467393505b8a5b6f8d15183d563e0c *xorg-server-common-1.15.0-4.tar.xz d12431ffa174028b8fdff7c9f132938d *xorg-server-debuginfo-1.15.0-4.tar.xz c5bece08ce1435a2b14cb356ebe5bc24 *xorg-server-devel-1.15.0-4.tar.xz 1b483964cc7196bb6f66c9097b3908b5 *xorg-server-dmx-1.15.0-4.tar.xz e0c6816c143b06cb08792461bd98ffed *xorg-server-extra-1.15.0-4.tar.xz 244ec52ab31578aa2c4f1e7b7ca89361 *xwinclip-1.15.0-4.tar.xz -- Unsubscribe info: http://cygwin.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 Mar 31 08:31:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Mon, 31 Mar 2014 08:31:00 -0000 Subject: [ANNOUNCEMENT] New: GTKmm C++ bindings Message-ID: The following packages have been added to the Cygwin distribution: * libatkmm1.6_1-2.22.7-1 * libatkmm1.6-devel-2.22.7-1 * libatkmm1.6-doc-2.22.7-1 * libcairomm1.0_1-1.10.0-2 * libcairomm1.0-devel-1.10.0-2 * libcairomm1.0-doc-1.10.0-2 * libgconfmm2.6_1-2.28.2-2 * libgconfmm2.6-devel-2.28.2-2 * libgconfmm2.6-doc-2.28.2-2 * libglademm2.4_1-2.6.7-11 * libglademm2.4-devel-2.6.7-11 * libglademm2.4-doc-2.6.7-11 * libglibmm2.4_1-2.38.1-1 * libglibmm2.4-devel-2.38.1-1 * libglibmm2.4-doc-2.38.1-1 * libgtkmm2.4_1-2.24.4-1 * libgtkmm2.4-devel-2.24.4-1 * libgtkmm2.4-doc-2.24.4-1 * libgtkmm3.0_1-3.10.1-1 * libgtkmm3.0-devel-3.10.1-1 * libgtkmm3.0-doc-3.10.1-1 * libpangomm1.4_1-2.34.0-1 * libpangomm1.4-devel-2.34.0-1 * libpangomm1.4-doc-2.34.0-1 gtkmm provides the official C++ bindings for the GTK+ GUI toolkit (both 2.x and 3.x versions) and other GNOME libraries. -- Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO ====================================== If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the "List-Unsubscribe: " tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain.com@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@users.sourceforge.net Mon Mar 31 08:46:00 2014 From: yselkowitz@users.sourceforge.net (Yaakov (Cygwin/X)) Date: Mon, 31 Mar 2014 08:46:00 -0000 Subject: [ANNOUNCEMENT] Updated: gtk3-3.10.7-2 Message-ID: The following packages have been updated in the Cygwin distribution: * libgtk3_0-3.10.7-2 * libgtk3-devel-3.10.7-2 * libgtk3-doc-3.10.7-2 * libgailutil3_0-3.10.7-2 * libgailutil3-devel-3.10.7-2 * libgailutil3-doc-3.10.7-2 * girepository-Gtk3.0-3.10.7-2 * gtk3-demo-3.10.7-2 * gtk-update-icon-cache-3.10.7-2 GTK+ is a multi-platform toolkit for creating graphical user interfaces. Offering a complete set of widgets, GTK+ is suitable for projects ranging from small one-off projects to complete application suites. This release includes two patches: * Reverse upstream change which caused the gtk-toolbar-style and gtk-toolbar-icon-size user settings to be ignored. * Make the GDK Broadway HTML5 backend work correctly by default. -- 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/