Tunnelblick could not display a window

149 views
Skip to first unread message

cloud...@gmail.com

unread,
Jul 1, 2015, 8:42:03 PM7/1/15
to tunnelbli...@googlegroups.com, p...@clouds.com
This is a fresh install. Ran the Uninstaller first...

Jul  1 09:51:29 dhc32.clouds.com Tunnelblick[904]: Created a symbolic link to /Users/pjd/Library/Application Support/Tunnelblick/Configurations at /Users/pjd/Library/openvp
n
Jul  1 09:51:30 dhc32.clouds.com Tunnelblick[904]: Tunnelblick cannot run when it is on /Volumes because the volume has the MNT_NOSUID statfs flag set.
Jul  1 09:51:35 dhc32.clouds.com Tunnelblick[904]: Beginning installation or repair
Jul  1 09:51:35 dhc32.clouds.com authexec[912]: executing /Volumes/Tunnelblick/Tunnelblick.app/Contents/Resources/installer
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: Installation or repair succeeded; Log:
        Tunnelblick installer started 2015-07-01 09:51:35. 1 arguments: 0x0017
        Created directory /Library/Application Support/Tunnelblick with owner 0:80 and permissions 755
        Changed ownership of /Library/Application Support/Tunnelblick from 0:80 to 0:0
        Created directory /Library/Application Support/Tunnelblick/Logs with owner 0:0 and permissions 755
        Created directory /var/log/Tunnelblick with owner 0:0 and permissions 755
        Created directory /Library/Application Support/Tunnelblick/Shared with owner 0:0 and permissions 755
        Created directory /Library/Application Support/Tunnelblick/Tblks with owner 0:0 and permissions 755
        Created directory /Library/Application Support/Tunnelblick/Users with owner 0:0 and permissions 755
        Created directory /Library/Application Support/Tunnelblick/Users/pjd with owner 0:0 and permissions 755
        Changed ownership of /Users/pjd/Library/Application Support/Tunnelblick from 501:20 to 501:80
        Changed ownership of /Users/pjd/Library/Application Support/Tunnelblick/Configurations from 501:20 to 501:80
        Copied /Volumes/Tunnelblick/Tunnelblick.app to /Applications/Tunnelblick.app
        Changed ownership of /Applications/Tunnelblick.app and its contents from 501:20 to 0:0
        Installed /Library/LaunchDaemons/net.tunnelblick.tunnelblick.tunnelblickd.plist
        Used launchctl to load tunnelblickd
        Tunnelblick installer finished without error
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: Installation succeeded:  Tunnelblick was successfully installed.
       
        Do you wish to launch Tunnelblick now?
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: CFUserNotificationCreate() returned with error = 1102; notification = 0x0, so TBRunAlertExtended is terminating Tunnelblick after attempting to display an error window using CFUserNotificationDisplayNotice
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: Alert:  Tunnelblick could not display a window.
       
        CFUserNotificationCreate() returned with error = 1102; notification = 0x0
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: CFUserNotificationDisplayNotice() returned 1102
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: Terminating because of error; stack trace:
        (
                0   Tunnelblick                         0x0001681e -[MenuController terminateBecause:] + 129
                1   Tunnelblick                         0x00035127 TBRunAlertPanelExtended + 1391
                2   Tunnelblick                         0x000352cf TBRunAlertPanel + 77
                3   Tunnelblick                         0x00022bfb -[MenuController relaunchIfNecessary] + 3370
                4   Tunnelblick                         0x000243f6 -[MenuController initialChecks:] + 1618
                5   Tunnelblick                         0x0002973d -[MenuController init] + 7060
                6   AppKit                              0x91d615fb -[NSCustomObject nibInstantiate] + 380
                7   AppKit                              0x91d0c5d8 -[NSIBObjectData instantiateObject:] + 319
                8   AppKit                              0x91d0badf -[NSIBObjectData nibInstantiateWithOwner:options:topLevelObjects:] + 450
                9   AppKit                              0x91d0b917 -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 56
                10  AppKit                              0x91ce8841 loadNib + 462
                11  AppKit                              0x91ce7c06 +[NSBundle(NSNibLoading) _loadNibFile:nameTable:options:withZone:ownerBundle:] + 330
                12  AppKit                              0x91eaac95 +[NSBundle(NSNibLoadingInternal) _loadNibFile:externalNameTable:options:withZone:] + 161
                13  AppKit                              0x9200e5d7 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 67
                14  AppKit                              0x91ce7875 +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 745
                15  AppKit                              0x91cdf650 NSApplicationMain + 690
                16  Tunnelblick                         0x00002639 _start + 208
                17  Tunnelblick                         0x00002568 start + 40
        )
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: applicationShouldTerminate: termination because of an error; delayed until 'shutdownTunnelblick' finishes
Jul  1 09:51:37 dhc32.clouds.com spindump[692]: Saved spin report for Tunnelblick version 3.6beta06 (build 4346) (4346) to /Library/Logs/DiagnosticReports/Tunnelblick_2015-07-01-095137_procloudscom.spin
Jul  1 09:51:37 dhc32.clouds.com Tunnelblick[904]: Finished shutting down Tunnelblick; allowing termination

Any ideas?

This is Yosemite 10.10.3

Thanks!

jkbull...gmail.com

unread,
Jul 1, 2015, 11:36:40 PM7/1/15
to tunnelbli...@googlegroups.com, cloud...@gmail.com, p...@clouds.com, cloud...@gmail.com
This is something that has happened to a few people for several years and I've never figured out what causes it. Tunnelblick uses an old and very basic system call to display most of its windows, and on some systems that system call fails consistently – that's what is happening here. Because most modern programs don't use that call, they don't have a problem.

You can search the discussion group for the other couple of threads about it, but as far as I know there is no solution other than reinstalling OS X.
Reply all
Reply to author
Forward
0 new messages