Re: [ANNOUNCEMENT] pcre2 10.21-1

[Andrew Schulman]

> The following packages have been uploaded to the Cygwin distribution:
> 
> * pcre2-10.21-1
> * libpcre2_8_0-10.21-1
> * libpcre2_16_0-10.21-1
> * libpcre2_32_0-10.21-1
> * libpcre2-posix0-10.21-1
> * libpcre2-devel-10.21-1
> * libpcre2-doc-10.21-1
> * mingw64-i686-pcre2-10.21-1
> * mingw64-x86_64-pcre2-10.21-1

Cool, thanks.
Andrew


--
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: system lags and dysfunctional after cygwin update

[Ben Altman]

On 5/12/2016 11:57 AM, Warren Young wrote:

On May 12, 2016, at 8:35 AM, Ben Altman  wrote:

I have been using the same version of ksh for a while

Be specific.  *Which* version?

I can see from your cygcheck.out that you aren’t talking about mksh, the only ksh 
that ships with Cygwin.  Therefore, I assume you mean AT&T ksh93.  Which 
version did you come from, and which did you upgrade to?
Doing a ksh --version gives me:  version sh (AT&T Research) 93u+ 
2012-08-01


I haven't upgraded yet because I have not been successful in compiling 
it. My attempt to do so is what began this unusual behavior (when I used 
the setup to get bison). I was compiling under 32-bit Cygwin and if 
successful would try it on the 64-bit version. The current version I am 
using will not work with 64-bit Cygwin.



Incidentally, please consider packaging ksh93u+ (stable) or ksh93v- (beta) for Cygwin.  
It would be nice to have AT&T ksh for Cygwin, if only for reference and comparison 
purposes.  While doing compatibility testing with mksh, it’s hard to know if any given 
odd behavior is due to an mksh weirdness or if it’s accurately emulating AT&T ksh.

Relevant:

   http://unix.stackexchange.com/questions/246338/is-the-shell-ksh93-dead
Right now I only have a binary of ksh which I have on all my systems.I 
am not sure what is involved in packaging ksh with Cygwin but would 
definitely be interested in finding out. Though, I was under the 
impression that if the licensing wasn't GNU it would be a problem even 
though it is open source.





did an update of cygwin

 From what version?  Or if you cannot be sure, about how long ago was your last 
update?
I am not sure but at the time it probably was at least 6 months but 
could have been much longer. In the end though I renamed my cygwin 
directory to _cygwin and renamed the branch in the registry as well to 
do a complete reinstall (I did not reinstall babun however) but this did 
not fix the problem. I have a new laptop that I just installed cygwin on 
but have not yet set it up so I can run my report script that would test 
it out on a new installation. Another script that gives me problems 
though worked fine.



I can see from your cygcheck.out that you are now on 1.7.35.  Did you read the 
release notes that strongly recommended that you to move /etc/passwd and 
/etc/group out of the way?  This is especially important in an AD-based 
organization like yours.

What is preventing you from becoming current?  (2.5.1)  I see in your message 
stuff about stuck postinstall scripts, but ipso facto, those are run *after* 
everything is installed, so that doesn’t explain it.
It might be because I ran the cygcheck from babun instead of cygwin. I 
have attached that cygcheck file, though the issue comes up with both.





One result is that everything takes many times longer to complete. E.g. "ls" 
goes from under a second to give a listing to 20 or more seconds.

The usual way to find out what’s happening is to run the problem program under 
strace, then see where the strace output hangs.

Realize that this is not a general problem, so we’re going to be relying on you 
to do much of the debugging.

That said, I don’t think strace will help here, because I don’t think you 
actually have a Cygwin-specific problem.


Another thing that happens is that Internet Explorer stops working - it loads 
unresponsive and then crashes.

Cygwin cannot affect IE, nor vice versa.  The only thing that can affect both 
is the OS kernel or something that ties into it: hardware drivers, antimalware 
software, certain types of malware...


Rebooting fixes the issue until I do something in one of my scripts that 
triggers it again.

Are you certain about that?  I mean, if you can cause the problem within a day 
by running these scripts, have you tried running a whole day without running 
any of those scripts, but doing everything else you’d normally do in that day 
the same way?

