@werneravr Hi, other folks experienced this error after upgrading to 10.10.3 OSX. This forum link has a workaround http://t.co/qjuwr2I7Bl

via Twitter ift.tt/ZOhZuQ

36 views
0 faves
0 comments
Uploaded on April 21, 2015