I tried running the 'hardy' script from that unpacked directory, and it also displays the window and then just hangs.
I should have mentioned that previously when it was hung, I checked for network traffic using tshark, and there was none.
The hang seems to be
root@lithe# strace -f -p 14963 Process 14963 attached - interrupt to quit futex(0xb7066794, FUTEX_WAIT, 2, NULL
root@lithe# pstree 14771 -a zsh └─hardy ./hardy ├─http ├─http ├─http ├─http ├─http └─http
Invoking the ./hardy script directly asking for the text frontend it does not hang -- at least it successfully gets up to telling me this may take several hours, etc.
So I think
./hardy --frontend DistUpgradeViewText
is probably the best workaround for now.
I tried running the 'hardy' script from that unpacked directory, and it also displays the window and then just hangs.
I should have mentioned that previously when it was hung, I checked for network traffic using tshark, and there was none.
The hang seems to be
root@lithe# strace -f -p 14963
Process 14963 attached - interrupt to quit
futex(0xb7066794, FUTEX_WAIT, 2, NULL
root@lithe# pstree 14771 -a
zsh
└─hardy ./hardy
├─http
├─http
├─http
├─http
├─http
└─http
Invoking the ./hardy script directly asking for the text frontend it does not hang -- at least it successfully gets up to telling me this may take several hours, etc.
So I think
./hardy --frontend DistUpgradeViewText
is probably the best workaround for now.