Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
Greetings, Bill Stewart! > On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote: >> Try it with a group that has several hundred members. Then try with >> several hundreds of such groups. Then try it again over a DSL line or >> some VPN routing you across the globe that has a roundtrip measured in >> tenths of seconds. > Understood - not ideal for all situations. > An even more appropriate approach is for sshd to ignore case in usernames > when listening for connections on a host OS that ignores case in usernames. > My understanding is that this change will be in the next version of OpenSSH > (unless I misunderstood). In the next major version, IIRC. (I.e. 8.x) -- With best regards, Andrey Repin Tuesday, March 12, 2019 3:09:41 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Mon, Mar 11, 2019 at 3:38 PM Achim Gratz wrote: > Try it with a group that has several hundred members. Then try with > several hundreds of such groups. Then try it again over a DSL line or > some VPN routing you across the globe that has a roundtrip measured in > tenths of seconds. Understood - not ideal for all situations. An even more appropriate approach is for sshd to ignore case in usernames when listening for connections on a host OS that ignores case in usernames. My understanding is that this change will be in the next version of OpenSSH (unless I misunderstood). Regards Bill -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
Bill Stewart writes: > FWIW, not sure if you're using the IADsNameTranslate interface ( > https://docs.microsoft.com/en-us/windows/desktop/api/iads/nn-iads-iadsnametranslate). […] > Init depends on a available AD server (GC in this example), of course, but > seems pretty fast in my tests. Try it with a group that has several hundred members. Then try with several hundreds of such groups. Then try it again over a DSL line or some VPN routing you across the globe that has a roundtrip measured in tenths of seconds. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Thu, Feb 28, 2019 at 2:39 AM Corinna Vinschen wrote: > > Since windows seems to adhere to the rule: > > "Case preserving", but "case ignoring", what does it > > mean to make sure all user and group names are > > case-correct? > > This all started here: > https://cygwin.com/ml/cygwin/2019-02/msg00109.html > > followed up with > > https://cygwin.com/ml/cygwin/2019-02/msg00113.html > > tl;dr: The easy and fast way out didn't work for accounts from > other domains than the machine's primary domain due to caching. > > So I thought it's a good idea to fetch the correct groupnames by an > additional LDAP call, but the performance hit is apparently too high in > some environments. FWIW, not sure if you're using the IADsNameTranslate interface ( https://docs.microsoft.com/en-us/windows/desktop/api/iads/nn-iads-iadsnametranslate). .. Example pseudo-code: NameTranslate::Init(ADS_NAME_INITTYPE_GC, null); Then: accountName = 'domain\username'; NameTranslate::Set(ADS_NAME_TYPE_NT4, accountName); caseCorrectedName = NameTranslate::Get(ADS_NAME_TYPE_NT4); // DOMAIN\UserName Init depends on a available AD server (GC in this example), of course, but seems pretty fast in my tests. Bill -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/28/2019 1:39 AM, Corinna Vinschen wrote: This is all more or less moot as soon as OpenSSH 8.0 comes out, which will contain patches to handle user and group names case-insensitive, finally. Please forgive my ignorance of cygwin's internals, but why does cygwin1.dll need to do anything on the network or enumerate the groups in LDAP/AD or whatever even when doing something as mundane as 'grep -V'? I'm just wondering if there's a better way to hold off on that until it's really needed. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Feb 27 19:11, L A Walsh wrote: > On 2/27/2019 12:50 PM, Corinna Vinschen wrote: > > The fix was this one: > > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb > > Corinna > > > > > > My question would be related to the comment with the fix: > > "made sure all user and group names are case-correct" > > Since windows seems to adhere to the rule: > "Case preserving", but "case ignoring", what does it > mean to make sure all user and group names are > case-correct? This all started here: https://cygwin.com/ml/cygwin/2019-02/msg00109.html followed up with https://cygwin.com/ml/cygwin/2019-02/msg00113.html tl;dr: The easy and fast way out didn't work for accounts from other domains than the machine's primary domain due to caching. So I thought it's a good idea to fetch the correct groupnames by an additional LDAP call, but the performance hit is apparently too high in some environments. This is all more or less moot as soon as OpenSSH 8.0 comes out, which will contain patches to handle user and group names case-insensitive, finally. Corinna -- Corinna Vinschen Cygwin Maintainer signature.asc Description: PGP signature
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/27/2019 12:50 PM, Corinna Vinschen wrote: > The fix was this one: > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb > Corinna > > My question would be related to the comment with the fix: "made sure all user and group names are case-correct" Since windows seems to adhere to the rule: "Case preserving", but "case ignoring", what does it mean to make sure all user and group names are case-correct? >From what little I understand in the area, the case that is preserved is the 1st one used on a given machine. However if we are talking non-Windows LDAP/AD, who knows what is done. Sigh. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/27/2019 12:50 PM, Corinna Vinschen wrote: Apparently same problem as reported in https://cygwin.com/ml/cygwin/2019-02/msg00301.html The fix was this one: https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb Thanks. Yeah, our AD has 152 groups. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Feb 27 12:44, Jerry Baker via cygwin wrote: > On 2/27/2019 12:23 PM, Jerry Baker via cygwin wrote: > > I am also happy to report that cygwin1-20190226.dll fixes the issue. > > For the curious, the fix happened between cygwin1-20190219.dll and > cygwin1-20190223.dll. > > Maybe the changes in sec_auth.cc. They look suspicious. Apparently same problem as reported in https://cygwin.com/ml/cygwin/2019-02/msg00301.html The fix was this one: https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=18c203fb6eb Corinna -- Corinna Vinschen Cygwin Maintainer signature.asc Description: PGP signature
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/27/2019 12:23 PM, Jerry Baker via cygwin wrote: I am also happy to report that cygwin1-20190226.dll fixes the issue. For the curious, the fix happened between cygwin1-20190219.dll and cygwin1-20190223.dll. Maybe the changes in sec_auth.cc. They look suspicious. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/27/19 2:19 PM, Jerry Baker via cygwin wrote: > On 2/26/2019 10:55 PM, Brian Inglis wrote: >> As Cygwin is a rolling release system, if you are not running current >> releases, >> some CVE security issues may remain unpatched, and your system may not be >> compliant to your corporate security policies (you may want to check >> with your >> IT security and/or IT auditors). > > I narrowed it down to my network. If I unplug the Ethernet cable the > problem disappears. If I plug it in, the problem returns. I can > reproduce it 100% for an hour straight, going back and forth. Off-hand, I would suspect that the newer Cygwin has code that tries to access a network resource (perhaps because you have a "//name" in your $PATH, or perhaps because of local vs. network username), and that the process hangs waiting for the resource to time out when you have the cable plugged in (or even has a bug that causes an inf-loop), but quickly falls back to something that works when the network is not present. Corinna will have more ideas about how to test which particular network call is hanging, as well as being more familiar with recent changes in network username validation, for ideas on better debugging this. -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/27/2019 12:19 PM, Jerry Baker via cygwin wrote: I narrowed it down to my network. If I unplug the Ethernet cable the problem disappears. If I plug it in, the problem returns. I can reproduce it 100% for an hour straight, going back and forth. I am also happy to report that cygwin1-20190226.dll fixes the issue. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 10:55 PM, Brian Inglis wrote: As Cygwin is a rolling release system, if you are not running current releases, some CVE security issues may remain unpatched, and your system may not be compliant to your corporate security policies (you may want to check with your IT security and/or IT auditors). I narrowed it down to my network. If I unplug the Ethernet cable the problem disappears. If I plug it in, the problem returns. I can reproduce it 100% for an hour straight, going back and forth. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Wed, Feb 27, 2019 at 4:45 AM Steven Penny wrote: > > On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote: > > Well I guess it's a good thing there's only one possible state of > > Windows 7 x64 which allows us to determine that there's no possibility > > of a bug simply by running a single instance in one VM. We're going to > > turn the world of unit testing on its ear with this information. > > correct, multiple states are possible. this is why the scientific method > defines > a control: > > https://wikipedia.org/wiki/Scientific_control > > in this case that would be a clean virtual machine. if you cant or wont do > that, > then you must understand that you only have yourself to blame. I understand this thread has been heated, and it hasn't been just you who's been impatient by any means. But maybe it will help smooth things over by avoiding words like "blame" and finger pointing. If someone has a broken Cygwin on their system that works on other, similar systems it's not necessarily the user who's to "tlame". Yes, PEBKAC is always a possibility, but since you mentioned the scientific method I'll just add that we have no evidence of that either. Windows, much someone's working installation of Windows (which can have a lot more going on on it than a fresh VM) is an enormously complex system, and it's entirely possible that Cygwin is *broken* on that particular configuration through no fault of the user. Unfortunately, without concrete steps to reproduce the problem, the rest of us can only speculate. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2019-02-26 16:00, Jerry Baker via cygwin wrote: > On 2/26/2019 2:48 PM, Doug Henderson wrote: >> Good. This tells us something important. Right after the path listing, >> cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a >> cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll. >> That narrow the problem. These three DLLs might have been corrupted, >> or something is interfering with their correct operation. >> See BLODA: See https://cygwin.com/acronyms/ >> Check the list of BLODAs to see if you are running one of those. > It's just cygwin1.dll for sure. I can replace that with 2.x version and > everything works fine. > I don't recognize most of the BLODAs and not running any of them that I know > of. > Are there any software packages known to interfere with 3.0 and not 2.x? >From what you said elsewhere, it sounds like you run an Enterprise image, so your org may have omitted components, features, or products essential to running Cygwin, may have added components, features, products (like many poor "security" solutions), or set policies inimical to running Cygwin. Compatibility of any specific release of any software product with any given enterprise image configuration requires adequate testing to ensure required dependencies are included in the image configuration. In addition, PCs with recent AMD and Intel CPUs, chipsets, and motherboards, and other newer hardware, are only supported under Windows 10 Enterprise, with support for selected enterprise vendor systems with Skylake CPUs under Windows 7, and nothing newer. A minimal datapoint might be running "cygcheck cygcheck" under cmd, with whatever explicit path is required to get the executable to run, and posting the output. If that works, then if you could try running "cygcheck -hrsv > cygcheck.out" under cmd, with the same path, and attach the output file as a text/plain attachment, that would help diagnose the problem. As Cygwin is a rolling release system, if you are not running current releases, some CVE security issues may remain unpatched, and your system may not be compliant to your corporate security policies (you may want to check with your IT security and/or IT auditors). -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 18:01:27, Jerry Baker via cygwin" wrote: > Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7 > system. The only difference I can think of is that the i7 system is a > member of a domain. (first I would suggest a good night's sleep :-) If you really believe it is the cygwin1.dll that causes the failure, and you also believe that your system fails because it is in a domain ... Why not test (using bisect) the cygwin1.dll 's at cygwin.com/snapshots? (do not the ones between 20190126 and 20190130, because, as far as I can remember, these are not OK). Start at the beginning of 2019, I would suggest ... Use a fresh minimal! installation (download from a mirror, not from your local repo). Minimize your path to "Cygwin-only" ... .. etc. (you are an experienced person, you should know what to do!). If you find the culprit, tell us. The project leader of Cygwin will be much interested!. Henri -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
> On Feb 26, 2019, at 8:55 PM, Jerry Baker wrote: > > I don't work for free, This is open source. Given that the people here do, that's not a very good argument. > especially for hostile people with over inflated egos and crippling social > disorders. Don't feed it by arguing. > The onus is on whoever is interested in having cygwin work in this particular > configuration. Again, this is open source; there is no onus. Win7x64 is a very common cygwin installation (including one of my VM's, which has no issues with 3.x). You're the only one reporting the problem. If this were a general Win7x64 problem, the list would have exploded by now. You're the only who has access to your system. Consequently, you're the only one that's going to be able to debug it. There's nothing obvious (to me, anyway) in your cygcheck.out. If you don't care enough to debug it, that's not a problem; just live with 2.x for as long as 2.x will continue to work. You might try strace'ing a cygwin program and see if anything obvious shows up in the output. Look for Windows errors, permission errors, etc. (Don't send it here unless someone asks for it). See the User's Guide (https://cygwin.com/cygwin-ug-net.html) for info on strace. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 19:21:15, "Jerry Baker via cygwin" wrote: Well I guess it's a good thing there's only one possible state of Windows 7 x64 which allows us to determine that there's no possibility of a bug simply by running a single instance in one VM. We're going to turn the world of unit testing on its ear with this information. correct, multiple states are possible. this is why the scientific method defines a control: https://wikipedia.org/wiki/Scientific_control in this case that would be a clean virtual machine. if you cant or wont do that, then you must understand that you only have yourself to blame. I would argue that what is a disservice to the community is jumping into a thread in which you were not involved for no apparent purpose other than to insult everyone who was already getting a long just fine without your genius to guide us. i provided a valuable data point, which is what happens with a clean windows environment - results disagree with your original post. i think you missed my link first time - i have put again below for convenience! https://yourlogicalfallacyis.com/ad-hominem cheers -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 7:12 PM, Doug Henderson wrote: There is one more place you could have a problem. It does not seem likely, but maybe you have a bad download cache area. When you run setup, on the fourth panel, where it asks for the Local Package Directory, you could try deleting that directory. (It must not be the same as your cygwin root from the previous panel). The state of mirrors changes over time. Which mirror(s) are you using (selected on the 6th panel)? I have successfully used http://mirrors.kernel.org for many years. It's not so important to pick a local mirror as it used to be, so I go for reliability (and fat pipes), rather than distance to the mirror. (I have a little program that times the download of the setup data file from each mirror.) BTW, what is your DEP setting? Control Panel -> Advanced system settings -> advanced tab -> Performance Settings -> Data Execution Prevention tab. I am using the top setting (Turn on DEP for essential Windows programs and services only) rather than (Turn on DEP for all programs ad services except those I select). I'm not sure how Address Space Layout Randomisation (ASLR) is managed on Windows 7, but I think cygwin exes and dlls get special handling. HTH Doug Thanks. I did try a couple of mirrors with the same result. I will try safe mode and a new mirror when the machine is accessible again. The machine with the problem isn't accessible at the moment, but the machine where it works has DEP enabled for all programs. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 7:05 PM, Steven Penny wrote: On Tue, 26 Feb 2019 18:55:56, "Jerry Baker via cygwin" wrote: Not really. I don't work for free, especially for hostile people with over inflated egos and crippling social disorders. https://yourlogicalfallacyis.com/ad-hominem The onus is on whoever is interested in having cygwin work in this particular configuration. Clearly not you. Since it works with 2.11, I'm not particularly interested in expending a lot of work figuring out what got botched in 3.0 or who did it. Wasn't me, so not my problem. It was my mistake to assume that the cygwin community was interested in interoperability. I should have done more research before making that unwarranted assumption. it very much is your problem, as im using Windows 7 x64 just fine with Cygwin. Well I guess it's a good thing there's only one possible state of Windows 7 x64 which allows us to determine that there's no possibility of a bug simply by running a single instance in one VM. We're going to turn the world of unit testing on its ear with this information. and its your problem else you wouldnt have come here posting. you can start threads with clickbait titles as youve done, buts its a disservice to the community when you dont have a reproducible problem. thats why this page has existed for 5 years: I would argue that what is a disservice to the community is jumping into a thread in which you were not involved for no apparent purpose other than to insult everyone who was already getting a long just fine without your genius to guide us. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 at 19:01, Jerry Baker via cygwin <> wrote: > > On 2/26/2019 5:50 PM, Jerry Baker via cygwin wrote: > > Glad to. Please let me know what evidence will suffice to prove that. > > > > If it is my system our organization is going to have bigger issues. > > There are about 3,700 workstations with this machine image just in this > > building. > > Problem machine is an Intel i7 system with 16GB RAM. Ironically, the > same Windows 7 on an old AMD Athlon X2 system with 4GB of RAM does not > exhibit the issue at all. > > Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7 > system. The only difference I can think of is that the i7 system is a > member of a domain. There is one more place you could have a problem. It does not seem likely, but maybe you have a bad download cache area. When you run setup, on the fourth panel, where it asks for the Local Package Directory, you could try deleting that directory. (It must not be the same as your cygwin root from the previous panel). The state of mirrors changes over time. Which mirror(s) are you using (selected on the 6th panel)? I have successfully used http://mirrors.kernel.org for many years. It's not so important to pick a local mirror as it used to be, so I go for reliability (and fat pipes), rather than distance to the mirror. (I have a little program that times the download of the setup data file from each mirror.) BTW, what is your DEP setting? Control Panel -> Advanced system settings -> advanced tab -> Performance Settings -> Data Execution Prevention tab. I am using the top setting (Turn on DEP for essential Windows programs and services only) rather than (Turn on DEP for all programs ad services except those I select). I'm not sure how Address Space Layout Randomisation (ASLR) is managed on Windows 7, but I think cygwin exes and dlls get special handling. HTH Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 18:55:56, "Jerry Baker via cygwin" wrote: Not really. I don't work for free, especially for hostile people with over inflated egos and crippling social disorders. https://yourlogicalfallacyis.com/ad-hominem The onus is on whoever is interested in having cygwin work in this particular configuration. Clearly not you. Since it works with 2.11, I'm not particularly interested in expending a lot of work figuring out what got botched in 3.0 or who did it. Wasn't me, so not my problem. It was my mistake to assume that the cygwin community was interested in interoperability. I should have done more research before making that unwarranted assumption. it very much is your problem, as im using Windows 7 x64 just fine with Cygwin. and its your problem else you wouldnt have come here posting. you can start threads with clickbait titles as youve done, buts its a disservice to the community when you dont have a reproducible problem. thats why this page has existed for 5 years: https://stackoverflow.com/help/mcve the "V" is Verifiable. and until your example is Verifiable then you shouldnt be surprised if the "problem" goes unsolved. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 6:43 PM, Steven Penny wrote: i would like to make that last point vividly clear: its on you to do that testing. ive already given a clear refutation of your original point, so the ball is now squarely in your court. Not really. I don't work for free, especially for hostile people with over inflated egos and crippling social disorders. The onus is on whoever is interested in having cygwin work in this particular configuration. Clearly not you. Since it works with 2.11, I'm not particularly interested in expending a lot of work figuring out what got botched in 3.0 or who did it. Wasn't me, so not my problem. It was my mistake to assume that the cygwin community was interested in interoperability. I should have done more research before making that unwarranted assumption. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 17:50:10, "Jerry Baker via cygwin" wrote: Glad to. Please let me know what evidence will suffice to prove that. pretty simple 1. get the Windows 7 x64 from here https://softlay.net/operating-system/windows-7-download.html 2. get virtualbox from here https://virtualbox.org after you test it and realize like i did that it works, *you* can work forward from there to figure out what updates if any are causing a problem. i would like to make that last point vividly clear: its on you to do that testing. ive already given a clear refutation of your original point, so the ball is now squarely in your court. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 5:50 PM, Jerry Baker via cygwin wrote: Glad to. Please let me know what evidence will suffice to prove that. If it is my system our organization is going to have bigger issues. There are about 3,700 workstations with this machine image just in this building. Problem machine is an Intel i7 system with 16GB RAM. Ironically, the same Windows 7 on an old AMD Athlon X2 system with 4GB of RAM does not exhibit the issue at all. Trying to think of what could make 2.11.x work and 3.0.1 fail on the i7 system. The only difference I can think of is that the i7 system is a member of a domain. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 5:17 PM, Steven Penny wrote: you know i just finished reading this entire thread and its kind of depressing. 7 replies from 5 people, and not one person explicitly answered the implicit, most important, and frankly only question worth answering: Can anyone else reproduce this problem? So i am here to answer that question. I was concerned as *I* use Windows 7 x64 as well. I just tested with a pristine virtual machine with Windows 7 x64 and Cygwin 3.0.1-1 and it works perfectly fine. Note it works fine with Cygwin.bat or with the shortcut. And you installed all the Windows Updates that apply to your system since the image you used to set up the VM, including all updates to .NET? And you're positive that there can't be any hardware issue that's not reproduceable in your VM? So *something* is wrong on your system. Cant say what it might be, and i hate for you to have to reinstall the whole OS. However as far as im concerned at this point, *its you*, not a Cygwin issue unless you can prove otherwise. Glad to. Please let me know what evidence will suffice to prove that. If it is my system our organization is going to have bigger issues. There are about 3,700 workstations with this machine image just in this building. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 15:00:03, "Jerry Baker via cygwin" wrote: It's just cygwin1.dll for sure. I can replace that with 2.x version and everything works fine. I don't recognize most of the BLODAs and not running any of them that I know of. Are there any software packages known to interfere with 3.0 and not 2.x? you know i just finished reading this entire thread and its kind of depressing. 7 replies from 5 people, and not one person explicitly answered the implicit, most important, and frankly only question worth answering: Can anyone else reproduce this problem? So i am here to answer that question. I was concerned as *I* use Windows 7 x64 as well. I just tested with a pristine virtual machine with Windows 7 x64 and Cygwin 3.0.1-1 and it works perfectly fine. Note it works fine with Cygwin.bat or with the shortcut. So *something* is wrong on your system. Cant say what it might be, and i hate for you to have to reinstall the whole OS. However as far as im concerned at this point, *its you*, not a Cygwin issue unless you can prove otherwise. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 2:48 PM, Doug Henderson wrote: Good. This tells us something important. Right after the path listing, cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll. That narrow the problem. These three DLLs might have been corrupted, or something is interfering with their correct operation. See BLODA: See https://cygwin.com/acronyms/ Check the list of BLODAs to see if you are running one of those. It's just cygwin1.dll for sure. I can replace that with 2.x version and everything works fine. I don't recognize most of the BLODAs and not running any of them that I know of. Are there any software packages known to interfere with 3.0 and not 2.x? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 at 15:10, Jerry Baker via cygwin <> wrote: > > On 2/26/2019 1:56 PM, Doug Henderson wrote: > > Two things. > > 1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64 > > in Explorer and opening a command or powershell window from explorer's > > shift-context menu. There, run the following command: > Here are the results: > > 1. That command gets part way through and then hangs with the blinking > cursor after listing the directories in the path variable. Good. This tells us something important. Right after the path listing, cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll. That narrow the problem. These three DLLs might have been corrupted, or something is interfering with their correct operation. See BLODA: See https://cygwin.com/acronyms/ Check the list of BLODAs to see if you are running one of those. HTH Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 2:10 PM, Jerry Baker wrote: Thanks for the tips. I made a completely fresh install in a new directory and attempted all three suggestions. Here are the results: 1. That command gets part way through and then hangs with the blinking cursor after listing the directories in the path variable. 2. bat file or desktop shortcut hangs with a black window and blinking cursor. 3. Set variable and run Cygwin.bat. Black window with blinking cursor. Literally every single way you can call a cygwin executable just hangs with a blinking cursor. I was also inspired to try unsetting the path variable altogether to rule out some rogue application or DLL somewhere else on my system. I did that and then tried to run 'bash.' No improvement. I tried 'grep' and 'base64' as well. All hang with blinking cursor. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 1:56 PM, Doug Henderson wrote: Two things. 1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64 in Explorer and opening a command or powershell window from explorer's shift-context menu. There, run the following command: .\cygcheck.exe -csr > ..\home\CYGWINUSERNAME\cygcheck.out or similar.If this does not work, I would look for a anti-virus or firewall that is interfering. 2. I don't recall you mentioning how you start cygwin. Please try both standard methods: a) execute c:\cygwin64\Cygwin.bat and b) executing the Cygwin icon that (by default) cygwin setup places on the desktop. 3. As an after thought, I always run cygwin with CYGWIN_NOWINPATH=1 set in my system environment variables. (From what I understand, I am one of the few people that do this!) This resets the PATH variable in the cygwin shell to only contain cygwin directories. If this resolves the problem, you can edit your .bashrc to add any needed windows path. For instance, I add the path to some go lang executables. And I set up aliases or functions to run a few specific Windows exes, such as Explorer, icacls, cmd, etc. If you want all the directories from your windows path, they are available in the ORIGINAL_PATH variable, so you can add all of them at the end of the PATH variable, so they do not shadow same-named cygwin exes. Thanks for the tips. I made a completely fresh install in a new directory and attempted all three suggestions. Here are the results: 1. That command gets part way through and then hangs with the blinking cursor after listing the directories in the path variable. 2. bat file or desktop shortcut hangs with a black window and blinking cursor. 3. Set variable and run Cygwin.bat. Black window with blinking cursor. Literally every single way you can call a cygwin executable just hangs with a blinking cursor. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, 26 Feb 2019 at 13:00, Jerry Baker via cygwin <> wrote: > > On 2/26/2019 11:32 AM, Jerry Baker via cygwin wrote: > > Yes, but by wiping out the whole tree and installing 64-bit. You filled > > me with doubt, so I browsed around with a hex editor looking at quite a > > few random executables and dll files in cygwin\bin and all of them I > > checked are 64-bit. > > I just installed from scratch in a new directory. Same issue. Nothing runs. Two things. 1. You can execute cygcheck by navigating to C:\cygwin or C:\cygwin64 in Explorer and opening a command or powershell window from explorer's shift-context menu. There, run the following command: .\cygcheck.exe -csr > ..\home\CYGWINUSERNAME\cygcheck.out or similar.If this does not work, I would look for a anti-virus or firewall that is interfering. 2. I don't recall you mentioning how you start cygwin. Please try both standard methods: a) execute c:\cygwin64\Cygwin.bat and b) executing the Cygwin icon that (by default) cygwin setup places on the desktop. 3. As an after thought, I always run cygwin with CYGWIN_NOWINPATH=1 set in my system environment variables. (From what I understand, I am one of the few people that do this!) This resets the PATH variable in the cygwin shell to only contain cygwin directories. If this resolves the problem, you can edit your .bashrc to add any needed windows path. For instance, I add the path to some go lang executables. And I set up aliases or functions to run a few specific Windows exes, such as Explorer, icacls, cmd, etc. If you want all the directories from your windows path, they are available in the ORIGINAL_PATH variable, so you can add all of them at the end of the PATH variable, so they do not shadow same-named cygwin exes. HTH Doug -- Doug Henderson, Calgary, Alberta, Canada - from gmail.com -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
> On Feb 26, 2019, at 2:00 PM, Jerry Baker wrote: > > I just installed from scratch in a new directory. Same issue. Nothing runs. If cygcheck doesn't run, then it would appear there's (at least) something non-cygwin-related going on. cygcheck isn't a cygwin program, i.e. it doesn't link to or depend on cygwin1.dll. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 11:32 AM, Jerry Baker via cygwin wrote: Yes, but by wiping out the whole tree and installing 64-bit. You filled me with doubt, so I browsed around with a hex editor looking at quite a few random executables and dll files in cygwin\bin and all of them I checked are 64-bit. I just installed from scratch in a new directory. Same issue. Nothing runs. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 11:19 AM, Ken Brown wrote: Here's a wild guess, based on the fact that your Cygwin installation is in C:\cygwin rather than C:\cygwin64. Do you have a 32-bit Cygwin installation that you updated using setup-x86_x64.exe instead of setup-x86.exe? Yes, but by wiping out the whole tree and installing 64-bit. You filled me with doubt, so I browsed around with a hex editor looking at quite a few random executables and dll files in cygwin\bin and all of them I checked are 64-bit. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 1:59 PM, Jerry Baker via cygwin wrote: > On 2/26/2019 10:44 AM, Vince Rice wrote: >> What is also described on the page are the reporting guidelines. Please read >> them again, paying special >> attention to the bolded part. Here's a wild guess, based on the fact that your Cygwin installation is in C:\cygwin rather than C:\cygwin64. Do you have a 32-bit Cygwin installation that you updated using setup-x86_x64.exe instead of setup-x86.exe? Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 10:44 AM, Vince Rice wrote: What is also described on the page are the reporting guidelines. Please read them again, paying special attention to the bolded part. That command has the same problem under 3.0.0.1-1 as all the others. Under 2.11.2-1 it is as follows: - Cygwin Configuration Diagnostics Current System Time: Tue Feb 26 09:42:22 2019 Windows 7 Professional Ver 6.1 Build 7601 Service Pack 1 Path: C:\ProgramData\Oracle\Java\javapath C:\app\product\11.2.0\client_1\bin 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 C:\PCOMWIN\ C:\Program Files (x86)\IBM\Trace Facility\ C:\Program Files\Google\Google Apps Migration\ C:\Program Files\OpenVPN\bin C:\Program Files (x86)\GNU\GnuPG\pub C:\Program Files (x86)\utils C:\cygwin\bin C:\Program Files (x86)\Nmap C:\Program Files\FLAC C:\Program Files\utils Output from C:\cygwin\bin\id.exe UID: 1082606(.) GID: 1049089(Domain Users) 1049089(Domain Users) 545(Users) 4(INTERACTIVE) 66049(CONSOLE LOGON) 11(Authenticated Users) ... long list of groups specific to organization redacted ... 15(This Organization) 4095(CurrentSession) 66048(LOCAL) 70145(Authentication authority asserted identity) 401408(Medium Mandatory Level) SysDir: C:\Windows\system32 WinDir: C:\Windows Path = 'C:\ProgramData\Oracle\Java\javapath;C:\app\product\11.2.0\client_1\bin;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;C:\PCOMWIN\;C:\Program Files (x86)\IBM\Trace Facility\;C:\Program Files\Google\Google Apps Migration\;C:\Program Files\OpenVPN\bin;C:\Program Files (x86)\GNU\GnuPG\pub;C:\Program Files (x86)\utils;C:\cygwin\bin;C:\Program Files (x86)\Nmap;C:\Program Files\FLAC;C:\Program Files\utils' ALLUSERSPROFILE = 'C:\ProgramData' APPDATA = 'C:\Users\.\AppData\Roaming' CommonProgramFiles = 'C:\Program Files\Common Files' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' CommonProgramW6432 = 'C:\Program Files\Common Files' COMPUTERNAME = 'FAC-P-08098' ComSpec = 'C:\Windows\system32\cmd.exe' FP_NO_HOST_CHECK = 'NO' HOMEDRIVE = 'C:' HOMEPATH = '\Users\.' LOCALAPPDATA = 'C:\Users\.\AppData\Local' LOGONSERVER = '\\DC1PA' NUMBER_OF_PROCESSORS = '8' OS = 'Windows_NT' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' PCOMM_Root = 'C:\PCOMWIN\' PROCESSOR_ARCHITECTURE = 'AMD64' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' PROCESSOR_LEVEL = '6' PROCESSOR_REVISION = '3c03' ProgramData = 'C:\ProgramData' ProgramFiles = 'C:\Program Files' ProgramFiles(x86) = 'C:\Program Files (x86)' ProgramW6432 = 'C:\Program Files' PROMPT = '$P$G' PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\' PUBLIC = 'C:\Users\Public' SESSIONNAME = 'Console' SystemDrive = 'C:' SystemRoot = 'C:\Windows' TEMP = 'C:\Users\.BAK\AppData\Local\Temp' TMP = 'C:\Users\.BAK\AppData\Local\Temp' UATDATA = 'C:\Windows\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77' USERDNSDOMAIN = 'xxx.xxx' USERDOMAIN = 'xxx' USERNAME = '.' USERPROFILE = 'C:\Users\.' VBOX_MSI_INSTALL_PATH = 'C:\Program Files\VirtualBox\' windir = 'C:\Windows' windows_tracing_flags = '3' windows_tracing_logfile = 'C:\BVTBin\Tests\installpackage\csilogfile.log' HKEY_CURRENT_USER\Software\Cygwin HKEY_CURRENT_USER\Software\Cygwin\Installations (default) = '\??\C:\cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations (default) = '\??\C:\cygwin' 0b1a0f41647558d5 = '\??\C:\Program Files' HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\setup (default) = 'C:\cygwin' HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Cygwin\Installations (default) = '\??\C:\Program Files (x86)\Exact Audio Copy' obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: c5e39b7a9d22bafb Path: C:\cygwin System: Key: 0b1a0f41647558d5 Path: C:\Program Files (ORPHANED) User: Key: c5e39b7a9d22bafb Path: C:\cygwin c: hd NTFS953767Mb 51% CP CS UN PA FCQU d: cd
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
> On Feb 26, 2019, at 12:37 PM, Jerry Baker wrote: > > That's why you're reading about it "on the appropriate list," as described on > that page. It's a take it or leave it thing. I report it, and the cygwin > community can do whatever they like with it - ignore it, investigate it, > shoot the messenger. It's their project. What is also described on the page are the reporting guidelines. Please read them again, paying special attention to the bolded part. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On Tue, Feb 26, 2019 at 12:38 PM Jerry Baker via cygwin wrote: > > That's why you're reading about it "on the appropriate list," as > described on that page. It's a take it or leave it thing. I report it, > and the cygwin community can do whatever they like with it - ignore it, > investigate it, shoot the messenger. It's their project. The requested cygcheck output would be helpful in this regard. "Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment in your report. Please do not compress or otherwise encode the output. Just attach it as a straight text file so that it can be easily viewed." -Richard Campbell. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
On 2/26/2019 10:30 AM, Houder wrote: Jerry, short answer: -- Problem reports: http://cygwin.com/problems.html ^^^ ^^^ ^^^ That's why you're reading about it "on the appropriate list," as described on that page. It's a take it or leave it thing. I report it, and the cygwin community can do whatever they like with it - ignore it, investigate it, shoot the messenger. It's their project. FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple . and please, use "bottom-posting" (observe my reordering above). Thank you. Will do. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
> On 2/26/2019 7:38 AM, Jerry Baker via cygwin wrote: > > I have a large installation of cygwin on Windows 7 x64 for the last > > decade that has been working without issue. When I use setup-x86_64.exe > > (2.895) to upgrade the cygwin 2.11.2-1 package to cygwin 3.0.1-1, all of > > my cygwin applications stop working. Simply executing a command (such as > > 'bash' or 'grep' or 'date') at a command line just yields a blinking > > cursor that never returns anything. As soon as I switch back to version > > 2.11.2-1 everything works again. On Tue, 26 Feb 2019 09:59:56, Jerry Baker via cygwin" wrote: > I have narrowed it down to cygwin1.dll. If I install cygwin 3.0.1-1 and > overwrite cygwin1.dll with the 2.11.2-1 version, everything works. > Likewise, if I install cygwin 2.11.2-1 and overwrite cygwin1.dll with > the 3.0.1-1 version everything stops working. > > Additional information about the broken applications: cygwin > applications running under 3.0.1-1 show no output but a blinking cursor > and do not respond to CTRL+C or ENTER keys. Jerry, short answer: > -- > Problem reports: http://cygwin.com/problems.html ^^^ ^^^ ^^^ > FAQ: http://cygwin.com/faq/ > Documentation: http://cygwin.com/docs.html > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple .. and please, use "bottom-posting" (observe my reordering above). Thank you. Henri -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
I have narrowed it down to cygwin1.dll. If I install cygwin 3.0.1-1 and overwrite cygwin1.dll with the 2.11.2-1 version, everything works. Likewise, if I install cygwin 2.11.2-1 and overwrite cygwin1.dll with the 3.0.1-1 version everything stops working. Additional information about the broken applications: cygwin applications running under 3.0.1-1 show no output but a blinking cursor and do not respond to CTRL+C or ENTER keys. On 2/26/2019 7:38 AM, Jerry Baker via cygwin wrote: I have a large installation of cygwin on Windows 7 x64 for the last decade that has been working without issue. When I use setup-x86_64.exe (2.895) to upgrade the cygwin 2.11.2-1 package to cygwin 3.0.1-1, all of my cygwin applications stop working. Simply executing a command (such as 'bash' or 'grep' or 'date') at a command line just yields a blinking cursor that never returns anything. As soon as I switch back to version 2.11.2-1 everything works again. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64
I have a large installation of cygwin on Windows 7 x64 for the last decade that has been working without issue. When I use setup-x86_64.exe (2.895) to upgrade the cygwin 2.11.2-1 package to cygwin 3.0.1-1, all of my cygwin applications stop working. Simply executing a command (such as 'bash' or 'grep' or 'date') at a command line just yields a blinking cursor that never returns anything. As soon as I switch back to version 2.11.2-1 everything works again. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
