Apple Silicon OS11 cannot Quit Viscosity

Got a problem with Viscosity or need help? Ask here!

tikijose2

Posts: 1
Joined: Thu Dec 31, 2020 4:27 am

Post by tikijose2 » Thu Dec 31, 2020 4:43 am
I recently upgraded to Apple Silicon MacBook Pro 13" M1 with OS11 Big Sur (version 11.1). I'm running Viscosity version 1.9 (1556)

The program runs fine, but I cannot quit. Sometimes the "Quit Viscosity" command is grey, sometimes it is white, but even when white, it will not shut down the program. It only disconnects. The the Process is still running in Activity monitor. Viscosity does not show up in "Force Quit", so I cannot shut it down that way. Disconnect is fine, but I want to assure that there is no way to accidentally connect to the remote server. This requires a shut down.

The only ways I've found to quit are to re-boot, or to kill the process in Activity monitor. It will quit with either "Quit" or "Force Quit." after clicking the process and the "X" in the octagon.

Is this a known bug, is there a solution?

Thanks,
JT

James

User avatar
Posts: 2313
Joined: Thu Sep 04, 2008 9:27 pm

Post by James » Mon Jan 04, 2021 3:56 pm
Hi JT,

Viscosity's "Quit Viscosity" menu item will be disabled if it has already received the instruction to Quit and it is waiting on one or more VPN connections to fully disconnect before quitting.

The most common reason for VPN connections to take a long time to disconnect is if there is a Disconnected script running that Viscosity or OpenVPN is waiting on. Viscosity will automatically terminate Disconnected AppleScript scripts after 60 seconds if they're still not finished, however OpenVPN scripts have no time limit. If you have any scripts set for your VPN connections you may like to try removing them and see if the issue persists.

I also recommend restarting your computer. Force quitting Viscosity can result in Viscosity's background helper ending up in an unexpected state, orphaned OpenVPN processes, or stuck DNS/network settings. These can potentially cause issues for future VPN connections without restarting first.

If you're still stuck, you may like to try the latest beta version of Viscosity to see if anything changes:
https://www.sparklabs.com/support/kb/ar ... -versions/

Finally, if you're still running into the same issue, I recommend checking whether there is any more information available in the Console:
https://www.sparklabs.com/support/kb/ar ... nsole-log/

Cheers,
James
Web: https://www.sparklabs.com
Support: https://www.sparklabs.com/support
Twitter: https://twitter.com/sparklabs
2 posts Page 1 of 1