Weird permission problems in TextEdit

I have noticed an intermittent permissions problem with TextEdit lately. I will be typing in a text file when suddenly I get an error message that either informs me that I don't have permissions to edit the file or that I don't have permissions to write to the file teh folder is in. (See attached image.)


User uploaded file


Hopefully it goes without saying that using both Get Info and terminal commands on the file reveal that my user (which has admin access) ought to have permission to do what it likes with the file. I've even tried setting the permissions with both chmod and the tools in the Get Info box to the most open (i.e, anyone can edit) with no luck. Rebooting seems to fix the problem, but it is a pain. Definitely seems to be an issue with TextEdit, as I can edit the offending files and folders in, say BBEdit, without incident.


The problem started up roughly around the time I started creating symbolic links via MacDropAny (http://www.zibity.com/macdropany) so that I could sync some of my folders via DropBox, and I thought that might be related, but I have noticed the problem even when using folders not synced in this way.


Any suggestions would be helpful. TextEdit is really my everyday text editor of choice and I'm finding this problem quite irrirtating.

Posted on Jun 21, 2012 8:24 PM

Reply
24 replies

Sep 14, 2017 9:25 PM in response to Thomas Tempelmann

User uploaded file

I’ve found the opening error issue with both TextEdit and Preview under El Capitan. Is there any way to permanently prevent this opening error occurring?


If it's the autosave process at fault and it sounds like it, then perhaps I should disable it if no better solution?

defaults write com.apple.TextEdit ApplePersistence -bool no

Else:

<dict>

<key>ApplePersistence</key>

<false/>


Just today TextEdit decided to have one of its permissions tantrums, disallowing me to open any text file. I run apps 24/7 and last thing I need is to interrupt those apps or my activities whilst I am in the middle of working. I don't want to be periodically pressured into a reboot. 6 months of using El Capitan has been both good and bad.


I cannot understand the logic of Preview’s minimum width of showing images. Nothing uglier than having grey borders filling up my screen when I’m attempting to compare multiple images and it also limits the number of images that can be placed side by side. But as hinted elsewhere, Apple is unlikely to fix these issues. Though with the iMacPro & next year's return of the MacPro, perhaps they will consider fixing some of these bugs.

Mar 22, 2017 1:56 PM in response to Joshua Fruhlinger2

ok, this is years after this post first appeared, but I have been having this issue with Sierra. I have been wondering if it has to do with iCloud and TextEdit because I was able to save a TextEdit file to iCloud when I could not to my desktop, or documents folder or in my dropbox files. So I went to System Preferences>iCloud and un-ticked Text Edit for iCloud Drive (because I do not use it that way anyways). And then I moved it via Finder to where I wanted it.


Not sure if that helped but was worth contributing to the conversation. It did not immediately but after I restarted I can now work with the file - although restarting has typically helped when I run into issues with saving or opening TextEdit files and getting the Permission errors even though I as user have permission.

Apr 3, 2017 12:50 PM in response to Joshua Fruhlinger2

It's a bug in TextEdit, and one of the most annoying bugs in the Mac environment. There's almost certainly nothing wrong with your file permissions. For some reason, TextEdit randomly loses track of them. While this is happening, other editors (TextWrangler, Emacs, etc) can save files to the same folders without issue. Restarting seems to clear up the TextEdit problem, until it randomly starts happening again.

Jul 30, 2017 5:34 AM in response to cdamon

Supposedly, the issue comes from TextEdit being a sandboxed app, and it doing something wrong when trying to auto-save the document, probably because it tries to save to a global location where sandboxed apps are not allowed to write to. This should be rather easy to fix, but Apple is obviously too busy getting incredibly rich with their iOS project and has little love for the Mac platform any more.

Jul 30, 2017 5:49 AM in response to MCPH

Yes, that did work for me, too. Supposedly, Text Edit has its own folder for that, inside its sandbox folder under ~/Library/Containers/com.apple.TextEdit, but I guess that if there's also a "Autosave Information" folder present at ~/Library, then it prefers that, and then gets an error because it has no permissions to save it there. As soon as the "Autosave Information" is deleted from the user's Library folder, this problem goes away. However, other apps may later again recreate this folder, and then the issue is back for TextEdit, I guess.

Jun 21, 2012 10:02 PM in response to Joshua Fruhlinger2

There might be something wrong with the file itself. You could use cat in Terminal and send the contents of the old (current) file into a new file and use rm to remove the old file. Then you could you mv to rename the new file's name to the old file's name and chmod to give you full access and others limited access.

i.e. - if the file you're having trouble with is called original.txt you could use (btw, I'm using sudo because their might be a problem with permissions):


