![]() If I were smarter and better versed in the ways of the Terminal, I wouldn’t have to look this sort of stuff up when I needed to do it. But as fun as that sounds, I opted for the lazy route: creating a symlink called Dropbox that pointed to Dropbox (Personal) so all my stuff would just work again. Now, when I first linked my two Dropbox accounts, I could have gone through all my Keyboard Maestro macros and shell scripts and done some find & replace work to make everything work again. ![]() Once you install the Dropbox app, the computer belongs to them, you’re just allowed to use it. Spaces? Parentheses? It’s like they’re trying to break all my scripts and customizations.Īnd before you ask, no, you can’t just rename the folder back to Dropbox. Which…seems silly to me, but okay, I guess.Īside from being an unattractive folder name, Dropbox (Personal) is pretty terrible for automation and general usability. When you do that, your folder previously-named Dropbox is renamed to Dropbox (Personal) and your business account is named Your Company Dropbox. I’m writing it so the next time I’m setting up a new Mac, I’ll know exactly where to find the solution to one of Dropbox’s most puzzling idiosyncrasies.ĭropbox users, like myself, who have both a personal Dropbox account and a business account, have the ability to link those two accounts and sync both folders to a single computer. In the other, the user had restored the system from Time Machine, and then, due to problems and with the help of Apple support, installed 10.15.1 over that system via recovery mode.I’ll be honest, this post is more for me than it is for you. ![]() ![]() In one case, the user had installed 10.15.1 first, then restored data onto it from Time Machine. There’s one thing the two affected systems had in common: both had installed 10.15.1 via recovery mode, and both had done a restore from Time Machine. I’m guessing this is an obscure Catalina bug, but that’s still speculation. That’s an excellent question! I’m still not sure. So, if the above instructions don’t work, these are two verified methods that should work. In the other, SIP was disabled, the tmp folder was fixed while booted normally, and then SIP was re-enabled. In one case, the system was wiped and restored from Time Machine. In the two cases we observed, the fix was more extreme. You must make the necessary changes to the one on the Data volume. If you specify /private/tmp, that refers to a folder on the read-only system volume, which is (of course) read-only. You do have to be careful to identify the correct /private/tmp, however, as there are two. While in recovery mode, you should be able to freely delete items with a restricted flag, and you will have root permissions by default. (Note that you will need to replace “Macintosh HD” with the name of your hard drive.) In theory, one should be able to fix this by rebooting in recovery mode, opening the Terminal, and executing the following commands: cd /Volumes/"Macintosh HD - Data"/private Which means I’ve been unable to duplicate the exact conditions, and so I cannot be 100% sure of the ideal fix. Testing has been difficult, as it appears to be impossible to add a restricted flag to the symlink in recovery mode. This apparently prevents the Malwarebytes installer from working, and I’d guess (although I haven’t been able to test) that this means any installer. ![]() □ % ls -alO 1 root wheel restricted,hidden 11 tmp -> private/tmp And, worse, that symlink was marked with a restricted flag, meaning that it was protected against being modified by System Integrity Protection. While investigating, both I and a Malwarebytes support engineer both independently found the same thing on these two systems: the /private/tmp folder had been replaced with a recursive symlink, pointing back to itself. Two people were having a problem installing Malwarebytes, and an error like the following was found in the install.log on both systems: 13:14:19-06 some-imac Installer: install:didFailWithError:Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory" UserInfo= I’ve been tracking a strange issue on macOS 10.15.1 since yesterday. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |