Cygwin triggers integrity scrubbing on ReFS filesystems, making searching files impossible on large datasets
I formatted a drive today, with ReFS on a Storage Pool mirror with integrity streams enabled, before copying data over from a backup. The data included several million files, which I search often with tools like find and grep. After the copy was finished, I tried doing a simple find: time find . -iname file.png I noticed that the search was taking much longer than expected, and I gave up after waiting for over 20 minutes. I confirmed that I could perform a search of the same data on an external USB3 drive formatted NTFS in between 1-1.5 minutes. To verify that this is in fact an incompatibility with ReFS's integrity streams, I formatted the same pool with this feature disabled and copied the files back over. Without integrity streams, the find operation took about 30 seconds. I confirmed this further by formatting the pool as NTFS, with a similar result. I then formatted the pool one last time with ReFS again with integrity streams enabled, and the problem returned. Although the behavior appears as a program hang, it's just very slow at searching, and not actually frozen. It continues to respond to Ctrl-C and, if a more permissive pattern is used, output can be seen during the search; it's just very slow. I believe the issue has to do with how Cygwin or find is accessing these files as it searches, triggering the integrity scrubber on each visit, causing the search to be unbearably slow. Using Windows search on the same disk does not have this problem. I haven't tried to do any performance comparison with grep, but I would expect the experience to be similarly poor or worse. It's interesting that the scrubber is triggered in this example with find, as I'm only examining the name of files, and not trying to read their contents. See here for more information on ReFS integrity streams: https://learn.microsoft.com/en-us/windows-server/storage/refs/integrity-streams To format a disk with this feature, PowerShell must be used, as it's not enabled by default or accessible from the GUI: Format-Volume -DriveLetter D -FileSystem REFS -SetIntegrityStreams $true The hardware I used was two Crucial MX500 2TB SSDs, recently trimmed, in a RAID1 mirror configuration in Storage Spaces on Windows 10 Professional for Workstations. My system just formatted and fully updated. Cygwin was also a fresh download and fully updated. The system is otherwise very fast, with a Ryzen 1800X and 64GB of memory. At this point, I am unable to use Cygwin whatsoever on any disk formatted ReFS with the integrity streams feature enabled for any kind of performant workload on a dataset that includes I/O on a large number of files. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Would it be possible to update the bash package?
Hi maintainers, Would it be possible to get an updated version of the bash package? The latest version available for cygwin is 4.4.12-3 which was released in 2017. There's been at least one major version of bash (5.0) released since then in January 2019 and 5.1 just came out in December 2020. Jack -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
On Tue, Jan 12, 2021 at 5:20 PM Andrey Repin wrote: > > Again, the properties are read BY SYSTEM at the moment the link is created. > In other words, Windows is unable to create a link to nonexistent > (unreachable) target (not directly, at least). This is false. Links can be created arbitrarily both at the Windows command line using MKLINK and programmatically with the CreateSymbolicLink function. The information about what type of link to make during a copy operation can be read from the link being copied. The target does not have to exist for a link to be created. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
Operations like cp and rsync etc. should still work. The type of symbolic link to be created can be read from the file attributes of the one being copied. On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote: > > On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com) wrote: > > I am using symbolic links native to Windows. My CYGWIN environment > > variable has been set to "winsymlinks:nativestrict" and my account has > > permission to make symbolic links. This is an issue specifically with > > Cygwin; I have no problems making links at the windows command line. > > Cygwin also does not have a problem making symbolic links-- if the > > target already exists. The issue is that I cannot create native > > symbolic links with Cygwin for targets that DON'T exist. > > > > The normal behavior for both Windows and Linux is to create the > > symbolic link whether the target exists or not. I don't know why > > Cygwin fails to do this only for native Windows symbolic links. It > > does not have a problem creating links to any target with the default > > Cygwin (non-Windows) symbolic links. > > Windows native symlinks encode the object type of the target and the > encoded type must match that of the target or the link will not work > when the target exists. > > A UNIX symlink does not encode any details of the target. > > Cygwin doesn't know what type of native symlink to create if the > target does not exist. > > I hope this knowledge helps. > > Jeffrey Altman > > > > > > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation:https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
I think there is a misunderstanding with how to set up your environment to reproduce my test cases. I did state in the subject "native symbolic links" but I can see that this can be misinterpreted and I should have clarified. I am using symbolic links native to Windows. My CYGWIN environment variable has been set to "winsymlinks:nativestrict" and my account has permission to make symbolic links. This is an issue specifically with Cygwin; I have no problems making links at the windows command line. Cygwin also does not have a problem making symbolic links-- if the target already exists. The issue is that I cannot create native symbolic links with Cygwin for targets that DON'T exist. The normal behavior for both Windows and Linux is to create the symbolic link whether the target exists or not. I don't know why Cygwin fails to do this only for native Windows symbolic links. It does not have a problem creating links to any target with the default Cygwin (non-Windows) symbolic links. On Mon, Jan 4, 2021 at 7:30 AM Eliot Moss wrote: > > On 1/4/2021 5:36 AM, Matt D. via Cygwin wrote: > > Did you try any of my test cases? This can't and doesn't work for the > > reasons I outlined in my previous message: > > > > $ cp -av folder_a/a folder_b/ > > 'folder_a/a' -> 'folder_b/a' > > cp: cannot create symbolic link 'folder_b/a': No such file or directory > > > > $ cp -dv folder_a/a folder_b/ > > 'folder_a/a' -> 'folder_b/a' > > cp: cannot create symbolic link 'folder_b/a': No such file or directory > > > > $ cp -Pv folder_a/a folder_b/ > > 'folder_a/a' -> 'folder_b/a' > > cp: cannot create symbolic link 'folder_b/a': No such file or directory > > So did you mkdir folder_b first? I don't think cp will create it for you. I > tried the commands above with folder_b not existing and got the behavior you > indicated, but when I created folder_b first, all three cp commands worked. > This overall behavior does not surprise me. > > On the other hand, if I have folder_b non-existing and do (e.g.) > > cp -rav folder_a folder_b > > then it _does_ create folder_b, and also copies the links. > > HTH - Eliot Moss > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation:https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
Did you try any of my test cases? This can't and doesn't work for the reasons I outlined in my previous message: $ cp -av folder_a/a folder_b/ 'folder_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory $ cp -dv folder_a/a folder_b/ 'folder_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory $ cp -Pv folder_a/a folder_b/ 'folder_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory On Sun, Jan 3, 2021 at 12:00 AM Brian Inglis wrote: > > On 2021-01-02 21:16, Matt D. via Cygwin wrote: > > I have a folder with a lot of native Windows symbolic links. I want to > > copy this folder. > > > > I cannot rsync or cp this folder due to Cygwin being unable to create > > symbolic links without also wanting to verify the link target. This > > can be demonstrated: > > > > $ ln -s a b > > ln: failed to create symbolic link 'b': No such file or directory > > > > If I create a test directory folder_a/ and folder_b/. Inside I will > > "touch a" and "ln -s a b". > > > > I cannot rsync this folder: > > > > $ rsync -a folder_a/ folder_b/ > > rsync: symlink "folder_a/b" -> "a" failed: No such file or directory (2) > > rsync error: some files/attrs were not transferred (see previous > > errors) (code 23) at main.c(1306) [sender=3.2.0dev] > > > > Using "cp -a folder_a/* folder_b/" in this test case DOES work but > > this is simply because files were returned in the correct order and > > the link could be created. > > > > This can be demonstrated where this works fine: > > > > $ cp -a folder_a/a folder_a/b folder_b/ > > > > But this does not: > > > > $ cp -a folder_a/b folder_a/b folder_b/ > > cp: cannot create symbolic link 'folder_b/b': No such file or directory > > cp: warning: source file 'folder_a/b' specified more than once > > > > The order in which files are returned while listing them in a > > directory and necessitating their pre-existence while performing a > > deep copy is impossible. It's also very normal for symbolic links to > > exist which may or may not point to a valid target depending on the > > observing path. > > > > Windows does NOT require a link to be valid before creation. This can > > be demonstrated with mklink: > > > > C:\mklink b a > > symbolic link created for b <<===>> a > > Depending on exactly what you have and what you want to do try: > > $ cp -av > $ cp -dv > $ cp -Pv > or > > robocopy /sl > > -- > 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. > [Data in binary units and prefixes, physical quantities in SI.] > -- > Problem reports: https://cygwin.com/problems.html > FAQ: https://cygwin.com/faq/ > Documentation:https://cygwin.com/docs.html > Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
I have a folder with a lot of native Windows symbolic links. I want to copy this folder. I cannot rsync or cp this folder due to Cygwin being unable to create symbolic links without also wanting to verify the link target. This can be demonstrated: $ ln -s a b ln: failed to create symbolic link 'b': No such file or directory If I create a test directory folder_a/ and folder_b/. Inside I will "touch a" and "ln -s a b". I cannot rsync this folder: $ rsync -a folder_a/ folder_b/ rsync: symlink "folder_a/b" -> "a" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1306) [sender=3.2.0dev] Using "cp -a folder_a/* folder_b/" in this test case DOES work but this is simply because files were returned in the correct order and the link could be created. This can be demonstrated where this works fine: $ cp -a folder_a/a folder_a/b folder_b/ But this does not: $ cp -a folder_a/b folder_a/b folder_b/ cp: cannot create symbolic link 'folder_b/b': No such file or directory cp: warning: source file 'folder_a/b' specified more than once The order in which files are returned while listing them in a directory and necessitating their pre-existence while performing a deep copy is impossible. It's also very normal for symbolic links to exist which may or may not point to a valid target depending on the observing path. Windows does NOT require a link to be valid before creation. This can be demonstrated with mklink: C:\mklink b a symbolic link created for b <<===>> a -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
How to ensure that /bin takes priority over System32 with "bash -c"?
I have Cygwin's /bin directory configured to be available on my login environment PATH by default. This behavior is inherited when I run a bash login shell: $ where sort C:\cygwin\bin\sort.exe C:\Windows\System32\sort.exe But if I run the following script from a Windows command prompt: C:\> bash -c "where sort" C:\Windows\System32\sort.exe C:\cygwin\bin\sort.exe This creates problems when I want to run a bash script from a process that does not inherit my login environment. Scripts can fail unexpectedly where identically named binaries from System32 take priority. I can't always know what binaries exist in C:\Windows\System32 when writing my scripts. Am I supposed to always launch scripts as "bash --login -i -c"? I don't want or need to have bash run all of its login scripts unnecessarily. How can I run my bash scripts without invoking it as a login shell and ensure that /bin has the environment priority over System32 binaries? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Error: "-gThe system cannot find the file specified." When bash script containing "cut" is run from cmd
Please ignore this. There was an error in my test case. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Error: "-gThe system cannot find the file specified." When bash script containing "cut" is run from cmd
Simple Bash script: > #!/bin/bash > > cut Save as "testme.sh" in C:\ or elsewhere. Open a Windows command prompt and type: > cmd /c bash -c /c/testme.sh I get the following error: > -gThe system cannot find the file specified. This only seems to trigger when bash is running as a child process of cmd. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: Setup reports "http://mirrors.kernel.org/sourceware/cygwin/" no longer supported
> From: Cygwin On Behalf Of Brian Inglis > > On 2020-07-18 19:09, Matt Seitz wrote: > > When I ran Setup today to get the latest Cygwin, Setup reported an error: > > > > Warning: One or more mirrors you have selected is/are not on the list of > official Cygwin mirrors any more. It/They may be out of date or missing some > packages. > > For more info check: https://cygwin.com/mirrors-report.html > the status counts agree with the server statuses in the tables below. > Most issues are transient or fairly short term; if the mirror status changes > to o > out-of-date, you may want to reach out to the mirror host support and report > an issue; if it is a weekend, there may be no support available. Thanks for your help! I just checked the page, and didn't see any errors reported for "http://mirrors.kernel.org/sourceware/cygwin/;. I downloaded and ran Setup again and still saw the same error. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Setup reports "http://mirrors.kernel.org/sourceware/cygwin/" no longer supported
When I ran Setup today to get the latest Cygwin, Setup reported an error: Warning: One or more mirrors you have selected is/are not on the list of official Cygwin mirrors any more. It/They may be out of date or missing some packages. cygcheck.out Description: cygcheck.out -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: Copying of symbolic links not working as expected
Note that this creates a chicken-and-the-egg problem when copying paths which contain symbolic links which will be but are not yet valid at the time of copying. For example, copying a very large and complex tree with many lots of links will result in a broken copy. I'm trying to copy a directory tree right now and it's a major headache. For example: $ cp -ra /c/data/repositories/ /c/development/repositories/ cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifest.xml': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/config': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/description': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/hooks': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/info': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/logs': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/objects': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/packed-refs': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/refs': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/rr-cache': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/shallow': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests/.git/svn': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests.git/hooks/commit-msg': No such file or directory cp: cannot create symbolic link '/c/development/repositories/repositories/aosp/source/.repo/manifests.git/hooks/pre-auto-gc': No such file or directory ... And so on. I had the same problem while trying to tar and untar: tar: aosp/source/system/vold/.git/shallow: Cannot create symlink to ‘../../../.repo/projects/system/vold.git/shallow’: No such file or directory tar: aosp/source/system/vold/.git/packed-refs: Cannot create symlink to ‘../../../.repo/projects/system/vold.git/packed-refs’: No such file or directory tar: aosp/source/system/netd/.git/shallow: Cannot create symlink to ‘../../../.repo/projects/system/netd.git/shallow’: No such file or directory tar: aosp/source/system/netd/.git/packed-refs: Cannot create symlink to ‘../../../.repo/projects/system/netd.git/packed-refs’: No such file or directory tar: aosp/source/system/media/.git/shallow: Cannot create symlink to ‘../../../.repo/projects/system/media.git/shallow’: No such file or directory tar: aosp/source/system/media/.git/packed-refs: Cannot create symlink to ‘../../../.repo/projects/system/media.git/packed-refs’: No such file or directory tar: aosp/source/system/extras/.git/shallow: Cannot create symlink to ‘../../../.repo/projects/system/extras.git/shallow’: No such file or directory tar: aosp/source/system/extras/.git/packed-refs: Cannot create symlink to ‘../../../.repo/projects/system/extras.git/packed-refs’: No such file or directory tar: aosp/source/system/core/.git/shallow: Cannot create symlink to ‘../../../.repo/projects/system/core.git/shallow’: No such file or directory tar: aosp/source/system/core/.git/packed-refs: Cannot create symlink to ‘../../../.repo/projects/system/core.git/packed-refs’: No such file or directory tar: aosp/source/system/bluetooth/.git/shallow: Cannot create symlink to ‘../../../.repo/projects/system/bluetooth.git/shallow’: No such file or directory tar: aosp/source/sdk/.git/shallow: Cannot create symlink to ‘../../.repo/projects/sdk.git/shallow’: No such file or directory tar: aosp/source/sdk/.git/packed-refs: Cannot create symlink to ‘../../.repo/projects/sdk.git/packed-refs’: No such file or directory tar: aosp/source/prebuilt/.git/shallow: Cannot create symlink to ‘../../.repo/projects/prebuilt.git/shallow’: No such file or directory tar: aosp/source/prebuilt/.git/packed-refs: Cannot create symlink to ‘../../.repo/projects/prebuilt.git/packed-refs’: No such file or directory tar: aosp/source/packages/wallpapers/PhaseBeam/.git/shallow: Cannot create symlink to ‘../../../../.repo/projects/packages/wallpapers/PhaseBeam.git/shallow’: No such file or directory tar: aosp/source/packages/wallpapers/PhaseBeam/.git/packed-refs:
Copying of symbolic links not working as expected
I'm experiencing a discrepancy between Linux cp and Cygwin cp when copying native symbolic links: Test/ FolderA/ 123/ 456/ -> 123/ On Linux I can: > cp -r FolderA/ FolderB/ > ls -l FolderB/ total 0 drwxrwxr-x. 2 account group 45 Apr 21 05:47 123 lrwxrwxrwx. 1 account group 4 Apr 21 05:47 456 -> 123/ Entire folder copied with relative symblic link paths preserved. *** (starting from the original state -- rm -rf FolderB/) *** > mkdir FolderB/ > cp -r FolderA/456 FolderB/ > ls -l FolderB/ total 0 lrwxrwxrwx. 1 account group 4 Apr 21 05:47 456 -> 123/ Note that "456 -> 123/" in "FolderB/" is a BROKEN link. This is DESIRABLE as it preserves my curated symbolic links with their relative paths. On Cygwin: > cp -r FolderA/ FolderB/ ... Works as expected But: > cp -r FolderA/456 FolderB/ ERRORS: cp: cannot create symbolic link 'FolderB/456': No such file or directory I know that there is no file or directory there. I'm trying to copy one to this location. -- 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
Can't create symbolic links in child directories
This works: > touch a > ln -s a b This no longer works: > touch a > mkdir b > ln -s a b/c Error: ln: failed to create symbolic link 'b/c': No such file or directory My CYGWIN environment is also configured using "winsymlinks:nativestrict". I am running the following version (updated today): CYGWIN_NT-10.0-WOW WORKSTATION 3.0.5(0.338/5/3) 2019-03-31 11:22 i686 Cygwin I cannot confirm at which point this bug appeared as I updated from some version prior to 3.0. I am reasonably certain that this has worked before as I use symbolic links often. -- 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
Cannot use screen when Cygwin is installed on a FAT32 filesystem / chmod does not work on FAT32 directories
I'm trying to use Cygwin on a Windows machine with the latest release. The system in question must run from a filesystem formatted with FAT32 and therefore inherits the 'noacl' field according to the documentation. After a clean install and running Cygwin.bat, I am greeted with the following error when attempting to call 'screen -ls': > $ screen -ls > Directory /tmp/uscreens/S-MyUserName must have mode 700. Note that at this point the /tmp/uscreens directory has been created for the first time. Closing this terminal, reopening it, and calling 'screen -ls' again results in the following error: > $ screen -ls > Directory '/tmp/uscreens' must have mode 777. The problem is that screen requires that the /tmp/uscreens directory have mode 777. This directory is already accessible to 'Everyone' with all permissions but is recognized only as 'drwxr-xr-x' (755). This appears to be an issue specifically with how permissions are displayed on a FAT32 drive as I can confirm that I have never had this issue on an NTFS filesystem with the 'noacl' flag specified in fstab. I thought that I could workaround this by simply patching these checks out so I downloaded the source and removing the offending lines: > if (((int)st.st_mode & 0777) != n) > Panic(0, "Directory '%s' must have mode %03o.", SockDir, n); .. > if ((st.st_mode & 0777) != 0700) > Panic(0, "Directory %s must have mode 700.", SockPath); This allows screen to run and for screens to be created. But now it fails to list any screens. When no screens exist I get the following output: > $ screen -ls > No Sockets found in /tmp/uscreens/S-MyUserName And when screens exists: > $ screen -ls > There is a screen on: > 1 Socket in /tmp/uscreens/S-MyUserName Notice that a screen is detected (the output is formatted correctly) but the screens are not populated in the list. I'm thinking that this new problem may reside within socket.c of screen's source code but I'm not sure. I have read a number of comments online about these permission errors for both Cygwin and various Linux installations. All of them recommend either setting the permissions to 777 with chmod or altering the NTFS permissions, both of which has no affect on the directory permissions for the FAT32 filesystem (but confirmed working on NTFS). Is there someone available to assist me in looking into this? It appears as though I've uncovered a somewhat obscure bug. Thank you. -- 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
libglut is missing library for MinGW static linking
libglut-devel provides libglut.a and libglut.dll.a but linking libglut.a with either "-lglut" or "-lglut.dll" both depend on either cygglut-3.dll or libglut-0.dll respectively when compiling for Cygwin or MinGW. I understand that this isn't a big deal for Cygwin binaries as it's not possible to statically link those executables anyways. But glut has the ability to link statically and this is of benefit on Windows with MinGW for convenience and ease of distribution. To perform static linking against glut, I have to download "libfreeglut_static.a" as provided by http://freeglut.sourceforge.net. I can still use libglut but the static library provides the missing dependencies to mitigate the need for the shared library. I can compile as such: i686-w64-mingw32-g++.exe -DFREEGLUT_STATIC main.cpp -lglut -lfreeglut_static -lgdi32 -lwinmm -lglu32 -lopengl32 -L. -oa.out The resulting executable is completely static and stand-alone and does not require a shared library. The key here is the define "FREEGLUT_STATIC" along with libfreeglut_static provided from the freeglut website. I don't know what Cygwin's policy is on providing static libraries for MinGW but this is a very good candidate as it already has all of the necessary declarations defined. Matt D. -- 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
What is the purpose of libglut32?
Does anyone know what libglut32 is used for? It comes as part of "w32api-runtime" and "mingw64-i686-runtime" and is installed into: usr/lib/w32api/libglut32.a and usr/i686-w64-mingw32/sys-root/mingw/lib/libglut32.a I haven't been able to find a use for this as attempting to link with it produces the following errors: undefined reference to `_impglutInitWithExit@12' undefined reference to `_impglutCreateWindowWithExit@8' undefined reference to `_impglutCreateMenuWithExit@8' It is possible to link with it if -DGLUT_DISABLE_ATEXIT_HACK is used to skip these declarations but then it depends upon glut32.dll which isn't provided by any package. How can libglut32 be used for anything if it is missing its binary dependency? Is this library unused? Is the glut32.dll dependency an error? Also note that this define really isn't meant to be used since it disables a necessary workaround as defined in freeglut_std.h. See here: > Win32 has an annoying issue where there are multiple C run-time > libraries (CRTs). If the executable is linked with a different CRT > from the GLUT DLL, the GLUT DLL will not share the same CRT static > data seen by the executable. In particular, atexit callbacks > registered in the executable will not be called if GLUT calls its > (different) exit routine. GLUT is typically built with the > "/MD" option (the CRT with multithreading DLL support), but the Visual > C++ linker default is "/ML" (the single threaded CRT). > > One workaround to this issue is requiring users to always link with > the same CRT as GLUT is compiled with. That requires users supply a > non-standard option. GLUT 3.7 has its own built-in workaround where > the executable's "exit" function pointer is covertly passed to GLUT. > GLUT then calls the executable's exit function pointer to ensure that > any "atexit" calls registered by the application are called if GLUT > needs to exit. > > Note that the __glut*WithExit routines should NEVER be called > directly. To avoid the atexit workaround, #define > GLUT_DISABLE_ATEXIT_HACK. This library is NOT the same as libgut, which seems to be the appropriate way to include glut, even when compiling for MinGW. Matt D. -- 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
How to find a package's maintainer?
How can I find who maintains a given Cygwin package?
Re: xterm / Windows 10 question
Hi Andrey, I'm starting to feel a bit guilty about wasting bandwidth on the Cygwin mailing list because my initial question was answered by other posters and the problem has, as a practical matter, been solved. That's not to say I understand all aspects of the interaction between Windows 10 keyboard layouts, the X Server, and xterm windows. To answer your questions: > Why? Do you need the INTL one? If not, just remove it. Yes, I agree. I did remove ENG INTL following Microsoft's documented procedure. (Settings > Time & Language > Region & Language, select ENG INTL, click Remove.) This appeared to work -- ENG INTL no longer shows up in the Region & Language dialog. However, it remains one of the choices I can toggle through using +space. So... presumably I don''t yet know how to actually remove it. > That makes little sense to me. > What if I have more than one input language? What if I actually NEED both > layouts? Yes, of course, if you need more than one input language you should keep them installed. What I was trying to say in my previous post was simply that the X Server uses the layout that's in effect when you start the X Server. So if, for example, you want xterm windows to start up with "ENG US" rather than "ENG INTL", then you should select "ENG US" before starting the X Server. If you fail to do that, it seems you can switch after the fact using "setxkbmap". Best Regards, --- Matt On Tue, Jun 12, 2018 at 7:51 PM, Andrey Repin wrote: > Greetings, Matt Nicholas! > > > Hi Jon, > > > Thanks for the additional comments. > > > The two keyboard layouts that are installed are "ENG US" and "ENG INTL". > > (These are the two I see when I toggle through them using > Key>+space.) > > Why? Do you need the INTL one? If not, just remove it. > > > I just rebooted the laptop and did not observe the problem with xterm > > windows that prompted my initial post. I suppose this all makes sense > > based on the fact that xterm windows use the layout that was in effect > when > > the X Server was started. I.e., you can't subsequently change the > behavior > > of xterm by selecting a different layout using +space. (At > > that point can use "setxkbmap us".) > > > My understanding at this point is that the only thing necessary is to > make > > sure the desired layout (in my case "ENG US") is selected before starting > > the X Server. > > That makes little sense to me. > What if I have more than one input language? What if I actually NEED both > layouts? > > > -- > With best regards, > Andrey Repin > Wednesday, June 13, 2018 5:50:14 > > 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: xterm / Windows 10 question
Hi Jon, Thanks for the additional comments. The two keyboard layouts that are installed are "ENG US" and "ENG INTL". (These are the two I see when I toggle through them using +space.) I just rebooted the laptop and did not observe the problem with xterm windows that prompted my initial post. I suppose this all makes sense based on the fact that xterm windows use the layout that was in effect when the X Server was started. I.e., you can't subsequently change the behavior of xterm by selecting a different layout using +space. (At that point can use "setxkbmap us".) My understanding at this point is that the only thing necessary is to make sure the desired layout (in my case "ENG US") is selected before starting the X Server. --- Matt On Sun, Jun 10, 2018 at 1:52 PM, Jon Turney wrote: > On 06/06/2018 23:33, Matt Nicholas wrote: > >> That was the clue I needed. Thanks! >> >> Here are the relevant lines from my */var/log/xwin/XWin.0.log*: >> >> [494293.296] (--) Windows keyboard layout: "00020409" (00020409) "United >> States-International", type 7 >> [494293.296] (--) Found matching XKB configuration "English >> (USA,International)" >> [494293.296] (--) Model = "pc105" Layout = "us_intl" Variant = "none" >> Options = "none" >> [494293.296] Rules = "base" Model = "pc105" Layout = "us_intl" Variant = >> "none" Options = "none" >> >> I'm not sure why the X server starts with *Layout = "us_intl"*, because if >> I look in *Control Panel > All Control Panel Items > Language* it says the >> language is *English (United States)*. >> > > "Display language" and "Keyboard Layout/Input method" are different > concepts, although they seem to be somewhat combined in the settings app > now. > > However, I found that if I enter the command "*setxkbmap us*" in an xterm >> window it solves the problem (i.e., single quote and double quote >> characters are no longer dead keys). >> >> I'm still not sure how best to configure it so that the X server starts >> with "us" instead of "us_intl" automatically, but that's a minor issue in >> any case -- entering the "setxkbmap us" command is easy enough. >> (I can probably put the "setxkbmap us" command in ".bash_profile", if I >> don't find a more appropriate place.) >> > > I don't think this is working as intended. If you don't have the US > international keyboard layout active when the X server is started (which > I'm assuming isn't the case, or you wouldn't be surprised by the deadkeys > that layout uses), it shouldn't be selected. > > Perhaps you can clarify what keyboard layouts you have installed? > > -- > Jon Turney > Volunteer Cygwin/X X Server maintainer > -- 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: xterm / Windows 10 question
Hi Jon, That was the clue I needed. Thanks! Here are the relevant lines from my */var/log/xwin/XWin.0.log*: [494293.296] (--) Windows keyboard layout: "00020409" (00020409) "United States-International", type 7 [494293.296] (--) Found matching XKB configuration "English (USA,International)" [494293.296] (--) Model = "pc105" Layout = "us_intl" Variant = "none" Options = "none" [494293.296] Rules = "base" Model = "pc105" Layout = "us_intl" Variant = "none" Options = "none" I'm not sure why the X server starts with *Layout = "us_intl"*, because if I look in *Control Panel > All Control Panel Items > Language* it says the language is *English (United States)*. However, I found that if I enter the command "*setxkbmap us*" in an xterm window it solves the problem (i.e., single quote and double quote characters are no longer dead keys). I'm still not sure how best to configure it so that the X server starts with "us" instead of "us_intl" automatically, but that's a minor issue in any case -- entering the "setxkbmap us" command is easy enough. (I can probably put the "setxkbmap us" command in ".bash_profile", if I don't find a more appropriate place.) Best Regards, --- Matt On Wed, Jun 6, 2018 at 1:17 PM, Jon Turney wrote: > On 05/06/2018 18:19, Matt Nicholas wrote: > >> Hi David, >> Thanks for the suggestion. Unfortunately, toggling the input method does >> not make a difference in an xterm window. (It does, by the way, have the >> effect you mention in a Cygwin64 terminal window.) >> > > The X server does not use the Windows input method, but tries to setup an > appropriate X keyboard configuration based on the Windows keyboard layout > selected when it starts up. > > I suspect that an unexpected keyboard configuration is being used, if it > has dead keys when you don't want them. > > Can you show /var/log/XWin.0.log, or at least the portion of that > describing what keyboard configuration is being selected, e.g.: > > [1236607.031] (--) Windows keyboard layout: "0809" (0809) "United >> Kingdom", type 4 >> [1236607.031] (--) Found matching XKB configuration "English (United >> Kingdom)" >> [1236607.031] (--) Model = "pc105" Layout = "gb" Variant = "none" Options >> = "none" >> > > --- Matt >> >> >> On Mon, Jun 4, 2018 at 7:21 PM, David Billinghurst >> wrote: >> >> On 2018-06-05 10:47, Matt Nicholas wrote: >>> >>> I recently obtained a Dell Precision laptop running Windows 10. >>> >>>> I installed 64-bit Cygwin, including various packages that are not part >>>> of >>>> the minimal install. >>>> >>>> >>> The problem I'm having is that when I type single quote or double quote >>> >>>> characters in the xterm window, no character appears with the first >>>> keystroke. >>>> >>>> This may be an issue with the input method configured for the keyboard. >>> You can toggle this with +. Many Dell machines are >>> configured to use the US-international keyboard that encodes " to >>> an >>> umlaut, so "e to ë and so on. As a monlingual Aussie I find the plain >>> "US >>> Keyboard" has fewer surprises. >>> >> > -- 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: xterm / Windows 10 question
Hi David, Thanks for the suggestion. Unfortunately, toggling the input method does not make a difference in an xterm window. (It does, by the way, have the effect you mention in a Cygwin64 terminal window.) --- Matt On Mon, Jun 4, 2018 at 7:21 PM, David Billinghurst wrote: > On 2018-06-05 10:47, Matt Nicholas wrote: > > I recently obtained a Dell Precision laptop running Windows 10. >> I installed 64-bit Cygwin, including various packages that are not part of >> the minimal install. >> > > The problem I'm having is that when I type single quote or double quote >> characters in the xterm window, no character appears with the first >> keystroke. >> > This may be an issue with the input method configured for the keyboard. > You can toggle this with +. Many Dell machines are > configured to use the US-international keyboard that encodes " to an > umlaut, so "e to ë and so on. As a monlingual Aussie I find the plain "US > Keyboard" has fewer surprises. > -- 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: xterm / Windows 10 question
Sorry, I left out the word "not" in my last message. I meant to say: I've seen various suggestions online stating that I need to change the setting under 'Control Panel, Languages' so that the selected language is "English (United States)", rather than "English (International)". I did that and it did *not *solve the problem (nor make any discernible difference). Apologies for the omission. --- Matt On Mon, Jun 4, 2018 at 5:47 PM, Matt Nicholas wrote: > Hello, > > I have a question that I hope someone may be able to help me with. > > I recently obtained a Dell Precision laptop running Windows 10. > I installed 64-bit Cygwin, including various packages that are not part of > the minimal install. > > I start Cygwin/X as follows: > > (1) open a Cygwin64 Terminal window > (2) cd /usr/bin > (3) ./xinit -- -multiwindow & > > That works as expected, and creates an initial xterm window. I can then > start multiple independent xterm windows. > > The problem I'm having is that when I type single quote or double quote > characters in the xterm window, no character appears with the first > keystroke. > Typing the character twice, causes the character to appear, but things > don't work as expected. > For example, a command like: > find . -name "*.exe" > fails to find any files even though there are ".exe" files to be found. > > I've seen various suggestions online stating that I need to change the > setting under 'Control Panel, Languages' so that the selected language is > "English (United States)", rather than "English (International)". > I did that and it did solve the problem (nor make any discernible > difference). > > A few other clues: > (1) The problem does not occur in a Cygwin64 Terminal window. > (2) I set things up the same way on a Windows 7 PC that I also use, > and do not experience this problem in xterm windows. > > So... now I'm confused. If this were entirely a Windows 10 issue I would > not expect a Cygwin64 Terminal window to behave differently from an xterm > window. > On the other hand, it this were entirely an issue with Cygwin/X and xterm > windows, I would not expect Windows 10 and Windows 7 to be different. > > (I verified that this is not an issue with the xterm version. I have > version 327 on the Win7 PC, and 330 on the Win10 PC, but I tried 327 on the > Win10 PC and it made no difference.) > > Anyone have any ideas about how to resolve this? > > Thanks > --- Matt > > mat...@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
xterm / Windows 10 question
Hello, I have a question that I hope someone may be able to help me with. I recently obtained a Dell Precision laptop running Windows 10. I installed 64-bit Cygwin, including various packages that are not part of the minimal install. I start Cygwin/X as follows: (1) open a Cygwin64 Terminal window (2) cd /usr/bin (3) ./xinit -- -multiwindow & That works as expected, and creates an initial xterm window. I can then start multiple independent xterm windows. The problem I'm having is that when I type single quote or double quote characters in the xterm window, no character appears with the first keystroke. Typing the character twice, causes the character to appear, but things don't work as expected. For example, a command like: find . -name "*.exe" fails to find any files even though there are ".exe" files to be found. I've seen various suggestions online stating that I need to change the setting under 'Control Panel, Languages' so that the selected language is "English (United States)", rather than "English (International)". I did that and it did solve the problem (nor make any discernible difference). A few other clues: (1) The problem does not occur in a Cygwin64 Terminal window. (2) I set things up the same way on a Windows 7 PC that I also use, and do not experience this problem in xterm windows. So... now I'm confused. If this were entirely a Windows 10 issue I would not expect a Cygwin64 Terminal window to behave differently from an xterm window. On the other hand, it this were entirely an issue with Cygwin/X and xterm windows, I would not expect Windows 10 and Windows 7 to be different. (I verified that this is not an issue with the xterm version. I have version 327 on the Win7 PC, and 330 on the Win10 PC, but I tried 327 on the Win10 PC and it made no difference.) Anyone have any ideas about how to resolve this? Thanks --- Matt mat...@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
Worried your hair is falling out? This will change that
I know I was late, sorry... Cygwin-xfree ** Wellness Wire () ** AS WE AGE MOST OF US BEGIN TO LOSE HAIR. IT'S JUST PART OF LIFE. TODAY WE LOOK AT A SIMPLE WAY YOU CAN GET YOUR HAIR BACK ALONG WITH YOUR CONFIDENCE. READ MORE... (http://gfsdgs.piperposhpuppies.com/bhas4sbrat45n6san6ypipNiPObFzTcHFrMYwqBSRvU1yqitnhGYxFaBvo2S%2FTzPWeTiwzpjpRfzI3gaTH9Hek19zk0KtoEPHdIf6FYcriSg%3D%3Derp) ** http://gfsdgs.piperposhpuppies.com/bhas4sbrat45n6san6ypipNiPObFzTcHFrMYwqBSRvU1yqitnhGYxFaBvo2S%2FTzPWeTiwzpjpRfzI3gaTH9Hek19zk0KtoEPHdIf6FYcriSg%3D%3Derp ...Has your hair fallen to peices? () Don't let your hair make you feel bad. There are things you can do right now..Read on (http://gfsdgs.piperposhpuppies.com/bhas4sbrat45n6san6ypipNiPObFzTcHFrMYwqBSRvU1yqitnhGYxFaBvo2S%2FTzPWeTiwzpjpRfzI3gaTH9Hek19zk0KtoEPHdIf6FYcriSg%3D%3Derp875) Reener Development Services /-/ Three Springwood Trail Ormond Beach FL 32174 /-/ This URL (http://fsdfgsd.piperposhpuppies.com/bhsyw5n7wsr5ypipNiPObFzTcHFrMYwqBSRvU1yqitnhGYxFaBvo2S%2FTzPWeTiwzpjpRfzI3gaTH9Hek19zk0KtoEPHdIf6FYcriSg%3D%3Derp) will terminate future messages i thought it was a tide ad i hope he?s just doing bad thing after bad thing he's been doing that since community. Like () Tweet () Forward () -- 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/
Broken junctions and symlinks halt recursive cp and rsync operations?
I can make a directory 'a/' and a symlink 'b' of 'b -> a' and copy 'b' to 'c' which also points to 'a': $mkdir a $CYGWIN= ln -s a b $CYGWIN= cp -a b c On Linux if I break the link as such: $rm -r a c I can still copy the broken link: $cp -a b c But on Cygwin I cannot do this for native junctions and native symbolic links (note that Cygwin symlinks work fine in this scenario). This issue breaks both cp and rsync when working with either form of native links. $rm -r a b c $mkdir a $CYGWIN=winsymlinks:nativestrict ln -s a b $rm -r a See here: $CYGWIN=winsymlinks:nativestrict cp -a b c cp: cannot create symbolic link 'c': No such file or directory And: $rsync -a b c rsync: symlink "/c/test/c" -> "a" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1196) [sender=3.1.2] Is there a way to recover from this? It breaks copy operations of directories which contain broken symlinks where I would expect the broken link to be copied as-is. Matt D. -- 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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 1:38 PM, Matt D. wrote: On 11/4/2017 1:15 PM, Matt D. wrote: > On 11/4/2017 11:43 AM, Achim Gratz wrote: >> That's the correct thing to do, even though you made this unnecessarily >> hard for yourself by mounting your home directory with "noacl". > > It's not perfect but I've always had trouble with all of the > modifications Cygwin makes to a file's permissions to support > POSIX-style ACLs. I do miss being able to manage them with chmod and > setfacl though. > > For those wishing to set their ssh config to 600 (as recognized by > Cygwin's ssh), use the following: > > Reset file permissions: >icacls config /t /q /c /reset > > Inheritence must be disabled to alter other groups: >icacls config /inheritance:d > > Effectively regarded as "group": >icacls config /remove:g "Authenticated Users" >icacls config /remove:g "Users" > > Regarded as "other": >icacls config /remove:g "Everyone" > > Add the current user as the owner: >icacls config /grant "%USERNAME%:rw" > > > Matt D. My previous reply was missing "takeown" to take ownership. The correct sequence of commands is: icacls config /t /q /c /reset icacls config /inheritance:d takeown /f config icacls config /remove:g "Authenticated Users" icacls config /remove:g "Users" icacls config /remove:g "Everyone" icacls config /grant "%USERNAME%:rw" This is equivalent to "chmod 600 config". Matt D. Here is a more portable version of taking ownership and setting permissions to 600. It uses SIDs instead of literal names which may vary between locale: icacls "id_rsa" /t /q /c /reset icacls "id_rsa" /inheritance:d takeown /f "id_rsa" icacls "id_rsa" /remove *S-1-5-11 icacls "id_rsa" /remove *S-1-5-32-545 icacls "id_rsa" /remove *S-1-1-0 icacls "id_rsa" /grant "%USERNAME%:rw" S-1-5-11 (Authenticated Users group) S-1-5-32-545 (Users group) S-1-1-0 (Everyone group) Matt D. -- 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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 1:15 PM, Matt D. wrote: > On 11/4/2017 11:43 AM, Achim Gratz wrote: >> That's the correct thing to do, even though you made this unnecessarily >> hard for yourself by mounting your home directory with "noacl". > > It's not perfect but I've always had trouble with all of the > modifications Cygwin makes to a file's permissions to support > POSIX-style ACLs. I do miss being able to manage them with chmod and > setfacl though. > > For those wishing to set their ssh config to 600 (as recognized by > Cygwin's ssh), use the following: > > Reset file permissions: >icacls config /t /q /c /reset > > Inheritence must be disabled to alter other groups: >icacls config /inheritance:d > > Effectively regarded as "group": >icacls config /remove:g "Authenticated Users" >icacls config /remove:g "Users" > > Regarded as "other": > icacls config /remove:g "Everyone" > > Add the current user as the owner: >icacls config /grant "%USERNAME%:rw" > > > Matt D. My previous reply was missing "takeown" to take ownership. The correct sequence of commands is: icacls config /t /q /c /reset icacls config /inheritance:d takeown /f config icacls config /remove:g "Authenticated Users" icacls config /remove:g "Users" icacls config /remove:g "Everyone" icacls config /grant "%USERNAME%:rw" This is equivalent to "chmod 600 config". Matt D. -- 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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 12:37 PM, Corinna Vinschen wrote: If your build does not show the same values, then I *bet*, your test application is not using the same path as if you're using the coreutils stat tool. Apparently they access the file via different mount points, one of them "acl", the other "noacl". Ssh's readconf.c is using fstat(). If these results are more accurate with "noacl" defined then why always say "-rw-r--r--" when more information is available? Matt D. -- 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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 11:43 AM, Achim Gratz wrote: That's the correct thing to do, even though you made this unnecessarily hard for yourself by mounting your home directory with "noacl". It's not perfect but I've always had trouble with all of the modifications Cygwin makes to a file's permissions to support POSIX-style ACLs. I do miss being able to manage them with chmod and setfacl though. For those wishing to set their ssh config to 600 (as recognized by Cygwin's ssh), use the following: Reset file permissions: icacls config /t /q /c /reset Inheritence must be disabled to alter other groups: icacls config /inheritance:d Effectively regarded as "group": icacls config /remove:g "Authenticated Users" icacls config /remove:g "Users" Regarded as "other": icacls config /remove:g "Everyone" Add the current user as the owner: icacls config /grant "%USERNAME%:rw" Matt D. -- 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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 9:31 AM, Matt D. wrote:
On 11/4/2017 7:47 AM, Matt D. wrote:
On 11/4/2017 7:37 AM, Corinna Vinschen wrote:
On Nov 4 05:47, Matt D. wrote:
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists that ~/.ssh/config be less
permissive. But this file is bound to --rw-r--r-- for this option.
Would it be appropriate to request ssh to ignore this requirement when
"noacl" present on the mounted volume?
Yes, in theory. However, this shouldn't be necessary.
Ssh already has code to check extrem perms only in "acl" mounted
directories, but it does not have this extra check for config files,
basically because it was never necessary:
If you use noacl, your file perms are faked to always be 644, or
444 if the DOS R/O bit is set, or 755/555 if executable/directory.
Additionally all files are faked as if they are owned by your own
account.
Ssh checks the config file like this:
if (((sb.st_uid != 0 && sb.st_uid != getuid()) ||
(sb.st_mode & 022) != 0))
fatal("Bad owner or permissions on %s", filename);
Which means, 0644 permissions are perfectly fine. As are 755 perms
for the ~/.ssh and ~ dirs.
I just mounted my home dir "noacl". The perms are as expected:
$ ls -ld . .ssh .ssh/config .ssh/id_local
drwxr-xr-x 1 corinna vinschen0 Nov 4 12:27 .
drwxr-xr-x 1 corinna vinschen0 Mar 14 2017 .ssh
-rw-r--r-- 1 corinna vinschen 703 Jan 19 2017 .ssh/config
-rw-r--r-- 1 corinna vinschen 7329 Jan 12 2017 .ssh/id_local
Note especially the too open perms in case of the private keyfile
"id_local". Still, I can ssh into one of my other machines just fine.
How come this doesn't work for you?
Corinna
I don't know why it doesn't work for me other than the reported error. I
am trying to use ssh combined with git. My .ssh permissions are:
$ls -ld . .ssh .ssh/config .ssh/github
drwxr-xr-x 1 Matthew D'Onofrio None0 Nov 4 06:42 .
drwxr-xr-x 1 Matthew D'Onofrio None0 Nov 4 04:51 .ssh
-rw-r--r-- 1 Matthew D'Onofrio None 80 Nov 4 04:51 .ssh/config
-rw-r--r-- 1 Matthew D'Onofrio None 3243 Nov 3 10:53 .ssh/github
I removed the noacl option in fstab, re-ran Cygwin setup, set
.ssh/config to 600 and ssh was happy. I then reverted back to noacl and
the problem returned.
I'm in the process of trying to build openssh with cygpath for debugging
but this is my first time building anything from Cygwin or using
cygports so it's taking some time.
Matt D.
Please stand by. Looking into this further.
Matt D.
The code "sb.st_mode & 022" will always be true unless the group and
other bits are set to 0. So 755, 644, 555, or whatever would not work.
I made a test build which output the value of sb.st_mode and it
displayed as "100770". This value reflected the actual NTFS ACLs and not
what was displayed at the bash prompt or by "stat -c %a" (which says 644).
This makes sense because Cygwin is pulling the NTFS permissions as there
are no Cygwin ACLs defined.
The only workaround is to use Window's Security diaglog to disable
inherited permissions and remove the Users group. This does seem to
satisfy things.
I suppose the argument now is whether this behavior should change in the
face of a drive mounted with "noacl". It took a bit of guesswork as
neither chmod or setfacl was changing the NTFS permissions.
Interestingly, a config file that I chmodded when the drive was mounted
with Cygwin ACLs still works with ssh even though "noacl" is now defined
and it is still part of the HOSTNAME\Users group. Neither stat or
getfacl show these permissions but they can be seen in the security tab
of the file properties. I'm guessing that it works because it has
HOSTNAME\None below HOSTNAME\ or something?
Matt D.
--
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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 7:47 AM, Matt D. wrote:
On 11/4/2017 7:37 AM, Corinna Vinschen wrote:
On Nov 4 05:47, Matt D. wrote:
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists that ~/.ssh/config be less
permissive. But this file is bound to --rw-r--r-- for this option.
Would it be appropriate to request ssh to ignore this requirement when
"noacl" present on the mounted volume?
Yes, in theory. However, this shouldn't be necessary.
Ssh already has code to check extrem perms only in "acl" mounted
directories, but it does not have this extra check for config files,
basically because it was never necessary:
If you use noacl, your file perms are faked to always be 644, or
444 if the DOS R/O bit is set, or 755/555 if executable/directory.
Additionally all files are faked as if they are owned by your own
account.
Ssh checks the config file like this:
if (((sb.st_uid != 0 && sb.st_uid != getuid()) ||
(sb.st_mode & 022) != 0))
fatal("Bad owner or permissions on %s", filename);
Which means, 0644 permissions are perfectly fine. As are 755 perms
for the ~/.ssh and ~ dirs.
I just mounted my home dir "noacl". The perms are as expected:
$ ls -ld . .ssh .ssh/config .ssh/id_local
drwxr-xr-x 1 corinna vinschen0 Nov 4 12:27 .
drwxr-xr-x 1 corinna vinschen0 Mar 14 2017 .ssh
-rw-r--r-- 1 corinna vinschen 703 Jan 19 2017 .ssh/config
-rw-r--r-- 1 corinna vinschen 7329 Jan 12 2017 .ssh/id_local
Note especially the too open perms in case of the private keyfile
"id_local". Still, I can ssh into one of my other machines just fine.
How come this doesn't work for you?
Corinna
I don't know why it doesn't work for me other than the reported error. I
am trying to use ssh combined with git. My .ssh permissions are:
$ls -ld . .ssh .ssh/config .ssh/github
drwxr-xr-x 1 Matthew D'Onofrio None0 Nov 4 06:42 .
drwxr-xr-x 1 Matthew D'Onofrio None0 Nov 4 04:51 .ssh
-rw-r--r-- 1 Matthew D'Onofrio None 80 Nov 4 04:51 .ssh/config
-rw-r--r-- 1 Matthew D'Onofrio None 3243 Nov 3 10:53 .ssh/github
I removed the noacl option in fstab, re-ran Cygwin setup, set
.ssh/config to 600 and ssh was happy. I then reverted back to noacl and
the problem returned.
I'm in the process of trying to build openssh with cygpath for debugging
but this is my first time building anything from Cygwin or using
cygports so it's taking some time.
Matt D.
Please stand by. Looking into this further.
Matt D.
--
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: Workflow for producing patches with cygport?
Thank you.
There is no documentation for this from 'cygport --help' or 'man
cygport'. Is this an oversight?
Matt D.
On 11/4/2017 9:04 AM, Jon Turney wrote:
On 04/11/2017 10:45, Matt D. wrote:
I've gotten this far:
download cygport
download package src
cd /usr/src/package*
cygport package.cygport prep
I can now edit the source, compile, etc. But what is the workflow for
producing a patch file of my changes?
You can use 'cygport diff' to produce a patch in
${PN}-${PVR}.${ARCH}/patch/
--
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
Building OpenSSH fails when '--with-kerberos5' in the default configuration
I downloaded the source for Cygwin's OpenSSH package and attempted to
build it with the defaults:
cygport openssh.cygport prep
cygport openssh.cygport compile
This resulted in the following compile errors:
In file included from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/openbsd-compat.h:180:0,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/includes.h:174,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/port-aix.c:27:
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/bsd-misc.h:124:39:
error: expected identifier or ‘(’ before ‘do’
# define krb5_free_error_message(a,b) do { } while(0)
^
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/bsd-misc.h:124:46:
error: expected identifier or ‘(’ before ‘while’
# define krb5_free_error_message(a,b) do { } while(0)
^
In file included from /usr/include/krb5/krb5.h:8488:0,
from /usr/include/krb5.h:8,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/auth.h:42,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/port-aix.c:33:
/usr/include/et/com_err.h:38:20: error: conflicting types for
‘error_message’
extern char const *error_message (long);
^
In file included from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/includes.h:171:0,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/port-aix.c:27:
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/defines.h:684:43:
note: previous declaration of ‘error_message’ was here
# define krb5_get_err_text(context,code) error_message(code)
^
make[1]: *** [Makefile:26: port-aix.o] Error 1
make[1]: Leaving directory
'/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/build/openbsd-compat'
make: *** [Makefile:156: openbsd-compat/libopenbsd-compat.a] Error 2
*** ERROR: make failed
Modifying openssh.cygport by removing "--with-kerberos5" allows compilation.
I have all of the applicable Kerberos packages:
$cygcheck -c | grep -i krb
libgssapi_krb5_2 1.15.2-1OK
libkrb5-devel 1.15.2-1OK
libkrb5_3 1.15.2-1OK
libkrb5support0 1.15.2-1OK
Am I missing something?
Matt D.
--
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: Building the Open SSH package from source
On 2/8/2016 3:31 PM, Sorin Adrian Savu wrote:
> On Mon, Feb 8, 2016 at 10:17 PM, Achim Gratz <strom...@nexgo.de> wrote:
>> Sorin Adrian Savu writes:
>>> I've been trying to build openssh-7.1p2-1.src using cyport. After
>>> several iterations due missing packages, I ended up with these errors
>>> after "cygport --debug openssh.cygport compile" and I have no idea how
>>> to proceed:
>> […]
>>
>> You are missing the devlopment packages for Kerberos5 at least on your
>> installation.
>>
>>
> I did install the Kerberos5 development packages just before getting
> these errors.
>
> $ cygcheck -c | grep -i krb
> libgssapi_krb5_2 1.13.2-4
OK
> libkrb5-devel1.13.2-4
OK
> libkrb5_31.13.2-4
OK
> libkrb5support0 1.13.2-4
OK
>
> Do I need anything else ?
>
> --
> 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
>
I'm having the same problem.
$cygcheck -c | grep -i krb
libgssapi_krb5_2 1.15.2-1 OK
libkrb5-devel 1.15.2-1 OK
libkrb5_3 1.15.2-1 OK
libkrb5support0 1.15.2-1 OK
Error log:
In file included from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/openbsd-compat.h:180:0,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/includes.h:174,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/port-aix.c:27:
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/bsd-misc.h:124:39:
error: expected identifier or ‘(’ before ‘do’
# define krb5_free_error_message(a,b) do { } while(0)
^
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/bsd-misc.h:124:46:
error: expected identifier or ‘(’ before ‘while’
# define krb5_free_error_message(a,b) do { } while(0)
^
In file included from /usr/include/krb5/krb5.h:8488:0,
from /usr/include/krb5.h:8,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/auth.h:42,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/port-aix.c:33:
/usr/include/et/com_err.h:38:20: error: conflicting types for
‘error_message’
extern char const *error_message (long);
^
In file included from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/includes.h:171:0,
from
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/openbsd-compat/port-aix.c:27:
/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/src/openssh-7.6p1/defines.h:684:43:
note: previous declaration of ‘error_message’ was here
# define krb5_get_err_text(context,code) error_message(code)
^
make[1]: *** [Makefile:26: port-aix.o] Error 1
make[1]: Leaving directory
'/usr/src/openssh-7.6p1-1.src/openssh-7.6p1-1.i686/build/openbsd-compat'
make: *** [Makefile:156: openbsd-compat/libopenbsd-compat.a] Error 2
*** ERROR: make failed
Matt D.
--
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: No way to use ssh ~/.ssh/config with "noacl" option
On 11/4/2017 7:37 AM, Corinna Vinschen wrote:
On Nov 4 05:47, Matt D. wrote:
I mount with "noacl" as I don't need ACLs for my purposes and prefer to
leave everything up to Windows permissions.
The problem with this is that ssh insists that ~/.ssh/config be less
permissive. But this file is bound to --rw-r--r-- for this option.
Would it be appropriate to request ssh to ignore this requirement when
"noacl" present on the mounted volume?
Yes, in theory. However, this shouldn't be necessary.
Ssh already has code to check extrem perms only in "acl" mounted
directories, but it does not have this extra check for config files,
basically because it was never necessary:
If you use noacl, your file perms are faked to always be 644, or
444 if the DOS R/O bit is set, or 755/555 if executable/directory.
Additionally all files are faked as if they are owned by your own
account.
Ssh checks the config file like this:
if (((sb.st_uid != 0 && sb.st_uid != getuid()) ||
(sb.st_mode & 022) != 0))
fatal("Bad owner or permissions on %s", filename);
Which means, 0644 permissions are perfectly fine. As are 755 perms
for the ~/.ssh and ~ dirs.
I just mounted my home dir "noacl". The perms are as expected:
$ ls -ld . .ssh .ssh/config .ssh/id_local
drwxr-xr-x 1 corinna vinschen0 Nov 4 12:27 .
drwxr-xr-x 1 corinna vinschen0 Mar 14 2017 .ssh
-rw-r--r-- 1 corinna vinschen 703 Jan 19 2017 .ssh/config
-rw-r--r-- 1 corinna vinschen 7329 Jan 12 2017 .ssh/id_local
Note especially the too open perms in case of the private keyfile
"id_local". Still, I can ssh into one of my other machines just fine.
How come this doesn't work for you?
Corinna
I don't know why it doesn't work for me other than the reported error. I
am trying to use ssh combined with git. My .ssh permissions are:
$ls -ld . .ssh .ssh/config .ssh/github
drwxr-xr-x 1 Matthew D'Onofrio None0 Nov 4 06:42 .
drwxr-xr-x 1 Matthew D'Onofrio None0 Nov 4 04:51 .ssh
-rw-r--r-- 1 Matthew D'Onofrio None 80 Nov 4 04:51 .ssh/config
-rw-r--r-- 1 Matthew D'Onofrio None 3243 Nov 3 10:53 .ssh/github
I removed the noacl option in fstab, re-ran Cygwin setup, set
.ssh/config to 600 and ssh was happy. I then reverted back to noacl and
the problem returned.
I'm in the process of trying to build openssh with cygpath for debugging
but this is my first time building anything from Cygwin or using
cygports so it's taking some time.
Matt D.
--
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
Workflow for producing patches with cygport?
I've gotten this far: download cygport download package src cd /usr/src/package* cygport package.cygport prep I can now edit the source, compile, etc. But what is the workflow for producing a patch file of my changes? Matt D. -- 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
No way to use ssh ~/.ssh/config with "noacl" option
I mount with "noacl" as I don't need ACLs for my purposes and prefer to leave everything up to Windows permissions. The problem with this is that ssh insists that ~/.ssh/config be less permissive. But this file is bound to --rw-r--r-- for this option. Would it be appropriate to request ssh to ignore this requirement when "noacl" present on the mounted volume? Matt D. -- 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
xinit is ignoring -displayfd option
I'm not sure at what release this bug appeared as my .display already existed with the value '0' which masked the problem. When I ran xinit on a system without a .display already present caused some of my scripts to fail as this file is no longer created due to the wrong fd being used. Here is the output of xinit: https://pastebin.com/raw/HJB9WGk7 Matt D. -- 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
XWin Server: no XDG Menu, no right-click menu
I am having two problems when I click the "XWin Server" item in the Windows "Start Menu" 1.The "Cygwin X/Server" icon appears in the notification area.But if I right click the notification icon, no menu appears. 2.The "X Applications Menu" (XDG Menu) icon does not appear in the notification area Cygcheck.out and XWin.0.log attached. Cygwin Configuration Diagnostics Current System Time: Thu Aug 17 01:37:38 2017 Windows 7 Enterprise Ver 6.1 Build 7601 Service Pack 1 Path: C:\cygwin64\usr\local\bin C:\cygwin64\bin C:\Ruby193\bin C:\ProgramData\Oracle\Java\javapath C:\Program Files\Common Files\Microsoft Shared\Windows Live C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live C:\Windows\system32 C:\Windows C:\Windows\System32\Wbem C:\Windows\System32\WindowsPowerShell\v1.0 C:\Windows\System32\WindowsPowerShell\v1.0 C:\Program Files (x86)\Windows Live\Shared C:\Program Files (x86)\QuickTime\QTSystem C:\Program Files (x86)\ActivIdentity\ActivClient C:\Program Files\ActivIdentity\ActivClient C:\Program Files (x86)\PuTTY C:\Program Files\TortoiseSVN\bin C:\Program Files (x86)\Sennheiser\SoftphoneSDK C:\Program Files (x86)\FAHClient C:\Users\matseitz\AppData\Local\Box\Box Edit . Output from C:\cygwin64\bin\id.exe UID: 1236279(matseitz) GID: 1049089(Domain Users) 1049089(Domain Users) 544(Administrators) 545(Users) 4(INTERACTIVE) 66049(CONSOLE LOGON) 11(Authenticated Users) 15(This Organization) 4095(CurrentSession) 66048(LOCAL) 12017936(jira_dev_rtp1) 1410434(group.dgoeckel) 2036099(SMT.SPVTG-SJC-ARCHIVE.R) 10894238(ntgstg.adgroup) 1796221(group.rchandra) 1051873(crypto) 9751444(SMT.SPRSG-OS-GROUP.M) 10894204(ntgdev.adgroup) 11356884(csg-business-intelligence) 1612192(sw-reflectionx) 10894237(ntgprd.adgroup) 1605608(sw-MicrosoftProjectStd) 9673438(smt.nostg-biz-ops.m) 10021128(SMT.spvtg-cdbu-releases.R) 1386906(SJC.SPRSG-OS-GROUP.M) 2120980(SMT.spvtg-rtp-scm.R) 1641618(XMM-ISA-Users) 11139750(windows-login-ecs-sjc-slim-user) 9849139(SMT.cbabu-ssp.M) 10037159(softex) 9848970(clarity_bo_users) 12495079(dascode-users-aurora-sjc) 1612179(sw-AdobeAcrobatPro) 1882530(CDO-ENGALL_Users) 10350400(access_to_betasoftware) 12568769(jira_sjc_shared1_test) 2081949(anycusers) 10876512(apuser) 10079159(CDO-ENGALL_Clone) 1882228(cisco-allmanagers) 10387042(project.392286.users) 12549333(csg_jira) 10377824(stash_sjc_shared1) 10962651(Desktop-CrashPlan-2015) 10896211(appportfolio-users) 10034041(aurora-users-all) 11870522(dascode-users-aurora) 11541998(group.ramsrir) 1442642(sw-MicrosoftProjectPro) 1636165(xch-harvest-opt-in) 10416749(SMT.TORVID-CONTENT.R) 10818695(jira_sjc_shared1) 1605401(sw-AdobeAcrobatStd) 2050050(group.syeluru) 1066438(BXB.CCBU-MILESTONEBUILDS.M) 10407486(dft-us-sdaas-users) 2025875(aurora-users-047-sjc) 9849140(SMT.cbabu-ssp.R) 1167350(EA-Software) 2124105(SMT.CCBU-MILESTONEBUILDS.M) 1409955(group.crobbins) 10257911(cdo-git-users) 10079169(VTG-FTP_ENGUSERS) 9743667(group.vnanniyu) 6704889(smt.chn_faw.r) 1416165(group.rlloyd) 12521306(dascode-mat-limit-max1) 11356690(bb_sjc_shared1) 1145383(crypto) 1140797(BXB.CCBU-MILESTONEBUILDS.M) 1167351(EA-Software) 1057818(crypto) 1102414(BXB.CCBU-MILESTONEBUILDS.M) 1150160(EA-Software) 1251636(BXB.CCBU-MILESTONEBUILDS.M) 1132097(crypto) 1385352(EA-Software) 1063262(BXB.CCBU-MILESTONEBUILDS.M) 1068099(crypto) 1149516(EA-Software) 1106931(BXB.CCBU-MILESTONEBUILDS.M) 1155796(BXB.CCBU-MILESTONEBUILDS.M) 1087827(BXB.CCBU-MILESTONEBUILDS.M) 1098196(BXB.CCBU-MILESTONEBUILDS.M) 1095438(BXB.CCBU-MILESTONEBUILDS.M) 1069489(crypto) 405504(High Mandatory Level) SysDir: C:\Windows\system32 WinDir: C:\Windows USER = 'matseitz' PWD = '/home/matseitz' HOME = '/home/matseitz' USERDOMAIN = 'CISCO' OS = 'Windows_NT' COMMONPROGRAMFILES = 'C:\Program Files\Common Files' PROCESSOR_LEVEL = '6' PSModulePath = 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\;C:\Program Files\Arellia\Powershell\' CommonProgramW6432 = 'C:\Program Files\Common Files' CommonProgramFiles(x86) = 'C:\Program Files (x86)\Common Files' FP_NO_HOST_CHECK = 'NO' LANG = 'en_US.UTF-8' TZ = 'America/Los_Angeles' HOSTNAME = 'MATSEITZ-WS02' PUBLIC = 'C:\Users\Public' OLDPWD = '/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs/Cygwin' UATDATA = 'C:\Windows\CCM\UATData\D9F8C395-CAB8-491d-B8AC-179A1FE1BE77' USERNAME = 'matseitz' LOGONSERVER = '\\ADC-SJC1-C1-4' PROCESSOR_ARCHITECTURE = 'AMD64' LOCALAPPDATA = 'C:\Users\matseitz\AppData\Local' COMPUTERNAME = 'MATSEITZ-WS02' !:: = '::\' DEFLOGDIR = 'C:\ProgramData\McAfee\Endpoint Security\Logs' SYSTEMDRIVE = 'C:' USERPROFILE = 'C:\Users\matseitz' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC' SYSTEMROOT = 'C:\Windows' USERDOMAIN_ROAMINGPROFILE = 'CISCO' PROCESSOR_IDENTIFIER = 'Intel64 Family 6 Model 60 Stepping 3, GenuineIntel' TMP = '/tmp'
Settings from lang.sh causing garbled output in dialog when run from cmd.exe
If I invoke a login shell from a Windows command prompt and run a dialog:
dialog --no-cancel --inputbox "test" 0 0 ""
I get garbled output. I do not have this issue when running from mintty.
See the following image examples:
http://imgur.com/a/Y4mEC
http://imgur.com/a/7akZQ
If I remove this line from /etc/profile.d/lang.sh:
test -z "${_LC_ALL_SET_:-${LC_CTYPE:-$LANG}}" && export
LANG=$(/usr/bin/locale -uU)
Then the problem goes away.
Why am I getting garbled output with this line present?
Matt D.
--
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
How to get GNU Parallel working with Cygwin
I noticed today that we don't have this package. I tried building it from source with a './configure && make && make install'. But when I run "sem" I get the following output: 1 [main] perl 7712 child_info_fork::abort: address space needed by 'Util.dll' (0x1E) is already occupied 1 [main] perl 13596 child_info_fork::abort: address space needed by 'Util.dll' (0x1E) is already occupied 1 [main] perl 13920 child_info_fork::abort: address space needed by 'Util.dll' (0x1E) is already occupied ... I don't have any issue running perl directly. The package in question: https://www.gnu.org/software/parallel/ Any ideas? Thank you. -- 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: [ANNOUNCEMENT] Updated: dash-0.5.9.1-1
Personally, I would invoke a variation of Linus's attitude to breaking user space apps: the distribution should not break existing user's scripts, even if they are not following "the rules". If you want to speed up the scripts distributed by Cygwin, then I would suggest modifying those scripts to use #!/bin/dash. Or give the user an option to change "/bin/sh" to point to dash, but don't make that the default setting. But breaking who-knows-how-many user scripts without the user's informed consent seems like an undesirable solution. -- 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: XWin no longer working for me with -nolisten tcp?
This workaround I mentioned only appears to work for my local X session. For example, I can open a local xterm from Cygwin: $ xterm But once I connect elsewhere: $ ssh me@somewhere -Y I get the following error when trying to bring up an xterm: $ xterm connect /tmp/.X11-unix/X0: Permission denied xterm: Xt error: Can't open display: localhost:10.0 I tried purging /tmp on Cygwin but to no avail. Note that the server I am connecting to has not been rebooted in months and nothing has changed there. Matt D. On 2/17/2017 2:20 PM, Matt D. wrote: I just recently formatted and reinstalled Windows 10 x64. I have not updated anything related to Cygwin and everything version-wise is just as it was. I was previously starting X with the following: $ xinit -- -multiplemonitors -multiwindow -clipboard -noprimary -dpi 96 -nolisten tcp -displayfd 3 3>/c/home/.display But now it fails to open the display: http://pastebin.com/raw/bLHTWcrS I can get around this issue by using "-listen tcp" instead of "-nolisten tcp" but I don't understand why. This is especially ironic considering that this is the complete opposite workaround to what I had to use three years ago: https://cygwin.com/ml/cygwin-xfree/2014-07/msg00017.html Matt D. -- 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
XWin no longer working for me with -nolisten tcp?
I just recently formatted and reinstalled Windows 10 x64. I have not updated anything related to Cygwin and everything version-wise is just as it was. I was previously starting X with the following: $ xinit -- -multiplemonitors -multiwindow -clipboard -noprimary -dpi 96 -nolisten tcp -displayfd 3 3>/c/home/.display But now it fails to open the display: http://pastebin.com/raw/bLHTWcrS I can get around this issue by using "-listen tcp" instead of "-nolisten tcp" but I don't understand why. This is especially ironic considering that this is the complete opposite workaround to what I had to use three years ago: https://cygwin.com/ml/cygwin-xfree/2014-07/msg00017.html Matt D. -- 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
Cannot access volumes mounted with 'mklink /d' which point to a volume UUID
On Windows you can create symbolic links which point to volume UUIDs as
a way of mounting and unmounting them without having to use the
administrative disk management tools.
For example, in cmd:
mountvol
...
\\?\Volume{079b79c9----1000}\
C:\
...
mklink /d test \\?\Volume{079b79c9----1000}\
...
dir test
I call mounvol to get a list of volumes and create a symbolic link
'test' which points to the C:\ UUID. When I then 'dir test' it will list
all files on that volume.
If I try to access it through Cygwin Bash I get the following error:
$ dir test/
dir: cannot access 'test/': No such file or directory
This makes it difficult to work with unmounted volumes as it's not
always possible to access the administrative disk management snap-in and
the mountvol/mklink has always been my go-to for this type of
functionality. It would be great if Cygwin would support it.
Matt D.
--
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: -displayfd outputting some garbage?
This is causing issues where I try to perform: echo $(cat .display) Which results in: bash: warning: command substitution: ignored null byte in input 0 Matt D. On 2/7/2017 7:46 PM, Matt D. wrote: I have an xinit script which outputs the display id to a file with the following option: xinit .. -displayfd 3 3>$HOME/.display This outputs correctly '0' but appends 0x00 and 0x0A. Why is it outputting a null byte and this 0x0A? Matt D. -- 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/
-displayfd outputting some garbage?
I have an xinit script which outputs the display id to a file with the following option: xinit .. -displayfd 3 3>$HOME/.display This outputs correctly '0' but appends 0x00 and 0x0A. Why is it outputting a null byte and this 0x0A? Matt D. -- 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/
Re: Bash declare built-in regression loses array quotations
My scripts have been updated to account for breaking changes in Bash 4.4 and I have updated all of my Cygwin packages back to the latest version. I am no longer receiving any assertions. Was I wrong to assume that I could selectively roll back Bash to 4.3 as I did? Matt D. On 1/13/2017 3:11 PM, Eric Blake wrote: On 01/13/2017 02:00 PM, Matt D. wrote: I updated yesterday to the latest Cygwin x86 release which included an updated Bash 4.4.5(1). This release changes the default behavior of the built-in 'declare' command which is causing scripts which relied on this functionality to break. The following test will illustrate the change: declare -A list list[a]=1 list[b]=2 list[c]=3 declare -p | grep list= On Bash 4.4.5(1) the output is: declare -A list=([a]="1" [b]="2" [c]="3" ) Previously the result was: declare -A list='([a]="1" [b]="2" [c]="3" )' This is an intentional upstream behavior change. Quoting the upstream release notes: There are a few incompatible changes between bash-4.3 and bash-4.4. Bash now retains the exit status only of asynchronous jobs, as opposed to all jobs. This means that it is not possible to use `wait' to retrieve the status of a previously-completed synchronous command. Bash no longer attempts to perform compound assignment if a variable expansion on the right-hand side of an assignment statement to `declare' or `local' has the form of a compound assignment. There are other changes to compound array assignments used as arguments to the `declare' and `local' builtins, but those should be backwards compatible, albeit with warning messages about deprecated constructs. Read the descriptions of the various compatibility options in COMPAT or the man page for more details. ... q. The declare builtin no longer displays array variables using the compound assignment syntax with quotes; that will generate warnings when re-used as input, and isn't necessary. Both output forms should produce the same results when re-evaluated; except that the form with the extra '' now issues warnings (which is why declare -p no longer uses the extra ''). I can confirm that this has always been the expected output when running this command on Cygwin and Linux. I run CentOS which does not track the latest Bash release and I don't know the procedure to check whether this is an upstream regression or not. It's not a regression, but an intentional change; you'll have to update your script to quit relying on unspecified output. -- 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: Bash declare built-in regression loses array quotations
While my simple test passed, I am now experiencing runtime assertions with Cygwin. These assertions occur on 2.6.1-1 and the alternatively available 2.6.0-1: assertion "(s - envblock) <= tl" failed: file "/home/corinna/src/cygwin/cygwin-2.6.1/cygwin-2.6.1-1.i686/src/newlib-cygwin/winsup/cygwin/environ.cc", line 1242, function: char** build_env(const char* const*, WCHAR*&, int&, bool, HANDLE) /c/data/workspaces/remote/plugins/shared/scripts/plugin.sh: line 64: 8448 Aborted (core dumped) /usr/local/lib/codespunk/scra.exp --p "$p" "bin/$plugin.jar" "$user@$host:$path/other/plugins/$plugin.jar" assertion "(s - envblock) <= tl" failed: file "/home/corinna/src/cygwin/cygwin-2.6.1/cygwin-2.6.1-1.i686/src/newlib-cygwin/winsup/cygwin/environ.cc", line 1242, function: char** build_env(const char* const*, WCHAR*&, int&, bool, HANDLE) /c/data/workspaces/remote/plugins/shared/scripts/plugin.sh: line 64: 13920 Aborted (core dumped) /usr/local/lib/codespunk/scrb.exp $h --u "$u" --p "$p" "chmod 660 $path/other/plugins/$plugin.jar" This bug is SEVERE and I can no longer perform any builds with these assertions. The Cygwin installer does not appear to provide a working version for me to roll back to. Please advise. I cannot get any work done with in this state. Matt D. On 1/13/2017 3:00 PM, Matt D. wrote: I updated yesterday to the latest Cygwin x86 release which included an updated Bash 4.4.5(1). This release changes the default behavior of the built-in 'declare' command which is causing scripts which relied on this functionality to break. The following test will illustrate the change: declare -A list list[a]=1 list[b]=2 list[c]=3 declare -p | grep list= On Bash 4.4.5(1) the output is: declare -A list=([a]="1" [b]="2" [c]="3" ) Previously the result was: declare -A list='([a]="1" [b]="2" [c]="3" )' I can confirm that this has always been the expected output when running this command on Cygwin and Linux. I run CentOS which does not track the latest Bash release and I don't know the procedure to check whether this is an upstream regression or not. I have rolled back to Bash 4.3.48-8 which has restored the previous functionality. Please advise. Matt D. -- 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
Bash declare built-in regression loses array quotations
I updated yesterday to the latest Cygwin x86 release which included an updated Bash 4.4.5(1). This release changes the default behavior of the built-in 'declare' command which is causing scripts which relied on this functionality to break. The following test will illustrate the change: declare -A list list[a]=1 list[b]=2 list[c]=3 declare -p | grep list= On Bash 4.4.5(1) the output is: declare -A list=([a]="1" [b]="2" [c]="3" ) Previously the result was: declare -A list='([a]="1" [b]="2" [c]="3" )' I can confirm that this has always been the expected output when running this command on Cygwin and Linux. I run CentOS which does not track the latest Bash release and I don't know the procedure to check whether this is an upstream regression or not. I have rolled back to Bash 4.3.48-8 which has restored the previous functionality. Please advise. Matt D. -- 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: httpd/sshd will not start due to "failed to create proxy mutex" error
I fixed it! I don't know if the fix is any good, but the server starts and serves pages. The key was this Mutex directive: https://httpd.apache.org/docs/current/mod/core.html#mutex I wound up adding this to my httpd.conf: > Mutex posixsem proxy I don't know if "posixsem" is the right choice, but it seems to work. All of the choices have warnings that make them all sound horrible: dizzyness, depression, erectile dysfunction...but we're going to try this. I'm just developing on my local system, anyway. Cheers, Matt -- 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
httpd/sshd will not start due to "failed to create proxy mutex" error
I can't remember if I've ever set up Apache on Cygwin before, but I'm trying to do so now and I'm not getting anywhere. I'm trying to install them as services and it's not working. I'm trying to run these commands in an administrator shell: $ cygrunsrv -I httpd -p /usr/sbin/httpd (The service successfully installs. I mean, I can see cygserver and httpd in services.msc. cygserver is running) $ cygrunsrv -S httpd cygrunsrv: Error starting a service: QueryServiceStatus: Win32 error 1062: The service has not been started. $ cat /var/log/httpd/error_log [Wed Apr 20 20:02:39.734289 2016] [core:emerg] [pid 604] (88)Function not implemented: AH00023: Couldn't create the proxy mutex [Wed Apr 20 20:02:39.735010 2016] [proxy:crit] [pid 604] (88)Function not implemented: AH02478: failed to create proxy mutex AH00016: Configuration Failed I've tried uninstalling, rebooting, and reinstalling httpd with no luck. I've recently upgraded from cygwin32 to cygwin64. Well, they're both installed, and my home directory is still in the 32-bit C:\cygwin. I believe I've got everything else pointing to cygwin64. I didn't actually move anything from C:\cygwin to C:\cygwin64, I just did a clean install of 64 alongside 32. Everything else is working great except for trying to run the httpd and sshd servers. I'm on Windows 10 Home version. Maybe Bill Gates' business acumen is preventing me from running a server on a home version? Thanks for any clues, Matt -- 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: Conflict between Cygwin 1.7 and Ubuntu for Windows 14316
> It's 100% RFC 1178 compliant, I have never seen that before. That's awesome. Thanks for that. I do have one thing they missed: I once named a machine "Null". Screwed up the whole network. I find it interesting that the string representation of "Null" is actually used for some networking purposes. Apparently it is also used as a special case in databases as well apparently as a last name of "Null" messes up all sorts of systems. -Matt -- 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: Re: Cannot Run X Programs
Jon, Wow. That worked! I had been beating my head against the wall! Thanks so much. Blessings, Matt myemai...@verizon.net (703) 795-9224 (c) On 03/24/16, Jon Turney<jon.tur...@dronecode.org.uk> wrote: On 24/03/2016 20:10, Matt Morrow wrote: > I'm on Windows 10 running: > CYGWIN_NT-6.2 HOME 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64 Cygwin > > I cannot run X programs like xclock or xterm. > With xclock I get this (depending on how I have $DISPLAY set): > Error: Can't open display: HOME:0 > Error: Can't open display: HOME:0.0 > Error: Can't open display: localhost:0 > Error: Can't open display: localhost:0.0 > Error: Can't open display: 192.168.1.7:0 > Error: Can't open display: 192.168.1.7:0.0 > [...] > > > Any ideas what's wrong? Did you try DISPLAY=:0.0? http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-xserver-nolisten-tcp-default -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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
Cannot Run X Programs
Hi, I'm on Windows 10 running: CYGWIN_NT-6.2 HOME 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64 Cygwin I cannot run X programs like xclock or xterm. With xclock I get this (depending on how I have $DISPLAY set): Error: Can't open display: HOME:0 Error: Can't open display: HOME:0.0 Error: Can't open display: localhost:0 Error: Can't open display: localhost:0.0 Error: Can't open display: 192.168.1.7:0 Error: Can't open display: 192.168.1.7:0.0 With xterm I get: xterm: Xt error: Can't open display: 192.168.1.7:0.0 xterm: Xt error: Can't open display: 192.168.1.7:0 xterm: Xt error: Can't open display: localhost:0.0 xterm: Xt error: Can't open display: localhost:0 xterm: Xt error: Can't open display: HOME:0.0 xterm: Xt error: Can't open display: HOME:0 xhost gives me: > xhost + xhost: unable to open display "192.168.1.7:0.0" After startx and startxwin (see below) I try again: > xclock Error: Can't open display: 192.168.1.7:0.0 > xterm xterm: Xt error: Can't open display: 192.168.1.7:0.0 Here's startx and startxwin: > startx Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.18.1.0 OS: CYGWIN_NT-6.2 HOME 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64 OS: Windows 10 [Windows NT 10.0 build 10586] (Win64) Package: version 1.18.1-2 built 2016-03-03 XWin was started with the following command line: /usr/bin/X :0 -auth C:/Users/matt/.serverauth.6572 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: C:/Users/matt/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - RemoteSession: no winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0005 winSetEngine - Using Shadow DirectDraw NonLocking winScreenInit - Using Windows display depth of 32 bits per pixel winWindowProc - WM_SIZE - new client area w: 1904 h: 1001 winFinishScreenInitFB - Masks: 00ff ff00 00ff 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_MESA_copy_sub_buffer (II) AIGLX: Loaded and initialized swrast (II) GLX: Initialized DRISWRAST GL provider for screen 0 winPointerWarpCursor - Discarding first warp: 952 500 (--) 3 mouse buttons found (--) Setting autorepeat to delay=500, rate=31 (--) Windows keyboard layout: "0409" (0409) "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" winClipboardThreadProc - DISPLAY=:0.0 OS maintains clipboard viewer chain: yes winProcEstablishConnection - winInitClipboard returned. winClipboardProc - XOpenDisplay () returned and successfully opened the display. C:/Users/matt/.xinitrc: line 1: /usr/local/kde1/bin/startkde: No such file or directory xinit: connection to X server lost waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop. winClipboardProc - XDestroyWindow succeeded. winDeinitMultiWindowWM - Noting shutdown in progress (II) Server terminated successfully (0). Closing log file. > startxwin Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.18.1.0 OS: CYGWIN_NT-6.2 HOME 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64 OS: Windows 10 [Windows NT 10.0 build 10586] (Win64) Package: version 1.18.1-2 built 2016-03-03 XWin was started with the following command line: /usr/bin/XWin :0 -multiwindow -auth C:/Users/matt/.serverauth.8388 (II) xorg.conf is not supported (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information LoadPreferences: C:/Users/matt/.XWinrc not found LoadPreferences: Loading /etc/X11/system.XWinrc LoadPreferences: Done parsing the configuration file... winDetectSupportedEngines - RemoteSession: no winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL winDetectSupportedEngines - Returning, supported engines 0005 winSetEngine - Multi Window or Rootless => ShadowGDI winScreenInit - Using Windows display depth of 32 bits per pixel winAllocateFBShadowGDI - Creating DIB with width: 1920 height: 1080 depth: 32 winFinishScreenInitFB - Masks: 00ff ff00 00ff winInitVisualsShadowGDI - Masks 00ff ff00 00ff BPRGB 8 d 24 bpp 32 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 glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' (II) A
git gui won't run: error: git-gui died of signal 11
When I try to run "git gui" I get the following error: Matt@hp /cygdrive/c/Users/Matt $ git gui error: git-gui died of signal 11 Log files attached. Sincerely, Matt Seitz cygcheck.out Description: cygcheck.out wish8.5.exe.stackdump Description: wish8.5.exe.stackdump -- 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
Segfault when running tests for SDL 1.2.15
I'm not sure where to direct this to but from my testing so far the segfault is only occurring when building the libraries with Cygwin. I've created a support script which will allow it to compile correctly under the latest Cygwin: SDL: https://www.libsdl.org/release/SDL-1.2.15.tar.gz Support Script: http://pastebin.com/2dGFwzhH Drop the script in the SDL-1.2.15 directory and run it; I named mine ./configure-cygwin for clarity. It will patch configure and configure.in and add some other minor changes to get it working. Then: make make install cd test ./configure make After the tests have been built you will find that testsprite.exe and testbitmap.exe seem to work but segfault when the mouse moves into the client area. testgl.exe segfaults immediately. I've build the same source using TDM-GCC with no issues. What can be done to look into this kind of segfault? My environment: CYGWIN_NT-10.0-WOW 2.3.1(0.291/5/3) 2015-11-14 12:42 i686 Cygwin Winows 10 x64, AMD FX-8370, GeForce 970 Thanks, Matt D. -- 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: Git issue.
Ok. I wasn't sure as the behavior changed. It worked in 1.9.5 and then stopped working when I moved to 2.5.x. I'm not sure if it matters to you, but doing some bisecting it looks like the behavior changed between 2.2.0 and 2.3.0: - [/cygdrive/d/projects] $ git --version git version 2.2.0.dirty [/cygdrive/d/projects] $ git --git-dir=d:/projects/git-git/.git config alias.foo ls-files [/cygdrive/d/projects] $ - [/cygdrive/d/projects] $ git --version git version 2.3.0.dirty [/cygdrive/d/projects] $ git --git-dir=d:/projects/git-git/.git config alias.foo ls-files error: could not lock config file d:/projects/git-git/.git/config: No such file or directory We'll adjust accordingly. Thanks! -Matt - Original Message - From: "Adam Dinwoodie" <a...@dinwoodie.org> To: cygwin@cygwin.com Sent: Thursday, December 3, 2015 1:42:21 PM Subject: Re: Git issue. On Sun, Nov 22, 2015 at 11:30:27PM +, boulderfans wrote: > [/cygdrive/d/projects] > $ git --git-dir=d:/projects/git-git/.git config alias.foo ls-files > error: Unable to open tempfile: > /cygdrive/d/projects/d:/projects/git-git/.git/config.lock > error: could not lock config file d:/projects/git-git/.git/config: No such > file or directory > > The problem is that the code that is checking the --git-dir option > doesn't work properly if you use a DOS drive:/path specification. Hi Matt, Cygwin applications, including applications you've compiled yourself using the Cygwin toolchain, normally expect Cygwin's Linux-like paths, e.g. /cygdrive/d/projects/git-git. Attempting to use Windows paths simply isn't meant to work. You can convert from a Windows path to the equivalent Cygwin path using the cygpath utility, e.g.: git --git-dir="$(cygpath 'd:/projects/git-git/.git')" config alias.foo ls-files Adam -- 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 -- 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: chere Bash Prompt Here window closes immediately
>From: Dave Kilroy [mailto:kilr...@googlemail.com] >>On 23/10/2015 16:16, Matt Seitz (matseitz) wrote: >> When I right click a folder in Windows Explorer and select "Bash >> Prompt Here", a window opens briefly and then closes immediately. > I suspect this may be due to the use of %DISPLAY% (which I don't recall). I > see that in your environment this is set to ":1.0" > What happens if you run the following from cmd: Thanks for the debugging steps. Unfortunately, I already worked around the problem by cleaning up a lock file so that the Xwin server would start as ":0.0" instead of ":1.0". If I run into the problem again, I will try your debugging steps. > Also, I presume the X server is already running? Yes, the X server was already running. -- 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
No support for ACLs on network shares?
I noticed today that when accessing a network share, the permissions for the current user are not resolving. For example, I'm connected to a network share //server/share which is a CentOS share with a unix login/password. The share is already logged in by Windows and on the keychain so I don't have to enter the login information. In Cygwin, 'cd //server/share' then 'ls -l' I get this: drwxrwx--- 1 Unknown+User Unix_Group+1001 0 Nov 23 2015 test I'm already logged in through windows as the 'Unknown+User' but Cygwin does not recognize that I have access to any of the ACLs for the owner or groups and also does not resolve the SID name. The problem with this is that files created or modified are only done so in the 'Everyone' permission and inherited permissions such as the execute bit are not recognized. My use-case is where I've mapped a network path to either a network drive or a symlinked folder (with Windows mklink) with the path on the environment's PATH. In this case, files which are executable are not recognized and do not appear when calling 'which'. It seems as though Cygwin only maps ACLs to the SIDs stored in passwd and group and cannot handle ACLs when accessing network devices where SIDs are not present in these files. Running passwd/mkgroup after the share is on the keychain does not provide additional SIDs. Is there no support for ACLs across network shares at all? Matt D. -- 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: No support for ACLs on network shares?
Andrey, My samba server is configured to use winbind and when inspecting the file using explorer properties, the SIDs resolve correctly as: "NAME (HOSTNAME\username)" where "NAME" is my name on the unix account and "username" is my login. The problem is that Cygwin isn't aware of this SID since it's the user I log in as to the remove server and isn't a local SID. Using noacl is a valid workaround but I would prefer an ACL-supported solution if possible. Matt D. On 11/23/2015 3:08 AM, Andrey Repin wrote: Greetings, Matt D.! I noticed today that when accessing a network share, the permissions for the current user are not resolving. For example, I'm connected to a network share //server/share which is a CentOS share with a unix login/password. The share is already logged in by Windows and on the keychain so I don't have to enter the login information. In Cygwin, 'cd //server/share' then 'ls -l' I get this: drwxrwx--- 1 Unknown+User Unix_Group+1001 0 Nov 23 2015 test This looks like a share on a Linux(samba) server with no UID mapping active. I'm already logged in through windows as the 'Unknown+User' but Cygwin does not recognize that I have access to any of the ACLs for the owner or groups and also does not resolve the SID name. This is really not Cygwin's fault. Windows does all the resolution here, Cygwin only relay that information to you. The problem with this is that files created or modified are only done so in the 'Everyone' permission and inherited permissions such as the execute bit are not recognized. My use-case is where I've mapped a network path to either a network drive or a symlinked folder (with Windows mklink) with the path on the environment's PATH. In this case, files which are executable are not recognized and do not appear when calling 'which'. It seems as though Cygwin only maps ACLs to the SIDs stored in passwd and group and cannot handle ACLs when accessing network devices where SIDs are not present in these files. Running passwd/mkgroup after the share is on the keychain does not provide additional SIDs. Is there no support for ACLs across network shares at all? There is. But in cases such as this, when two hosts are not parts of the same domain, you are bound to get weird behavior in the strict security context. You may try defer default ACL resolutions to Windows. Edit your /etc/fstab, add the 'noacl' flag to a 'cygdrive' mount. -- 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 gjar core dumps whereas Oracle jar does not
I'm not sure if this got lost, ignored, or wasn't forwarded appropriately, but I'm still getting this core dump: https://sourceware.org/ml/cygwin/2015-10/msg00257.html Matt D. -- 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
Calling cygpath from find exec?
Is there a reason why these produce different results?
find . -exec cygpath -wa {} \;
find . -exec echo $(cygpath -wa {}) \;
I have to do this which is much slower:
find . -exec bash -c 'echo $(cygpath -wa {})' \;
Or this:
find . | while read a; do echo $(cygpath -wa $a); done
Matt D.
--
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: gawk: Bad File Descriptor error with concurrent readonly access to a network file
I haven't had an opportunity to look into it but I've also encountered errors when performing a parallel make build (make -j) on a large C++ project which has multiple interdependencies across a network share with too many threads. The reported "Bad File Descriptor" is the same error that I get. Matt D. On 10/27/2015 5:52 AM, Corinna Vinschen wrote: On Sep 25 16:31, Vermessung AVT - Wolfgang Rieger wrote: 1) Concurrent read access to the setup files was possible and worked fine with local files (24 hrs testing with millions of file accesses in 4 parallel jobs). 2) However, when the file to be read (datafile.txt) is stored on a network share on a file server - which is the case in our working environment - the error could be reproduced. The number of Bad file descriptor errors seems to be related to the work load at the server where the file resides. 3) The MS copy command shows no such error, even with network files. So we can substitute the cat's by copy's. For gawk, however, there is no shell alternative. It looks like there is a small time frame in opening files when the server file is non-accessible to other processes. If a parallel job happens to access the same file within that short time period while another process is opening it, the "Bad File Descriptor" error is thrown. Cygwin uses full sharing for all files it opens, unless the file is opened in very specific circumstances (e.g, creating a symlink, deleting a file). "Bad file descriptor" doesn't point to a sharing problem. It seems the handle is unusable or something. I tried your testcase and I can't reproduce the problem in my environment. Have you tried catching a trace of the problem via strace? It would be helpful to see where the EBADF occurs. Corinna -- 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: git gui: assertion "font != NULL" failed
> From: Jon Turney [mailto:jon.tur...@dronecode.org.uk] > Sent: Monday, October 19, 2015 7:54 > > The dependency chain is git-gui -> gitk -> font-adobe-dpi75 > > It doesn't look like the fonts in xorg-x11-fonts-Type1 are available to > fontconfig, so I've changed the dependency of gitk to dejavu-fonts on > sourceware. Thanks. I ran setup and installed "dejavu-fonts". Now "git gui" is able to run without errors.
chere Bash Prompt Here window closes immediately
When I right click a folder in Windows Explorer and select "Bash Prompt Here", a window opens briefly and then closes immediately. If I select "Applications -> Xterm" from the Cygwin/X Server tray icon, XTerm opens fine. Cygcheck and Xwin logs attached. Chere -lr output below. matseitz@MATSEITZ-WS02 ~ $ chere -lr OS is CYGWIN_NT-6.1 chere version 1.4 run.exe is available at C:\cygwin64\bin\run.exe --- ash keys --- --- bash keys --- Directory menu item (all users) Prompt Here Directory command (all users) C:\cygwin64\bin\run.exe -p /usr/X11R6/bin C:\cygwin64\bin\xterm.exe -display %DISPLAY% -e /bin/xhere /bin/bash.exe "%L" Directory background menu item (all users) Prompt Here Directory background command (all users) C:\cygwin64\bin\run.exe -p /usr/X11R6/bin C:\cygwin64\bin\xterm.exe -display %DISPLAY% -e /bin/xhere /bin/bash.exe "%V" Drive menu item (all users) Prompt Here Drive command (all users) C:\cygwin64\bin\run.exe -p /usr/X11R6/bin C:\cygwin64\bin\xterm.exe -display %DISPLAY% -e /bin/xhere /bin/bash.exe "%L" Drive background menu item (all users) Prompt Here Drive background command (all users) C:\cygwin64\bin\run.exe -p /usr/X11R6/bin C:\cygwin64\bin\xterm.exe -display %DISPLAY% -e /bin/xhere /bin/bash.exe "%V" Uninstall description Cygwin Bash Prompt Here (x86_64) Uninstall command C:\cygwin64\bin\sh -c "PATH=/bin /bin/chere -u -s bash" --- cmd keys --- --- dash keys --- --- fish keys --- --- mksh keys --- --- pdksh keys --- --- posh keys --- --- tcsh keys --- --- zsh keys --- --- passwd keys --- Currently installed Cygwin Here shells (all users): Currently installed Cygwin Here shells (current user): matseitz@MATSEITZ-WS02 ~ $ cygcheck.out Description: cygcheck.out XWin.0.log Description: XWin.0.log XWin.0.log.old Description: XWin.0.log.old XWin.1.log Description: XWin.1.log XWin.1.log.old Description: XWin.1.log.old -- 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 gjar core dumps whereas Oracle jar does not
Latest release of setup-x86.exe downloaded today. Sample jar and folder for testing: https://www.dropbox.com/s/8cdworjifch79de/sample_jar.zip?dl=0 Test on gcc-java-4.9.2-3: $gjar -uf test.jar -C test icons Illegal instruction (core dumped) Test on gcc-5.2.0-1: $gjar -uf test.jar -C test icons Illegal instruction (core dumped) Test on Oracle JDK jar: $jar -uf test.jar -C test icons (works fine) Matt D. -- 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
gcc-java-4.9.2-3 has the wrong libgcj dependency
Latest release of setup-x86.exe downloaded today. gcc-java-4.9.2-3 has the wrong libgcj dependency. It erroneously depends on libgcj16-5.2.0-1 instead of libgcj15-4.9.3-1 and will complain that it can't find cyggcj-15.dll if I try to run gjar. Matt D. -- 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
git gui: assertion "font != NULL" failed
A few days ago, I ran Setup to update my currently installed package, including my git packages. Since then, whenever I run git gui, I get the following error: $ git gui assertion "font != NULL" failed: file "/usr/src/ports/fontconfig/fontconfig-2.11.1-3.x86_64/src/fontconfig-2.11.1/src/fcmatch.c", line 453, function: FcFontRenderPrepare error: git-gui died of signal 6 cygcheck and xwin logs attached cygcheck.out Description: cygcheck.out XWin.0.log Description: XWin.0.log XWin.0.log.old Description: XWin.0.log.old XWin.1.log Description: XWin.1.log XWin.1.log.old Description: XWin.1.log.old -- 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: Problems running hg convert with subversion[-python] 1.8.13-2
On Wed, 2015-07-29 at 12:48 +0200, Dr Rainer Woitok wrote: File /usr/lib/python2.7/site-packages/libsvn/core.py, line 7285, in module svn_pool_create() TypeError: svn_pool_create() takes exactly 2 arguments (0 given) This is apparently known breakage with libsvn's SWIG bindings related to new versions of SWIG. We're more or less powerless to do anything about it. You can tell it's not Mercurial's problem because the error occurs -in libsvn/core.py- while it's calling SVN. https://encrypted.google.com/search?output=searchsclient=psy-abq=svn_pool_create==oq=gs_l=pbx=1#q=svn_pool_create+exactly+2+arguments -- Mathematics is the supreme nostalgia of our time. -- 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 ssh and Windows authentication
From: Andrey Repin http://cygwin.com/faq/faq.html#faq.using.sshd-in-domain Any suggestions if you can't get your domain admin to create a generic cyg_server account for you? I suspect some people in corporate environments may have trouble getting domain admins to create a generic cyg_server domain account, especially one in the domain's Administrators group. -- 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: xwin Exit menu item doesn't work
From: cygwin-ow...@cygwin.com [mailto:cygwin-ow...@cygwin.com] On Behalf Of Matt Seitz (matseitz) From: Jon TURNEY If this is easy for you to reproduce, could you show me the logfile produced on reproduction, after starting XWin with the '-logverbose 3' option? Thanks for getting back to me. I was unable to reproduce the issue this morning, with or without the -logverbose 3 setting. I'll leave the verbose setting in place for a while and see if I am able to reproduce. I have not been able to reproduce the issue. I'll leave verbose logging enabled for now and let you know if I see the issue again.
RE: xwin Exit menu item doesn't work
From: Jon TURNEY If this is easy for you to reproduce, could you show me the logfile produced on reproduction, after starting XWin with the '-logverbose 3' option? Thanks for getting back to me. I was unable to reproduce the issue this morning, with or without the -logverbose 3 setting. I'll leave the verbose setting in place for a while and see if I am able to reproduce. After I sent the report last night, I put my laptop in hibernate mode. When I powered the computer on this morning and resumed operation (about 8 hours after I put it in hibernate mode), the Exit dialog box appeared warning me that exiting Xwin would close my connections. I went ahead and clicked Exit and XWin exited successfully. It might be worthwhile to check that are stopping the X server you think you are, if you accidentally have multiple X servers running, some of which have been hidden in the notification area? Prior to sending my report, I had checked the running processes with Microsoft's Process Explorer tool, and saw only one instance of XWin.exe running.
xwin Exit menu item doesn't work
Steps to reproduce: -Right click XWin notification tray icon -Left click Exit... Expected results: XWin notification tray icon disappears and process ends Actual results: No change, XWin continues to run cygcheck.out Description: cygcheck.out XWin.8.log Description: XWin.8.log -- 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 gcc mingw python development environment configuration
I need to find references describing methods to configure: - Cygwin gcc environment - the Cygwin version of MingGW environment - gcc or mingw configurations for python compilations My questions are: - how to include all needed gcc source paths (of many) - how to include all needed library paths - do the ar as nm and other tools need to be specified in a configuration? - how to include gcc/mingw options when needed for python setup.py situations I have noticed an extensive framework of source paths beyond the default observed via gcc -v and wonder how these would be tied in when needed. Unless I misunderstand, it appears that only a single directory, no subdirectories, can be included per -I path for gcc. It seems that only this specified location is searched for source files, non-recursively. Which begs the question, what if you need to include sources where a great many subdirectories are involved? I hope there is a method that does not include hard coding every single subdirectory. Is there some tool or config file where I can configure build environments? For example, if compiling Cython, which uses python setup.py, which in turn calls gcc using a select build environment - how can I configure this to use mingw, if this is required, instead of Cygwin gcc? How to configure paths or select gcc parameters? How can select source and library paths be selected per build environment? The choices are either an intrinsic Cygwin gcc build environment, or a Cygwin mingw based one. This provides for Cygwin and Windows dependent platform targets. I want to work from mintty, as opposed to using a separate C:\MingGW MSYS build environment. (Especially because I use python and other tools directly from Cygwin/mintty) I would like to cross compile to target other platforms later, but I need to sort out the best configuration method for these two first. I have been searching a lot of online references, but it is still unclear how to accomplish this with a practical approach. Ultimately I want a combination of Cython, python, Jython, gcc, mingw, sage, and other math tools to compliment my Java work. Any links and advice would be much appreciated, thanks, Matt Thomas -- 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
rpm-build issue
I've noticed that the newer version of the rpm-build package (4.11-1) has a really severe bug in that it ignores the %defattr flag in the % files section of .spec files, so that when you try to build a file with a files section like %files %defattr(-,root,root) /tmp/foo You get the error No file attributes found The 4.1-2 version does not have this bug. this looks very similar to debian bug 630163 I could generate the cygcheck output and attach it, but to do that, I'd have to break the server, then fix it again, and I'd rather get the process started. It's not really a bug in cygwin itself, just one of the packages. Matt -- 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: rpm-build issue
Ahh, interesting, I'll have to break that again and see if it needs a valid username. Thanks for the idea! Matt On Thu, 2014-08-07 at 15:08 -0500, Yaakov Selkowitz wrote: On 2014-08-07 15:01, Matt Rose wrote: I've noticed that the newer version of the rpm-build package (4.11-1) has a really severe bug in that it ignores the %defattr flag in the % files section of .spec files Note that a default %defattr is provided since rpm-4.4, and therefore most uses of it are considered obsolete in Fedora: https://fedorahosted.org/fpc/ticket/77 https://fedoraproject.org/wiki/Packaging:Guidelines?rd=Packaging/Guidelines#File_Permissions That being said, I haven't tried this on Cygwin. But do you actually have a root user (e.g. by renaming Administrator in /etc/passwd)? Yaakov -- 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 -- 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
XWin cursor huge on one computer but normal on another
I primarily work on my workstation which has four 1080p monitors (three on the bottom with the fourth at center top) and for the longest time I thought that it this was a configuration error on my part; and perhaps it still it. The issue is that on my worksation, the cursor is huge and is sometimes even cropped for being too large. This is especially noticeable for applications like xterm and gedit. I think it might be a DPI or scaling issue due to my large screen size, however I've always explicitly defined -dpi 96 in my xinit. I had thought that this was a known bug and hadn't thought much about it until I pulled up gedit on my laptop where I saw that the cursors were all fine. I thought that maybe I had different packages but even after copying my entire cygwin directory and startup scripts over, on my laptop it still shows cursors no larger than the default Windows size. Has anyone experienced this before? Thanks, Matt D. -- 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/
Re: xinit hangs on XWin infinite loop when using -displayfd
Doh! I was so blind! Windows XP does not have an IPv6 protocol installed by default. I added it and the problem went away. This sounds like a bug. XWin should verify whether a device which supports the target protocol exists before attempting to open a socket on it. What is this used for? Sharing a local X session with someone else? Logging onto an existing X session at work from home? I've only ever used X locally or through ssh forwarding. Matt D. On 7/28/2014 8:34 AM, Jon TURNEY wrote: Thanks for reporting this problem. On 21/07/2014 18:30, Matt D. wrote: I found as a workaround to add the arguments -nolisten tcp when invoking xinit. However, I was under the impression that it was incompatible with -multiwindow and -clipboard, both of which seem to be working fine: https://cygwin.com/ml/cygwin-xfree/2009-05/msg00016.html That restriction no longer exists. https://cygwin.com/ml/cygwin-xfree/2009-10/msg7.html On 7/21/2014 12:00 PM, Matt D. wrote: Ok.. so I let xinit do its thing to see if it got anywhere. Eventually it will pop and error box. Interestingly, I specified a displayfd value of 3 and yet both the popup and the log are reporting 5: This is expected. xinit must know the display number of the X server it starts, so it can pass it on to any clients it starts, so it has a patch which should notice the -displayfd option, transparently use it to determine the display number for any clients they start, and then pass on the display number to the specified file descriptor My XWin.0.log is about 15MB of repeated attempts to open a socket. Here is a snippet. I hope this helps: InitConnectionLimits: MaxClients = 255 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-5.1 matthew-17ffb52 1.7.30(0.272/5/3) 2014-05-23 10:36 i686 OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32) Snapshot: 20140709-git-2e9c13ea41c51df7 XWin was started with the following command line: X -displayfd 5 ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1062 h 703 winInitializeScreenDefaults - native DPI x 96 y 96 ddxProcessArgument - arg: -displayfd Trying to create socket for display number 0 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/matthew-17ffb52:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 .. Trying to create socket for display number 59534 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/matthew-17ffb52:59534 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 (EE) Fatal server error: (EE) Failed to find a socket to listen on(EE) [ 58128.390] (EE) Server terminated with error (1). Closing log file. Ah. So, it seems that we have checked all ports from 6000 to 59534 + 6000 = 65534 and decided they are no good because we can't open an ipv6 socket. (It looks like there is another minor bug here in that we don't try port 65535! :-)) I guess if you just run XWin, it reports that it can't create an inet6 listener, but it continues anyway (unless the -nopn option is used). But, the implementation of -displayfd requires that creating all the listener socket succeeds. (It's not clear that this should be changed, otherwise we could reach the conclusion that it's ok to start a server on display n with a limited set of protocols, when a server already exists on display n with an non-intersecting set of protocols) So, you may find that -nolisten inet6, rather than -nolisten tcp (which prevents both ipv4 and ipv6 listening) also works around the problem. You might want to also investigate why inet6 sockets can't be opened. -- 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/
Caveats for removing /cygdrive prefix?
I've always used Cygwin's fstab /cygdrive default but I'm growing tired of always typing it out; msys's simple /a /c /d prefix for drive letters always seemed closer to home while on a Windows machine. The only problem I've encountered is a borked ls display when an actual folder a, b, etc., appears in the Cygwin root folder and the inability to enumerate drive with ls /cygdrive. Are there any other caveats to consider? Also, it would be nice if doing a directory list on /cygdrive was a hard-coded operation, to preserve this functionality. Matt D. -- 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: xinit hangs on XWin infinite loop when using -displayfd
Still hangs with the latest 1.15.1-4 release. On my main machine, I get the following output: $ xinit -- -displayfd 1 read display number ':0' from X server 0 On the VM it just hangs. Taskmanager shows xinit.exe waiting or hung with XWin.exe churning cycles and eating memory; about 4kB a tick. Also on the VM, if I run the following: $ xinit -- -displayfd Then the display will open. So it seems to be an issue with whatever code is dealing with the file descriptors. Matt D. On 7/20/2014 9:06 PM, Matt D. wrote: The operating system is Windows XP Professional. It is a CLEAN install on a VMware virtual machine and is 100% patched up. Cygwin also is a clean install. I did try a rebaseall with no effect. This is the first time I've encountered this. When I run xinit -- -displayfd 3, xinit will hang and XWin takes up 100% of the cpu. I've confirmed that file descriptors are working: $ exec 3a $ echo test 3 $ cat a test $ exec 3- I can confirm that ports are available and that both xinit and XWin work without this argument by running: $ xinit -- Everything else works fine but without -displayfd I can't record where the display is for this session to disk. I've also tried copying known-working Cygwin installs into the VM and still have the same error. Copying the erroring install from the VM outside and running it on my development machine (Windows 7 x64) does not generate an error. Unless something stands out here, I can provide the VMware image for testing (how convenient). Matt D. -- 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/
Re: xinit hangs on XWin infinite loop when using -displayfd
Ok.. so I let xinit do its thing to see if it got anywhere. Eventually it will pop and error box. Interestingly, I specified a displayfd value of 3 and yet both the popup and the log are reporting 5: http://oi58.tinypic.com/106fono.jpg My XWin.0.log is about 15MB of repeated attempts to open a socket. Here is a snippet. I hope this helps: InitConnectionLimits: MaxClients = 255 Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.15.1.0 OS: CYGWIN_NT-5.1 matthew-17ffb52 1.7.30(0.272/5/3) 2014-05-23 10:36 i686 OS: Windows XP Service Pack 3 [Windows NT 5.1 build 2600] (Win32) Snapshot: 20140709-git-2e9c13ea41c51df7 XWin was started with the following command line: X -displayfd 5 ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1062 h 703 winInitializeScreenDefaults - native DPI x 96 y 96 ddxProcessArgument - arg: -displayfd Trying to create socket for display number 0 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/matthew-17ffb52:0 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 .. Trying to create socket for display number 59534 _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 _XSERVTransOpen: transport open failed for inet6/matthew-17ffb52:59534 _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 (EE) Fatal server error: (EE) Failed to find a socket to listen on(EE) [ 58128.390] (EE) Server terminated with error (1). Closing log file. Matt D. On 7/21/2014 11:49 AM, Matt D. wrote: Still hangs with the latest 1.15.1-4 release. On my main machine, I get the following output: $ xinit -- -displayfd 1 read display number ':0' from X server 0 On the VM it just hangs. Taskmanager shows xinit.exe waiting or hung with XWin.exe churning cycles and eating memory; about 4kB a tick. Also on the VM, if I run the following: $ xinit -- -displayfd Then the display will open. So it seems to be an issue with whatever code is dealing with the file descriptors. Matt D. On 7/20/2014 9:06 PM, Matt D. wrote: The operating system is Windows XP Professional. It is a CLEAN install on a VMware virtual machine and is 100% patched up. Cygwin also is a clean install. I did try a rebaseall with no effect. This is the first time I've encountered this. When I run xinit -- -displayfd 3, xinit will hang and XWin takes up 100% of the cpu. I've confirmed that file descriptors are working: $ exec 3a $ echo test 3 $ cat a test $ exec 3- I can confirm that ports are available and that both xinit and XWin work without this argument by running: $ xinit -- Everything else works fine but without -displayfd I can't record where the display is for this session to disk. I've also tried copying known-working Cygwin installs into the VM and still have the same error. Copying the erroring install from the VM outside and running it on my development machine (Windows 7 x64) does not generate an error. Unless something stands out here, I can provide the VMware image for testing (how convenient). Matt D. -- 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/ -- 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/
Re: [ANNOUNCEMENT] Updated: Cygwin 1.7.31-1
Cannot replicate on Windows XP SP3 with latest Cygwin DLL by launching Cygwin's ftp from Windows command prompt or from a bash prompt. Everything connects fine. Matt D. On 7/21/2014 10:52 AM, D. Boland wrote: Hi Warren, Warren Young wrote: On 7/21/2014 06:19, D. Boland wrote: With the snapshot in place, the ftp client hangs indefinitely after entering the password. Switching back to my old Cygwin DLL, it works again. Which FTP client is that? The ftp.exe that comes with Windows, the ftp.exe from Cygwin's inetutils (?) package, or some other FTP client? I used the ftp program from the inetutils package. D. -- 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 -- 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
xinit hangs on XWin infinite loop when using -displayfd
The operating system is Windows XP Professional. It is a CLEAN install on a VMware virtual machine and is 100% patched up. Cygwin also is a clean install. I did try a rebaseall with no effect. This is the first time I've encountered this. When I run xinit -- -displayfd 3, xinit will hang and XWin takes up 100% of the cpu. I've confirmed that file descriptors are working: $ exec 3a $ echo test 3 $ cat a test $ exec 3- I can confirm that ports are available and that both xinit and XWin work without this argument by running: $ xinit -- Everything else works fine but without -displayfd I can't record where the display is for this session to disk. I've also tried copying known-working Cygwin installs into the VM and still have the same error. Copying the erroring install from the VM outside and running it on my development machine (Windows 7 x64) does not generate an error. Unless something stands out here, I can provide the VMware image for testing (how convenient). Matt D. -- 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/
Re: using make without cygwin terminal
Rob, You need to setup your environment paths to include both the compiler's include and libs directories as well as the targeted platform sdk, if you're using one. I use a custom tool chain with Cygwin/GNU Make in my build system with support for every version of Visual Studio, including 6. Here is an example of the required paths: Includes: vs6/vc98/include vs6/vc98/mfc/include vs6/vc98/atl/include Libs: vs6/vc98/lib vs6/vc98/mfc/lib Visual Studio 6 is compatible with the Windows platform SDK up to Windows Server 2003 R2 Platform SDK, but you shouldn't need it. Your shell environment will need to be setup for both the compiler (cl.exe) and the linker (link.exe). See here: http://msdn.microsoft.com/en-us/library/aa236630(v=vs.60).aspx http://msdn.microsoft.com/en-us/library/aa270757(v=vs.60).aspx Matt D. On 7/10/2014 6:14 PM, Robert Pendell wrote: On Thu, Jul 10, 2014 at 12:46 PM, Okan Erat wrote: Dear Cygwin users, I am trying to compile a project using VS6 compiler and makefiles generated by imake. When i run make from cygwin terminal it compiles everything without any problem. However if i run make from windows terminal (c:/cygwin/bin is already in Path) VS6 complains about various problems. such as: winbase.h(1011) : error C2733: second C linkage of overloaded function 'InterlockedIncrement' not allowed mswsock.h(69) : error C2065: 'SOCKET' : undeclared identifier winsock2.h(85) : error C2378: 'SOCKET' : redefinition; symbol cannot be overloaded with a typedef Why make works with cygwin terminal but not with windows terminal. Thanks for your answers Those errors are not coming from cygwin make. That's coming from VS6 make. Cygwin make doesn't have errors formatted that way. With that in mind Visual Studio is a Microsoft product and not really supported here. Robert Pendell A perfect world is one of chaos. -- 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 -- 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: Wine creating windows offscreen when multiwindow is used?
Jon, Yes! That fixed it. Windows from Wine open up just as regular X windows on the primary monitor. To achieve this is appears as though you're ignoring the Window's requested x/y position entirely and favoring the placement heuristics, as these coordinates are being ignored. I do have a use-case where I want windows from Wine to be created at a designated position for testing, so I don't have to test on a Windows machine for placement as well. Is it at all possible to have these windows map their coordinates strictly, as in 0,0 on the primary monitor would be 1920x1080 in my case. For example, I may want a child window which is a custom dialog aligned to the center of its parent, or a newly created window to be center-aligned to the screen. You've done a great job with this, Jon. I'm not complaining, as this will allow me to begin writing code immediately (I can finally see the window!). Thanks so much for your help. :) Matt D. On 7/9/2014 12:10 PM, Jon TURNEY wrote: On 06/07/2014 17:27, Jon TURNEY wrote: There is some code in XWin which attempts to ensure that the window is placed somewhere visible, but that assumes that the Window virtual desktop is a rectangle of size GetSystemMetrics(SM_CXVIRTUALSCREEN) x GetSystemMetrics(SM_CYVIRTUALSCREEN). I think it should be pretty straightforward to change this, perhaps to use MonitorFromPoint() to determine if the window will be visible on a non-rectangular virtual desktop. I've built a snapshot with this change. Perhaps you could try that and see if it improves things for you? ftp://cygwin.com/pub/cygwinx/x86/XWin.20140709-git-2e9c13ea41c51df7.exe.bz2 ftp://cygwin.com/pub/cygwinx/x86_64/XWin.20140709-git-2e9c13ea41c51df7.exe.bz2 -- 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/
Re: Automatic X server startup
I know this thread is a bit old now but I just wanted to mention my solution. I've added X to start in a separate screen in my .bash_profile. That way every time I log into Cygwin, X is always available. It's kind of like the previous suggestion of adding it to Windows startup, but I have it more closely coupled to Cygwin. Matt D. On 6/2/2014 9:57 AM, Jon TURNEY wrote: On 28/05/2014 13:57, Pavel Fedin wrote: I believe this is arranged using launchd on OS X, which listens on the socket the X server will use, and starts the X server when something connects. Unfortunately, there is no similar system facility on Windows. But it should be possible to make xlib a little bit more smart, isn't it ? It could automatically run X server when a connection is attempted but refused. So we would achieve the same effect as on MacOS. We could e. g. have some directory like /etc/X11/autostart, to be examined by xlib. If it detects that e. g. :0 screen is not accessible, it would attempt to look up 0.xlaunch file there and run xlaunch -run /etc/X11/autostart/0.xlaunch command. What do you think ? I could implement this idea if you have no time to work on that, i believe it should be very easy. Patches are always welcome, so please feel free to work on this if you like. I have my doubts that that it's straightforward to add this in libX11 in a way that is generally useful (for e.g.: there would be a race condition if two processes both try to start the server at the same time, there's much room for confusion about how to specify the X server options to be used, if it could be started explicitly for the start menu, or implicitly by libX11,...) You can achieve a somewhat similar effect by copying the X server shortcut to the startup group to start it automatically at login, at the cost of slowing down system startup somewhat. Heh, it's already slow because of antivirus and other corporate stuff (i cannot disable it). Running on demand would be better. You might consider looking at starting it from launchd or perhaps xinitd if possible, and then just that can be started by the X server shortcut, or at startup. -- 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/
RE: Problem with xterm-301-1
From: Thomas Dickey [mailto:dic...@his.com] On Thu, Feb 20, 2014 at 06:45:00PM +, Matt Seitz (matseitz) wrote: From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. (whether xterm should use $SHELL incoming is a different issue that I am reconsidering) Is there any ETA for a resolution of this issue? I've been holding off on upgrading to xterm-301 because of this issue. I'm not sure if there is some patch coming soon (either to xterm or adding a default /etc/shells to Cygwin), or if I should just plan on manually creating my own /etc/shells. -- 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/
RE: Problem with xterm-301-1
From: Ola Strömfors [mailto:ola.stromf...@gmail.com] After updating from 291-1 to 301-1 xterm starts /bin/sh instead of my shell specified in /etc/passwd or in the SHELL environment variable. The workaround I have found is to create /etc/shells with a list of permitted shells, e.g. From http://invisible-island.net/xterm/xterm.log-contents.html#xterm_301: Patch #301 - 2014/01/19 only set SHELL environment variable to programs found in /etc/shells (prompted by patch/report by Al Poole). -- 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/
Copy/paste broken from X to Windows
Copy/paste seems to be broken when attempting to copy a large block of text from X to Windows. See the attachment for an example. Copying the text from Windows to X seems fine but the reverse causes the mouse cursor to spin and then a blank string to paste. Matt D. ACT III SCENE I. A public place. Enter MERCUTIO, BENVOLIO, Page, and Servants BENVOLIO I pray thee, good Mercutio, let's retire: The day is hot, the Capulets abroad, And, if we meet, we shall not scape a brawl; For now, these hot days, is the mad blood stirring. MERCUTIO Thou art like one of those fellows that when he enters the confines of a tavern claps me his sword upon the table and says 'God send me no need of thee!' and by the operation of the second cup draws it on the drawer, when indeed there is no need. BENVOLIO Am I like such a fellow? MERCUTIO Come, come, thou art as hot a Jack in thy mood as any in Italy, and as soon moved to be moody, and as soon moody to be moved. BENVOLIO And what to? MERCUTIO Nay, an there were two such, we should have none shortly, for one would kill the other. Thou! why, thou wilt quarrel with a man that hath a hair more, or a hair less, in his beard, than thou hast: thou wilt quarrel with a man for cracking nuts, having no other reason but because thou hast hazel eyes: what eye but such an eye would spy out such a quarrel? Thy head is as fun of quarrels as an egg is full of meat, and yet thy head hath been beaten as addle as an egg for quarrelling: thou hast quarrelled with a man for coughing in the street, because he hath wakened thy dog that hath lain asleep in the sun: didst thou not fall out with a tailor for wearing his new doublet before Easter? with another, for tying his new shoes with old riband? and yet thou wilt tutor me from quarrelling! BENVOLIO An I were so apt to quarrel as thou art, any man should buy the fee-simple of my life for an hour and a quarter. MERCUTIO The fee-simple! O simple! BENVOLIO By my head, here come the Capulets. MERCUTIO By my heel, I care not. Enter TYBALT and others TYBALT Follow me close, for I will speak to them. Gentlemen, good den: a word with one of you. MERCUTIO And but one word with one of us? couple it with something; make it a word and a blow. TYBALT You shall find me apt enough to that, sir, an you will give me occasion. MERCUTIO Could you not take some occasion without giving? TYBALT Mercutio, thou consort'st with Romeo,-- MERCUTIO Consort! what, dost thou make us minstrels? an thou make minstrels of us, look to hear nothing but discords: here's my fiddlestick; here's that shall make you dance. 'Zounds, consort! BENVOLIO We talk here in the public haunt of men: Either withdraw unto some private place, And reason coldly of your grievances, Or else depart; here all eyes gaze on us. MERCUTIO Men's eyes were made to look, and let them gaze; I will not budge for no man's pleasure, I. Enter ROMEO TYBALT Well, peace be with you, sir: here comes my man. MERCUTIO But I'll be hanged, sir, if he wear your livery: Marry, go before to field, he'll be your follower; Your worship in that sense may call him 'man.' TYBALT Romeo, the hate I bear thee can afford No better term than this,--thou art a villain. ROMEO Tybalt, the reason that I have to love thee Doth much excuse the appertaining rage To such a greeting: villain am I none; Therefore farewell; I see thou know'st me not. TYBALT Boy, this shall not excuse the injuries That thou hast done me; therefore turn and draw. ROMEO I do protest, I never injured thee, But love thee better than thou canst devise, Till thou shalt know the reason of my love: And so, good Capulet,--which name I tender As dearly as my own,--be satisfied. MERCUTIO O calm, dishonourable, vile submission! Alla stoccata carries it away. Draws Tybalt, you rat-catcher, will you walk? TYBALT What wouldst thou have with me? MERCUTIO Good king of cats, nothing but one of your nine lives; that I mean to make bold withal, and as you shall use me hereafter, drybeat the rest of the eight. Will you pluck your sword out of his pitcher by the ears? make haste, lest mine be about your ears ere it be out. TYBALT I am for you. Drawing ROMEO Gentle Mercutio, put thy rapier up. MERCUTIO Come, sir, your passado. They fight ROMEO Draw, Benvolio; beat down their weapons. Gentlemen, for shame, forbear this outrage! Tybalt, Mercutio, the prince expressly hath Forbidden bandying in Verona streets: Hold, Tybalt! good Mercutio! TYBALT under ROMEO's arm stabs MERCUTIO, and flies with his followers MERCUTIO I am hurt. A plague o' both your houses! I am sped. Is he gone, and hath nothing? BENVOLIO What, art thou hurt? MERCUTIO Ay, ay, a scratch, a scratch; marry, 'tis enough. Where is my page? Go, villain, fetch a surgeon. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ
Re: Copy/paste broken from X to Windows
Larry, This is the cygwin-xfree list? Matt D. On 10/21/2013 1:05 PM, Larry Hall (Cygwin-X) wrote: On 10/21/2013 12:45 AM, Matt D. wrote: Copy/paste seems to be broken when attempting to copy a large block of text from X to Windows. See the attachment for an example. Copying the text from Windows to X seems fine but the reverse causes the mouse cursor to spin and then a blank string to paste. Please send this report to the cygwin-xfree list. -- 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/
Re: Question on x3270 under 64bit cygwin/X
Thigpen, I see two options available to you for an immediate solution. Either recompile the package yourself from source targeted at x64 or simply continue using the cygwin-32 and its packages. Do you have some pressing requirement to use the cygwin-64? Also, I believe this question would be more appropriate for the main cygwin mailing list, as your question isn't directly related to cygwin/x. Matt D. On 10/8/2013 4:36 PM, Tony Thigpen wrote: I currently use x3270 as packaged with the 32 bit cygwin on several Win-XP computers. We are now migrating those computers to Win-7 boxes. The 64 bit cygwin does not contain the x3270 package. (Also, the 32 bit package is way out of date.) I emailed the original person who packaged this software for cygwin, but received no response. Is there someone willing to repackage the x3270 software for 64 bit cygwin? Is there someone willing to guide me (off-list) to get the latest version of x3270 running under cygwin 64? -- 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/
Re: Clipboard periodically breaks
Jon, Thanks for looking into this. I can confirm that your changes correct the issue where highlighting next would cause arbitrary pastes to occur. Good work! I also concede that there does not seem to be a good solution to transparently fix the two-to-one clipboard issue; as XWin may indeed be able to interpret calls to X's two clipboards, there wouldn't be any reasonable way for it to identify which clipboard is actually being used. However, an environment variable that tells it which clipboard to use would provide an immediate solution and be used used on a per-application basis. For example, I can use aliases when launching programs: $ xclip=clipboard1 gedit $@ (monitor only clipboard 1) $ xclip=clipboard2 gedit $@ (monitor only clipboard 2) No option would indicate that both clipboard 1 and clipboard 2 would be handled as they are now. I'm not familiar with X programming but I'm assuming here that it would be possible for xclip to read from a particular process's own environment (rather than xclip's own) while processing a clipboard event to do this. What do you think? Matt D. On 9/26/2013 11:37 AM, Jon TURNEY wrote: In-Reply-To: 51c44820.4010...@dronecode.org.uk Please start a new thread for a new subject. On 22/09/2013 03:38, Matt D. wrote: I often keep gedit sessions open on remote servers for maintaining various scripts. The problem I've encountered is that after a while I can no longer copy/paste between X and Windows. For example, I'll copy in windows and attempt to paste in gedit but nothing will happen. However, if I then proceed to copy something in gedit it will immediate paste that in place of where I had previously tried to paste from Windows. Sometimes I can get it working again by bombarding the clipboard with copy/pastes from both X and Windows. But most of the time I have to exit the ssh session and reconnect. Is this a known problem? We know there are bugs, but we don't know what they all are :-) Here is an example screen capture and repeatable bug of the clipboard breaking. Synopsis: Copy from Windows, highlight text in gedit, clipboard breaks (paste doesn't work). Proceed to copy from gedit and suddenly that text gets pasted. Sometimes it will just start pasting while a selection is being made.. ?? Download the video here in Xvid format: http://codespunk.com/files/upload/cygwinx_clipboard_breaking_xvid.avi Thanks for this. There's definitely a bug here when stuff fails to paste. You are also having difficulties because of a limitation of the current clipboard implementation I'll try to explain: As [1] tries to explain, there are 2 X selections of interest, the PRIMARY selection (the highlighted text) and the CLIPBOARD selection (the cut/copied text) (and some X applications only use one or the other), but only 1 windows clipboard. When you update the PRIMARY selection, by highlighting that text, it is made available for pasting from the Windows clipboard, which means that the previous Windows clipboard contents are removed. When you then go to paste, since the Windows clipboard contents have changed to the selected text, that's what you get in the CLIPBOARD selection. This is far from idea, but the proposed solutions I've seen so far aren't any better: i) Don't monitor the PRIMARY selection. This breaks with any application which only uses the PRIMARY selection (e.g. xterm, emacs in default configurations) ii) Use some more complex heuristic than 'most recently changed owner' for choosing which selection to make available in the Windows clipboard. It's very hard to know if this will make things better on average. I've fixed something else that might be related to the paste failure, so please try the latest snapshot [2],[3]. If you can still reproduce your problem with that, can you please try: * run XWin with the -noclipboard flag added to your usual flags. * Then run xwinclip, which should produce some useful logs when you reproduce your problem. [1] http://x.cygwin.com/docs/ug/using-clipboard-integration.html [2] ftp://cygwin.com/pub/cygwinx/XWin.20130924-git-d5a9aea0e48a088b.exe.bz2 [3] ftp://cygwin.com/pub/cygwinx/xwinclip.20130924-git-d5a9aea0e48a088b.exe.bz2 -- 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/
Re: Run bash script in cmd with cygwin
Try adding this to your script:
cd /cygdrive/d/path/to/dir;`for file..
Matt D.
On 9/24/2013 5:43 PM, Ulrich Pogson wrote:
Hello
I would like to run this script `for file in `find . -name *.po` ;
do msgfmt -o ${file/.po/.mo} $file ; done` in windows cmd. The script
need to run in a different folder. I have been able to run it though
cygwin but want to integrate it with another system where it will be
run through cmd.
C:\cygwin\bin
D:\path\to\dir
How can I do this?
Thanks.
--
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
--
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 and lz/lza running out of memory?
The link sounded promising but no matter how high I set it (tried up to 8192), I get the same error, even when bringing down the compression ratio a bit. I attempted to increase the cygwin heap on both /usr/lib/p7zip/7z.exe and 7za.exe. Matt D. On 9/22/2013 10:25 PM, Larry Hall (Cygwin) wrote: On 9/22/2013 5:30 PM, Matt D. wrote: Depending on the options I choose, I keep running into lz/lzma reporting: ERROR: Can't allocate required memory!. This can occur before or during compression. The lz/lza process tends to stop after gaining about 400MB on the process; then it exits with this error. The problem does not appear to be how much available memory I have but rather q question of why the process can't seem to allocate it. Any advice? Take a look at this thread and see if this leads you to an answer. http://cygwin.com/ml/cygwin/2012-11/msg00104.html If not, please follow the problem-reporting guidelines found here: Problem reports: http://cygwin.com/problems.html -- 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 and lz/lza running out of memory?
Depending on the options I choose, I keep running into lz/lzma reporting: ERROR: Can't allocate required memory!. This can occur before or during compression. The lz/lza process tends to stop after gaining about 400MB on the process; then it exits with this error. The problem does not appear to be how much available memory I have but rather q question of why the process can't seem to allocate it. Any advice? Matt D. -- 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
Clipboard periodically breaks
I often keep gedit sessions open on remote servers for maintaining various scripts. The problem I've encountered is that after a while I can no longer copy/paste between X and Windows. For example, I'll copy in windows and attempt to paste in gedit but nothing will happen. However, if I then proceed to copy something in gedit it will immediate paste that in place of where I had previously tried to paste from Windows. Sometimes I can get it working again by bombarding the clipboard with copy/pastes from both X and Windows. But most of the time I have to exit the ssh session and reconnect. Is this a known problem? I am using the Cygwin x32 with the latest packages. Matt D. -- 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/
Re: Clipboard periodically breaks
Here is an example screen capture and repeatable bug of the clipboard breaking. Synopsis: Copy from Windows, highlight text in gedit, clipboard breaks (paste doesn't work). Proceed to copy from gedit and suddenly that text gets pasted. Sometimes it will just start pasting while a selection is being made.. ?? Download the video here in Xvid format: http://codespunk.com/files/upload/cygwinx_clipboard_breaking_xvid.avi Matt D. On 9/21/2013 10:38 PM, Matt D. wrote: I often keep gedit sessions open on remote servers for maintaining various scripts. The problem I've encountered is that after a while I can no longer copy/paste between X and Windows. For example, I'll copy in windows and attempt to paste in gedit but nothing will happen. However, if I then proceed to copy something in gedit it will immediate paste that in place of where I had previously tried to paste from Windows. Sometimes I can get it working again by bombarding the clipboard with copy/pastes from both X and Windows. But most of the time I have to exit the ssh session and reconnect. Is this a known problem? I am using the Cygwin x32 with the latest packages. Matt D. -- 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/