I’ll bet that if you try that, you’ll find that the problem reoccurs anyway.
I am pretty sure that it depends on Cygwin. Meaning I have avoided 
cygwin for a day without the issue occurring and can make it happen at 
any time I want to by running my report script (which is why I only run 
it at night now). It takes a couple of minutes for it to download the 
data and then as soon as it prints "generating reports" it hangs and 
everything else does too. I.e. typing a simple command like "ls" will 
take upwards of 20 seconds and all the other side effects. I'll see 
about doing the strace with the script though I will probably have to do 
it next week though.



I see that you’re running Windows 7 Enterprise.  Doesn’t that get you a copy of 
HyperV and a license to run another copy of Windows within it?  Why not install 
a fresh copy of Windows and Cygwin in a HyperV VM, then see if it runs into the 
same problems?  I’ll bet it doesn’t, which will be interesting in its own 
right, plus it will let you get on with your work wh

Re: system lags and dysfunctional after cygwin update

[Marco Atzeri]

On 13/05/2016 16:02, Ben Altman wrote:

On 5/12/2016 11:57 AM, Warren Young wrote:

On May 12, 2016, at 8:35 AM, Ben Altman  wrote:





During the update that triggered this, it got stuck in the final part
dealing with the 0p_000_autorebase.dash script.

I’m not sure chasing this will have any effect.  If I am right that
there is a 3rd party agent outside of Cygwin causing the problem, any
autorebase problems could well be a side effect of that agent’s
behavior.  This sort of problem is generally classed as “BLODA” within
Cygwin:

   https://cygwin.com/faq/faq.html#faq.using.bloda

Do you have any of those listed software packages installed?  Which
ones?  Have you tried temporarily disabling or uninstalling them?

My organization has Symantec Endpoint Protection installed. It isn't
explicitly mentioned but it is Symantec so I'll try disabling it whilst
the script runs and see what happens.


Same organization setup here on W7-64

On my system, it was enough to add the cygwin directory in the exception 
list of "Symantec Endpoint Protection"




Thanks again for your help.
Ben


Marco


--
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: Interface friendly names for AF_INET6

[Marco Atzeri]

On 10/03/2016 18:41, Corinna Vinschen wrote:


I assume the ifall structures are not visible outside cygwin internal,
correct ?

If so a ifall_data pointer should cover my current trial.


Try the latest snapshot.  The ifa_data member now contains a pointer
to a struct ifa_hwdata which is defined in .


Thanks,
Corinna



Hi Corinna,

thanks for it

$ ./get-interface-64.exe
internal_name:  {EC2ABB5C-42A8-431D-A133-8F4BE0F309AF}
 flags: AF_INET6 up multicast
 address:   fe80::a479:1393:b7d0:fb25%18
 friendly_name: Local Area Connection 2

internal_name:  {EC2ABB5C-42A8-431D-A133-8F4BE0F309AF}
 flags: AF_INET  up broadcast multicast
 address:   169.254.251.37
 friendly_name: Local Area Connection 2

internal_name:  {9213DBB8-80C6-4316-AA7A-EBF8AD7661E1}
 flags: AF_INET6 up multicast
 address:   fe80::8c29:45f0:47fa:536%24
 friendly_name: Wireless Network Connection 3

internal_name:  {9213DBB8-80C6-4316-AA7A-EBF8AD7661E1}
 flags: AF_INET  up broadcast multicast
 address:   169.254.5.54
 friendly_name: Wireless Network Connection 3
...

Regards
Marco

--
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: system lags and dysfunctional after cygwin update

[Warren Young]

On May 13, 2016, at 8:02 AM, Ben Altman  wrote:
> 
> Doing a ksh --version gives me:  version sh (AT&T Research) 93u+ 
> 2012-08-01
> 
> I haven't upgraded yet

ksh93u+ is the latest stable version.  Everything after that are beta versions 
which have been in beta for many years, which may be a hint that they’re not 
quite ready for prime time.

> I was compiling under 32-bit Cygwin and if successful would try it on the 
> 64-bit version.

Cygwin 32 and Cygwin 64 are somewhat incompatible.  They share a filesystem and 
can run each others’ programs, but a whole bunch of other stuff will not work 
correctly between them.  If you must have both installed, treat them as wholly 
independent worlds, except possibly in terms of sharing files.

