Much of Tunnelblick's user interface uses an OS X system call to create and display a dialog window. The system call to create such a dialog window is CFUserNotificationCreate(), and I understand very few other programs use it. For some reason that system call is failing on your computer. It is such a fundamental call that it is hard to understand how anything other than a major (but hidden) program with your OS X installation is causing it.
This error happened to two other people that I know of:
Re: Failure to startup on tunnelblick 3.3 (build 3518). Neither (as far as I know) was able to fix it. For the original poster, Tunnelblick crashed when the error happened. More recent versions of Tunnelblick (including the version used by the second poster, and your version) fail and put an error in the Console log. The first person ended up using the closed-source Viscosity program instead of Tunnelblick.
The error (as you noted from the log) is error 1102, which appears to be "cbNotFound". That makes more sense to me than error -1102, which is an "NSURLErrorDomain" error).
However, if you search for
cbNotFound os x error 1102
you will get a bunch of advertisements and links to "MacKeeper".
It is my understanding the MacKeeper is NOT a good program and that you should NOT use it. See
https://discussions.apple.com/docs/DOC-3691 for details.
Two relatively easy things you could do to try to fix the problem include
- Restarting your computer
- Performing a "safe boot", followed by a normal boot.
You could also try performing a "safe boot" (as above) but trying to launch Tunnelblick in "safe boot" mode. You may not be able to actually connect to a configuration, but if you were able to see Tunnelblick dialog boxes (such as the one about not having any configurations), that would indicate that the problem is caused by one or more kexts that are loaded in a regular boot but not loaded with a "safe boot". If that's the case, do a normal boot, then post the results of typing the following command into Terminal (located in /Applications/Utilities):
kextstat | grep -v com.apple
(I may be able to see a kext that could be problematic.)