Thanks Matt, well spotted. It has been corrected in the full 1.0.6 release.
BTW, 64-bit version coming anytime soon?
Hi dfile, version 1.0.6 of Viscosity has 64 bit kernel support under Snow Leopard. However the Viscosity application itself is still 32 bit, and will probably be that way for a while (as the version of Python we use is 32 bit only). However it’s unlikely you’d see any performance benefit from a 64 bit version, as Viscosity isn’t all that CPU intensive (most of the time it should be sitting at 0% CPU usage).
The latest beta, version 1.0.8b2 as quoted above, is functioning normally thus far upon my initial testing. I was able to successfully access the internal network of each configured VPN connection without any visible issues nor any other difficulty related to updating.
I tested using Snow Leopard booted via the full 64-bit (x86_64) kernel on a MacBook Pro (17-inch, Mid 2009):
# uname -a && system_profiler SPSoftwareDataType | tr -s [:space:] | grep -v "Name"
Darwin host.local 10.2.0 Darwin Kernel Version 10.2.0: Tue Nov 3 10:35:19 PST 2009; root:xnu-1486.2.11~1/RELEASE_X86_64 x86_64
Software:
System Software Overview:
System Version: Mac OS X 10.6.2 (10C540)
Kernel Version: Darwin 10.2.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled
64-bit Kernel and Extensions: Yes
Time since boot: 2:22
Thank you for the 1.2 beta/prerelease; I’m looking forward to the enhancements added in this version.
Using Viscosity version 1.2b3 I am experiencing the following persistent issue:
Upon clicking the Viscosity menu bar icon there is no visible response; no drop-down menu is displayed.
The aforementioned symptom was experienced after performing the following steps:
Upgrade Viscosity:
Quit currently running instance of Viscosity
Remove old Viscosity.app from ~/Applications/
Install new Viscosity.app into ~/Applications/
Start/Run Viscosity.app
Click the Viscosity menu bar icon
Observe that my two (2) preexisting VPN connections (not actively connected) now have one of them duplicated, for a total of three (3) VPN connections; the duplicated entry appears to be of the last VPN connection that was used.
Open Viscosity Preferences
Create one (1) connection folder
Drag-and-drop to move two (2) unique entries of the three (3) total connections into the new folder, where 2 out of 3 connections are now in a submenu, leaving only a duplicate entry at the original “root” folder level that is not in a submenu.
Attempt to delete what appeared to be the duplicate entry from the “root” folder level, that is, keep only the two (2) unique connections that are organized into a subfolder (submenu).
Observe Viscosity crash upon attempting to delete the duplicate entry.
Observe the following detail logged:
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] Traceback (most recent call last):
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] File "/Users/$USERNAME/Applications/Viscosity.app/Contents/Resources/main.py", line 23, in <module>
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] AppHelper.runEventLoop()
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] File "/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyObjCTools/AppHelper.py", line 246, in runEventLoop
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] File "/System/Library/Frameworks/Python.framework/Versions/2.5/Extras/lib/python/PyObjCTools/AppHelper.py", line 134, in unexpectedErrorAlertPanel
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] File "PrefsWinConnections.py", line 380, in outlineView_objectValueForTableColumn_byItem_
2010/08/11 11:46:05 a.m. [0x0-0x6a06a].com.viscosityvpn.Viscosity[695] KeyError: '2'
2010/08/11 11:46:05 a.m. Viscosity[695] An uncaught exception was raised
2010/08/11 11:46:05 a.m. Viscosity[695] /Projects/Viscosity/trunk/main.m:92 main() PyRun_SimpleFile failed with file '/Users/$USERNAME/Applications/Viscosity.app/Contents/Resources/main.py'. See console for errors.
2010/08/11 11:46:05 a.m. Viscosity[695] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: '/Projects/Viscosity/trunk/main.m:92 main() PyRun_SimpleFile failed with file '/Users/$USERNAME/Applications/Viscosity.app/Contents/Resources/main.py'. See console for errors.'
*** Call stack at first throw:
(
0 CoreFoundation 0x0055dbba __raiseError + 410
1 libobjc.A.dylib 0x003d3509 objc_exception_throw + 56
2 CoreFoundation 0x0055d8e8 +[NSException raise:format:arguments:] + 136
3 CoreFoundation 0x0055d85a +[NSException raise:format:] + 58
4 Viscosity 0x00002b22 main + 796
5 Viscosity 0x000027da start + 54
)
2010/08/11 11:46:06 a.m. com.apple.launchd.peruser.$UID[137] ([0x0-0x6a06a].com.viscosityvpn.Viscosity[695]) Job appears to have crashed: Trace/BPT trap
2010/08/11 11:46:07 a.m. ReportCrash[808] Saved crash report for Viscosity[695] version 1.2b3 (1.2b3) to /Users/$USERNAME/Library/Logs/DiagnosticReports/Viscosity_2010-08-11-114606_$HOSTNAME.crash
Upon subsequent re-opening/restarting of Viscosity.app, the following error is logged to console:
Testing was performed using the following hardware and software platform:
# uname -mrsv && system_profiler SPHardwareDataType SPSoftwareDataType | tr -s [:space:] | egrep -v "UUID|Serial|(Computer|User)\ Name"
Darwin 10.4.0 Darwin Kernel Version 10.4.0: Fri Apr 23 18:27:12 PDT 2010; root:xnu-1504.7.4~1/RELEASE_X86_64 x86_64
Hardware:
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro5,2
Processor Name: Intel Core 2 Duo
Processor Speed: 3.06 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 6 MB
Memory: 8 GB
Bus Speed: 1.07 GHz
Boot ROM Version: MBP52.008E.B05
SMC Version (system): 1.42f4
Sudden Motion Sensor:
State: Enabled
Software:
System Software Overview:
System Version: Mac OS X 10.6.4 (10F569)
Kernel Version: Darwin 10.4.0
Boot Volume: Macintosh HD
Boot Mode: Normal
Secure Virtual Memory: Enabled
64-bit Kernel and Extensions: Yes
Time since boot: 1:58
Thanks for the feedback. It looks like Viscosity didn’t correctly upgrade the old connection order to the new format correctly. I’ll look into it.
In the meantime deleting Viscosity’s prefs file, or running the following command in the Terminal, should get you going again:
defaults delete com.viscosityvpn.Viscosity ConnectionOrder
Thank you for the tip; that allowed me to successfully start Viscosity. I was prompted to authenticate as an administrator so it could make changes (like normal) and was subsequently able to access the the Viscosity menu bar icon and drop-down menu to open its preferences. I don’t recall if when I first started the new version it asked me to authenticate as an administrator; it may have, but I do not remember this specific detail with certainty.
I noticed that the folder created earlier was nonexistent and the duplicated connection was missing both copies; however, I was able to restore from a backup of the duplicated connection that was exported before attempting to delete anything.
I had no difficulty reorganizing the two connections into a folder or submenu, and, subsequently, I was able to successfully connect and utilize my VPN connection using the new 1.2b3 version of Viscosity.
Thank you for assisting via the forums; your support is greatly appreciated.
I’m running SL 10.6.7 and I just installed Version 1.3b11 and my VPN gave me a .config file to use, which I saw when I installed 1.2 became associated with Viscosity so that all I had to do was click it and it gets added into Viscosity.
Well when I clicked the config file with Version 1.3b11 installed it does nothing, the VPN information doesn’t get loaded.
So I tried this a few ways.
I clicked the config file with Viscosity running showing in the taskbar.
I clicked the config file Viscosity was not showing/running in the taskbar.
I rebooted and then tried these steps over, with no success…
When I click the config file and Viscosity is not in the taskbar, clicking the config file however launches Viscosity making it appear, but that’s all…
Clicking my config file does nothing, it’s not being imported into 1.3b11…
So I uninstalled 1.3b11 and reinstalled 1.2 and then clicked my config and imported it, then uninstalled 1.2 and reinstalled 1.3b11 and then my config settings were in place…
Also leaving Viscosity in the menu, but not connected to a VPN and logging in and out of OS X caused my Eth0 connection in the System Preferences to disconnect and I had to restart to get it back…
Also when I installed Growl and then tried to connect I kept getting a popup from Viscosity in the middle of the screen and then one from Growl about not being able to connect because my connection was down, but it was active, so I restarted and it then worked. So seems to be a problem installing Growl for the first time with the beta getting online if you don’t restart the system, or maybe logging out might of worked…
Also I’ve been using a VPN with the same company for the past 2 months and it’s always been the same IP, then the first time I start the beta I have a different IP from the server, so I don’t know if it’s just coincidence that this happened, or the beta is causing some sort of routing issue causing the VPN server to assign me a different IP.
Another thing, I wouldn’t call this a bug, rather a preference if we can get an option for this. The Growl notification showed my connection to the Client IP of 10.x.x.x and honestly I think for most people, they are going to want to see the actual IP (Server) they are being assigned not the Client, so maybe we can get a preference added into Viscosity to allow you to pick which IP you want shown in the Growl notification…
THANKS James
P.S. I had to uninstall 1.3b11 it kept crashing my connection and bringing it down and the only way I could get it back was by restarting OS X…
There are a couple of known issues with the current beta build posted online. It sounds like you’ve run into one of them: Viscosity may nuke your system-set DNS servers if you have none specified for your VPN connection. This makes it seem like your computer has lost its network connection. A restart or a DHCP renewal fixes it.
We’ve already got a build that fixes this issue, however we’re just waiting for some new features to be finished off and some additional testing from our end before posting it to this thread.
Just a quick question. I specifically bought a license to test the new split-dns functionality that should be in 1.3. Is it already available in the current builds? For me either my standard DNS Server is used, or the one specified, no split configuration is possible.
Ok and I submitted a bug report over in the Support section with 1.2.3 giving me connectivity issues as well, so hopefully this will be worked out for this version…
The complete rewrite of the DNS system for 1.3 brings us closer to supporting split-DNS and lays the groundwork we need to properly support it, however I’m afraid it’s still not fully implemented yet. For now you’ll need to use scripting as outlined in this thread.
Thanks for the info. I created my own script in the meantime which seems to work ok there is no “Use alternate DNS support” function available in 1.3 though.
My main issue right now with 1.3 is that the DNS entries are flushed on disconnect so I have to renew the lease here. But as you said this is fixed already.
% ps axo stat,pid,ppid,comm G ‘^Z’
Z 210 181 (Little Snitch UI)
Z 87916 87912 (chown)
Z 87920 87912 (chmod)
Z 87921 87912 (chown)
Z 87922 87912 (chmod)
Z 87923 87912 (chown)
Z 87924 87912 (chmod)
Z 88405 87912 (ViscosityHelper)
Z 88407 87912 (ViscosityHelper)
Z 88409 87912 (ViscosityHelper)
Z 96571 96365 (ssh)
% ps axo pid,comm G 87912
87912 /Applications/Viscosity.app/Contents/MacOS/Viscosity
Thank you for being interested in keeping up with the latest news from us! Please double-check your email address below and then click the Subscribe button.
