Re: Programs become a no-op [SOLVED]

2018-05-15 Thread Boylan, Ross
Thanks Marco, David and Brian for your responses. After the diagnostic steps described below, suggested by you, I ran the setup program and told it to reinstall cygwin, cygwin-base, and adwaita-icon-theme. ssh and man are working again. I'm a little puzzled how I got in this state, although it

Re: Programs become a no-op

2018-05-03 Thread Brian Inglis
On 2018-05-02 14:13, Boylan, Ross wrote: > I've tried > ssh -V > ssh --help > ssh -v somene@somewhere > and in all cases nothing happens except that I get a new command prompt. > They used to work fine. > I tried reinstalling ssh and libssh2_1. No help. > I think the problem is more general: > man

Re: Programs become a no-op

2018-05-02 Thread Brian Inglis
On 2018-05-02 17:52, David Rothenberger wrote: > Kaz Kylheku wrote: >> On 2018-05-02 14:15, David Rothenberger wrote: >>> On 5/2/2018 1:13 PM, Boylan, Ross wrote: I've tried ssh -V ssh --help ssh -v somene@somewhere and in all cases nothing happens except that I get a new c

Re: Programs become a no-op

2018-05-02 Thread David Rothenberger
Kaz Kylheku wrote: > On 2018-05-02 14:15, David Rothenberger wrote: >> On 5/2/2018 1:13 PM, Boylan, Ross wrote: >>> I've tried >>> ssh -V >>> ssh --help >>> ssh -v somene@somewhere >>> and in all cases nothing happens except that I get a new command >>> prompt.  They used to work fine. >> >> This

Re: Programs become a no-op

2018-05-02 Thread Kaz Kylheku
On 2018-05-02 14:15, David Rothenberger wrote: On 5/2/2018 1:13 PM, Boylan, Ross wrote: I've tried ssh -V ssh --help ssh -v somene@somewhere and in all cases nothing happens except that I get a new command prompt. They used to work fine. This is usually due to a missing dependency. You can t

Re: Programs become a no-op

2018-05-02 Thread David Rothenberger
On 5/2/2018 1:13 PM, Boylan, Ross wrote: > I've tried > ssh -V > ssh --help > ssh -v somene@somewhere > and in all cases nothing happens except that I get a new command prompt. > They used to work fine. This is usually due to a missing dependency. You can try "echo $?" after one of the failing

Re: Programs become a no-op

2018-05-02 Thread Marco Atzeri
On 5/2/2018 10:13 PM, Boylan, Ross wrote: I've tried ssh -V ssh --help ssh -v somene@somewhere and in all cases nothing happens except that I get a new command prompt. They used to work fine. likely broken dependency due to a package update gone wrong. It usually happens when you do NOT shut

Programs become a no-op

2018-05-02 Thread Boylan, Ross
I've tried ssh -V ssh --help ssh -v somene@somewhere and in all cases nothing happens except that I get a new command prompt. They used to work fine. I tried reinstalling ssh and libssh2_1. No help. I think the problem is more general: man ssh man -V man --help man man also all get nothing. O