From schilpfamily@gmail.com Fri Jan 2 20:11:00 2015 From: schilpfamily@gmail.com (schilpfamily) Date: Fri, 02 Jan 2015 20:11:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 Message-ID: i have been running cygwin/x for a long time. i was on 1.14.4 and decided to upgrade to 1.16.3. the problem is that i am unable to start an xterm from a dos prompt. i have been using the following command line for years now: D:\cygwin\bin\run.exe -p /bin bash ~/scripts/xtermLaptop the contents of xtermLaptop are: #!/usr/bin/env bash export DISPLAY=127.0.0.1:0.0 xterm -geometry 80x75 -sb -rightbar & exit this has worked for years, now when i run this command, a window very briefly blinks into existence but then goes away. any idea why this would stop working now? -- Unsubscribe info: http://cygwin.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 laurens@blankersfamily.com Fri Jan 2 20:21:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Fri, 02 Jan 2015 20:21:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: References: Message-ID: <54A6FDB8.9070106@blankersfamily.com> On 2-1-2015 21:10, schilpfamily wrote: > this has worked for years, now when i run this command, a window very > briefly blinks into existence but then goes away. any idea why this > would stop working now? This is most likely due to a major rewrite of the xinit package which contains all start-up scripts. If you downgrade the xinit package from 1.3.4-1 to 1.3.2-1 does your setup work again? Here is how you downgrade: 1. Start the Cygwin installer 2. Select the appropriate mirror and directories 3. In the package selection screen search for 'xinit' 4. Select the one from the 'X11' category and click on the version until it cycles to 1.3.2-1 in stead of 1.3.4-1. 5. Click Next and install If this does solve your problem you may want to read my request to the maintainers: https://cygwin.com/ml/cygwin-xfree/2014-12/msg00060.html Laurens -- Unsubscribe info: http://cygwin.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 schilpfamily@gmail.com Fri Jan 2 20:35:00 2015 From: schilpfamily@gmail.com (schilpfamily) Date: Fri, 02 Jan 2015 20:35:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54A6FDB8.9070106@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> Message-ID: rolling back to 1.3.2-1 fixed it. thank you very much for this, i was really pulling my hair out on this. i read your request to the maintainers and fully agree. while i only brought up this one bug, since it was basically making cygwin/x useless, there were other issues that made it annoying. thanks again. bill On Fri, Jan 2, 2015 at 3:21 PM, Laurens Blankers wrote: > On 2-1-2015 21:10, schilpfamily wrote: >> this has worked for years, now when i run this command, a window very >> briefly blinks into existence but then goes away. any idea why this >> would stop working now? > This is most likely due to a major rewrite of the xinit package which > contains all start-up scripts. > > If you downgrade the xinit package from 1.3.4-1 to 1.3.2-1 does your > setup work again? Here is how you downgrade: > > 1. Start the Cygwin installer > 2. Select the appropriate mirror and directories > 3. In the package selection screen search for 'xinit' > 4. Select the one from the 'X11' category and click on the version until > it cycles to 1.3.2-1 in stead of 1.3.4-1. > 5. Click Next and install > > If this does solve your problem you may want to read my request to the > maintainers: > > https://cygwin.com/ml/cygwin-xfree/2014-12/msg00060.html > > Laurens > > -- > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html > Documentation: http://x.cygwin.com/docs/ > FAQ: http://x.cygwin.com/docs/faq/ > -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From reply-to-list-only-lh@cygwin.com Sat Jan 3 03:49:00 2015 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Sat, 03 Jan 2015 03:49:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: References: <54A6FDB8.9070106@blankersfamily.com> Message-ID: <54A766A7.7020609@cygwin.com> On 01/02/2015 03:35 PM, schilpfamily wrote: > rolling back to 1.3.2-1 fixed it. thank you very much for this, i was > really pulling my hair out on this. i read your request to the > maintainers and fully agree. while i only brought up this one bug, > since it was basically making cygwin/x useless, there were other > issues that made it annoying. Certainly it is good feedback to know that the issue you were seeing is related to the new version of xinit. I would encourage you and others that see issues with the latest release to report the problems (as you have) and to try the solutions offered in the cygwin-xfree mailing list discussions from the last couple of months. If there are technical issues with those solutions, they need to be reported as well. Obviously, the key thing here is to figure out how to make this transition smoother, so the more useful feedback there is, the better. Downgrading may be a practical short-term solution to the problems you're having at the moment and that's fine. But the functionality in the latest release of the xinit corrects some long-standing Cygwin incompatibilities with startx, so there's no benefit to turning back as a strategy. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From laurens@blankersfamily.com Sat Jan 3 08:04:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Sat, 03 Jan 2015 08:04:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54A766A7.7020609@cygwin.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> Message-ID: <54A7A26E.7090801@blankersfamily.com> On 3-1-2015 04:48, Larry Hall (Cygwin-X) wrote: > But the functionality in the latest release of the xinit corrects some > long-standing Cygwin incompatibilities with startx, so there's > no benefit to turning back as a strategy. This is exactly why I have such hard time convincing people that using open source software is a good idea: "The solution is technically better, so if it breaks for you I don't care." I am not arguing that the solution should be discarded, I am arguing that the way the transition was handled, or not handled actually, it not worthy of being called engineering, development, or even programming. The best, and actually only way to move forward is to revert back to the behaviour of 1.3.2-1 and rethink this whole approach. Once a good transition plan is in place the changes can be reapplied. But it is obvious that I won't find a sympathetic ear to the plight of the user here, so I will escalate this to the main Cygwin mailing list. Hopefully people their actually care about user experience. Laurens -- Unsubscribe info: http://cygwin.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 rcunningham@ucsd.edu Sat Jan 3 09:25:00 2015 From: rcunningham@ucsd.edu (rcunningham@ucsd.edu) Date: Sat, 03 Jan 2015 09:25:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54A7A26E.7090801@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> Message-ID: <83E13E19-3E7A-446B-82DB-A331A2F84D43@ucsd.edu> On January 3, 2015 12:03:58 AM PST, Laurens Blankers wrote: >I am not arguing that the solution should be discarded, I am arguing >that the way the transition was handled, or not handled actually, it >not >worthy of being called engineering, development, or even programming. Strong words, but absolutely correct. Transitions affecting the user experience should be gradual, not violent. This was an unnecessarily violent transition with much breakage. Revert, replan, redeploy. -BobC -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From reply-to-list-only-lh@cygwin.com Sat Jan 3 23:02:00 2015 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Sat, 03 Jan 2015 23:02:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54A7A26E.7090801@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> Message-ID: <54A874F1.8000203@cygwin.com> On 01/03/2015 03:03 AM, Laurens Blankers wrote: > On 3-1-2015 04:48, Larry Hall (Cygwin-X) wrote: >> But the functionality in the latest release of the xinit corrects some >> long-standing Cygwin incompatibilities with startx, so there's >> no benefit to turning back as a strategy. > This is exactly why I have such hard time convincing people that using > open source software is a good idea: "The solution is technically > better, so if it breaks for you I don't care." Interesting that you should gather that from my comments, since I never said I don't care nor do I believe that the maintainer doesn't care. Seems to me like you're attributing perceptions you've gathered from other people and interactions in your life to me. Please don't do that. My point, which I will reiterate again because I think it received overtones I wasn't conveying the first time, is that the changes made are indeed needed and beneficial in general. You can find evidence of this in the email archives. Removing the newly introduced changes means these other folks that expect Cygwin's X to work like it does on Linux and other platforms will continue to be surprised, etc. The fact that the recent changes interfere with previous usage is an issue that needs attention for sure but reverting, while the maintainer's call, just trades misbehaviour in the eyes of one group for that of the other. And the individual is always free to revert the package version in the short-term to address any immediate need. So with the short-term bases covered, it makes sense to move forward by looking and going forward. I encourage those that want to smooth the transition to help by trying the solutions so far and offering feedback on what works well and what doesn't. This is the way we can reach a solution that addresses the concerns of both groups. > The best, and actually only way to move forward is to revert back to the > behaviour of 1.3.2-1 and rethink this whole approach. Once a good > transition plan is in place the changes can be reapplied. But it is > obvious that I won't find a sympathetic ear to the plight of the user > here, so I will escalate this to the main Cygwin mailing list. Hopefully > people their actually care about user experience. I think your point has been heard. There's no need to take it to another Cygwin list or reiterate it here. Since the issue is related to the changes in the xinit package and this is the list for X issues, you have the right forum if you want to help work towards a smoother transition for existing users with the xinit package. The Cygwin main list is really for everything but X. Talking about X things there will likely get you redirected back to this list. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From laurens@blankersfamily.com Sun Jan 4 11:41:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Sun, 04 Jan 2015 11:41:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54A874F1.8000203@cygwin.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> Message-ID: <54A926F9.4090902@blankersfamily.com> On 2015-01-04 00:02, Larry Hall (Cygwin-X) wrote: > The fact that the recent > changes interfere with previous usage is an issue that needs attention > for > sure but reverting, while the maintainer's call, just trades misbehaviour > in the eyes of one group for that of the other. That may be true, but you are prioritizing new users over your existing user base here. There are many many users out there for which the behaviour as exhibited by 1.3.2-1 has worked for many years. Behaviour which is now broken, without even the slightest hint of what is going on! And without a way to get all the functionality back, even with changes! > I encourage those that want > to smooth the transition to help by trying the solutions so far and > offering feedback on what works well and what doesn't. This is the > way we > can reach a solution that addresses the concerns of both groups. I would like to help smoothing the transition, however not by forcing changes down peoples throats and then saying may be when can make this better some time in the future. If you want my help, do the right thing, acknowledge that the way of handling this was wrong. Revert the changes. And solicit the help of the people on this mailing list to come up with a well designed, well tested, and well documented solution. > I think your point has been heard. There's no need to take it to another > Cygwin list or reiterate it here. I don't think so. You maintain that the approach chosen was the right one. I think the saying in English is "It Takes a Real Man to Admit when He's Wrong". I am sorry, I can't help you if you keep maintaining nothing went wrong. Laurens -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From reply-to-list-only-lh@cygwin.com Mon Jan 5 04:04:00 2015 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Mon, 05 Jan 2015 04:04:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54A926F9.4090902@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> <54A926F9.4090902@blankersfamily.com> Message-ID: <54AA0D4D.2030803@cygwin.com> On 01/04/2015 06:41 AM, Laurens Blankers wrote: > On 2015-01-04 00:02, Larry Hall (Cygwin-X) wrote: >> The fact that the recent >> changes interfere with previous usage is an issue that needs attention for >> sure but reverting, while the maintainer's call, just trades misbehaviour >> in the eyes of one group for that of the other. > That may be true, but you are prioritizing new users over your existing user > base here. There are many many users out there for which the behaviour as > exhibited by 1.3.2-1 has worked for many years. Behaviour which is now > broken, without even the slightest hint of what is going on! And without a > way to get all the functionality back, even with changes! > >> I encourage those that want >> to smooth the transition to help by trying the solutions so far and >> offering feedback on what works well and what doesn't. This is the way we >> can reach a solution that addresses the concerns of both groups. > I would like to help smoothing the transition, however not by forcing > changes down peoples throats and then saying may be when can make this > better some time in the future. > > If you want my help, do the right thing, acknowledge that the way of > handling this was wrong. Revert the changes. And solicit the help of the > people on this mailing list to come up with a well designed, well tested, > and well documented solution. > >> I think your point has been heard. There's no need to take it to another >> Cygwin list or reiterate it here. > I don't think so. You maintain that the approach chosen was the right one. I > think the saying in English is "It Takes a Real Man to Admit when He's > Wrong". I am sorry, I can't help you if you keep maintaining nothing went > wrong. So I'm guessing with your statement above that English isn't your primary language. If true, then perhaps that's why you keep saying I've made statements I didn't make. You say above that I "keep maintaining nothing went wrong." And yet you quoted me in your response saying "The fact that the recent changes interfere with previous usage is an issue that needs attention...." If this is really just a language issue, then I understand but let's try to avoid it in the future. If not, I have to again ask you not to attribute statements you make as ones I have made. If you persist, I won't continue to respond to your thread, assuming there would be any redeeming value to continuing this thread at this point. OK, let me try to be as clear as possible: 1. I am not the maintainer of the xinit package. That is Yaakov Selkowitz. You can see this by his announcement of the latest version. So when I say that how the upgrade of the xinit is handled is up to the maintainer, I mean it is up to Yaakov, not me. 2. Yaakov is a very capable and prolific contributor to the Cygwin project and has been for many years. Because of his many hats and tasks, others (including me), from time to time, try to help people with issues they see, even if the package or packages in question are maintained by someone else (and this is the case with xinit as I mentioned above). 3. There have been a number of related issues that have popped up relative to the latest version of xinit. I've listed quite a few entry points to the relevant threads. You'll notice that sometimes Yaakov is answering the question raised and other times others are doing it. That's standard operating procedure. When I mentioned above that you or others can help out by pointing out where the solutions proposed fall short, I wa referring to the solutions offered in the threads above, in case it wasn't clear to anyone. I gather from your comments in that the only issue that you're aware of that isn't addressed by the solutions offered so far is the one about the icon showing in the task bar rather than the tray. If you or others know of other issues, that would be useful to report. 4. I realize that you have a policy issue that you raised as a result of your xinit upgrade experience, which you posted about in and have subsequently taken to the Cygwin main list . The policy question of managing package updates, I submit, is separate from getting current installations running after the xinit 1.3.4-1 upgrade, since this update is already here and for all the reasons I've stated previously. So I withdraw my previous request that you not post your policy question to the Cygwin main list (since I agree it is a general issue) but instead request that you only discuss the policy and not overlap with the specifics covered in the xinit package threads, since that will take it into X-land which takes it off-topic on the main list. -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From laurens@blankersfamily.com Mon Jan 5 09:07:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Mon, 05 Jan 2015 09:07:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54AA0D4D.2030803@cygwin.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> <54A926F9.4090902@blankersfamily.com> <54AA0D4D.2030803@cygwin.com> Message-ID: <54AA5429.1090907@blankersfamily.com> On 5-1-2015 05:04, Larry Hall (Cygwin-X) wrote: > So I'm guessing with your statement above that English isn't your primary > language. > [..] > 1. I am not the maintainer of the xinit package. [..] English is indeed not my first language, but that is no excuse for not carefully reading your replies and not verifying assumptions about you being a maintainer. I did not read your replies carefully enough and did not check my assumptions. Please accept my apologies. > [..] > 2. Yaakov is a very capable and prolific contributor to the Cygwin project > and has been for many years. [..] I do appreciate your (yours, Yaakov's, and others) efforts very much. I tried to express that in the last paragraph of my original mail [1]. Please tell me if this intent did not come across or was drowned somehow, so I can phrase it better next time. > [..] > You'll notice that sometimes Yaakov is answering > the question raised and other times others are doing it. That's > standard operating procedure. [..] I did read all the previous questions and answers. I interpreted the focus on having users change their configuration rather than changing the xinit package as a denial of the problem. However, now I see that none of the replies were by the package maintainer. I now realize that you were doing the best you could in helping me and others. > [..] > When I mentioned above that you or others can help out by pointing out > where the solutions proposed fall short [..] As far as I can tell, from the available information, users which meet any of the following criteria will run into trouble: - Custom .startxwinrc or .xinitrc - Using untrusted X11 forwards over SSH (e.g. ssh -X or PuTTY) My assumption is that this covers the vast majority of xinit users. Including these which previously complained about the non-standard way of handling configuration. As a software engineer I strongly believe in the principle of least astonishment [2]. At least for the vast majority of users. In this case, in my opinion at least, that would mean that changing the behaviour of startxwin should be done in such a way as to provide a seamless way of users to upgrade. Preferably by maintaining compatibility with existing configurations, or by automatic conversion, or, if necessary through a well documented manual transition process. What I am trying to say is that I don't object to your solutions, but I would really like this to be solved in a way that provides a create user experience. For me that would mean that the first step would be to retract the update (revert back to 1.3.2-1) as to prevent more users from running into problems. I do realize that that would mean forcing people who have already converted to go back. But I assume this is a minority of users. Then I would propose to evaluate what could be done to provide a smooth transition, possibly over a longer time, popping up increasingly annoying warnings about the configuration, for example. I would like to help with this. I think I can assist in figuring out what kind of configurations are out there, as well as in testing, and in writing documentation. I could even code the solution, but that would probably be more efficient of people with more experience in bash scripting would do that. > [..] > So I withdraw my previous request that you not post > your policy question to the Cygwin main list (since I agree it is a > general issue) but instead request that you only discuss the policy and > not overlap with the specifics covered in the xinit package threads [..] Thank you, I would like to discussion on the general list to be broader. Because, for me, this issue was highlighted by xinit, but is by no means related to it. I, and I assume many others, rely on Cygwin and also assume, possibly incorrectly, that it will continue to function as expected, after applying (security) updates. An incompatible change in any other package would also be problematic for me. The reason I mentioned xinit explicitly is to provide the reader with a background, and as soft of a 'full disclosure' of my involvement. I will also make it very explicit on the common list that the post is not specific to xinit, but that is merely serves as an example. > A: Yes. > > Q: Are you sure? > >> A: Because it reverses the logical flow of conversation. > >>> Q: Why is top posting annoying in email? I really like your signature, do you mind if I borrow/steal it? Laurens [1] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00060.html [2] http://en.wikipedia.org/wiki/Principle_of_least_astonishment -- Unsubscribe info: http://cygwin.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@cygwin.com Mon Jan 5 09:49:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Mon, 05 Jan 2015 09:49:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54AA5429.1090907@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> <54A926F9.4090902@blankersfamily.com> <54AA0D4D.2030803@cygwin.com> <54AA5429.1090907@blankersfamily.com> Message-ID: <54AA5E05.2040600@cygwin.com> On 2015-01-05 03:06, Laurens Blankers wrote: > On 5-1-2015 05:04, Larry Hall (Cygwin-X) wrote: > As far as I can tell, from the available information, users which meet > any of the following criteria will run into trouble: > > - Custom .startxwinrc or .xinitrc Just .startxwinrc, and the changes were explained in the announcement. > - Using untrusted X11 forwards over SSH (e.g. ssh -X or PuTTY) ssh -X hasn't been supported since X11R7.4 way back in 2008 (see the FAQ for details). > As a software engineer I strongly believe in the principle of least > astonishment [2]. At least for the vast majority of users. In this case, > in my opinion at least, that would mean that changing the behaviour of > startxwin should be done in such a way as to provide a seamless way of > users to upgrade. Preferably by maintaining compatibility with existing > configurations, or by automatic conversion, or, if necessary through a > well documented manual transition process. That's what the announcement was for. > What I am trying to say is that I don't object to your solutions, but I > would really like this to be solved in a way that provides a create user > experience. For me that would mean that the first step would be to > retract the update (revert back to 1.3.2-1) as to prevent more users > from running into problems. I do realize that that would mean forcing > people who have already converted to go back. But I assume this is a > minority of users. Then I would propose to evaluate what could be done > to provide a smooth transition, possibly over a longer time, popping up > increasingly annoying warnings about the configuration, for example. I am not going to revert the recent changes, which are important and long overdue. If any has constructive suggestions for incremental improvements thereto, they will be duly considered, but going backwards is not the solution. >> So I withdraw my previous request that you not post >> your policy question to the Cygwin main list (since I agree it is a >> general issue) but instead request that you only discuss the policy and >> not overlap with the specifics covered in the xinit package threads [..] > > Thank you, I would like to discussion on the general list to be broader. That won't be necessary. As a rolling distribution without stable releases, these kind of changes in UX happen from time to time. That's what announcements are for. Yaakov -- Unsubscribe info: http://cygwin.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 laurens@blankersfamily.com Mon Jan 5 10:03:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Mon, 05 Jan 2015 10:03:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54AA5E05.2040600@cygwin.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> <54A926F9.4090902@blankersfamily.com> <54AA0D4D.2030803@cygwin.com> <54AA5429.1090907@blankersfamily.com> <54AA5E05.2040600@cygwin.com> Message-ID: <54AA617B.6050105@blankersfamily.com> On 5-1-2015 10:48, Yaakov Selkowitz wrote: > Just .startxwinrc, and the changes were explained in the announcement. The information is contained within the announcement, but it is a bit difficult to figure out what to do from just the list of changes. A more detailed step-by-step guide, preferably as part of the FAQ would be very much appreciated. > ssh -X hasn't been supported since X11R7.4 way back in 2008 (see the > FAQ for details). I see, but PuTTY which apparently uses insecure forwards has worked for many years all the way up to 1.3.2-1. > That's what the announcement was for. As mentioned above a bit more guidance would be nice. > I am not going to revert the recent changes, which are important and > long overdue. If any has constructive suggestions for incremental > improvements thereto, they will be duly considered, but going > backwards is not the solution. OK, I am a bit disappointed, but I do have some suggestions. How would you prefer I post them? In this thread or a new one? All together or one post per suggestion? > That won't be necessary. As a rolling distribution without stable > releases, these kind of changes in UX happen from time to time. > That's what announcements are for. Are you saying it is inappropriate to discuss or that you personally don't see value in this? Laurens -- Unsubscribe info: http://cygwin.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@cygwin.com Mon Jan 5 10:34:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Mon, 05 Jan 2015 10:34:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54AA617B.6050105@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> <54A926F9.4090902@blankersfamily.com> <54AA0D4D.2030803@cygwin.com> <54AA5429.1090907@blankersfamily.com> <54AA5E05.2040600@cygwin.com> <54AA617B.6050105@blankersfamily.com> Message-ID: <54AA68A2.2080808@cygwin.com> On 2015-01-05 04:03, Laurens Blankers wrote: > On 5-1-2015 10:48, Yaakov Selkowitz wrote: >> Just .startxwinrc, and the changes were explained in the announcement. > The information is contained within the announcement, but it is a bit > difficult to figure out what to do from just the list of changes. A more > detailed step-by-step guide, preferably as part of the FAQ would be very > much appreciated. I can't be everyone's personal IT department. I believe the information in the announcement contains sufficient information for users to make the necessary changes, but the most important part would be the new requirements of ~/.startxwinrc. >> ssh -X hasn't been supported since X11R7.4 way back in 2008 (see the >> FAQ for details). > I see, but PuTTY which apparently uses insecure forwards has worked for > many years all the way up to 1.3.2-1. Then please provide complete details in a separate thread. >> I am not going to revert the recent changes, which are important and >> long overdue. If any has constructive suggestions for incremental >> improvements thereto, they will be duly considered, but going >> backwards is not the solution. > OK, I am a bit disappointed, but I do have some suggestions. How would > you prefer I post them? In this thread or a new one? All together or one > post per suggestion? Please start a new thread. >> That won't be necessary. As a rolling distribution without stable >> releases, these kind of changes in UX happen from time to time. >> That's what announcements are for. > Are you saying it is inappropriate to discuss or that you personally > don't see value in this? There is simply no point. Yaakov -- Unsubscribe info: http://cygwin.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 laurens@blankersfamily.com Mon Jan 5 11:32:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Mon, 05 Jan 2015 11:32:00 -0000 Subject: Can't open display with PuTTY and xinit 1.3.4-1 Message-ID: <54AA7624.1050205@blankersfamily.com> When using PuTTY with X11 forwarding enabled X clients are no longer able to connect to the X server running locally. When reverting back to 1.3.2-1 the problem goes away. This may be related to the -nolisten tcp which is now the default[1]. If this is indeed the case it would be create of adding the '-listen' flag to startxwin could be added to the FAQ. Or another, more secure, solution would also be appreciated. [1] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00024.html Laurens -- Unsubscribe info: http://cygwin.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 laurens@blankersfamily.com Mon Jan 5 11:46:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Mon, 05 Jan 2015 11:46:00 -0000 Subject: Suggestion for improving xinit 1.3.4 Message-ID: <54AA7981.7080805@blankersfamily.com> Hi, As requested [1] a separate thread for suggesting improvements to xinit, in order to solve some of the issues people have been having since the release of 1.3.4-1 [2]. 1. Handling of empty .startxwinrc Given the new behaviour of startxwin having an empty is never a correct configuration. It would be really nice if startxwin could check for a zero length .startxwinrc and in that case just start the X server without any programs, as it used to do in 1.3.2-1. This would solve a problem reported several times [3, 4] and also solve the problem of having an icon on the task bar for 'sleep inf' [5]. 2. Adding a hint about 'sleep inf' to the FAQ Not everyone reads the release notes, most people, when running into problems will read the FAQ first. How about adding an entry similar to this one: Q: startxwin exits immediately on start-up without error A: ~/.startxwinrc must be executable and block or else X server will exist, adding a 'sleep inf' to the end of the file should help, also see [2] 3. Adding 'listen' option to the FAQ Consider adding something similar: Q: X server is no longer accepting client connections, how come? A: For security reasons, by default the X server no longer listen for tcp connections, if you really want this add '-listen' to the start-up parameters. Also see [6]. 4. Semantic versioning Signalling major changes in the version number makes it a lot easier to find the problem, at least for me. Semantic versioning [7] suggest does thing. Practically this would have mend calling the latest release 2.0.0-1 rather than 1.3.4-1. No additional effort required, but a clear signal to people to read the release notes. I hope these suggestions don't require too much work. I think they would have a significant positive impact on UX. Laurens [1] https://cygwin.com/ml/cygwin-xfree/2015-01/msg00012.html [2] https://cygwin.com/ml/cygwin-xfree/2014-11/msg00029.html [3] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00012.html [4] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00013.html [5] https://cygwin.com/ml/cygwin-xfree/2014-12/msg00059.html [6] https://cygwin.com/ml/cygwin-xfree/2015-01/msg00013.html [7] http://semver.org/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@cygwin.com Mon Jan 5 17:31:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Mon, 05 Jan 2015 17:31:00 -0000 Subject: Can't open display with PuTTY and xinit 1.3.4-1 In-Reply-To: <54AA7624.1050205@blankersfamily.com> References: <54AA7624.1050205@blankersfamily.com> Message-ID: <54AACA74.3080201@cygwin.com> On 2015-01-05 05:31, Laurens Blankers wrote: > When using PuTTY with X11 forwarding enabled X clients are no longer > able to connect to the X server running locally. When reverting back to > 1.3.2-1 the problem goes away. > > This may be related to the -nolisten tcp which is now the default[1]. If > this is indeed the case it would be create of adding the '-listen' flag > to startxwin could be added to the FAQ. Or another, more secure, > solution would also be appreciated. Wait, are you talking about a Windows version of PuTTY? Then that makes sense, as it would be unable of using the *NIX socket typically used by local X clients, and I am indeed able to duplicate that behaviour. I can't think of an alternative to -listen if you wish to use a Windows PuTTY (or, for that matter, any MinGW-compiled X client) with Cygwin/X. This will be added to the FAQ in due course. However, a Cygwin PuTTY does not have that limitation, and X11 forwarding works just fine as is. (If there is interest, I can easily add this to the distribution.) Similarly, the Cygwin (open)ssh obviously has no problems with X11 forwarding either. BTW, reverting this behaviour isn't an option either, as it will actually become the upstream default in the next major release of the X server. HTH, Yaakov -- Unsubscribe info: http://cygwin.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@cygwin.com Mon Jan 5 17:43:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Mon, 05 Jan 2015 17:43:00 -0000 Subject: Suggestion for improving xinit 1.3.4 In-Reply-To: <54AA7981.7080805@blankersfamily.com> References: <54AA7981.7080805@blankersfamily.com> Message-ID: <54AACD28.9060407@cygwin.com> On 2015-01-05 05:46, Laurens Blankers wrote: > As requested [1] a separate thread for suggesting improvements to xinit, > in order to solve some of the issues people have been having since the > release of 1.3.4-1 [2]. > > 1. Handling of empty .startxwinrc > Given the new behaviour of startxwin having an empty is never a correct > configuration. It would be really nice if startxwin could check for a > zero length .startxwinrc and in that case just start the X server > without any programs, as it used to do in 1.3.2-1. This would solve a > problem reported several times [3, 4] and also solve the problem of > having an icon on the task bar for 'sleep inf' [5]. And what if it's not zero-length but still blank? > 2. Adding a hint about 'sleep inf' to the FAQ > Not everyone reads the release notes, most people, when running into > problems will read the FAQ first. How about adding an entry similar to > this one: > > Q: startxwin exits immediately on start-up without error > A: ~/.startxwinrc must be executable and block or else X server will > exist, adding a 'sleep inf' to the end of the file should help, also see [2] Yes, something along these lines should be added to the FAQ soon. > 3. Adding 'listen' option to the FAQ See my response to your PuTTY thread. > 4. Semantic versioning > Signalling major changes in the version number makes it a lot easier to > find the problem, at least for me. Semantic versioning [7] suggest does > thing. Practically this would have mend calling the latest release > 2.0.0-1 rather than 1.3.4-1. No additional effort required, but a clear > signal to people to read the release notes. xinit -- the startx and xinit parts -- is an upstream X.Org package, and they determine the package version. The startxwin components are Cygwin-specific additions to the package, as they have been since we first released modular X11R7.4. Therefore, changing the version in this way isn't a viable option here. However, from personal experience, I disagree that a different version number would have made a bit of difference. Either people will read the announcements -- and the subject of mine should have indicated that this wasn't a routing update -- or they won't. -- Yaakov -- Unsubscribe info: http://cygwin.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@cygwin.com Mon Jan 5 18:17:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Mon, 05 Jan 2015 18:17:00 -0000 Subject: Suggestion for improving xinit 1.3.4 In-Reply-To: <54AACD28.9060407@cygwin.com> References: <54AA7981.7080805@blankersfamily.com> <54AACD28.9060407@cygwin.com> Message-ID: <54AAD53C.8050403@cygwin.com> On 2015-01-05 11:43, Yaakov Selkowitz wrote: > On 2015-01-05 05:46, Laurens Blankers wrote: >> As requested [1] a separate thread for suggesting improvements to xinit, >> in order to solve some of the issues people have been having since the >> release of 1.3.4-1 [2]. >> >> 1. Handling of empty .startxwinrc >> Given the new behaviour of startxwin having an empty is never a correct >> configuration. It would be really nice if startxwin could check for a >> zero length .startxwinrc and in that case just start the X server >> without any programs, as it used to do in 1.3.2-1. This would solve a >> problem reported several times [3, 4] and also solve the problem of >> having an icon on the task bar for 'sleep inf' [5]. > > And what if it's not zero-length but still blank? I could have startxwin check if ~/.startxwinrc is executable, and skip if it not, which might also cover many of these empty .startxwinrc's. OTOH all that might accomplish is trade the "why won't it start" for "why doesn't it respect my config". :-) -- Yaakov -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From reply-to-list-only-lh@cygwin.com Tue Jan 6 04:19:00 2015 From: reply-to-list-only-lh@cygwin.com (Larry Hall (Cygwin-X)) Date: Tue, 06 Jan 2015 04:19:00 -0000 Subject: run.exe will not work with upgrade from 1.14.4 to 1.16.3 In-Reply-To: <54AA5429.1090907@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> <54A766A7.7020609@cygwin.com> <54A7A26E.7090801@blankersfamily.com> <54A874F1.8000203@cygwin.com> <54A926F9.4090902@blankersfamily.com> <54AA0D4D.2030803@cygwin.com> <54AA5429.1090907@blankersfamily.com> Message-ID: <54AB624B.5030206@cygwin.com> On 01/05/2015 04:06 AM, Laurens Blankers wrote: Since I believe the rest of what you wrote above has been covered in one form or another since my last reply, I won't bore anyone with my responses. This leaves just one very critical piece of business which absolutely must be addressed: >> >A: Yes. >>> > >Q: Are you sure? >>>> > >>A: Because it reverses the logical flow of conversation. >>>>> > >>>Q: Why is top posting annoying in email? > I really like your signature, do you mind if I borrow/steal it? Of course! I actually "borrowed" it from someone else a few lifetimes ago so it would hardly be sporting of me to deny you equal rights. :-) -- Larry _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From laurens@blankersfamily.com Tue Jan 6 09:12:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Tue, 06 Jan 2015 09:12:00 -0000 Subject: Can't open display with PuTTY and xinit 1.3.4-1 In-Reply-To: <54AACA74.3080201@cygwin.com> References: <54AA7624.1050205@blankersfamily.com> <54AACA74.3080201@cygwin.com> Message-ID: <54ABA706.8030104@blankersfamily.com> On 5-1-2015 18:31, Yaakov Selkowitz wrote: > Wait, are you talking about a Windows version of PuTTY? There is a PuTTY for *nix? And it has been ported to Cygwin? I didn't know. That is, let's say, amazing :-) Yes I mean the native PuTTY for Windows. > This will be added to the FAQ in due course. Thank you. > BTW, reverting this behaviour isn't an option either, as it will > actually become the upstream default in the next major release of the > X server. I am perfectly fine with keeping this behaviour since it is more secure, especially if it becomes the default. An entry in the FAQ is perfect. -- Laurens _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From laurens@blankersfamily.com Tue Jan 6 09:38:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Tue, 06 Jan 2015 09:38:00 -0000 Subject: Suggestion for improving xinit 1.3.4 In-Reply-To: <54AACD28.9060407@cygwin.com> References: <54AA7981.7080805@blankersfamily.com> <54AACD28.9060407@cygwin.com> Message-ID: <54ABACF8.90406@blankersfamily.com> On 5-1-2015 19:17, Yaakov Selkowitz wrote: > On 2015-01-05 11:43, Yaakov Selkowitz wrote: >> On 2015-01-05 05:46, Laurens Blankers wrote: >>> [..] >>> 1. Handling of empty .startxwinrc >>> [..] >> >> And what if it's not zero-length but still blank? > > I could have startxwin check if ~/.startxwinrc is executable, and skip > if it not, which might also cover many of these empty .startxwinrc's. > OTOH all that might accomplish is trade the "why won't it start" for > "why doesn't it respect my config". :-) Nice edge case, well, you could use sed to filter commented lines and white space and determine whether the file is effectively empty. But I guess that might be even more surprising to people who don't expect it. How about this: Handle a missing execution flag on .startxwinrc as if the file was missing, thereby executing the default behaviour. Technically this should be what people expect since they should not expect non executable scripts to be executed. Although people would probably still be confused, but at least X will start and the question people will ask will be "why is my config not working?" rather than "why is X not starting?", which is much easier to handle in a FAQ/mailing list. If you really want to make it fancy you can consider popping up a dialog when .startxwinrc exists but is not executable and referring them to the FAQ (clickable link?!). That would still not solve my use case, in which the .startxwinrc is empty and I expect the X server to start in the background without starting any programs. But may be this is a special case which should be handled separately. Currently the Cygwin-X program group only contains a single item "XWin Server". How would you feel about adding a few more items there may be "XWin Server (background)" and "XWin Server (background, listen)". There shortcuts could execute code similar to the one suggested by Angelo Graziosi [1] basically something like: run.exe /usr/bin/bash.exe -l -c /usr/bin/XWin -multiwindow -clipboard -silent-dup-error -nolisten tcp for the first and run.exe /usr/bin/bash.exe -l -c /usr/bin/XWin -multiwindow -clipboard -silent-dup-error -listen tcp for the second. Not really the *nix approach, but probably what Windows users would expect. I believe this is how Hummingbird Exceed (a commercial X server for Windows) handled it. You could add FAQ items like: Q: How do I start X without any programs or window manager? A: Use "XWin Server (background)" Q: How do I allow PuTTY to connect to X? A: Use "XWin Server (background, listen)", but be aware that this may open a security vulnerability. On 5-1-2015 18:43/19:17, Yaakov Selkowitz wrote: > 4. Semantic versioning >> Signalling major changes in the version number makes it a lot easier to >> find the problem, at least for me. Semantic versioning [7] suggest does >> thing. Practically this would have mend calling the latest release >> 2.0.0-1 rather than 1.3.4-1. No additional effort required, but a clear >> signal to people to read the release notes. > > xinit -- the startx and xinit parts -- is an upstream X.Org package, > and they determine the package version. The startxwin components are > Cygwin-specific additions to the package, as they have been since we > first released modular X11R7.4. Therefore, changing the version in > this way isn't a viable option here. I didn't think about the link with upstream. You are right, using a different versioning scheme as upstream would be even more confusing. Although, technically, since your startxwin script is no longer an adaptation of xinit it qualifies as an original program and could be put in a package on its own, with its own versioning. I am not suggesting you do this, without support for transitional packages in Cygwin this would be even more confusing to users. But you script is now more than just a patch to xinit! > However, from personal experience, I disagree that a different version > number would have made a bit of difference. Either people will read > the announcements -- and the subject of mine should have indicated > that this wasn't a routing update -- or they won't. Personally I do check release notes on major updates, but I admit I am probably an anomaly. [1] https://cygwin.com/ml/cygwin-xfree/2014-11/msg00040.html -- Laurens _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From yselkowitz@cygwin.com Wed Jan 7 06:08:00 2015 From: yselkowitz@cygwin.com (Yaakov Selkowitz) Date: Wed, 07 Jan 2015 06:08:00 -0000 Subject: Suggestion for improving xinit 1.3.4 In-Reply-To: <54ABACF8.90406@blankersfamily.com> References: <54AA7981.7080805@blankersfamily.com> <54AACD28.9060407@cygwin.com> <54ABACF8.90406@blankersfamily.com> Message-ID: <54ACCD52.1010309@cygwin.com> On 2015-01-06 03:38, Laurens Blankers wrote: > On 5-1-2015 19:17, Yaakov Selkowitz wrote: >> On 2015-01-05 11:43, Yaakov Selkowitz wrote: >>> On 2015-01-05 05:46, Laurens Blankers wrote: >>>> [..] >>>> 1. Handling of empty .startxwinrc >>>> [..] >>> >>> And what if it's not zero-length but still blank? >> >> I could have startxwin check if ~/.startxwinrc is executable, and skip >> if it not, which might also cover many of these empty .startxwinrc's. >> OTOH all that might accomplish is trade the "why won't it start" for >> "why doesn't it respect my config". :-) > Nice edge case, well, you could use sed to filter commented lines and > white space and determine whether the file is effectively empty. But I > guess that might be even more surprising to people who don't expect it. > > How about this: Handle a missing execution flag on .startxwinrc as if > the file was missing, thereby executing the default behaviour. That's exactly what I'm considering. > How would you feel about adding a few more > items there may be "XWin Server (background)" and "XWin Server > (background, listen)". I would consider this too, but: > There shortcuts could execute code similar to the > one suggested by Angelo Graziosi [1] basically something like: > > run.exe /usr/bin/bash.exe -l -c /usr/bin/XWin -multiwindow -clipboard > -silent-dup-error -nolisten tcp > > for the first and > > run.exe /usr/bin/bash.exe -l -c /usr/bin/XWin -multiwindow -clipboard > -silent-dup-error -listen tcp > > for the second. One of the recent improvements to startxwin was that it would now find an available $DISPLAY itself, just like startx does. Using -silent-dup-error doesn't do that; think of the case where another user on the same system has started an X server first, then you wouldn't get an X server at all. > On 5-1-2015 18:43/19:17, Yaakov Selkowitz wrote: >> xinit -- the startx and xinit parts -- is an upstream X.Org package, >> and they determine the package version. The startxwin components are >> Cygwin-specific additions to the package, as they have been since we >> first released modular X11R7.4. Therefore, changing the version in >> this way isn't a viable option here. > I didn't think about the link with upstream. You are right, using a > different versioning scheme as upstream would be even more confusing. > > Although, technically, since your startxwin script is no longer an > adaptation of xinit it qualifies as an original program and could be put > in a package on its own, with its own versioning. I am not suggesting > you do this, without support for transitional packages in Cygwin this > would be even more confusing to users. But you script is now more than > just a patch to xinit! Now it's more a patch to startx instead. -- Yaakov -- Unsubscribe info: http://cygwin.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 laurens@blankersfamily.com Wed Jan 7 21:39:00 2015 From: laurens@blankersfamily.com (Laurens Blankers) Date: Wed, 07 Jan 2015 21:39:00 -0000 Subject: Suggestion for improving xinit 1.3.4 In-Reply-To: <54ACCD52.1010309@cygwin.com> References: <54AA7981.7080805@blankersfamily.com> <54AACD28.9060407@cygwin.com> <54ABACF8.90406@blankersfamily.com> <54ACCD52.1010309@cygwin.com> Message-ID: <54ADA76C.8080709@blankersfamily.com> On 7-1-2015 07:08, Yaakov Selkowitz wrote: > One of the recent improvements to startxwin was that it would now find > an available $DISPLAY itself, just like startx does. Using > -silent-dup-error doesn't do that; think of the case where another > user on the same system has started an X server first, then you > wouldn't get an X server at all. It would be very nice if that functionality, and anything else that might be added in the future, applies regardless of which shortcut you click. Would it be difficult to maintain an addition option to startxwin e.g. --skip-rc? >> Although, technically, since your startxwin script is no longer an >> adaptation of xinit it qualifies as an original program and could be put >> in a package on its own, with its own versioning. I am not suggesting >> you do this, without support for transitional packages in Cygwin this >> would be even more confusing to users. But you script is now more than >> just a patch to xinit! > > Now it's more a patch to startx instead. I still consider it an original program rather than just a patch :-) Laurens -- Laurens _____________________________________________________________________ A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From ben.alkov@gmail.com Thu Jan 8 17:13:00 2015 From: ben.alkov@gmail.com (Ben) Date: Thu, 08 Jan 2015 17:13:00 -0000 Subject: Q: What is the correct configuration for client and server when using '-nolisten'? Message-ID: Due to the recent changes to Xorg et al., I've had two major breakages; one with the update to `xinit` which now requires a `.startxwinrc`, and one this week with the update to `xorg-server`. I managed to work around the first breakage, but the second has required me to roll back to the previous packages for both. The issue I'm having is that, in spite of Doing It Right (`ssh -f -Y user@remote_host xterm`), I'm now getting `connect /tmp/.X11-unix/X0: Connection refused` when trying to connect to my servers (which are also now, and always have been, running with `-nolisten tcp`). To be explicit; rolling `xinit` back to 1.3.4-1 and `xorg-server` back to 1.16.3-1 fixed this immediately with no other changes, although I suspect that the `xinit` downgrade may not be necessary. What am I doing wrong? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From benjamin.richards86@gmail.com Fri Jan 9 18:55:00 2015 From: benjamin.richards86@gmail.com (Benjamin Richards) Date: Fri, 09 Jan 2015 18:55:00 -0000 Subject: Need help to replicate old behavior of my X setup scripts with latest Xfree86 update In-Reply-To: <5499BFC1.2030006@gmail.com> References: <5499BFC1.2030006@gmail.com> Message-ID: <3b5201d02c3d$c549f510$4fdddf30$@gmail.com> > -----Original Message----- > From: Marco Atzeri [mailto:marco.atzeri@gmail.com] > Sent: Tuesday, December 23, 2014 2:17 PM > To: cygwin-xfree@cygwin.com > Subject: Re: Need help to replicate old behavior of my X setup scripts with > latest Xfree86 update > > > > > try putting "sleep inf" in .startxwinrc > It should simulate the old behaviour > > Regards Thanks for the suggestion. I actually figured out something similar. I launched fbpanel instead with this command: exec /usr/bin/fbpanel -p multiwindow I also discovered that the X server is not always opened on display 0, which I wanted to force, so I did some digging and found I can do that by creating a ~/.xserverrc file to change how it launches the X server. I put this in the file instead: /usr/bin/XWin :0 -multiwindow -nolisten tcp I don?t need external connections as I?m primarily using the X server for local programs or with ssh -Y, so the nolisten switch works fine for me. I also didn?t want xterm to start up at launch, so I had to create an empty ~/.Xclients file. Finally, I had change my startup script so that, if the X server isn't running yet, it would launch startxwin in the background and loop until it sees the fbpanel process in the process list, or time out (after 30 seconds). If it sees the process start, it sets up my configurations as before. It works, albeit not as cleanly as before. I get the extra icon in my taskbar for fbpanel since it?s running, and I see the job number get echoed out to the terminal when it backgrounds the startxwin script. It also takes longer to start since I?m launching fbpanel on top of the server, though I suppose putting the sleep command would alleviate some of that. I?ll look into it. Thanks! Sincerely, Benjamin Richards -- Unsubscribe info: http://cygwin.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 Mon Jan 12 00:26:00 2015 From: cygwin@tlinx.org (Linda Walsh) Date: Mon, 12 Jan 2015 00:26:00 -0000 Subject: solution for package startup scripts changing: do your own (was Re: run.exe will not work with upgrade from 1.14.4 to 1.16.3) In-Reply-To: <54A6FDB8.9070106@blankersfamily.com> References: <54A6FDB8.9070106@blankersfamily.com> Message-ID: <54B314B7.5010008@tlinx.org> Laurens Blankers wrote: > On 2-1-2015 21:10, schilpfamily wrote: >> this has worked for years, now when i run this command, a window very >> briefly blinks into existence but then goes away. any idea why this >> would stop working now? ==== Because the default options in the distribution provided startup script changed to a more secure setting, consistent with upstream changes and the general atmosphere of security paranoia that is gradually eroding usability (as security issues get alot more attention than usability -- so much so, that while a benefit of computers was that they could adapt to the user for a friendly user experience, the opposite is becoming the standard. I.e. users are expected to adapt themselves to the changing machine programs. I start my X server on login -- which means it has to work when called at login -- and I wanted to make sure I could pass custom arguments for the font path (among other things). As a result I simply "wrote my own" startup script that has it's own defaults. I expect it to work until some argument I expect to be there is deleted. I don't instantly get new features and benefits that might be invoked from the distribution script, but usually it starts, and every once in a while I review it and the cygwin start scripts to see if there is something I should change. But at least I don't get caught by this particular problem. I *do* still get caught by the installer overwriting Windows mount points with physical directories which causes various programs to stop functioning until I move the updated files to the 'mount-point' and change the physdir back to a mount point. Anyway, --- The script is started by a shortcut in: C:\Users\\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup That has a shortcut to 'bash' with arguments: (Target:) C:\bin\bash.exe -c '/bin/setsid "%USERPROFILE%/bin/startxwin.sh"' (Start in:) %HOMEDRIVE%%HOMEPATH% (Run:) Minimized ---- It is also an icon on my 'Quick Launch' bar (i.e. in directory): C:\Users\\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch ---startxwin.sh--- #!/bin/bash # (c) LA Walsh 2004-2014, licenced under GPLv2 #export DISPLAY=:0 #export XAPPLRESDIR=/usr/X11R6/lib/X11/app-defaults #export XCMSDB=/usr/X11R6/lib/X11/Xcms.txt #export XKEYSYMDB=/usr/X11R6/lib/X11/XKeysymDB #export XNLSPATH=/usr/X11R6/lib/X11/locale #unexport XAPPLRESDIR XCMSDB XKEYSYMDB XNLSPATH # see cygwin Xwin for more option examples # relevant ops: # -multiwindow = use windows manage; not w/(-rootless|-fullscreen) # -clipboard = use built-in version (integrated w/windows) # -unixkill = Enable Ctrl-Alt-BS as X-server shutdown cmnd # -nowinkill = Disable Alt+F4 as a server shutdown key combination. # -trayicon = (default) windows tray icon enabled mount -c / export PATH=/bin:$(/bin/cygpath "$USERPROFILE")/bin:$PATH #ensure our bin is 1st shopt -s expand_aliases extglob alias notify=$(type -P notifu) alias int=declare\ -i alias sub=function alias xset=$(type -P xset); alias array=declare\ -a alias my=declare export DISPLAY="${DISPLAY:-":0"}" sub xup { local stat read -t .1 stat <<<$(xset q >&/dev/null; echo $?) && return $stat ((-1)) } sub Xwin_pids { ( cd /proc && for p in +([0-9])/ ;do p2=${p%/} prg=$(<${p2}/exename) if [[ $prg =~ .*XWin ]]; then printf "%d:%s\n" "$p2" "$prg" fi done ) } sub Xwin_pid { array Xprgs readarray Xprgs< <(Xwin_pids) if ((!${#Xprgs[@]}));then echo 0 return 1 fi my x=${Xprgs[0]} my pid=${x%%:**} prg=${x##*:} array out=( "$pid" "$prg") printf "%s " "${out[@]}" printf "\n" return 0 } sub Xwin_running { int pd; my pg read pd pg < <(Xwin_pid) return $(((!pd))) } export -f Xwin_pids Xwin_pid sub tidy_old_Xwin { local -a sigs=(TERM TERM KILL) # try 2 TERMs then KILL upto maxsigs int pd; my pg int maxsigs=3 lastsig=${#sigs[*]} while ((1)); do read pd pg < <(Xwin_pid) ((pd)) || break #int i=--maxsigs>lastsig ? lastsig:maxsigs kill -${sigs[--maxsigs>lastsig ? lastsig:maxsigs]} $pd ((maxsigs)) || break sleep 1 done rm -fr /tmp/.X11-unix } sub get_dpi { dpi=$(regtool -d get '/HKLM/Software/Microsoft/Windows NT/CurrentVersion/FontDPI/LogPixels') # check for insane values ((dpi<50||dpi>>400)) && dpi=96 echo "$dpi" } sub get_fontpath { local fontpath="/usr/share/TTF:tcp/ishtar:7100,built-ins,/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/100dpi" echo -n "$fontpath" } sub start_XWin { local fontpath="/usr/share/fonts/TTF,built-ins,/usr/share/fonts/Type1,/usr/share/fonts/misc,/usr/share/fonts/100dpi" int dpi=$(get_dpi) cmd="/bin/run /bin/XWin ${dpi:+-dpi $dpi} -nomultimonitors -clipboard -ac -unixkill -nowinkill -wgl -bs -fp "$fontpath" -multiwindow" echo cmd="$cmd" $cmd } declare -a default_switches=(-dpi -clipboard -unixkill -nowinkill -bs -ac -fp -multiwindow -wgl) readarray -t args< <( a="$default_switches[@]"; IFS=$'\n'; echo "${a[*]#?}"|sort -k1.2 ) sub read_users_mind { #(reads file in lieu of HW support for actual) if [[ -O ~/.mind && -O ~/.mind/Xserver-dflt-overrides ]]; then readarray -t overrides < <( -x <~/.mind/Xserver-dflt-overrides perl -wnE ' chomp; s/\s*(?:#.*)?$//; s/^\s*// s/\s\s+/\s/ ; $_ || next; print $_."\n" ') fi typeset -a switches } sub start_dbus { /bin/run /bin/dbus-launch --exit_with_session ~/.Xsession } sub _in { local x=${1:?};shift for ((;$#>0;)); do [[ $x == $1 ]] && return 0;shift; done return 1 } int tries=3 if Xwin_running && xup; then notify /t info /m "Xserver already running and ready" /d 5000 else echo Cannot contact X Server tidy_old_Xwin while ((1)); do start_XWin $(read_users_mind) sleep 1 for ((i=0;i<5;++i)); do xup && break 2 sleep 1 done if ((--tries<=0)); then m="EXITING: Timeout Waiting for Xserver Startup!!" echo "$m" notify /t error /m "$m" exit 1; fi done #start_dbus || { m="Error Starting Dbus"; echo "$m"; notify /t error /m "$m"; } fi # vim: ts=2:sw=2 -------------- > This is most likely due to a major rewrite of the xinit package which > contains all start-up scripts. ---- Not if you write your own -- then you will get your own "customized" behavior (so at least when it breaks, you have a chance to fix it yourself)... If you don't like mine, fine, copy the cygwin script and make the changes to it and call it the same way. At least you'll get whatever behavior you want and upgrades won't be altering your script... BTW, Laurens Blankers, the opensource model for developers doing their own thing is called a "do-acracy". Those that do, make the rules. Not saying it is a great thing, just putting a handle on it... ;-) -- Unsubscribe info: http://cygwin.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 hoes.maarten@gmail.com Sat Jan 17 11:49:00 2015 From: hoes.maarten@gmail.com (Maarten Hoes) Date: Sat, 17 Jan 2015 11:49:00 -0000 Subject: Cygwin/X XDMCP Issue Message-ID: <54BA4C5C.4020400@gmail.com> Hi, Im having some issues when running Cygwin/X in combination with XDMCP. Opening a cygwin prompt and running 'startx' works as expected. When I try to connect to my remote Linux system with the command 'xwin -query 192.168.178.22' (or with the 'XLaunch' program and choose XDMCP) the screen stays black. I get the impression that I do get an connection, but that there is a display problem. When I try to close the blacked out Window, I get the message 'Exiting will close all screens on this display. There are currently 6 clients connected. Proceed with the shutdown of this display/server ?' When i specify 'xwin -retro -query 192.168.178.22', the cursor appears and the screen gets gray-ish, but mouse clicking has no effect. Setting 'xwin -engine 16 -query 192.168.178.22' results in a blue background and an error: 'Failed asserion key -> size == 0 at line 147 of file /qip/cygport-git/x-org-server/x-org-server-1.16.3-1.x86_64/src/xserver-cygwin-1.16.3-1/include/privates.h in function dixSetPrivate' and a core dump. Any and all ideas are more than welcome, as I have no idea whats going on here. This is the output of the 'xwin -query 192.168.178.22' command : $ xwin -query 192.168.178.22 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.3.0 OS: CYGWIN_NT-6.3 DUSTY123 1.7.33-2(0.280/5/3) 2014-11-13 15:47 x86_64 OS: Windows 8.1 [Windows NT 6.3 build 9600] (Win64) Package: version 1.16.3-1 built 2014-12-30 XWin was started with the following command line: xwin -query 192.168.178.22 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: /home/Maarten/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 00000015 winSetEngine - Using Shadow DirectDraw NonLocking winScreenInit - Using Windows display depth of 32 bits per pixel winWindowProc - WM_SIZE - new client area w: 1424 h: 821 winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff MIT-SHM extension disabled due to lack of kernel support XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel (EE) AIGLX: No native OpenGL in modes with a root window (II) AIGLX: enabled GLX_EXT_texture_from_pixmap (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 712 410 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 (--) Found matching XKB configuration "English (USA)" (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" winProcEstablishConnection - winInitClipboard returned. winClipboardThreadProc - DISPLAY=:0.0 OS maintains clipboard viewer chain: yes winClipboardProc - XOpenDisplay () returned and successfully opened the display. winWindowProc - WM_*KEYDOWN - Closekey hit, quitting winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress (EE) Server terminated successfully (0). Closing log file. Regards, - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From hoes.maarten@gmail.com Sat Jan 17 21:06:00 2015 From: hoes.maarten@gmail.com (Maarten Hoes) Date: Sat, 17 Jan 2015 21:06:00 -0000 Subject: Cygwin/X XDMCP Issue In-Reply-To: <54BA4C5C.4020400@gmail.com> References: <54BA4C5C.4020400@gmail.com> Message-ID: <54BACED2.6070204@gmail.com> Hi, Also, when I run wireshark/tshark, I seem to be watching a regular/successful XDCMP/X11 session ? : - Maarten 1 0.000000 192.168.178.20 -> 192.168.178.22 XDMCP 49 Query 2 0.013070 192.168.178.22 -> 192.168.178.20 XDMCP 106 Willing 3 0.178469 192.168.178.20 -> 192.168.178.22 XDMCP 312 Request 4 0.183798 192.168.178.22 -> 192.168.178.20 XDMCP 94 Accept 5 0.183901 192.168.178.20 -> 192.168.178.22 XDMCP 71 Manage 6 0.687156 192.168.178.22 -> 192.168.178.20 TCP 74 49008??????6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=8283439 TSecr=0 WS=128 7 0.687297 192.168.178.20 -> 192.168.178.22 TCP 74 6000??????49008 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=1056917 TSecr=8283439 8 0.687462 192.168.178.22 -> 192.168.178.20 TCP 66 49008??????6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=8283439 TSecr=1056917 9 0.687695 192.168.178.22 -> 192.168.178.20 X11 114 Initial connection request 10 0.687992 192.168.178.20 -> 192.168.178.22 TCP 74 [TCP segment of a reassembled PDU] 11 0.688064 192.168.178.20 -> 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 12 0.688086 192.168.178.20 -> 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 13 0.688104 192.168.178.20 -> 192.168.178.22 X11 254 Initial connection reply 14 0.688127 192.168.178.22 -> 192.168.178.20 TCP 66 49008??????6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=8283440 TSecr=1056917 15 0.688225 192.168.178.22 -> 192.168.178.20 TCP 66 49008??????6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=8283440 TSecr=1056917 16 0.688451 192.168.178.22 -> 192.168.178.20 X11 86 Requests: QueryExtension 17 0.688654 192.168.178.20 -> 192.168.178.22 X11 98 Reply: QueryExtension 18 0.688823 192.168.178.22 -> 192.168.178.20 X11 70 Requests: BIG-REQUESTS 19 0.688958 192.168.178.20 -> 192.168.178.22 X11 98 Reply: BIG-REQUESTS 20 0.689164 192.168.178.22 -> 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 21 0.689567 192.168.178.20 -> 192.168.178.22 X11 98 Reply: GetProperty 22 0.689752 192.168.178.22 -> 192.168.178.20 X11 86 Requests: QueryExtension 23 0.690102 192.168.178.20 -> 192.168.178.22 X11 98 Reply: QueryExtension 24 0.690259 192.168.178.22 -> 192.168.178.20 X11 74 Requests: XKEYBOARD 25 0.690419 192.168.178.20 -> 192.168.178.22 X11 98 Reply: XKEYBOARD 26 0.692905 192.168.178.22 -> 192.168.178.20 X11 82 Requests: QueryExtension 27 0.693104 192.168.178.20 -> 192.168.178.22 X11 98 Reply: QueryExtension 28 0.693326 192.168.178.22 -> 192.168.178.20 X11 98 Requests: QueryExtension 29 0.693477 192.168.178.20 -> 192.168.178.22 X11 98 Reply: QueryExtension 30 0.693627 192.168.178.22 -> 192.168.178.20 X11 74 Requests: Generic Event Extension 31 0.693881 192.168.178.20 -> 192.168.178.22 X11 98 Reply: Generic Event Extension 32 0.694061 192.168.178.22 -> 192.168.178.20 X11 78 Requests: RANDR 33 0.694183 192.168.178.20 -> 192.168.178.22 X11 98 Reply: RANDR 34 0.694334 192.168.178.22 -> 192.168.178.20 X11 74 Requests: RANDR 35 0.694481 192.168.178.20 -> 192.168.178.22 X11 98 Reply: RANDR 36 0.694628 192.168.178.22 -> 192.168.178.20 X11 74 Requests: RANDR 37 0.694759 192.168.178.20 -> 192.168.178.22 X11 98 Reply: RANDR 38 0.734457 192.168.178.22 -> 192.168.178.20 TCP 66 49008??????6000 [ACK] Seq=229 Ack=3445 Win=35456 Len=0 TSval=8283487 TSecr=1056918 39 0.774514 192.168.178.22 -> 192.168.178.20 TCP 74 49009??????6000 [SYN] Seq=0 Win=29200 Len=0 MSS=1460 SACK_PERM=1 TSval=8283526 TSecr=0 WS=128 40 0.774620 192.168.178.20 -> 192.168.178.22 TCP 74 6000??????49009 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 WS=4 SACK_PERM=1 TSval=1056926 TSecr=8283526 41 0.774780 192.168.178.22 -> 192.168.178.20 TCP 66 49009??????6000 [ACK] Seq=1 Ack=1 Win=29312 Len=0 TSval=8283527 TSecr=1056926 42 0.774978 192.168.178.22 -> 192.168.178.20 X11 114 Initial connection request 43 0.775254 192.168.178.20 -> 192.168.178.22 TCP 74 [TCP segment of a reassembled PDU] 44 0.775304 192.168.178.20 -> 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 45 0.775327 192.168.178.20 -> 192.168.178.22 TCP 1514 [TCP segment of a reassembled PDU] 46 0.775336 192.168.178.20 -> 192.168.178.22 X11 254 Initial connection reply 47 0.775382 192.168.178.22 -> 192.168.178.20 TCP 66 49009??????6000 [ACK] Seq=49 Ack=9 Win=29312 Len=0 TSval=8283527 TSecr=1056926 48 0.775458 192.168.178.22 -> 192.168.178.20 TCP 66 49009??????6000 [ACK] Seq=49 Ack=3093 Win=35456 Len=0 TSval=8283527 TSecr=1056926 49 0.775580 192.168.178.22 -> 192.168.178.20 X11 86 Requests: QueryExtension 50 0.775697 192.168.178.20 -> 192.168.178.22 X11 98 Reply: QueryExtension 51 0.775818 192.168.178.22 -> 192.168.178.20 X11 70 Requests: BIG-REQUESTS 52 0.775916 192.168.178.20 -> 192.168.178.22 X11 98 Reply: BIG-REQUESTS 53 0.776069 192.168.178.22 -> 192.168.178.20 X11 110 Requests: CreateGC, GetProperty 54 0.776186 192.168.178.20 -> 192.168.178.22 X11 98 Reply: GetProperty 55 0.776337 192.168.178.22 -> 192.168.178.20 X11 86 Requests: QueryExtension 56 0.776441 192.168.178.20 -> 192.168.178.22 X11 98 Reply: QueryExtension 57 0.776579 192.168.178.22 -> 192.168.178.20 X11 74 Requests: XKEYBOARD 58 0.776678 192.168.178.20 -> 192.168.178.22 X11 98 Reply: XKEYBOARD 59 0.776998 192.168.178.22 -> 192.168.178.20 X11 138 Requests: InternAtom 60 0.777102 192.168.178.20 -> 192.168.178.22 X11 98 Reply: InternAtom 61 0.777219 192.168.178.22 -> 192.168.178.20 X11 102 Requests: InternAtom 62 0.777308 192.168.178.20 -> 192.168.178.22 X11 98 Reply: InternAtom 63 0.777466 192.168.178.22 -> 192.168.178.20 X11 98 Requests: InternAtom 64 0.777558 192.168.178.20 -> 192.168.178.22 X11 98 Reply: InternAtom -- Unsubscribe info: http://cygwin.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 hoes.maarten@gmail.com Sun Jan 18 08:57:00 2015 From: hoes.maarten@gmail.com (Maarten Hoes) Date: Sun, 18 Jan 2015 08:57:00 -0000 Subject: Cygwin/X XDMCP Issue In-Reply-To: <54BACED2.6070204@gmail.com> References: <54BA4C5C.4020400@gmail.com> <54BACED2.6070204@gmail.com> Message-ID: <54BB7568.2030002@gmail.com> Hi, Sorry, I forgot to include it in my previous posts: please find the contents of 'cygcheck -s -v -r' attached in 'cygcheck.out' - Maarten -------------- next part -------------- Cygwin Configuration Diagnostics Current System Time: Sun Jan 18 08:54:47 2015 Windows 8.1 Ver 6.3 Build 9600 Path: C:\cygwin64\usr\local\bin C:\cygwin64\bin C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common C:\PROGRAM FILES (X86)\INTEL\ICLS CLIENT C:\PROGRAM FILES\INTEL\ICLS CLIENT C:\Windows\SYSTEM32 C:\Windows C:\Windows\SYSTEM32\WBEM C:\Windows\SYSTEM32\WINDOWSPOWERSHELL\V1.0 C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL C:\PROGRAM FILES\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\DAL C:\PROGRAM FILES (X86)\INTEL\INTEL(R) MANAGEMENT ENGINE COMPONENTS\IPT D:\Progra~1\Java\jre7\bin C:\MinGW\bin D:\Program Files\Calibre2 C:\MinGW\bin C:\MinGW\mingw32\bin C:\MinGW\msys\1.0\bin C:\GnuWin32\bin C:\Program Files (x86)\QuickTime\QTSystem Output from C:\cygwin64\bin\id.exe UID: 1001(Maarten) GID: 513(Geen) 513(Geen) 545(Gebruikers) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'Maarten' PWD = '/home/Maarten' HOME = '/home/Maarten' USERDOMAIN_ROAMINGPROFILE = 'DUSTY123' HOMEPATH = '\Users\Maarten' APPDATA = 'C:\Users\Maarten\AppData\Roaming' ProgramW6432 = 'C:\Program Files' HOSTNAME = 'DUSTY123' SHELL = '/bin/bash' TERM = 'xterm' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' PROFILEREAD = 'true' WINDIR = 'C:\Windows' PUBLIC = 'C:\Users\Public' OLDPWD = '/cygdrive/d/Users/Maarten/Desktop' ORIGINAL_PATH = '/cygdrive/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/cygdrive/c/PROGRAM FILES (X86)/INTEL/ICLS CLIENT:/cygdrive/c/PROGRAM FILES/INTEL/ICLS CLIENT:/cygdrive/c/Windows/SYSTEM32:/cygdrive/c/Windows:/cygdrive/c/Windows/SYSTEM32/WBEM:/cygdrive/c/Windows/SYSTEM32/WINDOWSPOWERSHELL/V1.0:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/DAL:/cygdrive/c/PROGRAM FILES (X86)/INTEL/INTEL(R) MANAGEMENT ENGINE COMPONENTS/IPT:/cygdrive/d/Progra~1/Java/jre7/bin:/cygdrive/c/MinGW/bin:/cygdrive/d/Program Files/Calibre2:/cygdrive/c/MinGW/bin:/cygdrive/c/MinGW/mingw32/bin:/cygdrive/c/MinGW/msys/1.0/bin:/cygdrive/c/GnuWin32/bin:/cygdrive/c/Program Files (x86)/QuickTime/QTSystem' USERDOMAIN = 'DUSTY123' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' OS = 'Windows_NT' ALLUSERSPROFILE = 'C:\ProgramData' !:: = '::\' TEMP = '/tmp' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' USERNAME = 'Maarten' PROCESSOR_LEVEL = '6' ProgramFiles(x86) = 'C:\Program Files (x86)' PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\' FP_NO_HOST_CHECK = 'NO' SYSTEMDRIVE = 'C:' JAVA_HOME = 'D:\Progra~1\Java\jre7' LANG = 'en_US.UTF-8' USERPROFILE = 'C:\Users\Maarten' TZ = 'Europe/Amsterdam' PS1 = '\[\e]0;\w\a\]\n\[\e[32m\]\u@\h \[\e[33m\]\w\[\e[0m\]\n\$ ' LOGONSERVER = '\\DUSTY123' CommonProgramW6432 = 'C:\Program Files\Common Files' PROCESSOR_ARCHITECTURE = 'AMD64' LOCALAPPDATA = 'C:\Users\Maarten\AppData\Local' ProgramData = 'C:\ProgramData' EXECIGNORE = '*.dll' SHLVL = '1' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' HOMEDRIVE = 'C:' COMSPEC = 'C:\Windows\system32\cmd.exe' TMP = '/tmp' SYSTEMROOT = 'C:\Windows' PRINTER = 'HP Photosmart C5200 series' PROCESSOR_REVISION = '3c03' INFOPATH = '/usr/local/info:/usr/share/info:/usr/info' PROGRAMFILES = 'C:\Program Files' NUMBER_OF_PROCESSORS = '8' asl.log = 'Destination=file' SESSIONNAME = 'Console' COMPUTERNAME = 'DUSTY123' _ = '/usr/bin/cygcheck' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Installations (default) = '\??\C:\cygwin64' c5e39b7a9d22bafb = '\??\C:\cygwin' HKEY_CURRENT_USER\Software\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\DefaultIcon (default) = 'C:\cygwin64\bin\xlaunch.exe,1' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Edit\command (default) = '"C:\cygwin64\bin\run" "C:\cygwin64\bin\bash" -l -c "xlaunch -load \"%1\""' HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open HKEY_LOCAL_MACHINE\SOFTWARE\Classes\XLaunch.cygwin\Shell\Open\command (default) = '"C:\cygwin64\bin\run" "C:\cygwin64\bin\bash" -l -c "xlaunch -run \"%1\""' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\cygwin64' HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\Installations (default) = '\??\C:\cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\Program Options HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\setup (default) = 'C:\cygwin' obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: e022582115c10879 Path: C:\cygwin64 User: Key: e022582115c10879 Path: C:\cygwin64 User: Key: c5e39b7a9d22bafb Path: C:\cygwin (ORPHANED) c: hd NTFS 229600Mb 42% CP CS UN PA FC Windows d: hd NTFS 1907726Mb 70% CP CS UN PA FC Data e: hd NTFS 4769295Mb 11% CP CS UN PA FC Seagate Expansion Drive f: cd N/A N/A v: fd N/A N/A w: fd N/A N/A x: fd N/A N/A y: fd N/A N/A C:\cygwin64 / system binary,auto C:\cygwin64\bin /usr/bin system binary,auto C:\cygwin64\lib /usr/lib system binary,auto cygdrive prefix /cygdrive user binary,posix=0,auto Found: C:\cygwin64\bin\awk Found: C:\MinGW\msys\1.0\bin\awk.exe Warning: C:\cygwin64\bin\awk hides C:\MinGW\msys\1.0\bin\awk.exe Found: C:\GnuWin32\bin\awk.exe Warning: C:\cygwin64\bin\awk hides C:\GnuWin32\bin\awk.exe -> C:\cygwin64\bin\gawk.exe Found: C:\cygwin64\bin\bash.exe Found: C:\MinGW\msys\1.0\bin\bash.exe Warning: C:\cygwin64\bin\bash.exe hides C:\MinGW\msys\1.0\bin\bash.exe Found: C:\cygwin64\bin\cat.exe Found: C:\MinGW\msys\1.0\bin\cat.exe Warning: C:\cygwin64\bin\cat.exe hides C:\MinGW\msys\1.0\bin\cat.exe Found: C:\GnuWin32\bin\cat.exe Warning: C:\cygwin64\bin\cat.exe hides C:\GnuWin32\bin\cat.exe Found: C:\cygwin64\bin\cp.exe Found: C:\MinGW\msys\1.0\bin\cp.exe Warning: C:\cygwin64\bin\cp.exe hides C:\MinGW\msys\1.0\bin\cp.exe Found: C:\GnuWin32\bin\cp.exe Warning: C:\cygwin64\bin\cp.exe hides C:\GnuWin32\bin\cp.exe Found: C:\MinGW\bin\cpp.exe Found: C:\MinGW\bin\cpp.exe Found: C:\MinGW\msys\1.0\bin\cpp.exe Warning: C:\MinGW\bin\cpp.exe hides C:\MinGW\msys\1.0\bin\cpp.exe Not Found: crontab Found: C:\cygwin64\bin\find.exe Found: C:\Windows\SYSTEM32\find.exe Warning: C:\cygwin64\bin\find.exe hides C:\Windows\SYSTEM32\find.exe Found: C:\MinGW\msys\1.0\bin\find.exe Warning: C:\cygwin64\bin\find.exe hides C:\MinGW\msys\1.0\bin\find.exe Found: C:\GnuWin32\bin\find.exe Warning: C:\cygwin64\bin\find.exe hides C:\GnuWin32\bin\find.exe Found: C:\MinGW\bin\gcc.exe Found: C:\MinGW\bin\gcc.exe Found: C:\MinGW\msys\1.0\bin\gcc.exe Warning: C:\MinGW\bin\gcc.exe hides C:\MinGW\msys\1.0\bin\gcc.exe Found: C:\MinGW\bin\gdb.exe Found: C:\MinGW\bin\gdb.exe Found: C:\cygwin64\bin\grep.exe Found: C:\MinGW\msys\1.0\bin\grep.exe Warning: C:\cygwin64\bin\grep.exe hides C:\MinGW\msys\1.0\bin\grep.exe Found: C:\GnuWin32\bin\grep.exe Warning: C:\cygwin64\bin\grep.exe hides C:\GnuWin32\bin\grep.exe Found: C:\cygwin64\bin\kill.exe Found: C:\MinGW\msys\1.0\bin\kill.exe Warning: C:\cygwin64\bin\kill.exe hides C:\MinGW\msys\1.0\bin\kill.exe Found: C:\GnuWin32\bin\kill.exe Warning: C:\cygwin64\bin\kill.exe hides C:\GnuWin32\bin\kill.exe Found: C:\cygwin64\bin\ld.exe Found: C:\MinGW\bin\ld.exe Warning: C:\cygwin64\bin\ld.exe hides C:\MinGW\bin\ld.exe Found: C:\MinGW\bin\ld.exe Warning: C:\cygwin64\bin\ld.exe hides C:\MinGW\bin\ld.exe Found: C:\MinGW\mingw32\bin\ld.exe Warning: C:\cygwin64\bin\ld.exe hides C:\MinGW\mingw32\bin\ld.exe Found: C:\MinGW\msys\1.0\bin\ld.exe Warning: C:\cygwin64\bin\ld.exe hides C:\MinGW\msys\1.0\bin\ld.exe Found: C:\cygwin64\bin\ls.exe Found: C:\MinGW\msys\1.0\bin\ls.exe Warning: C:\cygwin64\bin\ls.exe hides C:\MinGW\msys\1.0\bin\ls.exe Found: C:\GnuWin32\bin\ls.exe Warning: C:\cygwin64\bin\ls.exe hides C:\GnuWin32\bin\ls.exe Found: C:\MinGW\msys\1.0\bin\make.exe Found: C:\GnuWin32\bin\make.exe Warning: C:\MinGW\msys\1.0\bin\make.exe hides C:\GnuWin32\bin\make.exe Found: C:\cygwin64\bin\mv.exe Found: C:\MinGW\msys\1.0\bin\mv.exe Warning: C:\cygwin64\bin\mv.exe hides C:\MinGW\msys\1.0\bin\mv.exe Found: C:\GnuWin32\bin\mv.exe Warning: C:\cygwin64\bin\mv.exe hides C:\GnuWin32\bin\mv.exe Found: C:\MinGW\msys\1.0\bin\patch.exe Found: C:\GnuWin32\bin\patch.exe Warning: C:\MinGW\msys\1.0\bin\patch.exe hides C:\GnuWin32\bin\patch.exe Found: C:\cygwin64\bin\perl.exe Found: C:\MinGW\msys\1.0\bin\perl.exe Warning: C:\cygwin64\bin\perl.exe hides C:\MinGW\msys\1.0\bin\perl.exe Found: C:\cygwin64\bin\rm.exe Found: C:\MinGW\msys\1.0\bin\rm.exe Warning: C:\cygwin64\bin\rm.exe hides C:\MinGW\msys\1.0\bin\rm.exe Found: C:\GnuWin32\bin\rm.exe Warning: C:\cygwin64\bin\rm.exe hides C:\GnuWin32\bin\rm.exe Found: C:\cygwin64\bin\sed.exe Found: C:\MinGW\msys\1.0\bin\sed.exe Warning: C:\cygwin64\bin\sed.exe hides C:\MinGW\msys\1.0\bin\sed.exe Found: C:\GnuWin32\bin\sed.exe Warning: C:\cygwin64\bin\sed.exe hides C:\GnuWin32\bin\sed.exe Found: C:\cygwin64\bin\ssh.exe Found: C:\MinGW\msys\1.0\bin\ssh.exe Warning: C:\cygwin64\bin\ssh.exe hides C:\MinGW\msys\1.0\bin\ssh.exe Found: C:\cygwin64\bin\sh.exe Found: C:\MinGW\msys\1.0\bin\sh.exe Warning: C:\cygwin64\bin\sh.exe hides C:\MinGW\msys\1.0\bin\sh.exe Found: C:\cygwin64\bin\tar.exe Found: C:\MinGW\msys\1.0\bin\tar.exe Warning: C:\cygwin64\bin\tar.exe hides C:\MinGW\msys\1.0\bin\tar.exe Found: C:\GnuWin32\bin\tar.exe Warning: C:\cygwin64\bin\tar.exe hides C:\GnuWin32\bin\tar.exe Found: C:\cygwin64\bin\test.exe Found: C:\MinGW\msys\1.0\bin\test.exe Warning: C:\cygwin64\bin\test.exe hides C:\MinGW\msys\1.0\bin\test.exe Found: C:\GnuWin32\bin\test.exe Warning: C:\cygwin64\bin\test.exe hides C:\GnuWin32\bin\test.exe Found: C:\cygwin64\bin\vi.exe Found: C:\MinGW\msys\1.0\bin\vim.exe 575k 2013/05/30 C:\cygwin64\bin\cygarchive-13.dll - os=4.0 img=0.0 sys=5.2 "cygarchive-13.dll" v0.0 ts=2013-05-30 03:06 38k 2013/07/19 C:\cygwin64\bin\cygargp-0.dll - os=4.0 img=0.0 sys=5.2 "cygargp-0.dll" v0.0 ts=2013-07-19 15:07 643k 2013/04/30 C:\cygwin64\bin\cygaspell-15.dll - os=4.0 img=0.0 sys=5.2 "cygaspell-15.dll" v0.0 ts=2013-04-30 08:11 107k 2014/03/12 C:\cygwin64\bin\cygatk-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygatk-1.0-0.dll" v0.0 ts=2014-03-12 07:45 145k 2014/03/12 C:\cygwin64\bin\cygatk-bridge-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygatk-bridge-2.0-0.dll" v0.0 ts=2014-03-12 08:36 137k 2014/03/12 C:\cygwin64\bin\cygatspi-0.dll - os=4.0 img=0.0 sys=5.2 "cygatspi-0.dll" v0.0 ts=2014-03-12 08:18 16k 2013/03/26 C:\cygwin64\bin\cygattr-1.dll - os=4.0 img=0.0 sys=5.2 "cygattr-1.dll" v0.0 ts=2013-03-26 18:26 80k 2013/05/30 C:\cygwin64\bin\cygaudio-2.dll - os=4.0 img=0.0 sys=5.2 "cygaudio-2.dll" v0.0 ts=2013-05-30 23:41 59k 2013/06/04 C:\cygwin64\bin\cygavahi-client-3.dll - os=4.0 img=0.0 sys=5.2 "cygavahi-client-3.dll" v0.0 ts=2013-06-04 05:29 42k 2013/06/04 C:\cygwin64\bin\cygavahi-common-3.dll - os=4.0 img=0.0 sys=5.2 "cygavahi-common-3.dll" v0.0 ts=2013-06-04 05:28 13k 2013/06/04 C:\cygwin64\bin\cygavahi-glib-1.dll - os=4.0 img=0.0 sys=5.2 "cygavahi-glib-1.dll" v0.0 ts=2013-06-04 05:29 179k 2014/12/01 C:\cygwin64\bin\cygblkid-1.dll - os=4.0 img=0.0 sys=5.2 "cygblkid-1.dll" v0.0 ts=2014-12-01 23:56 64k 2013/03/07 C:\cygwin64\bin\cygbz2-1.dll - os=4.0 img=0.0 sys=5.2 "cygbz2-1.dll" v0.0 ts=2013-03-07 02:54 1064k 2014/11/16 C:\cygwin64\bin\cygcairo-2.dll - os=4.0 img=0.0 sys=5.2 "cygcairo-2.dll" v0.0 ts=2014-11-16 23:01 27k 2014/11/16 C:\cygwin64\bin\cygcairo-gobject-2.dll - os=4.0 img=0.0 sys=5.2 "cygcairo-gobject-2.dll" v0.0 ts=2014-11-16 23:01 118k 2014/11/16 C:\cygwin64\bin\cygcairo-script-interpreter-2.dll - os=4.0 img=0.0 sys=5.2 "cygcairo-script-interpreter-2.dll" v0.0 ts=2014-11-16 23:02 10k 2013/03/07 C:\cygwin64\bin\cygcharset-1.dll - os=4.0 img=0.0 sys=5.2 "cygcharset-1.dll" v0.0 ts=2013-03-07 03:03 12k 2014/06/09 C:\cygwin64\bin\cygcom_err-2.dll - os=4.0 img=0.0 sys=5.2 "cygcom_err-2.dll" v0.0 ts=1970-01-01 00:00 203k 2013/04/21 C:\cygwin64\bin\cygcroco-0.6-3.dll - os=4.0 img=0.0 sys=5.2 "cygcroco-0.6-3.dll" v0.0 ts=2013-04-21 06:25 9k 2013/03/07 C:\cygwin64\bin\cygcrypt-0.dll - os=4.0 img=0.0 sys=5.2 "cygcrypt-0.dll" v0.0 ts=2013-03-07 09:29 1752k 2015/01/08 C:\cygwin64\bin\cygcrypto-1.0.0.dll - os=4.0 img=0.0 sys=5.2 "cygcrypto-1.0.0.dll" v0.0 ts=2015-01-08 20:02 24k 2014/11/12 C:\cygwin64\bin\cygdatrie-1.dll - os=4.0 img=0.0 sys=5.2 "cygdatrie-1.dll" v0.0 ts=2014-11-12 07:24 1526k 2013/03/08 C:\cygwin64\bin\cygdb-5.3.dll - os=4.0 img=0.0 sys=5.2 "cygdb-5.3.dll" v0.0 ts=2013-03-08 07:55 242k 2014/12/10 C:\cygwin64\bin\cygdbus-1-3.dll - os=4.0 img=0.0 sys=5.2 "cygdbus-1-3.dll" v0.0 ts=2014-12-10 01:14 124k 2013/04/21 C:\cygwin64\bin\cygdbus-glib-1-2.dll - os=4.0 img=0.0 sys=5.2 "cygdbus-glib-1-2.dll" v0.0 ts=2013-04-21 07:12 111k 2013/03/08 C:\cygwin64\bin\cygdb_cxx-5.3.dll - os=4.0 img=0.0 sys=5.2 "cygdb_cxx-5.3.dll" v0.0 ts=2013-03-08 07:56 472k 2013/03/08 C:\cygwin64\bin\cygdb_sql-5.3.dll - os=4.0 img=0.0 sys=5.2 "cygdb_sql-5.3.dll" v0.0 ts=2013-03-08 07:58 15k 2013/06/06 C:\cygwin64\bin\cygdmx-1.dll - os=4.0 img=0.0 sys=5.2 "cygdmx-1.dll" v0.0 ts=2013-06-06 20:04 154k 2013/10/20 C:\cygwin64\bin\cygedit-0.dll - os=4.0 img=0.0 sys=5.2 "cygedit-0.dll" v0.0 ts=2013-10-20 21:56 68k 2014/12/09 C:\cygwin64\bin\cygEGL-1.dll - os=4.0 img=0.0 sys=5.2 "cygEGL-1.dll" v0.0 ts=2014-12-09 20:35 36k 2013/06/05 C:\cygwin64\bin\cygenchant-1.dll - os=4.0 img=0.0 sys=5.2 "cygenchant-1.dll" v0.0 ts=2013-06-06 00:25 216k 2013/06/05 C:\cygwin64\bin\cygexif-12.dll - os=4.0 img=0.0 sys=5.2 "cygexif-12.dll" v0.0 ts=2013-06-06 00:31 246k 2013/07/24 C:\cygwin64\bin\cygexo-1-0.dll - os=4.0 img=0.0 sys=5.2 "cygexo-1-0.dll" v0.0 ts=2013-07-25 00:37 147k 2013/07/31 C:\cygwin64\bin\cygexpat-1.dll - os=4.0 img=0.0 sys=5.2 "cygexpat-1.dll" v0.0 ts=2013-07-31 22:53 72k 2013/09/02 C:\cygwin64\bin\cygexslt-0.dll - os=4.0 img=0.0 sys=5.2 "cygexslt-0.dll" v0.0 ts=2013-09-02 17:55 30k 2014/10/14 C:\cygwin64\bin\cygfam-0.dll - os=4.0 img=0.0 sys=5.2 "cygfam-0.dll" v0.0 ts=2014-10-14 21:33 22k 2013/05/12 C:\cygwin64\bin\cygffi-6.dll - os=4.0 img=0.0 sys=5.2 "cygffi-6.dll" v0.0 ts=2013-05-12 22:53 959k 2013/09/10 C:\cygwin64\bin\cygfltk-1.3.dll - os=4.0 img=0.0 sys=5.2 "cygfltk-1.3.dll" v0.0 ts=2013-09-10 19:39 21k 2013/09/10 C:\cygwin64\bin\cygfltk_forms-1.3.dll - os=4.0 img=0.0 sys=5.2 "cygfltk_forms-1.3.dll" v0.0 ts=2013-09-10 19:39 90k 2013/09/10 C:\cygwin64\bin\cygfltk_gl-1.3.dll - os=4.0 img=0.0 sys=5.2 "cygfltk_gl-1.3.dll" v0.0 ts=2013-09-10 19:39 47k 2013/09/10 C:\cygwin64\bin\cygfltk_images-1.3.dll - os=4.0 img=0.0 sys=5.2 "cygfltk_images-1.3.dll" v0.0 ts=2013-09-10 19:39 218k 2014/04/29 C:\cygwin64\bin\cygfontconfig-1.dll - os=4.0 img=0.0 sys=5.2 "cygfontconfig-1.dll" v0.0 ts=1970-01-01 00:00 25k 2013/06/06 C:\cygwin64\bin\cygfontenc-1.dll - os=4.0 img=0.0 sys=5.2 "cygfontenc-1.dll" v0.0 ts=2013-06-06 22:13 55k 2014/12/14 C:\cygwin64\bin\cygformw-10.dll - os=4.0 img=0.0 sys=5.2 "cygformw-10.dll" v0.0 ts=2014-12-14 23:13 584k 2014/12/10 C:\cygwin64\bin\cygfreetype-6.dll - os=4.0 img=0.0 sys=5.2 "cygfreetype-6.dll" v0.0 ts=2014-12-10 16:49 91k 2013/06/05 C:\cygwin64\bin\cygfribidi-0.dll - os=4.0 img=0.0 sys=5.2 "cygfribidi-0.dll" v0.0 ts=2013-06-05 18:14 41k 2014/04/04 C:\cygwin64\bin\cygFS-6.dll - os=4.0 img=0.0 sys=5.2 "cygFS-6.dll" v0.0 ts=1970-01-01 00:00 28k 2014/12/01 C:\cygwin64\bin\cyggailutil-18.dll - os=4.0 img=0.0 sys=5.2 "cyggailutil-18.dll" v0.0 ts=2014-12-01 19:41 94k 2013/07/24 C:\cygwin64\bin\cyggarcon-1-0.dll - os=4.0 img=0.0 sys=5.2 "cyggarcon-1-0.dll" v0.0 ts=2013-07-24 23:09 69k 2014/11/02 C:\cygwin64\bin\cyggcc_s-seh-1.dll - os=4.0 img=0.0 sys=5.2 "cyggcc_s-seh-1.dll" v0.0 ts=2014-11-01 23:00 176k 2014/03/20 C:\cygwin64\bin\cyggck-1-0.dll - os=4.0 img=0.0 sys=5.2 "cyggck-1-0.dll" v0.0 ts=2014-03-20 03:06 470k 2014/03/20 C:\cygwin64\bin\cyggcr-base-3-1.dll - os=4.0 img=0.0 sys=5.2 "cyggcr-base-3-1.dll" v0.0 ts=2014-03-20 03:07 357k 2014/03/20 C:\cygwin64\bin\cyggcr-ui-3-1.dll - os=4.0 img=0.0 sys=5.2 "cyggcr-ui-3-1.dll" v0.0 ts=2014-03-20 03:09 470k 2014/06/01 C:\cygwin64\bin\cyggcrypt-11.dll - os=4.0 img=0.0 sys=5.2 "cyggcrypt-11.dll" v0.0 ts=1970-01-01 00:00 40k 2014/05/27 C:\cygwin64\bin\cyggdbm-4.dll - os=4.0 img=0.0 sys=5.2 "cyggdbm-4.dll" v0.0 ts=1970-01-01 00:00 13k 2014/05/27 C:\cygwin64\bin\cyggdbm_compat-4.dll - os=4.0 img=0.0 sys=5.2 "cyggdbm_compat-4.dll" v0.0 ts=1970-01-01 00:00 218k 2013/07/22 C:\cygwin64\bin\cyggdk-1-2-0.dll - os=4.0 img=0.0 sys=5.2 "cyggdk-1-2-0.dll" v0.0 ts=2013-07-22 04:00 548k 2014/07/17 C:\cygwin64\bin\cyggdk-3-0.dll - os=4.0 img=0.0 sys=5.2 "cyggdk-3-0.dll" v0.0 ts=1970-01-01 00:00 602k 2014/12/01 C:\cygwin64\bin\cyggdk-x11-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggdk-x11-2.0-0.dll" v0.0 ts=2014-12-01 19:37 159k 2013/07/22 C:\cygwin64\bin\cyggdk_imlib-1.dll - os=4.0 img=0.0 sys=5.2 "cyggdk_imlib-1.dll" v0.0 ts=2013-07-22 05:26 215k 2014/03/12 C:\cygwin64\bin\cyggdk_pixbuf-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggdk_pixbuf-2.0-0.dll" v0.0 ts=2014-03-12 08:07 67k 2013/06/19 C:\cygwin64\bin\cyggeoclue-0.dll - os=4.0 img=0.0 sys=5.2 "cyggeoclue-0.dll" v0.0 ts=2013-06-19 23:42 32k 2013/07/22 C:\cygwin64\bin\cyggif-4.dll - os=4.0 img=0.0 sys=5.2 "cyggif-4.dll" v0.0 ts=2013-07-22 05:17 1188k 2014/09/12 C:\cygwin64\bin\cyggio-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggio-2.0-0.dll" v0.0 ts=2014-09-12 20:38 594k 2014/12/09 C:\cygwin64\bin\cygGL-1.dll - os=4.0 img=0.0 sys=5.2 "cygGL-1.dll" v0.0 ts=2014-12-09 20:35 250k 2014/12/09 C:\cygwin64\bin\cygglapi-0.dll - os=4.0 img=0.0 sys=5.2 "cygglapi-0.dll" v0.0 ts=2014-12-09 20:29 25k 2014/12/09 C:\cygwin64\bin\cygGLESv1_CM-1.dll - os=4.0 img=0.0 sys=5.2 "cygGLESv1_CM-1.dll" v0.0 ts=2014-12-09 20:29 38k 2014/12/09 C:\cygwin64\bin\cygGLESv2-2.dll - os=4.0 img=0.0 sys=5.2 "cygGLESv2-2.dll" v0.0 ts=2014-12-09 20:29 149k 2013/07/22 C:\cygwin64\bin\cygglib-1-2-0.dll - os=4.0 img=0.0 sys=5.2 "cygglib-1-2-0.dll" v0.0 ts=2013-07-22 03:11 903k 2014/09/12 C:\cygwin64\bin\cygglib-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygglib-2.0-0.dll" v0.0 ts=2014-09-12 20:35 477k 2013/04/09 C:\cygwin64\bin\cygGLU-1.dll - os=4.0 img=0.0 sys=5.2 "cygGLU-1.dll" v0.0 ts=2013-04-09 07:56 220k 2013/04/09 C:\cygwin64\bin\cygglut-3.dll - os=4.0 img=0.0 sys=5.2 "cygglut-3.dll" v0.0 ts=2013-04-09 08:57 22k 2013/07/07 C:\cygwin64\bin\cygGLw-1.dll - os=4.0 img=0.0 sys=5.2 "cygGLw-1.dll" v0.0 ts=2013-07-07 23:57 13k 2013/07/22 C:\cygwin64\bin\cyggmodule-1-2-0.dll - os=4.0 img=0.0 sys=5.2 "cyggmodule-1-2-0.dll" v0.0 ts=2013-07-22 03:11 14k 2014/09/12 C:\cygwin64\bin\cyggmodule-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggmodule-2.0-0.dll" v0.0 ts=2014-09-12 20:35 516k 2014/04/05 C:\cygwin64\bin\cyggmp-10.dll - os=4.0 img=0.0 sys=5.2 "cyggmp-10.dll" v0.0 ts=1970-01-01 00:00 880k 2014/11/19 C:\cygwin64\bin\cyggnutls-28.dll - os=4.0 img=0.0 sys=5.2 "cyggnutls-28.dll" v0.0 ts=2014-11-19 10:20 25k 2014/11/19 C:\cygwin64\bin\cyggnutls-openssl-27.dll - os=4.0 img=0.0 sys=5.2 "cyggnutls-openssl-27.dll" v0.0 ts=2014-11-19 10:21 22k 2014/11/19 C:\cygwin64\bin\cyggnutls-xssl-0.dll - os=4.0 img=0.0 sys=5.2 "cyggnutls-xssl-0.dll" v0.0 ts=2014-11-19 10:20 43k 2014/11/19 C:\cygwin64\bin\cyggnutlsxx-28.dll - os=4.0 img=0.0 sys=5.2 "cyggnutlsxx-28.dll" v0.0 ts=2014-11-19 10:20 277k 2014/09/12 C:\cygwin64\bin\cyggobject-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggobject-2.0-0.dll" v0.0 ts=2014-09-12 20:36 19k 2014/06/01 C:\cygwin64\bin\cyggpg-error-0.dll - os=4.0 img=0.0 sys=5.2 "cyggpg-error-0.dll" v0.0 ts=1970-01-01 00:00 116k 2013/08/05 C:\cygwin64\bin\cyggraphite2-3.dll - os=4.0 img=3.0 sys=5.2 "cyggraphite2-3.dll" v0.0 ts=2013-08-05 07:33 253k 2014/09/19 C:\cygwin64\bin\cyggssapi_krb5-2.dll - os=4.0 img=0.0 sys=5.2 "cyggssapi_krb5-2.dll" v0.0 ts=2014-09-19 18:42 13k 2014/11/30 C:\cygwin64\bin\cyggstallocators-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstallocators-1.0-0.dll" v0.0 ts=2014-11-30 05:25 43k 2014/11/30 C:\cygwin64\bin\cyggstapp-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstapp-1.0-0.dll" v0.0 ts=2014-11-30 05:24 261k 2014/11/30 C:\cygwin64\bin\cyggstaudio-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstaudio-1.0-0.dll" v0.0 ts=2014-11-30 05:24 314k 2014/11/18 C:\cygwin64\bin\cyggstbase-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstbase-1.0-0.dll" v0.0 ts=2014-11-18 18:19 53k 2014/11/18 C:\cygwin64\bin\cyggstcontroller-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstcontroller-1.0-0.dll" v0.0 ts=2014-11-18 18:19 40k 2014/11/30 C:\cygwin64\bin\cyggstfft-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstfft-1.0-0.dll" v0.0 ts=2014-11-30 05:24 29k 2014/11/18 C:\cygwin64\bin\cyggstnet-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstnet-1.0-0.dll" v0.0 ts=2014-11-18 18:19 124k 2014/11/30 C:\cygwin64\bin\cyggstpbutils-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstpbutils-1.0-0.dll" v0.0 ts=2014-11-30 05:25 869k 2014/11/18 C:\cygwin64\bin\cyggstreamer-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstreamer-1.0-0.dll" v0.0 ts=2014-11-18 18:19 52k 2014/11/30 C:\cygwin64\bin\cyggstriff-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstriff-1.0-0.dll" v0.0 ts=2014-11-30 05:25 84k 2014/11/30 C:\cygwin64\bin\cyggstrtp-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstrtp-1.0-0.dll" v0.0 ts=2014-11-30 05:24 88k 2014/11/30 C:\cygwin64\bin\cyggstrtsp-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstrtsp-1.0-0.dll" v0.0 ts=2014-11-30 05:25 36k 2014/11/30 C:\cygwin64\bin\cyggstsdp-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstsdp-1.0-0.dll" v0.0 ts=2014-11-30 05:24 202k 2014/11/30 C:\cygwin64\bin\cyggsttag-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggsttag-1.0-0.dll" v0.0 ts=2014-11-30 05:24 241k 2014/11/30 C:\cygwin64\bin\cyggstvideo-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggstvideo-1.0-0.dll" v0.0 ts=2014-11-30 05:24 12k 2013/07/22 C:\cygwin64\bin\cyggthread-1-2-0.dll - os=4.0 img=0.0 sys=5.2 "cyggthread-1-2-0.dll" v0.0 ts=2013-07-22 03:11 9k 2014/09/12 C:\cygwin64\bin\cyggthread-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggthread-2.0-0.dll" v0.0 ts=2014-09-12 20:36 1282k 2013/07/22 C:\cygwin64\bin\cyggtk-1-2-0.dll - os=4.0 img=0.0 sys=5.2 "cyggtk-1-2-0.dll" v0.0 ts=2013-07-22 04:01 4721k 2014/07/17 C:\cygwin64\bin\cyggtk-3-0.dll - os=4.0 img=0.0 sys=5.2 "cyggtk-3-0.dll" v0.0 ts=1970-01-01 00:00 3930k 2014/12/01 C:\cygwin64\bin\cyggtk-x11-2.0-0.dll - os=4.0 img=0.0 sys=5.2 "cyggtk-x11-2.0-0.dll" v0.0 ts=2014-12-01 19:40 178k 2014/03/23 C:\cygwin64\bin\cyggvfscommon-0.dll - os=4.0 img=0.0 sys=5.2 "cyggvfscommon-0.dll" v0.0 ts=2014-03-23 20:48 316k 2014/01/09 C:\cygwin64\bin\cygharfbuzz-0.dll - os=4.0 img=0.0 sys=5.2 "cygharfbuzz-0.dll" v0.0 ts=2014-01-09 07:16 10k 2014/01/09 C:\cygwin64\bin\cygharfbuzz-icu-0.dll - os=4.0 img=0.0 sys=5.2 "cygharfbuzz-icu-0.dll" v0.0 ts=2014-01-09 07:16 29k 2013/03/14 C:\cygwin64\bin\cyghistory7.dll - os=4.0 img=0.0 sys=5.2 "cyghistory7.dll" v0.0 ts=2013-03-14 11:14 166k 2013/05/14 C:\cygwin64\bin\cyghogweed-2.dll - os=4.0 img=0.0 sys=5.2 "cyghogweed-2.dll" v0.0 ts=2013-05-14 07:42 77k 2014/08/10 C:\cygwin64\bin\cygICE-6.dll - os=4.0 img=0.0 sys=5.2 "cygICE-6.dll" v0.0 ts=1970-01-01 00:00 998k 2013/03/07 C:\cygwin64\bin\cygiconv-2.dll - os=4.0 img=0.0 sys=5.2 "cygiconv-2.dll" v0.0 ts=2013-03-07 03:03 21806k 2013/06/25 C:\cygwin64\bin\cygicudata51.dll - os=4.0 img=0.0 sys=5.2 "cygicudata51.dll" v0.0 ts=2013-06-25 06:30 1717k 2013/06/25 C:\cygwin64\bin\cygicui18n51.dll - os=4.0 img=0.0 sys=5.2 "cygicui18n51.dll" v0.0 ts=2013-06-25 06:28 43k 2013/06/25 C:\cygwin64\bin\cygicuio51.dll - os=4.0 img=0.0 sys=5.2 "cygicuio51.dll" v0.0 ts=2013-06-25 06:30 305k 2013/06/25 C:\cygwin64\bin\cygicule51.dll - os=4.0 img=0.0 sys=5.2 "cygicule51.dll" v0.0 ts=2013-06-25 06:28 38k 2013/06/25 C:\cygwin64\bin\cygiculx51.dll - os=4.0 img=0.0 sys=5.2 "cygiculx51.dll" v0.0 ts=2013-06-25 06:28 49k 2013/06/25 C:\cygwin64\bin\cygicutest51.dll - os=4.0 img=0.0 sys=5.2 "cygicutest51.dll" v0.0 ts=2013-06-25 06:29 140k 2013/06/25 C:\cygwin64\bin\cygicutu51.dll - os=4.0 img=0.0 sys=5.2 "cygicutu51.dll" v0.0 ts=2013-06-25 06:29 1231k 2013/06/25 C:\cygwin64\bin\cygicuuc51.dll - os=4.0 img=0.0 sys=5.2 "cygicuuc51.dll" v0.0 ts=2013-06-25 06:27 39k 2014/11/18 C:\cygwin64\bin\cygintl-8.dll - os=4.0 img=0.0 sys=5.2 "cygintl-8.dll" v0.0 ts=2014-11-18 07:04 273k 2014/12/08 C:\cygwin64\bin\cygjasper-1.dll - os=4.0 img=0.0 sys=5.2 "cygjasper-1.dll" v0.0 ts=2014-12-08 11:05 3389k 2014/07/11 C:\cygwin64\bin\cygjavascriptcoregtk-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygjavascriptcoregtk-1.0-0.dll" v0.0 ts=1970-01-01 00:00 48k 2014/06/17 C:\cygwin64\bin\cygjbig-2.dll - os=4.0 img=0.0 sys=5.2 "cygjbig-2.dll" v0.0 ts=1970-01-01 00:00 18k 2014/06/17 C:\cygwin64\bin\cygjbig85-2.dll - os=4.0 img=0.0 sys=5.2 "cygjbig85-2.dll" v0.0 ts=1970-01-01 00:00 256k 2014/05/26 C:\cygwin64\bin\cygjpeg-8.dll - os=4.0 img=0.0 sys=5.2 "cygjpeg-8.dll" v0.0 ts=1970-01-01 00:00 179k 2014/09/19 C:\cygwin64\bin\cygk5crypto-3.dll - os=4.0 img=0.0 sys=5.2 "cygk5crypto-3.dll" v0.0 ts=2014-09-19 18:41 701k 2014/09/19 C:\cygwin64\bin\cygkrb5-3.dll - os=4.0 img=0.0 sys=5.2 "cygkrb5-3.dll" v0.0 ts=2014-09-19 18:42 35k 2014/09/19 C:\cygwin64\bin\cygkrb5support-0.dll - os=4.0 img=0.0 sys=5.2 "cygkrb5support-0.dll" v0.0 ts=2014-09-19 18:41 188k 2013/04/10 C:\cygwin64\bin\cyglcms-1.dll - os=4.0 img=0.0 sys=5.2 "cyglcms-1.dll" v0.0 ts=2013-04-10 12:13 17273k 2014/10/29 C:\cygwin64\bin\cygLLVM-3.4.dll - os=4.0 img=0.0 sys=5.2 "cygLLVM-3.4.dll" v0.0 ts=2014-10-28 23:39 6k 2014/11/13 C:\cygwin64\bin\cyglsa64.dll - os=4.0 img=0.0 sys=5.2 "cyglsa64.dll" v0.0 ts=2014-11-13 14:47 129k 2014/05/29 C:\cygwin64\bin\cyglzma-5.dll - os=4.0 img=0.0 sys=5.2 "cyglzma-5.dll" v0.0 ts=1970-01-01 00:00 126k 2014/11/17 C:\cygwin64\bin\cyglzo2-2.dll - os=4.0 img=0.0 sys=5.2 "cyglzo2-2.dll" v0.0 ts=2014-11-17 11:24 107k 2014/10/29 C:\cygwin64\bin\cygmagic-1.dll - os=4.0 img=0.0 sys=5.2 "cygmagic-1.dll" v0.0 ts=2014-10-29 20:44 158k 2014/08/12 C:\cygwin64\bin\cygman-2-6-7.dll - os=4.0 img=0.0 sys=5.2 "cygman-2-6-7.dll" v0.0 ts=1970-01-01 00:00 132k 2014/01/21 C:\cygwin64\bin\cygmcpp-0.dll - os=4.0 img=0.0 sys=5.2 "cygmcpp-0.dll" v0.0 ts=2014-01-21 18:41 29k 2014/12/14 C:\cygwin64\bin\cygmenuw-10.dll - os=4.0 img=0.0 sys=5.2 "cygmenuw-10.dll" v0.0 ts=2014-12-14 23:12 710k 2014/07/18 C:\cygwin64\bin\cygmidori-core-1.dll - os=4.0 img=0.0 sys=5.2 "cygmidori-core-1.dll" v0.0 ts=1970-01-01 00:00 370k 2013/05/02 C:\cygwin64\bin\cygmng-1.dll - os=4.0 img=0.0 sys=5.2 "cygmng-1.dll" v0.0 ts=2013-05-02 12:20 319k 2013/05/05 C:\cygwin64\bin\cygmpfr-4.dll - os=4.0 img=0.0 sys=5.2 "cygmpfr-4.dll" v0.0 ts=2013-05-05 13:40 119k 2014/08/10 C:\cygwin64\bin\cygMrm-4.dll - os=4.0 img=0.0 sys=5.2 "cygMrm-4.dll" v0.0 ts=1970-01-01 00:00 479k 2014/12/30 C:\cygwin64\bin\cygnativeGLthunk.dll - os=4.0 img=0.0 sys=5.2 "cygnativeGLthunk.dll" v0.0 ts=2014-12-30 15:42 52k 2014/12/14 C:\cygwin64\bin\cygncurses++w-10.dll - os=4.0 img=0.0 sys=5.2 "cygncurses++w-10.dll" v0.0 ts=2014-12-14 23:15 296k 2014/12/14 C:\cygwin64\bin\cygncursesw-10.dll - os=4.0 img=0.0 sys=5.2 "cygncursesw-10.dll" v0.0 ts=2014-12-14 23:12 177k 2013/05/14 C:\cygwin64\bin\cygnettle-4.dll - os=4.0 img=0.0 sys=5.2 "cygnettle-4.dll" v0.0 ts=2013-05-14 07:42 25k 2014/03/12 C:\cygwin64\bin\cygnotify-4.dll - os=4.0 img=0.0 sys=5.2 "cygnotify-4.dll" v0.0 ts=2014-03-12 21:45 30k 2014/12/09 C:\cygwin64\bin\cygOpenVG-1.dll - os=4.0 img=0.0 sys=5.2 "cygOpenVG-1.dll" v0.0 ts=2014-12-09 20:30 474k 2013/11/12 C:\cygwin64\bin\cygorc-0.4-0.dll - os=4.0 img=0.0 sys=5.2 "cygorc-0.4-0.dll" v0.0 ts=2013-11-12 10:46 27k 2013/11/12 C:\cygwin64\bin\cygorc-test-0.4-0.dll - os=4.0 img=0.0 sys=5.2 "cygorc-test-0.4-0.dll" v0.0 ts=2013-11-12 10:46 3687k 2014/12/09 C:\cygwin64\bin\cygOSMesa-8.dll - os=4.0 img=0.0 sys=5.2 "cygOSMesa-8.dll" v0.0 ts=2014-12-09 20:34 220k 2014/10/19 C:\cygwin64\bin\cygp11-kit-0.dll - os=4.0 img=0.0 sys=5.2 "cygp11-kit-0.dll" v0.0 ts=2014-10-19 14:36 14k 2014/12/14 C:\cygwin64\bin\cygpanelw-10.dll - os=4.0 img=0.0 sys=5.2 "cygpanelw-10.dll" v0.0 ts=2014-12-14 23:12 261k 2014/03/20 C:\cygwin64\bin\cygpango-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygpango-1.0-0.dll" v0.0 ts=2014-03-20 10:59 41k 2014/03/20 C:\cygwin64\bin\cygpangocairo-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygpangocairo-1.0-0.dll" v0.0 ts=2014-03-20 10:59 69k 2014/03/20 C:\cygwin64\bin\cygpangoft2-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygpangoft2-1.0-0.dll" v0.0 ts=2014-03-20 10:59 27k 2014/03/20 C:\cygwin64\bin\cygpangoxft-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygpangoxft-1.0-0.dll" v0.0 ts=2014-03-20 10:59 280k 2014/12/08 C:\cygwin64\bin\cygpcre-1.dll - os=4.0 img=0.0 sys=5.2 "cygpcre-1.dll" v0.0 ts=2014-12-08 23:50 257k 2014/12/08 C:\cygwin64\bin\cygpcre16-0.dll - os=4.0 img=0.0 sys=5.2 "cygpcre16-0.dll" v0.0 ts=2014-12-08 23:50 250k 2014/12/08 C:\cygwin64\bin\cygpcre32-0.dll - os=4.0 img=0.0 sys=5.2 "cygpcre32-0.dll" v0.0 ts=2014-12-08 23:50 31k 2014/12/08 C:\cygwin64\bin\cygpcrecpp-0.dll - os=4.0 img=0.0 sys=5.2 "cygpcrecpp-0.dll" v0.0 ts=2014-12-08 23:50 11k 2014/12/08 C:\cygwin64\bin\cygpcreposix-0.dll - os=4.0 img=0.0 sys=5.2 "cygpcreposix-0.dll" v0.0 ts=2014-12-08 23:50 1580k 2013/03/11 C:\cygwin64\bin\cygperl5_14.dll - os=4.0 img=0.0 sys=5.2 "cygperl5_14.dll" v0.0 ts=2013-03-12 00:25 38k 2014/05/12 C:\cygwin64\bin\cygpipeline-1.dll - os=4.0 img=0.0 sys=5.2 "cygpipeline-1.dll" v0.0 ts=1970-01-01 00:00 654k 2014/11/16 C:\cygwin64\bin\cygpixman-1-0.dll - os=4.0 img=0.0 sys=5.2 "cygpixman-1-0.dll" v0.0 ts=2014-11-16 22:16 148k 2014/05/26 C:\cygwin64\bin\cygpng15-15.dll - os=4.0 img=0.0 sys=5.2 "cygpng15-15.dll" v0.0 ts=1970-01-01 00:00 41k 2013/10/21 C:\cygwin64\bin\cygpopt-0.dll - os=4.0 img=0.0 sys=5.2 "cygpopt-0.dll" v0.0 ts=2013-10-21 21:52 122k 2013/04/21 C:\cygwin64\bin\cygproxy-1.dll - os=4.0 img=1.0 sys=5.2 "cygproxy-1.dll" v0.0 ts=2013-04-21 10:24 8k 2013/04/30 C:\cygwin64\bin\cygpspell-15.dll - os=4.0 img=0.0 sys=5.2 "cygpspell-15.dll" v0.0 ts=2013-04-30 08:12 2696k 2014/11/30 C:\cygwin64\bin\cygQtCore-4.dll - os=4.0 img=0.0 sys=5.2 "cygQtCore-4.dll" v0.0 ts=2014-11-30 09:30 9969k 2014/11/30 C:\cygwin64\bin\cygQtGui-4.dll - os=4.0 img=0.0 sys=5.2 "cygQtGui-4.dll" v0.0 ts=2014-11-30 09:39 945k 2014/11/30 C:\cygwin64\bin\cygQtOpenGL-4.dll - os=4.0 img=0.0 sys=5.2 "cygQtOpenGL-4.dll" v0.0 ts=2014-11-30 09:43 248k 2014/11/30 C:\cygwin64\bin\cygQtXml-4.dll - os=4.0 img=0.0 sys=5.2 "cygQtXml-4.dll" v0.0 ts=2014-11-30 09:31 193k 2013/03/14 C:\cygwin64\bin\cygreadline7.dll - os=4.0 img=0.0 sys=5.2 "cygreadline7.dll" v0.0 ts=2013-03-14 11:14 200k 2014/03/12 C:\cygwin64\bin\cygrsvg-2-2.dll - os=4.0 img=0.0 sys=5.2 "cygrsvg-2-2.dll" v0.0 ts=2014-03-13 00:52 248k 2014/03/12 C:\cygwin64\bin\cygsecret-1-0.dll - os=4.0 img=0.0 sys=5.2 "cygsecret-1-0.dll" v0.0 ts=2014-03-12 21:29 28k 2014/01/14 C:\cygwin64\bin\cygSM-6.dll - os=4.0 img=0.0 sys=5.2 "cygSM-6.dll" v0.0 ts=2014-01-14 23:23 88k 2014/12/01 C:\cygwin64\bin\cygsmartcols-1.dll - os=4.0 img=0.0 sys=5.2 "cygsmartcols-1.dll" v0.0 ts=2014-12-01 23:56 564k 2014/04/02 C:\cygwin64\bin\cygsoup-2.4-1.dll - os=4.0 img=0.0 sys=5.2 "cygsoup-2.4-1.dll" v0.0 ts=1970-01-01 00:00 12k 2014/04/02 C:\cygwin64\bin\cygsoup-gnome-2.4-1.dll - os=4.0 img=0.0 sys=5.2 "cygsoup-gnome-2.4-1.dll" v0.0 ts=1970-01-01 00:00 743k 2014/12/09 C:\cygwin64\bin\cygsqlite3-0.dll - os=4.0 img=0.0 sys=5.2 "cygsqlite3-0.dll" v0.0 ts=2014-12-09 15:20 382k 2015/01/08 C:\cygwin64\bin\cygssl-1.0.0.dll - os=4.0 img=0.0 sys=5.2 "cygssl-1.0.0.dll" v0.0 ts=2015-01-08 20:02 12k 2014/11/02 C:\cygwin64\bin\cygssp-0.dll - os=4.0 img=0.0 sys=5.2 "cygssp-0.dll" v0.0 ts=2014-11-01 23:51 30k 2013/06/05 C:\cygwin64\bin\cygstartup-notification-1-0.dll - os=4.0 img=0.0 sys=5.2 "cygstartup-notification-1-0.dll" v0.0 ts=2013-06-06 00:39 941k 2014/11/02 C:\cygwin64\bin\cygstdc++-6.dll - os=4.0 img=0.0 sys=5.2 "cygstdc++-6.dll" v0.0 ts=2014-11-01 23:14 64k 2014/11/13 C:\cygwin64\bin\cygtasn1-6.dll - os=4.0 img=0.0 sys=5.2 "cygtasn1-6.dll" v0.0 ts=2014-11-13 18:20 32k 2014/11/12 C:\cygwin64\bin\cygthai-0.dll - os=4.0 img=0.0 sys=5.2 "cygthai-0.dll" v0.0 ts=2014-11-12 16:31 38k 2014/03/20 C:\cygwin64\bin\cygthunarx-2-0.dll - os=4.0 img=0.0 sys=5.2 "cygthunarx-2-0.dll" v0.0 ts=2014-03-20 02:26 52k 2014/12/14 C:\cygwin64\bin\cygticw-10.dll - os=4.0 img=0.0 sys=5.2 "cygticw-10.dll" v0.0 ts=2014-12-14 23:12 363k 2014/05/15 C:\cygwin64\bin\cygtiff-5.dll - os=4.0 img=0.0 sys=5.2 "cygtiff-5.dll" v0.0 ts=1970-01-01 00:00 415k 2014/05/30 C:\cygwin64\bin\cygtiff-6.dll - os=4.0 img=0.0 sys=5.2 "cygtiff-6.dll" v0.0 ts=1970-01-01 00:00 12k 2014/05/15 C:\cygwin64\bin\cygtiffxx-5.dll - os=4.0 img=0.0 sys=5.2 "cygtiffxx-5.dll" v0.0 ts=1970-01-01 00:00 12k 2014/05/30 C:\cygwin64\bin\cygtiffxx-6.dll - os=4.0 img=0.0 sys=5.2 "cygtiffxx-6.dll" v0.0 ts=1970-01-01 00:00 363k 2014/08/10 C:\cygwin64\bin\cygUil-4.dll - os=4.0 img=0.0 sys=5.2 "cygUil-4.dll" v0.0 ts=1970-01-01 00:00 15k 2014/12/01 C:\cygwin64\bin\cyguuid-1.dll - os=4.0 img=0.0 sys=5.2 "cyguuid-1.dll" v0.0 ts=2014-12-01 23:56 572k 2013/06/24 C:\cygwin64\bin\cygvte-9.dll - os=4.0 img=0.0 sys=5.2 "cygvte-9.dll" v0.0 ts=2013-06-24 03:45 24009k 2014/07/11 C:\cygwin64\bin\cygwebkitgtk-1.0-0.dll - os=4.0 img=0.0 sys=5.2 "cygwebkitgtk-1.0-0.dll" v0.0 ts=1970-01-01 00:00 310k 2014/03/13 C:\cygwin64\bin\cygwebp-5.dll - os=4.0 img=0.0 sys=5.2 "cygwebp-5.dll" v0.0 ts=2014-03-14 00:12 208k 2013/06/24 C:\cygwin64\bin\cygwnck-1-22.dll - os=4.0 img=0.0 sys=5.2 "cygwnck-1-22.dll" v0.0 ts=2013-06-24 02:39 30k 2013/11/15 C:\cygwin64\bin\cygwrap-0.dll - os=4.0 img=0.0 sys=5.2 "cygwrap-0.dll" v0.0 ts=2013-11-15 19:58 1121k 2014/10/21 C:\cygwin64\bin\cygX11-6.dll - os=4.0 img=0.0 sys=5.2 "cygX11-6.dll" v0.0 ts=2014-10-21 02:59 9k 2014/10/21 C:\cygwin64\bin\cygX11-xcb-1.dll - os=4.0 img=0.0 sys=5.2 "cygX11-xcb-1.dll" v0.0 ts=2014-10-21 02:59 12k 2013/06/06 C:\cygwin64\bin\cygXau-6.dll - os=4.0 img=0.0 sys=5.2 "cygXau-6.dll" v0.0 ts=2013-06-06 06:23 368k 2014/08/10 C:\cygwin64\bin\cygXaw-7.dll - os=4.0 img=0.0 sys=5.2 "cygXaw-7.dll" v0.0 ts=1970-01-01 00:00 102k 2014/05/20 C:\cygwin64\bin\cygxcb-1.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-1.dll" v0.0 ts=1970-01-01 00:00 71k 2014/05/20 C:\cygwin64\bin\cygxcb-glx-0.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-glx-0.dll" v0.0 ts=1970-01-01 00:00 17k 2014/08/10 C:\cygwin64\bin\cygxcb-icccm-4.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-icccm-4.dll" v0.0 ts=1970-01-01 00:00 16k 2013/03/17 C:\cygwin64\bin\cygxcb-image-0.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-image-0.dll" v0.0 ts=2013-03-17 22:42 11k 2013/08/01 C:\cygwin64\bin\cygxcb-keysyms-1.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-keysyms-1.dll" v0.0 ts=2013-08-01 08:15 32k 2014/05/20 C:\cygwin64\bin\cygxcb-render-0.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-render-0.dll" v0.0 ts=1970-01-01 00:00 14k 2014/05/20 C:\cygwin64\bin\cygxcb-shape-0.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-shape-0.dll" v0.0 ts=1970-01-01 00:00 13k 2014/05/20 C:\cygwin64\bin\cygxcb-shm-0.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-shm-0.dll" v0.0 ts=1970-01-01 00:00 17k 2013/03/17 C:\cygwin64\bin\cygxcb-util-1.dll - os=4.0 img=0.0 sys=5.2 "cygxcb-util-1.dll" v0.0 ts=2013-03-17 22:33 11k 2013/03/18 C:\cygwin64\bin\cygXcomposite-1.dll - os=4.0 img=0.0 sys=5.2 "cygXcomposite-1.dll" v0.0 ts=2013-03-18 23:05 34k 2013/06/06 C:\cygwin64\bin\cygXcursor-1.dll - os=4.0 img=0.0 sys=5.2 "cygXcursor-1.dll" v0.0 ts=2013-06-06 21:15 10k 2013/04/08 C:\cygwin64\bin\cygXdamage-1.dll - os=4.0 img=0.0 sys=5.2 "cygXdamage-1.dll" v0.0 ts=2013-04-08 22:24 21k 2013/03/13 C:\cygwin64\bin\cygXdmcp-6.dll - os=4.0 img=0.0 sys=5.2 "cygXdmcp-6.dll" v0.0 ts=2013-03-13 04:58 56k 2014/08/10 C:\cygwin64\bin\cygXext-6.dll - os=4.0 img=0.0 sys=5.2 "cygXext-6.dll" v0.0 ts=1970-01-01 00:00 32k 2013/07/24 C:\cygwin64\bin\cygxfce4kbd-private-2-0.dll - os=4.0 img=0.0 sys=5.2 "cygxfce4kbd-private-2-0.dll" v0.0 ts=2013-07-25 00:01 76k 2013/07/25 C:\cygwin64\bin\cygxfce4panel-1.0-4.dll - os=4.0 img=0.0 sys=5.2 "cygxfce4panel-1.0-4.dll" v0.0 ts=2013-07-25 01:28 59k 2013/07/24 C:\cygwin64\bin\cygxfce4ui-1-0.dll - os=4.0 img=0.0 sys=5.2 "cygxfce4ui-1-0.dll" v0.0 ts=2013-07-25 00:01 46k 2013/07/25 C:\cygwin64\bin\cygxfce4util-6.dll - os=4.0 img=0.0 sys=5.2 "cygxfce4util-6.dll" v0.0 ts=2013-07-25 03:02 61k 2013/07/24 C:\cygwin64\bin\cygxfconf-0-2.dll - os=4.0 img=0.0 sys=5.2 "cygxfconf-0-2.dll" v0.0 ts=2013-07-24 23:45 19k 2013/06/06 C:\cygwin64\bin\cygXfixes-3.dll - os=4.0 img=0.0 sys=5.2 "cygXfixes-3.dll" v0.0 ts=2013-06-06 20:27 205k 2014/08/10 C:\cygwin64\bin\cygXfont-1.dll - os=4.0 img=0.0 sys=5.2 "cygXfont-1.dll" v0.0 ts=1970-01-01 00:00 14k 2014/11/27 C:\cygwin64\bin\cygxfsm-4.6-0.dll - os=4.0 img=0.0 sys=5.2 "cygxfsm-4.6-0.dll" v0.0 ts=2014-11-27 20:21 73k 2014/08/10 C:\cygwin64\bin\cygXft-2.dll - os=4.0 img=0.0 sys=5.2 "cygXft-2.dll" v0.0 ts=1970-01-01 00:00 56k 2014/08/10 C:\cygwin64\bin\cygXi-6.dll - os=4.0 img=0.0 sys=5.2 "cygXi-6.dll" v0.0 ts=1970-01-01 00:00 10k 2013/06/06 C:\cygwin64\bin\cygXinerama-1.dll - os=4.0 img=0.0 sys=5.2 "cygXinerama-1.dll" v0.0 ts=2013-06-06 21:33 125k 2013/04/08 C:\cygwin64\bin\cygxkbfile-1.dll - os=4.0 img=0.0 sys=5.2 "cygxkbfile-1.dll" v0.0 ts=2013-04-08 21:24 89k 2013/07/24 C:\cygwin64\bin\cygxklavier-16.dll - os=4.0 img=0.0 sys=5.2 "cygxklavier-16.dll" v0.0 ts=2013-07-24 07:40 2274k 2014/08/10 C:\cygwin64\bin\cygXm-4.dll - os=4.0 img=0.0 sys=5.2 "cygXm-4.dll" v0.0 ts=1970-01-01 00:00 1207k 2014/10/19 C:\cygwin64\bin\cygxml2-2.dll - os=4.0 img=0.0 sys=5.2 "cygxml2-2.dll" v0.0 ts=2014-10-19 08:52 85k 2014/01/15 C:\cygwin64\bin\cygXmu-6.dll - os=4.0 img=0.0 sys=5.2 "cygXmu-6.dll" v0.0 ts=2014-01-15 02:27 14k 2014/01/15 C:\cygwin64\bin\cygXmuu-1.dll - os=4.0 img=0.0 sys=5.2 "cygXmuu-1.dll" v0.0 ts=2014-01-15 02:27 59k 2014/01/15 C:\cygwin64\bin\cygXpm-4.dll - os=4.0 img=0.0 sys=5.2 "cygXpm-4.dll" v0.0 ts=2014-01-15 00:59 34k 2014/01/14 C:\cygwin64\bin\cygXrandr-2.dll - os=4.0 img=0.0 sys=5.2 "cygXrandr-2.dll" v0.0 ts=2014-01-14 23:56 35k 2013/06/14 C:\cygwin64\bin\cygXrender-1.dll - os=4.0 img=0.0 sys=5.2 "cygXrender-1.dll" v0.0 ts=2013-06-14 09:29 10k 2013/06/06 C:\cygwin64\bin\cygXRes-1.dll - os=4.0 img=0.0 sys=5.2 "cygXRes-1.dll" v0.0 ts=2013-06-06 21:47 207k 2013/09/02 C:\cygwin64\bin\cygxslt-1.dll - os=4.0 img=0.0 sys=5.2 "cygxslt-1.dll" v0.0 ts=2013-09-02 17:55 12k 2013/03/14 C:\cygwin64\bin\cygXss-1.dll - os=4.0 img=0.0 sys=5.2 "cygXss-1.dll" v0.0 ts=2013-03-14 04:07 320k 2014/08/10 C:\cygwin64\bin\cygXt-6.dll - os=4.0 img=0.0 sys=5.2 "cygXt-6.dll" v0.0 ts=1970-01-01 00:00 21k 2013/06/06 C:\cygwin64\bin\cygXtst-6.dll - os=4.0 img=0.0 sys=5.2 "cygXtst-6.dll" v0.0 ts=2013-06-06 20:36 80k 2014/11/19 C:\cygwin64\bin\cygz.dll - os=4.0 img=0.0 sys=5.2 "cygz.dll" v0.0 ts=2014-11-19 23:08 105k 2013/07/25 C:\cygwin64\bin\cygzeitgeist-1.0-1.dll - os=4.0 img=0.0 sys=5.2 "cygzeitgeist-1.0-1.dll" v0.0 ts=2013-07-25 09:19 3102k 2014/11/13 C:\cygwin64\bin\cygwin1.dll - os=4.0 img=0.0 sys=5.2 "cygwin1.dll" v0.0 ts=1970-01-01 00:00 Cygwin DLL version info: DLL version: 1.7.33 DLL epoch: 19 DLL old termios: 5 DLL malloc env: 28 Cygwin conv: 181 API major: 0 API minor: 280 Shared data: 5 DLL identifier: cygwin1 Mount registry: 3 Cygwin registry name: Cygwin Program options name: Program Options Installations name: Installations Cygdrive default prefix: Build date: Shared id: cygwin1S5 272k 2008/09/26 C:\GnuWin32\bin\cygicons.dll (not x86_64 dll) No Cygwin services found. Cygwin Package Information Last downloaded files to: D:\Users\Maarten\Downloads\Software\cygwin Last downloaded files from: ftp://ftp.snt.utwente.nl/pub/software/cygwin/ Package Version Status _autorebase 000321-1 OK _update-info-dir 00364-1 OK alternatives 1.3.30c-10 OK at-spi2-core 2.10.2-1 OK base-cygwin 3.5-1 OK base-files 4.2-3 OK bash 4.1.17-9 OK binutils 2.25-1 OK bzip2 1.0.6-2 OK ca-certificates 2.2-1 OK compositeproto 0.4.2-1 OK coreutils 8.23-4 OK csih 0.9.8-4 OK cygrunsrv 1.61-1 OK cygutils 1.4.14-1 OK cygutils-x11 1.4.14-1 OK cygwin 1.7.33-1 OK cygwin-debuginfo 1.7.33-1 OK cygwin-devel 1.7.33-1 OK damageproto 1.2.1-1 OK dash 0.5.8-3 OK dbus 1.8.12-1 OK dbus-x11 1.8.12-1 OK dconf-service 0.18.0-1 OK desktop-file-utils 0.21-1 OK diffutils 3.3-2 OK dri-drivers 10.3.5-1 OK editrights 1.03-1 OK exo 0.10.2-1 OK fbpanel 6.1-5 OK file 5.20-1 OK findutils 4.5.12-1 OK fixesproto 5.0-1 OK Empty package fltk fltk 1.3.2.9965-1 OK font-adobe-dpi75 1.0.2-1 OK font-adobe-utopia-dpi100 1.0.3-1 OK font-adobe-utopia-dpi75 1.0.3-1 OK font-adobe-utopia-type1 1.0.3-1 OK font-alias 1.0.3-1 OK font-arabic-misc 1.0.2-1 OK font-bh-dpi100 1.0.2-1 OK font-bh-dpi75 1.0.2-1 OK font-bh-lucidatypewriter-dpi100 1.0.2-1 OK font-bh-lucidatypewriter-dpi75 1.0.2-1 OK font-bh-ttf 1.0.3-1 OK font-bh-type1 1.0.2-1 OK font-bitstream-dpi100 1.0.2-1 OK font-bitstream-dpi75 1.0.2-1 OK font-bitstream-speedo 1.0.1-1 OK font-bitstream-type1 1.0.2-1 OK font-bitstream-vera-ttf 1.10-1 OK font-cantarell-otf 0.0.15-1 OK font-cronyx-cyrillic 1.0.2-1 OK font-cursor-misc 1.0.2-1 OK font-daewoo-misc 1.0.2-1 OK font-dec-misc 1.0.2-1 OK font-encodings 1.0.4-1 OK font-ibm-type1 1.0.2-1 OK font-isas-misc 1.0.2-1 OK font-jis-misc 1.0.2-1 OK font-micro-misc 1.0.2-1 OK font-misc-cyrillic 1.0.2-1 OK font-misc-ethiopic 1.0.2-1 OK font-misc-meltho 1.0.2-1 OK font-misc-misc 1.1.1-1 OK font-mutt-misc 1.0.2-1 OK font-schumacher-misc 1.1.1-1 OK font-screen-cyrillic 1.0.3-1 OK font-sony-misc 1.0.2-1 OK font-sun-misc 1.0.2-1 OK font-tektronix-misc 2.6-3 OK font-util 1.3.0-1 OK font-winitzki-cyrillic 1.0.2-1 OK font-xfree86-type1 1.0.3-1 OK fontconfig 2.11.1-1 OK fonttosfnt 1.0.4-1 OK fslsfonts 1.0.4-1 OK fvwm 2.6.5-1 OK gamin 0.1.10-15 OK garcon 0.2.1-1 OK gawk 4.1.1-1 OK gcr 3.10.1-1 OK gdk-pixbuf2.0-svg 2.40.1-1 OK getent 2.18.90-4 OK glib2.0-networking 2.38.2-1 OK gnome-icon-theme 3.10.0-1 OK gnome-keyring 3.10.1-1 OK gnome-themes-standard 3.10.0-1 OK grep 2.21-1 OK groff 1.22.2-2 OK gsettings-desktop-schemas 3.10.1-1 OK gtk-update-icon-cache 3.10.9-1 OK gtk1.2-engines 0.12-11 OK gtk2.0-engines-pixmap 2.24.25-1 OK gvfs 1.18.3-1 OK gzip 1.6-1 OK hicolor-icon-theme 0.12-1 OK hostname 3.13-1 OK iceauth 1.0.6-1 OK inetutils 1.9.1-2 OK inetutils-server 1.9.1-2 OK info 5.2-3 OK inputproto 2.3.1-1 OK ipc-utils 1.0-2 OK iso-codes 3.56-1 OK kbproto 1.0.6-1 OK keychain 2.7.1-1 OK khronos-opengl-registry 20141230_svn27684-1 OK less 458-1 OK libarchive13 3.1.2-2 OK libargp 20110921-2 OK libaspell15 0.60.6.1-1 OK libatk-bridge2.0_0 2.10.2-1 OK libatk1.0-devel 2.10.0-1 OK libatk1.0_0 2.10.0-1 OK libatspi0 2.10.2-1 OK libattr1 2.4.46-1 OK libaudio-devel 1.9.3-1 OK libaudio2 1.9.3-1 OK libavahi-client3 0.6.31-2 OK libavahi-common3 0.6.31-2 OK libavahi-glib1 0.6.31-2 OK libblkid1 2.25.2-1 OK libbz2-devel 1.0.6-2 OK libbz2_1 1.0.6-2 OK libcairo-devel 1.12.18-1 OK libcairo2 1.12.18-1 OK libcharset1 1.14-1 OK libcom_err2 1.42.10-1 OK libcroco0.6_3 0.6.8-1 OK libcrypt0 1.1-1 OK libdatrie1 0.2.8-1 OK libdb5.3 5.3.21-1 OK libdbus-glib_1_2 0.100.2-1 OK libdbus1_3 1.8.12-1 OK libdmx1 1.1.3-1 OK libedit0 20130712-1 OK libEGL-devel 10.3.5-1 OK libEGL1 10.3.5-1 OK libenchant1 1.6.0-1 OK libexif-common 0.6.21-2 OK libexif12 0.6.21-2 OK libexo1-common 0.10.2-1 OK libexo1_0 0.10.2-1 OK libexpat-devel 2.1.0-3 OK libexpat1 2.1.0-3 OK libfam0 0.1.10-15 OK libffi-devel 3.0.13-1 OK libffi6 3.0.13-1 OK libfltk1.3 1.3.2.9965-1 OK libfontconfig-devel 2.11.1-1 OK libfontconfig1 2.11.1-1 OK libfontenc1 1.1.2-1 OK libfreetype-devel 2.5.4-1 OK libfreetype6 2.5.4-1 OK libfribidi0 0.19.2-1 OK libFS6 1.0.6-1 OK libgailutil18 2.24.25-1 OK libgarcon1_0 0.2.1-1 OK libgcc1 4.9.2-1 OK libgck1_0 3.10.1-1 OK libgcr3-common 3.10.1-1 OK libgcr3_1 3.10.1-1 OK libgcrypt11 1.5.3-1 OK libgdbm4 1.11-1 OK libgdk_imlib1 1.9.15-14 OK libgdk_pixbuf2.0-devel 2.30.4-1 OK libgdk_pixbuf2.0_0 2.30.4-1 OK libgeoclue0 0.12.99-1 OK libgif4 4.1.6-12 OK libGL-devel 10.3.5-1 OK libGL1 10.3.5-1 OK libglapi0 10.3.5-1 OK libGLESv1_CM1 10.3.5-1 OK libGLESv2_2 10.3.5-1 OK libglib1.2_0 1.2.10-12 OK libglib2.0-devel 2.38.2-4 OK libglib2.0_0 2.38.2-4 OK libGLU-devel 9.0.0-1 OK libGLU1 9.0.0-1 OK libglut3 2.8.1-1 OK libGLw1 8.0.0-1 OK libgmp10 6.0.0a-1 OK libgnutls28 3.2.20-1 OK libgpg-error0 1.12-1 OK libgraphite2_3 1.2.3-1 OK libgssapi_krb5_2 1.12.2-1 OK libgstinterfaces1.0_0 1.2.4-1 OK libgstreamer1.0_0 1.2.4-1 OK libgtk1.2_0 1.2.10-12 OK libgtk2.0-devel 2.24.25-1 OK libgtk2.0_0 2.24.25-1 OK libgtk3_0 3.10.9-1 OK libharfbuzz-devel 0.9.25-1 OK libharfbuzz0 0.9.25-1 OK libhogweed2 2.7-1 OK libICE-devel 1.0.9-1 OK libICE6 1.0.9-1 OK libiconv 1.14-1 OK libiconv-devel 1.14-1 OK libiconv2 1.14-1 OK libicu-devel 51.2-1 OK libicu51 51.2-1 OK libintl-devel 0.19.3-1 OK libintl8 0.19.3-1 OK libjasper1 1.900.1-14 OK libjavascriptcoregtk1.0_0 2.0.4-1 OK libjbig2 2.0-14 OK libjpeg8 1.3.1-1 OK libk5crypto3 1.12.2-1 OK libkrb5_3 1.12.2-1 OK libkrb5support0 1.12.2-1 OK liblcms1 1.19-1 OK libllvm3.4 3.4.2-4 OK liblzma5 5.0.5-1 OK liblzo2_2 2.08-1 OK libmcpp0 2.7.2-2 OK libmng1 1.0.10-1 OK libmpfr4 3.1.2-1 OK libncursesw10 5.9-20141213-1 OK libnettle4 2.7-1 OK libnotify4 0.7.6-1 OK libopenssl100 1.0.1k-1 OK libOpenVG1 10.3.5-1 OK liborc0.4_0 0.4.18-2 OK libOSMesa-devel 10.3.5-1 OK libOSMesa8 10.3.5-1 OK libp11-kit0 0.20.7-1 OK libpango1.0-devel 1.36.3-1 OK libpango1.0_0 1.36.3-1 OK libpcre-devel 8.36-1 OK libpcre1 8.36-1 OK libpcre16_0 8.36-1 OK libpcre32_0 8.36-1 OK libpcrecpp0 8.36-1 OK libpcreposix0 8.36-1 OK libpipeline1 1.3.0-3 OK libpixman1-devel 0.32.6-1 OK libpixman1_0 0.32.6-1 OK libpng-devel 1.5.18-1 OK libpng15 1.5.18-1 OK Empty package libpopt0 libpopt0 1.16-1 OK libproxy1 0.4.11-2 OK libQtCore4 4.8.6-3 OK libQtCore4-devel 4.8.6-3 OK libQtGui4 4.8.6-3 OK libQtGui4-devel 4.8.6-3 OK libQtOpenGL4 4.8.6-3 OK libQtOpenGL4-devel 4.8.6-3 OK libQtXml4 4.8.6-3 OK libreadline7 6.2-1 OK librsvg2_2 2.40.1-1 OK libsecret1_0 0.16-1 OK libSM-devel 1.2.2-1 OK libSM6 1.2.2-1 OK libsmartcols1 2.25.2-1 OK libsoup-gnome2.4_1 2.44.2-2 OK libsoup2.4_1 2.44.2-2 OK libsqlite3_0 3.8.7.4-1 OK libssp0 4.9.2-1 OK libstartup-notification1_0 0.12-2 OK libstdc++6 4.9.2-1 OK libtasn1_6 4.2-1 OK libthai0 0.1.21-1 OK libtiff5 3.9.7-4 OK libtiff6 4.0.3-2 OK libuuid-devel 2.25.2-1 OK libuuid1 2.25.2-1 OK libvte9 0.28.2-4 OK libwebkitgtk1.0_0 2.0.4-1 OK libwebp5 0.4.0-1 OK libwnck1_22 2.30.7-2 OK libwrap0 7.6-22 OK libX11-devel 1.6.2-2 OK libX11-xcb-devel 1.6.2-2 OK libX11-xcb1 1.6.2-2 OK libX11_6 1.6.2-2 OK libXau-devel 1.0.8-1 OK libXau6 1.0.8-1 OK libXaw7 1.0.12-2 OK libxcb-devel 1.10-1 OK libxcb-glx-devel 1.10-1 OK libxcb-glx0 1.10-1 OK libxcb-icccm4 0.4.1-1 OK libxcb-image0 0.3.9-1 OK libxcb-keysyms1 0.3.9-1 OK libxcb-render-devel 1.10-1 OK libxcb-render0 1.10-1 OK libxcb-shape0 1.10-1 OK libxcb-shm-devel 1.10-1 OK libxcb-shm0 1.10-1 OK libxcb-util1 0.3.9-1 OK libxcb1 1.10-1 OK libXcomposite-devel 0.4.3-1 OK libXcomposite1 0.4.3-1 OK libXcursor-devel 1.1.14-1 OK libXcursor1 1.1.14-1 OK libXdamage-devel 1.1.4-1 OK libXdamage1 1.1.4-1 OK libXdmcp-devel 1.1.1-1 OK libXdmcp6 1.1.1-1 OK libXext-devel 1.3.3-1 OK libXext6 1.3.3-1 OK libxfce4kbd-private2_0 4.10.0-1 OK libxfce4ui1_0 4.10.0-1 OK libxfce4util-common 4.10.1-1 OK libxfce4util-devel 4.10.1-1 OK libxfce4util6 4.10.1-1 OK libxfconf0_2 4.10.0-2 OK libXfixes-devel 5.0.1-1 OK libXfixes3 5.0.1-1 OK libXfont1 1.5.0-1 OK libxfsm4.6_0 4.10.1-2 OK libXft-devel 2.3.2-1 OK libXft2 2.3.2-1 OK libXi-devel 1.7.4-1 OK libXi6 1.7.4-1 OK libXinerama-devel 1.1.3-1 OK libXinerama1 1.1.3-1 OK libxkbfile1 1.0.8-1 OK libxklavier16 5.3-1 OK libXm4 2.3.4-2 OK libxml2 2.9.2-1 OK libXmu6 1.1.2-1 OK libXmuu1 1.1.2-1 OK libXpm4 3.5.11-1 OK libXrandr-devel 1.4.2-1 OK libXrandr2 1.4.2-1 OK libXrender-devel 0.9.8-1 OK libXrender1 0.9.8-1 OK libXRes1 1.0.7-1 OK libxslt 1.1.28-1 OK libXss1 1.2.2-1 OK libXt-devel 1.1.4-2 OK libXt6 1.1.4-2 OK libXtst6 1.2.2-1 OK libzeitgeist1.0_1 0.3.18-1 OK login 1.11-1 OK luit 20130217-1 OK lynx 2.8.7-2 OK man-db 2.6.7-2 OK mcpp 2.7.2-2 OK mesa 10.3.5-1 OK mesa-demos 8.2.0-1 OK midori 0.5.8-1 OK mintty 1.2-beta1-1 OK mkfontdir 1.0.7-1 OK mkfontscale 1.1.1-1 OK motif 2.3.4-2 OK motif-debuginfo 2.3.4-2 OK openssh 6.7p1-2 OK openssl 1.0.1k-1 OK p11-kit 0.20.7-1 OK p11-kit-trust 0.20.7-1 OK perl 5.14.4-1 OK perl-Encode-Locale 1.03-1 OK perl-ExtUtils-Depends 0.306-1 OK perl-File-Listing 6.04-1 OK perl-Glib 1.304-1 OK perl-HTML-Parser 3.70-1 OK perl-HTML-Tagset 3.20-1 OK perl-HTTP-Cookies 6.01-1 OK perl-HTTP-Date 6.02-1 OK perl-HTTP-Message 6.06-1 OK perl-HTTP-Negotiate 6.01-1 OK perl-LWP 6.05-1 OK perl-LWP-MediaTypes 6.02-1 OK perl-Net-HTTP 6.06-1 OK perl-Tk 804.030-3 OK perl-URI 1.60-1 OK perl-WWW-RobotRules 6.02-1 OK perl-Xfce4-Xfconf 4.10.0-2 OK perl-XML-Parser 2.41-1 OK popt 1.16-1 OK procps 3.2.8-3 OK python 2.7.8-1 OK python3 3.2.5-4 OK python3-lxml 3.2.3-1 OK randrproto 1.4.0-1 OK rebase 4.4.1-1 OK renderproto 0.11.1-1 OK rodent-icon-theme 5.0-1 OK run 1.3.3-1 OK sed 4.2.2-3 OK setxkbmap 1.3.0-1 OK shared-mime-info 1.3-3 OK tar 1.27.1-1 OK terminfo 5.9-20141213-1 OK Thunar 1.6.3-2 OK tiff-opengl 4.0.3-2 OK tzcode 2014j-1 OK util-linux 2.25.2-1 OK vim-minimal 7.4.560-1 OK which 2.20-2 OK xauth 1.0.9-1 OK xclock 1.0.7-1 OK xcursor-themes 1.0.4-1 OK xdg-user-dirs 0.15-1 OK xextproto 7.3.0-1 OK xf86-video-dummy 0.3.7-2 OK xf86-video-nested 0.1.0-5 OK xfce-themes 3.0.1-1 OK xfce4-about 4.10.0-1 OK xfce4-appfinder 4.10.1-1 OK xfce4-panel 4.10.1-1 OK xfce4-panel-devel 4.10.1-1 OK xfce4-places-plugin 1.6.0-1 OK xfce4-session 4.10.1-2 OK xfce4-settings 4.10.1-1 OK xfce4-taskmanager 1.0.1-1 OK xfce4-terminal 0.6.3-1 OK xfconfd 4.10.0-2 OK xfdesktop 4.10.2-1 OK xfontsel 1.0.5-1 OK xfs 1.1.3-20140603-1 OK xfsinfo 1.0.4-1 OK xfwm4 4.10.1-1 OK xhost 1.0.6-1 OK xineramaproto 1.2.1-1 OK xinit 1.3.4-1 OK xkbcomp 1.2.4-1 OK xkeyboard-config 2.12-1 OK xlaunch 20140605-1 OK xmessage 1.0.4-1 OK xmodmap 1.0.8-1 OK xorg-scripts 1.0.1-1 OK xorg-server 1.16.3-1 OK xorg-server-common 1.16.3-1 OK xorg-server-dmx 1.16.3-1 OK xorg-server-extra 1.16.3-1 OK xproto 7.0.26-1 OK xrdb 1.1.0-1 OK xsetroot 1.1.0-1 OK xsm 1.0.3-1 OK xterm 313-1 OK xwininfo 1.1.3-1 OK xz 5.0.5-1 OK zlib-devel 1.2.8-3 OK zlib0 1.2.8-3 OK Use -h to see help about each section -------------- 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 hoes.maarten@gmail.com Thu Jan 22 07:46:00 2015 From: hoes.maarten@gmail.com (Maarten Hoes) Date: Thu, 22 Jan 2015 07:46:00 -0000 Subject: Cygwin/X XDMCP Issue In-Reply-To: <54BB7568.2030002@gmail.com> References: <54BA4C5C.4020400@gmail.com> <54BACED2.6070204@gmail.com> <54BB7568.2030002@gmail.com> Message-ID: <54C0AACF.6060501@gmail.com> Hi, Well I changed from GDM to KDM, and now everything is working as expected. Just one last question: are there any known issues with XDMCP and Gnome GDM ? Or is that combination supposed to just work ? Just for the record, here is the XWin.0.log of a working KDM session. - Maarten -------------- next part -------------- A non-text attachment was scrubbed... Name: XWin.0.log Type: application/octet-stream Size: 20569 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 hoes.maarten@gmail.com Thu Jan 22 07:55:00 2015 From: hoes.maarten@gmail.com (Maarten Hoes) Date: Thu, 22 Jan 2015 07:55:00 -0000 Subject: Saved Xlaunch 'config.xlaunch' issue In-Reply-To: <54C0AACF.6060501@gmail.com> References: <54BA4C5C.4020400@gmail.com> <54BACED2.6070204@gmail.com> <54BB7568.2030002@gmail.com> <54C0AACF.6060501@gmail.com> Message-ID: <54C0AD02.9070109@gmail.com> Hi, When I create and save a configuration with 'XLaunch', for example as 'config.xlaunch', I have the following behavior when double clicking the saved config file: It just launches XLaunch as if no configuration was saved at all. Wehn I open up the saved configuration file in an text editor, all the right settings are there in the xml file. Is this expected behavior, or am I running into a bug ? Im expecting the saved configuration in the xml file to be used instead of having to fill it in again. Thanks, - Maarten -------------- next part -------------- A non-text attachment was scrubbed... Name: config.xlaunch Type: text/xml Size: 419 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 bigeye@fleri.net Wed Jan 28 17:20:00 2015 From: bigeye@fleri.net (Lavelle Welles) Date: Wed, 28 Jan 2015 17:20:00 -0000 Subject: THAMES & HUDSON LTD Message-ID: THAMES & HUDSON LTD 44 Clockhouse Rd Farnborough Hampshire GU14 7QZ Hampshire UK +44 (1252) 97 22 60 Attachment: thames_and_hudson_ltd.cab Description: application/vnd.ms-cab-compressed -- Unsubscribe info: http://cygwin.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 Jan 30 20:00:00 2015 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 30 Jan 2015 20:00:00 -0000 Subject: Saved Xlaunch 'config.xlaunch' issue In-Reply-To: <54C0AD02.9070109@gmail.com> References: <54BA4C5C.4020400@gmail.com> <54BACED2.6070204@gmail.com> <54BB7568.2030002@gmail.com> <54C0AACF.6060501@gmail.com> <54C0AD02.9070109@gmail.com> Message-ID: <54CBE2B3.4020607@dronecode.org.uk> On 22/01/2015 07:55, Maarten Hoes wrote: > When I create and save a configuration with 'XLaunch', for example as > 'config.xlaunch', I have the following behavior when double clicking the > saved config file: It just launches XLaunch as if no configuration was > saved at all. When I open up the saved configuration file in an text > editor, all the right settings are there in the xml file. Is this > expected behaviour, or am I running into a bug ? I'm expecting the saved > configuration in the xml file to be used instead of having to fill it in > again. Thanks for reporting this issue. It seems that this stopped working correctly a while ago due to some changes in run or cygwin argument parsing. I've uploaded an updated xlaunch-20150130-1 today which should fix this. -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Fri Jan 30 20:13:00 2015 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Fri, 30 Jan 2015 20:13:00 -0000 Subject: [ANNOUNCEMENT] Updated: xlaunch-20150130-1 In-Reply-To: <5390A30C.9040609@dronecode.org.uk> References: <4F719346.7050007@dronecode.org.uk> <5130CE7E.2070408@dronecode.org.uk> <5390A30C.9040609@dronecode.org.uk> Message-ID: *** xlaunch-20150130-1 * Fix Open/Edit actions on .xlaunch files to use 'run --quote' * Workaround an issue with invalid binary being produced due to embedded manifest x86: ee9a6c1ed383eff1a476ca3748397bbd *xlaunch-20150130-1-src.tar.xz f17834c7968e1eec0ff056b88b3abc28 *xlaunch-20150130-1.tar.xz x86_64: 8a30e69ba76751e0f5b8d59dbf978ead *xlaunch-20150130-1-src.tar.xz b9e3390a9c075ebb5c29ac77bbf2707b *xlaunch-20150130-1.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 cppcheck.libreoffice@gmail.com Sat Jan 31 01:19:00 2015 From: cppcheck.libreoffice@gmail.com (Maarten Hoes) Date: Sat, 31 Jan 2015 01:19:00 -0000 Subject: Saved Xlaunch 'config.xlaunch' issue In-Reply-To: <54CBE2B3.4020607@dronecode.org.uk> References: <54BA4C5C.4020400@gmail.com> <54BACED2.6070204@gmail.com> <54BB7568.2030002@gmail.com> <54C0AACF.6060501@gmail.com> <54C0AD02.9070109@gmail.com> <54CBE2B3.4020607@dronecode.org.uk> Message-ID: <54CC2DAB.9040603@gmail.com> Hi, On 30-1-2015 20:59, Jon TURNEY wrote: > On 22/01/2015 07:55, Maarten Hoes wrote: >> When I create and save a configuration with 'XLaunch', for example as >> 'config.xlaunch', I have the following behavior when double clicking the >> saved config file: It just launches XLaunch as if no configuration was >> saved at all. When I open up the saved configuration file in an text >> editor, all the right settings are there in the xml file. Is this >> expected behaviour, or am I running into a bug ? I'm expecting the saved >> configuration in the xml file to be used instead of having to fill it in >> again. > > Thanks for reporting this issue. > > It seems that this stopped working correctly a while ago due to some > changes in run or cygwin argument parsing. > > I've uploaded an updated xlaunch-20150130-1 today which should fix this. > Thanks, the new version fixes the issue for me: double clicking a saved .xlaunch file now uses the saved configuration settings. - Maarten -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/ From jon.turney@dronecode.org.uk Sat Jan 31 14:22:00 2015 From: jon.turney@dronecode.org.uk (Jon TURNEY) Date: Sat, 31 Jan 2015 14:22:00 -0000 Subject: build error on 1.16.2-1 In-Reply-To: <5481BEDF.1000807@dronecode.org.uk> References: <5481BEDF.1000807@dronecode.org.uk> Message-ID: <54CCE51F.8080703@dronecode.org.uk> On 05/12/2014 14:19, Jon TURNEY wrote: > On 01/12/2014 23:37, J. Offerman wrote: >> This is an obvious source-header discrepancy. The source >> file(auto-generated anyway) doesn't seem to be changed recently, while >> the header file(glext.h) has a timestamp of Nov 16 now. So it looks >> like only the header file got advanced here. Looking at the >> announcements, it should be the Mesa update on Nov 17 that renewed it. >> Should I just add the extra arguments for those 3 funcs in the source >> file as defined in the new header file? That looks like working. > > Thanks for drawing this to my attention. > > Yes, it seems that the the glext.h header file (which comes from Khronos > via the w32api-headers package) now has the fix (svn r27313) to add the > extra argument to the prototype, but the XML used for the generated code > (which comes from Khronos via the khronos-opengl-registry package) is > only on svn r27116. > > I'm afraid you'll have to fix this manually until I generate a new > khronos-opengl-registry package This build issue should be resolved with khronos-opengl-registry 20141230_svn27684-1 and xorg-server 1.16.3-1 -- 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/