Re: "setup-x86 --quiet-mode" problems

[Brian Inglis]

On 2018-04-19 10:31, Ulli Horlacher wrote:
> I have an update script which calls "setup-x86 --quiet-mode".
> So far, this works great, but now it tries to install a new mintty.exe,
> but one mintty still running (where I started setup-x86), so setup-x86
> kills this process... and setup-x86.exe is killed, too, which resulted in
> a damaged cygwin installation :-(
> I was able to fix it by running setup-x86.exe via Windows Explorer (pu!).
> How can I avoid this kind of problem in the future?
> I tried it with:
> setup-x86 --quiet-mode &
> sleep 1
> kill -9 $PPID
> But setup-x86 was killed again, too.

cygstart .../setup-x86 --quiet-mode ... && sleep 1 && kill -9 $$ $PPID

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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

libharfbuzz0 1.7.6-1 update causing xwin-xdg-menu.exe to crash

[Gilles Detillieux]

Has anybody else run into this problem? I've done two installations of 
Cygwin/X on Windows 10 systems this week, and they both had problems 
with the XWin Server dying just a few seconds after starting up. I 
traced the problem back to xwin-xdg-menu.exe getting a Segmentation 
fault, which then causes XWin Server to exit. I hacked an alternate 
.startxwinrc file to prevent XWin Server from dying (it ends with a 
"sleep infinity"), so I could debug it further.


With the XWin Server running reliably, I then ran "strace 
xwin-xdg-menu.exe" and saw that it got a segmentation fault just after 
reading a TTF font from the Windows Font directory (bahnschrift.ttf if 
it matters). I noticed there were two recent library updates related to 
font handling, so I tried back out to the previous version for each. It 
turns out that when I reverted to version 1.7.4-1 of libharfbuzz0, 
xwin-xdg-menu.exe stopped crashing.


If it matters, both these systems are the Fall Creator's Update (1709) 
of Windows 10 64-bit, and I'm running the 32-bit version of Cygwin.


Hopefully someone can track down and fix this recent bug!

Thanks,
Gilles

--
Gilles R. Detillieux  E-mail: 
Spinal Cord Research Centre   WWW:http://www.scrc.umanitoba.ca/
Dept. of Physiology and Pathophysiology, Rady Faculty of Health Sciences,
Univ. of Manitoba  Winnipeg, MB  R3E 0J9  (Canada)


--
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: 64-bit urxvt?

[Greywolf]

On 4/19/2018 0:19, Marco Atzeri wrote:

On 4/19/2018 6:13 AM, Greywolf wrote:

Greetings;

Does there not exist a 64-bit urxvt?  I fetched the most recent 
setup-x86_64.exe and I could swear I have the 64-bit package at work, 
but can't seem to find it for home...


 --*greywolf;



install rxvt-unicode


Egad! I hate it when my brain shuts off!  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: "setup-x86 --quiet-mode" problems

[Vince Rice]

> On Apr 19, 2018, at 11:31 AM, Ulli Horlacher wrote:
> 
> I have an update script which calls "setup-x86 --quiet-mode".
> So far, this works great, but now it tries to install a new mintty.exe,
> but one mintty still running (where I started setup-x86), so setup-x86
> kills this process... and setup-x86.exe is killed, too, which resulted in
> a damaged cygwin installation :-(
> 
> I was able to fix it by running setup-x86.exe via Windows Explorer (pu!).
> 
> How can I avoid this kind of problem in the future?
> 
> I tried it with:
> 
> setup-x86 --quiet-mode &
> sleep 1
> kill -9 $PPID
> 
> But setup-x86 was killed again, too.

The way you fixed it already — don't run setup under mintty (or dash or …).
Setup is not a cygwin program (it's not linked to cygwin1.dll).
It's safest to have all of your cygwin processes stopped when you run setup,
anyway, to prevent problems just like this.
--
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

"setup-x86 --quiet-mode" problems

[Ulli Horlacher]

I have an update script which calls "setup-x86 --quiet-mode".
So far, this works great, but now it tries to install a new mintty.exe,
but one mintty still running (where I started setup-x86), so setup-x86
kills this process... and setup-x86.exe is killed, too, which resulted in
a damaged cygwin installation :-(

I was able to fix it by running setup-x86.exe via Windows Explorer (pu!).

How can I avoid this kind of problem in the future?

I tried it with:

setup-x86 --quiet-mode &
sleep 1
kill -9 $PPID

But setup-x86 was killed again, too.


-- 
Ullrich Horlacher  Server und Virtualisierung
Rechenzentrum TIK 
Universitaet Stuttgart E-Mail: horlac...@tik.uni-stuttgart.de
Allmandring 30aTel:++49-711-68565868
70569 Stuttgart (Germany)  WWW:http://www.tik.uni-stuttgart.de/
REF:<20180419163128.ga7...@rus.uni-stuttgart.de>

--
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: Issue when trying to access files on a locked BitLocker volume

[Brian Inglis]

On 2018-04-19 07:45, Corinna Vinschen wrote:
> On Apr 19 13:38, Vincent Gheur wrote:
>> Hi,
>>
>> I'm using a Bitlocker encrypted SD card, which stays most of the time in my
>> laptop, but is generally not unlocked. I'm unlocking it only when I need to
>> access files on it.
>>
>> I have also a script which is started at regular intervals, which copies
>> some critical files on the SD card when it is unlocked. I was using till
>> recently a *very* old version of cygwin (probably downloaded 10 years ago),
>> in which I could check whether my SD card was unlocked or not by using *if
>> [ -d  ]*. I have downloaded a new version of cygwin in
>> January, as I migrated to Windows 10 and was encountering some issues with
>> it. Since I upgraded, this test is not working anymore. When the SD card is
>> unlocked, testing " -d  " returns TRUE. It returns FALSE when I do
>> the same test on a non Bitlocker volume for a non-existent folder (which is
>> the expected behaviour).
> 
> I'm not sure I understand.
> 
> You're testing with -d  if the drive is unlocked?
> And you're expecting... what exactly?  The test should return FALSE in
> all cases, regardless of the drive being locked or unlocked.
> 
> Sure, it sounds wrong if -d  returns TRUE, but
> I wonder if I misunderstand what you're doing.
> 
> Can you rephrase this to make it more clear?
> 
> Also, can you create an strace of the wrong behaviour to see if there's
> a certain error or NT status code which indicates the problem to be
> handled more correctly?

ISTM he's saying (badly) he's testing for an *existing* BitLocker folder which
should only be accessible when the volume is unlocked, but current Cygwin
returns that the folder is accessible, even when the volume should be locked.
Sounds like current Windows may be being "helpful" or caching volume info.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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: Issue when trying to access files on a locked BitLocker volume

[Corinna Vinschen]

On Apr 19 13:38, Vincent Gheur wrote:
> Hi,
> 
> I'm using a Bitlocker encrypted SD card, which stays most of the time in my
> laptop, but is generally not unlocked. I'm unlocking it only when I need to
> access files on it.
> 
> I have also a script which is started at regular intervals, which copies
> some critical files on the SD card when it is unlocked. I was using till
> recently a *very* old version of cygwin (probably downloaded 10 years ago),
> in which I could check whether my SD card was unlocked or not by using *if
> [ -d  ]*. I have downloaded a new version of cygwin in
> January, as I migrated to Windows 10 and was encountering some issues with
> it. Since I upgraded, this test is not working anymore. When the SD card is
> unlocked, testing " -d  " returns TRUE. It returns FALSE when I do
> the same test on a non Bitlocker volume for a non-existent folder (which is
> the expected behaviour).

I'm not sure I understand.

You're testing with -d  if the drive is unlocked?
And you're expecting... what exactly?  The test should return FALSE in
all cases, regardless of the drive being locked or unlocked.

Sure, it sounds wrong if -d  returns TRUE, but
I wonder if I misunderstand what you're doing.

Can you rephrase this to make it more clear?

Also, can you create an strace of the wrong behaviour to see if there's
a certain error or NT status code which indicates the problem to be
handled more correctly?


Thanks,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


signature.asc
Description: PGP signature

Re: Issue when trying to access files on a locked BitLocker volume

[Vincent Gheur]

Hi,

There are indeed several workarounds to this issue (this is why I'm not
waiting for a fix), but I thought it was worth mentioning the problem, as I
suspect other incorrect behaviors to be caused by the underlying issue.

Thanks for your answer !

   Vincent


On 19 April 2018 at 13:38, Vincent Gheur  wrote:

> Hi,
>
> I'm using a Bitlocker encrypted SD card, which stays most of the time in
> my laptop, but is generally not unlocked. I'm unlocking it only when I need
> to access files on it.
>
> I have also a script which is started at regular intervals, which copies
> some critical files on the SD card when it is unlocked. I was using till
> recently a *very* old version of cygwin (probably downloaded 10 years ago),
> in which I could check whether my SD card was unlocked or not by using *if
> [ -d  ]*. I have downloaded a new version of cygwin in
> January, as I migrated to Windows 10 and was encountering some issues with
> it. Since I upgraded, this test is not working anymore. When the SD card is
> unlocked, testing " -d  " returns TRUE. It returns FALSE when I do
> the same test on a non Bitlocker volume for a non-existent folder (which is
> the expected behaviour).
>
> I guess there are probably other issues related to accessing locked
> Bitlocker volumes.
>
>
> If someone is wanting to solve this, don't hesitate to contact me if you
> need more details or if you want me to make tests.
>
>
> Kind regards,
>
>Vincent
>
>

--
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: Issue when trying to access files on a locked BitLocker volume

[Eliot Moss]

On 4/19/2018 7:38 AM, Vincent Gheur wrote:

Hi,

I'm using a Bitlocker encrypted SD card, which stays most of the time in my
laptop, but is generally not unlocked. I'm unlocking it only when I need to
access files on it.

I have also a script which is started at regular intervals, which copies
some critical files on the SD card when it is unlocked. I was using till
recently a *very* old version of cygwin (probably downloaded 10 years ago),
in which I could check whether my SD card was unlocked or not by using *if
[ -d  ]*. I have downloaded a new version of cygwin in
January, as I migrated to Windows 10 and was encountering some issues with
it. Since I upgraded, this test is not working anymore. When the SD card is
unlocked, testing " -d  " returns TRUE. It returns FALSE when I do
the same test on a non Bitlocker volume for a non-existent folder (which is
the expected behaviour).

I guess there are probably other issues related to accessing locked
Bitlocker volumes.


If someone is wanting to solve this, don't hesitate to contact me if you
need more details or if you want me to make tests.


I agree that this outcome is strange, but here are some suggestions for
workarounds:

- Test some other property of the same or some other file
- Try some program, such as ls, on the file.  You can direct standard
  output and error to /dev/null and check the result code to see if the
  program failed.
- Try a program that requires write capability, such as touch, if ls does
  not do what you need.

Regards - Eliot Moss

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

Issue when trying to access files on a locked BitLocker volume

[Vincent Gheur]

Hi,

I'm using a Bitlocker encrypted SD card, which stays most of the time in my
laptop, but is generally not unlocked. I'm unlocking it only when I need to
access files on it.

I have also a script which is started at regular intervals, which copies
some critical files on the SD card when it is unlocked. I was using till
recently a *very* old version of cygwin (probably downloaded 10 years ago),
in which I could check whether my SD card was unlocked or not by using *if
[ -d  ]*. I have downloaded a new version of cygwin in
January, as I migrated to Windows 10 and was encountering some issues with
it. Since I upgraded, this test is not working anymore. When the SD card is
unlocked, testing " -d  " returns TRUE. It returns FALSE when I do
the same test on a non Bitlocker volume for a non-existent folder (which is
the expected behaviour).

I guess there are probably other issues related to accessing locked
Bitlocker volumes.


If someone is wanting to solve this, don't hesitate to contact me if you
need more details or if you want me to make tests.


Kind regards,

   Vincent

--
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: UX tweaks: installer should be emphasized

[Corinna Vinschen]

On Apr 18 14:51, Christos Hayward wrote:
>  At present both installer links are presented without visual emphasis:
> 
> The most recent version of the Cygwin DLL is 2.10.0
> . Install it
> by running setup-x86_64.exe  (64-bit
> installation) or setup-x86.exe (32-bit
> installation)
> 
> 
> I would at least make the links bold:
> 
> The most recent version of the Cygwin DLL is 2.10.0
> . Install it
> by running *setup-x86_64.exe*  (64-bit
> installation) or *setup-x86.exe*  (32-bit
> installation).
> 
> 
> Or emphasize 64-bit setup:
> 
> The most recent version of the Cygwin DLL is 2.10.0
> . *Install it
> by running setup-x86_64.exe * (64-bit
> installation) or setup-x86.exe  (32-bit
> installation).

I see what you mean.  I slightly tweaked the layout.


HTH,
Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat


signature.asc
Description: PGP signature

Re: 64-bit urxvt?

[Marco Atzeri]

On 4/19/2018 6:13 AM, Greywolf wrote:

Greetings;

Does there not exist a 64-bit urxvt?  I fetched the most recent 
setup-x86_64.exe and I could swear I have the 64-bit package at work, 
but can't seem to find it for home...


     --*greywolf;



install rxvt-unicode

--
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: Society of Toxicology 2018 - Attendees Info

[Jimmy Morgan]

Hi,

I hope you are the right person to discuss about SOT Annual Meeting and
ToxExpo - Society of Toxicology Attendees Email List?

Society of Toxicology Attendees email list of 4,500+ contacts with complete
contact details and verified email addresses.

List will be provided for unlimited usage.

Interested? Email me back, I'd love to provide more information on the list.

 

Thank you.

Regards,

Jimmy Morgan

Demand Generation Executive.

If you do not wish to receive future emails from us,
please reply as "opt-out"


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