A new version of Adobe CC has been released to fix this problem.
Version 3.5.1.209 released on 2/14/2016
Fixed an issue in the Creative Cloud for desktop app for Mac where in some scenarios the application may incorrectly remove files with user writeable permissions from the system root directory.
- Don
I spent a lot of time investigating this one, it is a nasty "feature" no doubt, and shame on Adobe, but it is being overblown. It only applied to alphabetically named hidden files in the root directory that are granted user access permissions.
In UNIX hidden files use .file_names so IF the user was storing their data on the Mac in the / directory using the dot naming convention for the files then they would have lost the highest ordered dot-named file when the buggy CC Adobe update was installed and they logged in to the CC.
The bug affected the Backblaze company's software, because they place a user .config file of some sort under root, that usually ended up at the top of the file order.
I am not making excuses for Adobe, shame on them for the bug, but put in perspective, the bug only affected a subset of Mac users.
Having said that, I have learned my lesson, and will henceforth wait on invoking any CC updates until the dust has cleared. Having to wait does suck he joy out of the CC instant update feature but not nearly as much as having to clean up the mess created by a buggy update.
I sent feedback to Adobe about the Creative Cloud (CC) updates yesterday.
This is what I sent them:
************** Begin Adobe Feedback ****************
The MacOS update bug matter is closed for me now but it was a nasty scare, took a lot of my time, and was not much appreciated. This is twice now that recent updates from Adobe have had me spending time fixing the mess they created. That is not a good record. And that double clutch update with the new importer then reverting to the old importer, was not impressive.
So I am hoping Adobe can improve on this record VERY SOON. I like the CC a lot. The CC is supposed to provide instant updates, which I like, but having to spend my time mopping up afterword takes away the joy. So while Adobe issues created by Adobe updates are annoying but tolerable, I am NOT going to tolerate system issues created by Adobe updates. Just saying. After all, there is a lot of competition out there. I added .AADOBE_DELETEME1,2 files to /root just in case Adobe doesnt fix the MacOS problem in the next update. If that is the case I will know, and it will be adios Adobe. I really do not want that to happen because I like the CC but enough is enough.
Sorry for the rant.
****************** End Adobe Feedback ****************
Background, Creative Cloud MacOS update Issue:
http://arstechnica.com/apple/2016/02/warning-bug-in-adobe-creative-cloud-deletes-mac-user-data-without-warning/This is the reply I received the next day.
************** Begin Adobe Reply ****************
Sandeep Singh (Adobe)
Feb 18, 20:50
Hi Jerry,
Please contact our support team at 800-833-6687 MondayFriday, 5am7pm PT
Regards,
Sandeep Singh
Global Consumer Customer Success (Tier 3)
Adobe.
************** End Adobe Reply ****************
JD750 wrote:
I sent feedback to Adobe about the Creative Cloud (CC) updates yesterday.
This is what I sent them:
************** Begin Adobe Feedback ****************
The MacOS update bug matter is closed for me now but it was a nasty scare, took a lot of my time, and was not much appreciated. This is twice now that recent updates from Adobe have had me spending time fixing the mess they created. That is not a good record. And that double clutch update with the new importer then reverting to the old importer, was not impressive.
So I am hoping Adobe can improve on this record VERY SOON. I like the CC a lot. The CC is supposed to provide instant updates, which I like, but having to spend my time mopping up afterword takes away the joy. So while Adobe issues created by Adobe updates are annoying but tolerable, I am NOT going to tolerate system issues created by Adobe updates. Just saying. After all, there is a lot of competition out there. I added .AADOBE_DELETEME1,2 files to /root just in case Adobe doesnt fix the MacOS problem in the next update. If that is the case I will know, and it will be adios Adobe. I really do not want that to happen because I like the CC but enough is enough.
Sorry for the rant.
****************** End Adobe Feedback ****************
Background, Creative Cloud MacOS update Issue:
http://arstechnica.com/apple/2016/02/warning-bug-in-adobe-creative-cloud-deletes-mac-user-data-without-warning/This is the reply I received the next day.
************** Begin Adobe Reply ****************
Sandeep Singh (Adobe)
Feb 18, 20:50
Hi Jerry,
Please contact our support team at 800-833-6687 MondayFriday, 5am7pm PT
Regards,
Sandeep Singh
Global Consumer Customer Success (Tier 3)
Adobe.
************** End Adobe Reply ****************
I sent feedback to Adobe about the Creative Cloud ... (
show quote)
I'm Adobe. Trust me!
I Don't trust cloud based computing. Adobe has often disregarded the welfare of users.
If you want to reply, then
register here. Registration is free and your account is created instantly, so you can post right away.