-
All replies
-
Helpful answers
-
Oct 2, 2015 8:49 AM in response to rgorelikby Jeep-Pong,★HelpfulHaving the exact same issue as rgorelik. This issue appears on login of any user on my mac mini and when I attempt to connect to network drives, disconnecting me from said drives the second the message pop-up. Any ideas are greatly appreciated.
-
Oct 2, 2015 10:09 PM in response to rgorelikby ancall,★HelpfulSame error here. Dialog box disappears after a short time.
-
-
Oct 4, 2015 3:23 AM in response to seb90deby laerning,★HelpfulSame here..
El Capitan 10.11
MacBook Pro 15" Mid 2012
-
Oct 4, 2015 10:44 AM in response to laerningby rhekinek,And also here...
This problem came up after update to OS X El Capitan.
Any ideas?
MacBook Air (2014)
-
Oct 4, 2015 11:22 AM in response to rgorelikby rgorelik,Something wrong with system/library/frameworks/coretelephony.framework Maybe...
-
Oct 7, 2015 6:17 AM in response to rgorelikby Gohtac,Same issue with my Retina MacBook Pro 15" Late 2013 and El Capitan.
-
Oct 7, 2015 11:59 AM in response to rgorelikby jlw61,I am having the problem under El Catitan (Server) only for network users.
-
Oct 7, 2015 12:22 PM in response to jlw61by Demetrios,★HelpfulYup. same problem under El Capitan. Can't log into server account locally or from a mobile home folder. I get that error and then the spinning beachball + the spinning black & white round thingy.
-
Oct 7, 2015 9:12 PM in response to rgorelikby OSX AbUser,★HelpfulExact same error/dialog here following an upgrade to El Capitan 10.11 from Yosemite 10.10.5 on an iMac.
- Replaced /System/Library/Frameworks/CoreTelephony.framework from the El Capitan installer
- Deleted/reset all the iMessage DB/files/plists (I had no problems with iMessage, it was already and is still working fine under El Capitan)
- Same error occurs under a new test user-account (makes it look like a system-config/corruption/bug problem)
No issues with iCloud, iMessage, connecting to CIFS network shares, etc. Dialog pops up after user login, hangs around waiting for me to click "OK", and if ignored, it'll go away on its own after a few mins.
Of interest in my config, I have two drive, one SSD and one HDD. The iMac boots from SSD, but the actual "Home Directory" (/User) has been relocated to the HDD with a link pointing to the new location. Perhaps the 0755 error indicates that the new/beta CoreTelephony.framework cannot directly write to the filesystem linked "/User" folder as the actual/real HFS+ FS path is "/Volumes/DataDrive/Users/" (eg: a hardcoded FS write attempt to the /User path)? If this is the case, perhaps this is simply a minor bug that can be easily addressed in an update... If not, it must be a specific/unique mis-configuration issue.
Any ideas/trouble-shooting welcome! No joy from the folks at Apple (iMac is out of support window).
-
Oct 10, 2015 10:55 AM in response to rgorelikby nummer2001,Same issue here with iMac 27 inch, Retina 5k. User files are all external. Internal SSD only has system, programs and link to user directory. Another error occurs when I try to sync my contacts with a Baikal server. According to some other sources El Capitan update obviously creates some error when trying to access the user database on the server. It cannot identify the user as having access rights. Some people report about a workaround for owncloud.
Both errors started to occur at the same time. Not sure if they are connected.
-
Oct 12, 2015 1:03 PM in response to OSX AbUserby jandockx,Same error immediately after first login as a network used after update of 10.10.5 to El Capitan. No issue with a local user.
Another reason to ditch network users completely (OneDrive doesn't work, IPhoto sharing didn't work, ...(.
-
Oct 14, 2015 4:20 AM in response to rgorelikby 112madgamer,Is this still unsolved if so i have the same issue but mine is with /Users
-
Oct 17, 2015 4:50 AM in response to rgorelikby macigbook,★HelpfulSame problem here after updating to El Capitan.
I have my user directory on a SD card. Maybe thats part of the problem?
I switched back to Yosemite. At least until theres a solution for that bug.