And not necessarily even then, since files produced from 32-bit Cygwin may not 
be compatible with a consumer linked against 64-bit Cygwin, nor vice versa.  
The most obvious case is compiler object files, but there are other cases.

It’s best if you install only one or the other, not both.

That option isn’t always available.  Those of us maintaining packages typically 
need both installed, for example.

> The current version I am using will not work with 64-bit Cygwin.

We can’t help you if you won’t provide details.

I infer from your prior posts that you are a programmer.  How do you like “does 
not work” when you get it in a bug report?

Give us the sort of bug report you wish you’d receive from your users.

> I am not sure what is involved in packaging ksh with Cygwin

https://cygwin.com/setup.html

> I was under the impression that if the licensing wasn't GNU it would be a 
> problem even though it is open source.

Not exactly.  The license merely has to be *compatible* with the GPL as far as 
binary distribution goes, since the binaries distributed in the Cygwin package 
repo are linked to cygwin1.dll, which is GPL’d.

But after taking a peek at the AST license, it’s pretty clear it’s incompatible 
with the GPL.

So, new advice: switch to mksh. :)

> I renamed my cygwin directory...a complete reinstall...this did not fix the 
> problem.

So that would exonerate Cygwin, then, unless your contention is that a fresh 
installation somehow causes problems on only your machine, and not on all the 
others Cygwin is installed on every day.

No.  The problem must be in the environment external to Cygwin.

> typing a simple command like "ls" will take upwards of 20 seconds and all the 
> other side effects. I'll see about doing the strace with the script though I 
> will probably have to do it next week though.

You can do the strace test with ls.  Simpler tests are better.

> My script runs VPNClient

Ah hah!

Many VPNs are…stringent in that they try to force *everything* through the VPN. 
 So, if Cygwin is trying to do AD lookups to map NTFS ACLs to human readable 
names in ls, and there is no AD server on the other end of the VPN that can 
answer those questions, you could very easily get that sort of symptom.

Solution: test with and without the VPN.

For instance, reboot cleanly, bring up the VPN, then say “ls -l”.  If that 
gives the same symptom, you know it’s something like I described above.

It is possible the new AD-aware permission handling in Cygwin 1.7.34 is causing 
a problem for you.  If you can’t fix the VPN or the AD setup, you could adjust 
the /etc/nsswitch.conf file as described here to revert to the old /etc/passwd 
based permission handling:

  https://cygwin.com/cygwin-ug-net/ntsec.html

In effect, /etc/passwd and /etc/group act as static AD caches that can work 
while the AD server is unavailable.
--
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: system lags and dysfunctional after cygwin update

[Yaakov Selkowitz]

On 2016-05-13 10:38, Warren Young wrote:

On May 13, 2016, at 8:02 AM, Ben Altman wrote:

I am not sure what is involved in packaging ksh with Cygwin
I was under the impression that if the licensing wasn't GNU it would be a
problem even though it is open source.


Not exactly.  The license merely has to be *compatible* with the GPL as far
as binary distribution goes, since the binaries distributed in the Cygwin
package repo are linked to cygwin1.dll, which is GPL’d.


Please review: https://cygwin.com/licensing.html

Cygwin's license contains a linking exception for software licensed 
under terms which satisfy the Open Source Definition 
.  For our purposes, a good reference is 
.



But after taking a peek at the AST license, it’s pretty clear it’s incompatible
with the GPL.


True, but it is Open Source and therefore would be acceptable.

--
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

Re: system lags and dysfunctional after cygwin update

[Warren Young]

On May 13, 2016, at 10:41 AM, Yaakov Selkowitz wrote:
> 
> On 2016-05-13 10:38, Warren Young wrote:
> 
>> But after taking a peek at the AST license, it’s pretty clear it’s 
>> incompatible
>> with the GPL.
> 
> True, but it is Open Source and therefore would be acceptable.

It depends on what “it” is.

The old AT&T AST license was most definitely not acceptable, requiring written 
acceptance of the license in order to transfer the source code.  You may 
remember the clickthrough license on the old AT&T AST site.  That’s fine for 
AT&T, but it doesn’t let Cygwin distribute source packages, for example.

