menu bar icon unresponsive

[rob...@rstoeber.com]

My first installation of Tunnelblick was after I had already updated to macOS, so I had no update problems or older versions of Tunnelblick laying around.

My Tunnelblick is 3.6.7c (build 4606)

Everything is working great and I'm very impressed with the performance. The only problem I have noticed is that the icon in the menubar becomes unresponsive.

I think this happens after a period of time where the VPN is disconnected and the computer has been asleep. I usually notice when I take the computer out to a coffee shop. The icon (disconnected) appears, but clicking on it has no effect. The status window does not appear and I can't use the icon to connect. Launching the app from the Applications folder works properly, but even after connecting, the icon in the menubar does not change and is still unresponsive to clicking.

Rebooting the computer will make the menubar icon work properly again. But after a while it will become stuck again.

I have tried this with two different versions of the menubar icon and both acted the same way.

Not a big problem because Tunnelblick continues working properly, just a little cosmetic/annoying issue.

[Tunnelblick developer]

Thanks for your report.

If I understand you correctly, it sounds like a big issue to me: you can't control Tunnelblick and have to restart your computer to regain control!

Clicking on the Tunnelblick icon should almost always result in the menu popping down immediately. There are a few times that won't happen, when Tunnelblick has a window open asking you for something.

If this is happening at other times (when there is no Tunnelblick window open and asking for a response from you):

• See if you see the "spinning pizza of death" when you move the pointer over the Tunnelblick icon in the menu bar.
  
  
• See what the macOS "Activity Monitor" application shows about Tunnelblick. Does it say "not responding" after the name?
  
  
• See if you can figure out if it happens only when the computer has been asleep. If so, does it happen only if a VPN was connected when it went asleep, or does it happen even if there was not a connected VPN?