Page 1 of 1

viscosity hangs to the eternal beach ball state

Posted: Thu Jan 03, 2019 4:57 am
by hatihati
I have two connections, both have google authenticator generated pass i can't save.
If I start viscosity at login, the both password windows open up.
Username does not save itself (tunnelblick did it for me),
but what is much worse,
if I'm not going to connect to VPN, i can close only one window, second hangs with beach ball,
status bar client also hangs, only thing i can do is to issue ps -ax | grep iscosity | xargs kill -9 in the terminal.

tl;dr:
This is very annoying since password windows are modal and cannot be hidden. I can close only one window out of two,
second one hangs up and client also hangs up.

Re: viscosity hangs to the eternal beach ball state

Posted: Thu Jan 03, 2019 9:45 pm
by James
Hi hatihati,

If you don't want the connections attempting to connect when Viscosity starts, you can edit each one and turn off the "Connect when Viscosity opens" option (located in the lower left corner of the editor).

If you'd like Viscosity to remember the username, without remembering the password, you can enable the RememberUsername option. Please see:
viewtopic.php?f=4&t=1382&p=4058#p4058

In regards to the second window failing to close, please see if this is still an issue in the latest beta version of Viscosity:
https://www.sparklabs.com/support/kb/ar ... -versions/

Cheers,
James

Re: viscosity hangs to the eternal beach ball state

Posted: Fri Jan 04, 2019 1:19 am
by hatihati
Thanks for your suggestions!
James wrote:
Hi hatihati,
If you don't want the connections attempting to connect when Viscosity starts, you can edit each one and turn off the "Connect when Viscosity opens" option (located in the lower left corner of the editor).
I do want this feature on weekdays, but i don't want VPNs on weekends.
James wrote:
In regards to the second window failing to close, please see if this is still an issue in the latest beta version of Viscosity:
https://www.sparklabs.com/support/kb/ar ... -versions/
Unfortunately, beta does not fix this bug. First authentification window closes, but attempt to close second one sends app to beachball state.