There are other onerous terms in the AST license, too, such as a requirement 
that you tell AT&T in writing any time you made a patch to their software.  
Thus if it doesn’t build OOTB on Cygwin, we couldn’t distribute it in 
binary-only form, either.

All of that apparently went away at some point, though, because the header 
comment in a few of the ksh source files I looked at say it’s under the Eclipse 
Public License now:

  https://github.com/att/ast

The old AST wasn’t even compatible with GitHub — no explicit license acceptance 
on git clone — but I think we can trust that as an official distribution of the 
ksh source code, since AT&T themselves link to the GitHub repo from here:

  http://www.research.att.com/software_tools

So never mind, I think we’re in the clear here.  But IANAL.
--
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] clamav 0.99.1-1

[Mike Bonnet]

On 5/11/16 9:14 AM, Warren Young wrote:

On May 11, 2016, at 10:10 AM, Mike Bonnet wrote:


On 5/11/16 8:18 AM, Yaakov Selkowitz wrote:

On 2016-05-11 09:35, Mike Bonnet wrote:


Any chance we could get a new 64-bit build?


We'd need to find the real cause of this before it would be of any help.
I'd start with updating to 0.99.2, however we borrow Fedora's -norar
sources but they haven't bumped yet (#1333949).


I'll retry with 0.99.2 when it's available.


Or you could rebuild 0.99.1 from the sources and see if that fixes the symptom. 
 If it does, you have a reason to reject Yaakov’s answer.  If not, Yaakov was 
right to disbelieve your hypothesis.


The build issue was a red herring, sorry about that. It turns out a 
specific file, xdate.exe, is causing clamscan to segfault. This is an 
old file, from 2012, used for date formatting, but it has just started 
causing problems. I've reproduced the segfault in 0.99.1-1 and 0.98.7-2 
running on Cygwin64 on Windows Server 2012, but didn't go any further 
back than that. I've verified that there are no viruses in the file 
(according to virustotal.com):


https://virustotal.com/en/file/937800ed6b0408b9dba4e4dc507cd0b1962d3adb6285947db520009d19cbe24e/analysis/1463097443/

The file is here (it's listed as "free for any use"):

http://people.redhat.com/mikeb/clamscan-segfault/xdate.exe

The output from running "clamscan --debug xdate.exe" is here:

http://people.redhat.com/mikeb/clamscan-segfault/clamscan-debug-xdate.log

and the stackdump is here:

http://people.redhat.com/mikeb/clamscan-segfault/clamscan.exe.stackdump

Sounds like this should be reported to Clamav upstream. Is anyone 
involved with Clamav already, that could report this to the right 
people, or do I need to start signing up for mailing lists? :)



--
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: xpdf relocation error

[Jaakov Jaakov]

Dear Mark:

After rebooting and starting a fresh non-X terminal, rebasing worked. xpdf 
starts again. 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

Can't login to Cygwin SSH server with domain account

[Andrei Remenchuk]

I am running Cygwin SSH server under local cyg_server account, and I 
can't login with domain accounts (using password).
Connection and authentication succeed, from what I can tell, but then 
the server immediately closes connection:


$ ssh domaintest@localhost
domaintest@localhost's password:
Last login: Fri May 13 13:14:44 2016 from ::1
Connection to localhost closed.

The only clue in server log is "Received SIGCHLD" message:

debug1: Allocating pty.
debug1: session_pty_req: session 0 alloc /dev/pty3
debug1: server_input_channel_req: channel 0 request shell reply 1
debug1: session_by_channel: session 0 channel 0
debug1: session_input_channel_req: session 0 req shell
Starting session: shell on pty3 for domaintest from ::1 port 
49287 id 0

debug1: Setting controlling tty using TIOCSCTTY.
debug1: Received SIGCHLD.
debug1: session_by_pid: pid 3464

At the same time, logins into local accounts do work.
When I switch the service to run under domain account instead, the 
opposite happens -  I can log in with domain accounts, but cannot login 
using local accounts anymore. Only in that case, the error is different:


/bin/bash: Operation not permitted

In all cases, it looks like authentication succeeds, but then some 
privileges don't match up.


