I’m aiming to contact AppleCare Support about this but thought I’d run it by y’all here ‘course, I’m not ruling out Excel (and Office in general) as the culprit considering their sometimes problematic file access security warning system (anyone know how to disable that?) but I’ve not encountered this access denied situation EVER, until today and I use the ‘offending’ Excel document nearly every dayĪny other thoughts or suggestions are welcome If not, what’s the current recommended method to reset permissions? I see TechTool Pro 14 has such a tool… (Home Permissions) The same situation appears in my other ‘pristine’ Admin user account. Is this a ‘new normal’ for the Documents folder to be “custom access”? - Cruising back in Time Machine shows it WAS Read/Write before the update. I continue to be able to add, delete, and open other files in Documents folder, and other nested folders, and, in fact the Excel document itself is nested within Documents - no problem editing and saving that. The only cloud storage that syncs with a folder on my Mac is iCloud, and that’s only because I need it for the Books app to sync my PDFs to my phone and iPod. When I work with Google or Microsoft, I use their web interface and explicitly upload/download the content I want. But I do know that Google likes to make everything cloud-centric, and there may be occasional glitches as data is synced on-demand from one location to another.įWIW, I don’t use any third-party cloud storage. It’s impossible for me to know without a lot more details. But if the Google software was downloading content in the background (possibly initiated by your previous open attempt), then the file might be present the next time.Īt least that’s a theory. So you double-click it and get an error (instead of a download followed by a document-open). The documents may be hosted on a Google cloud server, with only an alias (of some form) on your Mac. Especially if you are using Google’s docs (as you are). It’s impossible to know, but I know that Google and Chrome do do some weird things. Unfortunately, changing ownership of a file requires some mucking about from a command-line session. You can change permissions and remove ACLs from the GUI. If your owner-permission is not “Read & Write” or if the owner is a user other than yourself, or if there are ACLs blocking your access, that would easily be the cause of your problem. (The GUI doesn’t let you do uncommon things like make a file write-only but not readable). These correspond to Unix-standard permissions rw-, r- and -, respectively. On each line, you can set permissions to “Read & Write”, “Read only” or “No access”. You can add/remove them using the +/- buttons. If there are any additional lines, they correspond to access-control-lists (ACLs). The third line (three person-icons) is the permissions for “everyone” - that is, anybody who is not the owner and doesn’t belong to its group. The permissions here are typically “Read only” - so other members of the group can read it but not modify it. In my case, it’s the default “staff” group that macOS creates for all non-admin users. The next line (two person-icons) is the document’s group membership and group-permission. It should be “Read & Write”, unless you explicitly changed it to something else. It should be your short username and be indicated as “Me” if you are currently logged in as that user. The first line (icon of a person in a circle) represents the document’s owner and owner-permissions. What do the permissions show when you do a “Get Info”?Īt the bottom of the window, you should see something like this: I wonder if there’s a sound supposed to signal the process is over that we can’t hear because it’s changed the Output Sound preference. I also noticed that the Mac was virtually quiet after the upgrade, and when I checked Sound under System Preferences, Output was hooked to a headset where I couldn’t hear the sound. So it appears to be going not into turn-on mode but into something like sleep. Getting bored, I touched the Shift key to see if it was alive, and it opened immediately to my startup screen asking me to enter user name and password, which opened quickly. Then it sat there for a few minutes doing absolutely nothing I could see. About halfway through it presented me with the startup screen with the BigSur screen asking me for user name and password, then went through another series of progress bars. It ran through a series of progress bars followed by another restart and progress bar. The update took around half an hour on my 2018 MacMini running Big Sur.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |