CoreTelephony Trace File Error

I don't know about that. The error never prevented my computer from booting, or me from logging in.

Hi Muttatta,

First and foremost, please check all answers for the phrase "in response to xxx", because most of the posts were not addressed to your issue.

Now, from your description of the issue you have, I suspect that your SSD is dead, therefore you can't boot, can't format disk, etc.. In your place I would try to boot from an external device and see if you can salvage the internal SSD, I mean, at least if you can format it using DiskUtility. If not, you have no other choice as to replace it and re-install.

Hope it helps.

Thanks for your comments Lix. If the ssd has failed as you suggest it may have - would it still be possible for me to access my MS Window's partition? So, is it possible for just one partition to fail and not the other.

Cheers

In theory, if the SSD has a hardware failure, no, it should not be possible. Therefore, as you say you still can boot in Windows, you might still have a chance that the SSD is not defective, and only the partition is damaged beyond repair. The only way to find out is to boot from e.g. an USB stick in OS X and reformat the drive using Disk Utility. I have no experience with Boot Camp and Windows, but I suspect in this process the Windows partition will be also gone. If you have another Mac, you can easily prepare an 8 GB (or larger) USB stick to hold MacOS X and boot out if it. I always keep such a boot USB stick around, as you never know when you need one. See also http://www.macworld.com/article/2981585/operating-systems/how-to-make-a-bootable -os-x-10-11-el-capitan-installer-drive.html

Lix

Hi,

After a month of this I got the following steps from Apple to fix this ugly thing.

First Run Disk Utility and run Disk First on your drive

Then take the following steps.

I had no access to anything relating to iCloud until I did this and now everything works again.

No more using Outlook for email!

To repair home permissions and ACLs:

1. Shut down the computer.

2. Locate the Command key and the R key on the keyboard. As you turn the computer on, press and hold Command-R before the gray screen appears but after you press the power button.

3. If you get a language screen, select your language and move forward.

4. You will now be in the OS X Utilities screen. At the top of the monitor select the Utilities menu.

5. Select Terminal

6. In the window that opens, type "resetpassword" (without the quotations, with no spaces and no capitals).

7. In the new window that comes up select the Macintosh HD at the top, then your user.

8. Click the button at the bottom right of that window to Reset Home Permissions and ACL's

9. When it is done, click the Apple menu () at the top left and select Restart

Thank you Lyle for the posting. In my case it doesn't help. My configuration is on MacOS X server and most of the users are of the Network type. The CoreTelephony message error appearing at login for all the users refers to the /Network directory (not /Users as in most cases). So when trying your hint, the "reset password" utility doesn't display any Network user, so there is none to set the ACLs on.

Most probably the issue is similar, however, the solution must be different. There must be a way to set the ACLs for Network users too, but I have no idea how. Probably I will call Apple, they might know how to solve this too.

I was able to resolve this by changing the permissions on the on /Library. I noticed on one of my computers that didn't have the issue the permissions were setup as 'ystem - Read & Write', wheel 'Read only', everyone - 'Read only'. On the mac with the issue, System was not even listed in the permissions and 'everyone' had 'no access'. So I changed the permissions to mirror the other computer. I didn't mess around with it to see if both changes were needed but this is how I resolved it.

Same issue. I have updated to 10.11 since it released. There was something wrong with the application windows when I resize them. So I restart my laptop.

Then the error hanpped. I create a file /tmp/ct.shutdwon, but it can't work.

Model Name: MacBook Pro

Model Identifier: MacBookPro11,1

Processor Name: Intel Core i5

Processor Speed: 2.4 GHz

Number of Processors: 1

Total Number of Cores: 2

L2 Cache (per Core): 256 KB

L3 Cache: 3 MB

Memory: 8 GB

Boot ROM Version: MBP111.0138.B16

SMC Version (system): 2.16f68

It'a about permission problem.

$ sudo chmod 1777 /tmp

now it ok

Re: CoreTelephony Trace File Error

worked for me

iMac 27, 5k and El Capitan

huoqi,

Perfect! Simple fix and it did the job.

Yep. fixed it for me too. Thanks

Did not help me. I am running OS X server. In my case, the message refers to the Network directory. I tried the trick with the permissions on it (and on other directories as suggested here), but to no avail. In fact, I suspect the issue might be different, as the error claims the Network directory already exists. All network users are affected, while local users are not.

This is apparently an excellent solution for those of us who have our /Users/~usernamedata stored somewhere other than directly in the /Users directory.

While addressing another problem with the Mac App Store, I'd hacked around with my directories and various sym links for quite a while. I came upon this to address the problem Core Telephony Trace problem I encountered when I upgrade to El Cap, and after one restart, it seems to have alleviated the issue.

Thanks!

I also am having the same problem. I am running OS X El Captain using OS X Server. I get the Core Telephony error when trying to login to a network account on the server itself. If I login into the network account on a network machine, the error does not come up.