https://cygwin.com/ml/cygwin/2010-01/msg00334.html talks about similar 
problem in relation to passwordless logons, and says that in order to 
ssh into domain accounts, I also have to run the service under domain 
account. That makes sense, however I am using password logons, which 
theoretically should work in all cases, as far as I understand.


Ideally, I'm looking for SSH setup where both local and domain users can 
login. Is that even possible ?





--
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] clamav 0.99.1-1

[Yaakov Selkowitz]

On 2016-05-13 13:51, Mike Bonnet wrote:

The build issue was a red herring, sorry about that. It turns out a
specific file, xdate.exe, is causing clamscan to segfault. This is an
old file, from 2012, used for date formatting, but it has just started
causing problems. I've reproduced the segfault in 0.99.1-1 and 0.98.7-2
running on Cygwin64 on Windows Server 2012, but didn't go any further
back than that.


Mike,

Thanks for narrowing this down to a test case.

I was able to reproduce this too on both Windows 7 (sporadically) and 
Server 2012 (consistently), but only after updating the "daily" 
signatures from 21513 to 21539.  Upgrading to 0.99.2 locally did not 
help, but disabling bytecode (e.g. --bytecode=no in CLI) seems to be a 
workaround.


Therefore, I suspect its either a bug in LLVM JIT (certainly possible) 
or in register handling in Cygwin.  Either way, it's going to be some 
"fun" to track this down further.



Sounds like this should be reported to Clamav upstream. Is anyone
involved with Clamav already, that could report this to the right
people, or do I need to start signing up for mailing lists? :)


There is a bugzilla, but I suspect this will have to be fixed on our end 
somewhere.


--
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

The font "TeX Gyre Termes" cannot be found.

[Jaakov Jaakov]

How to reproduce:

[
user@host:~$ cp -a /usr/share/texmf-dist/doc/fonts/tex-gyre-math /tmp/test
user@host:~$ cd /tmp/test
user@host:/tmp/test$ xelatex test-xelatex-texgyre_termes_math
This is XeTeX, Version 3.14159265-2.6-0.2 (TeX Live 2015/Cygwin) (preloaded 
format=xelatex)
restricted \write18 enabled.
entering extended mode
(./test-xelatex-texgyre_termes_math.tex
LaTeX2e <2016/03/31>
Babel <3.9q> and hyphenation patterns for 81 language(s) loaded.
(/usr/share/texmf-dist/tex/latex/base/article.cls
Document Class: article 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texmf-dist/tex/latex/base/size12.clo))
(/usr/share/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec.sty
(/usr/share/texmf-dist/tex/latex/l3kernel/expl3.sty
(/usr/share/texmf-dist/tex/latex/l3kernel/expl3-code.tex)
(/usr/share/texmf-dist/tex/latex/l3kernel/l3xdvipdfmx.def))
(/usr/share/texmf-dist/tex/latex/l3packages/xparse/xparse.sty)
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec-xetex.sty
(/usr/share/texmf-dist/tex/latex/base/fontenc.sty
(/usr/share/texmf-dist/tex/latex/euenc/eu1enc.def)
(/usr/share/texmf-dist/tex/latex/euenc/eu1lmr.fd))
(/usr/share/texmf-dist/tex/xelatex/xunicode/xunicode.sty
(/usr/share/texmf-dist/tex/latex/tipa/t3enc.def
(/usr/share/texmf-dist/tex/latex/euenc/eu1lmss.fd))
(/usr/share/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texmf-dist/tex/latex/latexconfig/graphics.cfg)
(/usr/share/texmf-dist/tex/xelatex/xetex-def/xetex.def
(/usr/share/texmf-dist/tex/generic/oberdiek/infwarerr.sty)
(/usr/share/texmf-dist/tex/generic/oberdiek/ltxcmds.sty)
(/usr/share/texmf-dist/tex/latex/fontspec/fontspec.cfg)))kpathsea:make_tex: 
Invalid fontname `TeX Gyre Termes', contains ' '



!
! fontspec error: "font-not-found"
! 
! The font "TeX Gyre Termes" cannot be found.
! 
! See the fontspec documentation for further information.
! 
! For immediate help type H .
!...  
 
l.9 \setromanfont[Ligatures=TeX]{TeX Gyre Termes}

?

]

executing   fc-cache -f  won't help. Any way to repair the system?
--
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