sudo cat original.txt > copy.txt


sudo rm original.txt


sudo mv copy.txt original.txt


sudo chmod 755 original.txt


If the problem persists, let me know.

Jun 21, 2012 10:28 PM in response to evilninjection

Is there any particular reason the process you describe would be any different from cutting the text from the offending article in TextEdit, pasting it in a new document, trashing the old document, and saving the new one under the same file name? Because I've already done that and got the same problem. Also, I've been able to open the offending file in other editors without running into the problem, which seems to me to indicate that the file itself is not the issue.


(Of course, TextEdit isn't giving me the problem now -- it's always hard to diagnose these intermittent issues!)

Jun 21, 2012 11:21 PM in response to Joshua Fruhlinger2

Joshua Fruhlinger2 wrote:


The problem started up roughly around the time I started creating symbolic links via MacDropAny (http://www.zibity.com/macdropany) so that I could sync some of my folders via DropBox, and I thought that might be related, but I have noticed the problem even when using folders not synced in this way


Can you completely disable MacDropAny and see what happens?


By the way, repair permissions is not going to fix anything. It has no affect on user files.


TextEdit is really my everyday text editor of choice and I'm finding this problem quite irrirtating.


First time I ever heard anyone say that. Why anyone would choose textedit over a real text editor like BBEdit (or little brother TextWrangler) is beyond me.

Jun 21, 2012 11:31 PM in response to X423424X

1. All MacDropAny does is provide a GUI front end for the creation of Unix symbolic links, so there's no real "activating" or "deactivating" it (the links remain even if you delete the program from your computer). It's possible that the problem might be with the existence of the symbolic links, or in how DropBox works -- as I said, this was my initial suspicion but the fact that I'm having the problem in folders not synced to DropBox or symbolically linked anywhere would seem to mitigate against that theory. I'll try turning DropBox off the next time I hit the problem and see if that helps.


2. I do use BBEdit for more advanced stuff but if all you want to do is write and spell-check plain text files in a lightweight applicaiton that loads more or less instantly, has zero visual destractions, and comes for free with your computer, I don't see anything wrong with TextEdit. Not like I can't open files in BBEdit if I need to.

Oct 3, 2012 12:16 PM in response to Joshua Fruhlinger2

This happens nearly every day to me. I lose the last modification, quit TextEdit, and relaunch it and the problem goes away.


Another weird thing w/ TextEdit has now developped: local files get a strange code appended to the filename. (This code disappears once uploaded to a website.)


For example: //Active/client.org/index.html#.UGyL6xiL0Z5


Anyone know how to get rid of this?

Oct 16, 2012 9:40 AM in response to Joshua Fruhlinger2

I have the same (or similar) issue and here's a theory: it's related to MS Word. Seems like the issue for me pops up after running a Word update using the Microsoft AutoUpdate app (and Installler). I'm running MS Office 2011 v14.2.4.


It's happened before and plagued me for a bit then went away. I tried all the usual remedies and can't remember which ended up fixing it, but I know it wasn't a simple permissions repair.

Nov 17, 2012 11:01 AM in response to Joshua Fruhlinger2

11-17-12. I am having the exact same problem; including the intermittency of it. I am using a MacBook AIr with Mountain Lion. Two Apple Senior Advisors were unable to remedy. Now in the hands of Apple Engineering. Haven't heard from them for 4 working days. A System Reboot did not fix the problem. We also "repaired permissions". I am not using MacDropAnything, The problem seemed to arise all on its own. I do have Office for Mac 2011 installed. The problem occurs in many, many files. New ones. old ones, converted rtx (AOL) files, etc. The Folder Permissions error message pops up, but goes away after pressing "OK", and then I can continue with the file and save it just fine.


I want to instantaneously create plain text files with minimal functionality (italics, font, underline). I don't need any html or code maniupulation. I use over 10,000 text files. My office is nearly paperless. Notepad is too simple, Microsoft Word is too slow and feature rich. I want a simple text box with minimal menu bars taking up space. Text Edit has these features. Does anyone know of a simple application that replicates it and is reliable on Mountain Lion? Joshua, have you fixed this problem??

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Weird permission problems in TextEdit

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.