Luminous Landscape Forum
Raw & Post Processing, Printing => Digital Image Processing => Topic started by: David Eichler on February 13, 2016, 02:45:58 pm
-
http://arstechnica.com/apple/2016/02/warning-bug-in-adobe-creative-cloud-deletes-mac-user-data-without-warning/
-
Stunning - thank you so much for the warning. Looks like another Adobe debacle following the Lightroom debacle with the Import module several months ago. I am given to understand that Adobe's sloppiness is causing Adobe customers to flee to alternatives such as Capture One in droves. This would just add to customer flight. I still like Lightroom very much and will give them a chance to get their act together, but as soon as I see a trend of technical sloppiness starting to affect the security of my computer environment they will lose me too - and I suspect many others. I wonder whether affected users could mount a class action in the circumstance of being able to demonstrate real harm of commercial consequence?
-
Stunning - thank you so much for the warning. Looks like another Adobe debacle following the Lightroom debacle with the Import module several months ago. I am given to understand that Adobe's sloppiness is causing Adobe customers to flee to alternatives such as Capture One in droves. This would just add to customer flight. I still like Lightroom very much and will give them a chance to get their act together, but as soon as I see a trend of technical sloppiness starting to affect the security of my computer environment they will lose me too - and I suspect many others. I wonder whether affected users could mount a class action in the circumstance of being able to demonstrate real harm of commercial consequence?
And what would you use as an alternative to Photoshop?
-
I hardly ever use Photoshop. Either Lightroom or Capture One are just about complete solutions for my image editing requirements. Almost the only thing for which I revert to Photoshop are Skew corrections because the Lightroom Lens Correction panel, while Upright is pretty good, just isn't quite there yet when such corrections are needed.
-
Is there any evidence that PC users are similarly affected by the latest PS CC upgrade?
Doug
-
I hardly ever use Photoshop. Either Lightroom or Capture One are just about complete solutions for my image editing requirements. Almost the only thing for which I revert to Photoshop are Skew corrections because the Lightroom Lens Correction panel, while Upright is pretty good, just isn't quite there yet when such corrections are needed.
You could switch over to the perpetual license version of LR and avoid automatic updates until all the smoke has cleared. That's been my option as I don't need the features in the CC version and as you don't use PS that much these days.
-
I see the article is referring to Creative Cloud v 3.5.0.206, my version is now at v 3.5.1.209 and not seeing any ill effects. iMac with latest software version. I have no idea of the application BackBlaze or what procedures it performs. . It begs the question what is causing the problem BackBlaze or Adobe CC?
-
You could switch over to the perpetual license version of LR and avoid automatic updates until all the smoke has cleared. That's been my option as I don't need the features in the CC version and as you don't use PS that much these days.
There are useful features in the CC version; but you're right - the perpetual license version is an option. One would hope the new features get ported into it with its own cyclical updates - and that those updates don't suffer from sloppy QC/QA. There should not be a situation where smoke needs to clear. This is a fairly new thing with Adobe.
-
I see the article is referring to Creative Cloud v 3.5.0.206, my version is now at v 3.5.1.209 and not seeing any ill effects. iMac with latest software version. I have no idea of the application BackBlaze or what procedures it performs. . It begs the question what is causing the problem BackBlaze or Adobe CC?
The Ars Technica article seemed to indicate that the problem is not specific to BackBlaze and that Adobe has discontinued this update.
-
Is there any evidence that PC users are similarly affected by the latest PS CC upgrade?
Doug
The article says it's OSX-related.
-
The article says it's OSX-related.
Its strange I see no chatter about this on the Adobe Lightroom User to User forum.
-
Well, if it's very recent (article is dated Feb 12), happening silently in the background to hidden files in the system root structure and people haven't noticed computer dysfunctions yet, there would be no chatter.
-
Stunning - thank you so much for the warning. Looks like another Adobe debacle following the Lightroom debacle with the Import module several months ago.
Different IMHO but both not good signs. The Import debacle was pretty bad because the beta testers told Adobe long before release this was a really bad move. The people running the team didn't listen as they should have. This new issue is a nasty engineering bug that I can't imagine anyone inside Adobe had a clue about. Neither are acceptable but one's far worse as far as I'm concerned.
-
I have no idea of the application BackBlaze or what procedures it performs. It begs the question what is causing the problem BackBlaze or Adobe CC?
Cloud backup product that Adobe's installer deleted for whatever reason, some necessary files on the host computer. BackBlaze is a competitor to CrashPlan which is what I use (so I'm thankful I wasn't affected).
-
what is causing the problem BackBlaze or Adobe CC?
According to TidBits (http://tidbits.com/article/16259), it's the Adobe CC installer, which deletes data from the first (alphabetically) hidden folder. BackBlaze creates a hidden folder called .bzvol, which is the one that gets tampered with.
Edit: see also BackBlaze's response, here (https://backblaze.zendesk.com/entries/98786348).
Jeremy
-
Is there any evidence that PC users are similarly affected by the latest PS CC upgrade?
Doug
No problem here(Windows 10 x64).
-
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.
-
Nice, thanks. Now I shall wait several weeks for the early adopters to determine whether more needs to be fixed.
-
Nice, thanks. Now I shall wait several weeks for the early adopters to determine whether more needs to be fixed.
There's always seems to be something to be fixed in Adobe apps, it's just a matter of the criticality of the bug.
Everything with this CC app update seems to be working properly for me.
-
The article says it's OSX-related.
So is it Adobe's fault or Apple's?
-
So is it Adobe's fault or Apple's?
Adobe's. And it's been fixed (so hopefully all can move on). It ONLY affected customers of a single product, that's no excuse for this sloppiness. But I suppose one could suggest none of the Mac beta testers or Adobe Q&E testers had the product and missed this Adobe bug which has been fixed.
-
It ONLY affected customers of a single product, that's no excuse for this sloppiness.
It affected BackBlaze users and we learned about it because they were immediately affected. We don't know what else might be affected. This was a place few of us touch in our Mac file system but it's no guarantee that other apps didn't have info there.
-
We don't know what else might be affected. This was a place few of us touch in our Mac file system but it's no guarantee that other apps didn't have info there.
Well if and when you find out what else was affected, let us know. Going to be somewhat difficult as that installer is now dead and gone. I don't know that there's an ounce of evidence anything else was affected. Again, the blame should fall onto Adobe, it was a bug. Not that Adobe has never produced bugs let alone other companies. Today, this entire discussion is kind of moot unless folks want to hash more criticism on Adobe which these days is so fashionable.
-
Hmmm. Adobe CC is still showing 3.5.0.206 as the update, not 209. Tried quitting and relaunching and still the same.
-
Hmmm. Adobe CC is still showing 3.5.0.206 as the update, not 209. Tried quitting and relaunching and still the same.
Log out then back in again or log out of your Adobe CC account then back in again.
-
Another question. What, if anything, do I lose by not updating the CC app? The release notes only seem to refer to bug fixes, not to other changes. Does not updating CC impair my ability to update the individual CC apps?
-
Another question. What, if anything, do I lose by not updating the CC app? The release notes only seem to refer to bug fixes, not to other changes. Does not updating CC impair my ability to update the individual CC apps?
You don't have to update. Each app should individually indicate if it needs to be updated so you can if you wish, update just those. But if you're worried about the update to Photoshop CC, what makes you think there are zero issues or will never be issues updating say InDesign?
Backup, have the ability to go back a version, just in case, you'll be fine. But stuff happens.
-
You don't have to update. Each app should individually indicate if it needs to be updated so you can if you wish, update just those. But if you're worried about the update to Photoshop CC, what makes you think there are zero issues or will never be issues updating say InDesign?
Backup, have the ability to go back a version, just in case, you'll be fine. But stuff happens.
Thanks. I realize that. I just tend to wait to do updates, in part for this very reason, but also if a particular update doesn't really do anything that I really need at the moment. Not really sure what the CC updates actually do, so how long can I wait to update these? With the individual CC apps, we know what the new features are.
-
Not really sure what the CC updates actually do, so how long can I wait to update these?
Adobe specifies what the updates provide. And yes, you can wait as long as you want! Just don't select Update.
-
Adobe specifies what the updates provide.
Oh. I see. With earlier updates there were functional improvements. With the last four updates, however, the only changes have been bug fixes. That doesn't seem too promising.
-
Installation of 3.5.0.209 failed. Error code 1003. "Get help" link says "uninstall and reinstall" the CC app. Tried running the CC uninstaller, the message is: "Couldn't uninstall CC for desktop. You still have CC apps installed on your computer that require it."
WTH!?
-
Well if and when you find out what else was affected, let us know. Going to be somewhat difficult as that installer is now dead and gone. I don't know that there's an ounce of evidence anything else was affected.
Andrew, I have no interest in bashing Adobe or belaboring the issue. I just want to point out that we're not completely out of the woods. It may well be only BackBlaze users are affected but no one knows yet. I don't look at the root directory on my Mac and you probably don't either.
Upon sign in, a script activated by Creative Cloud deletes the contents in the alphabetically first folder in a Mac's root directory.
Updating the CC app won't bring back any files the old CC app deleted. Most of us will simply find out the hard way if something other than BackBlaze was negatively impacted. It may be unlikely but so was a meteorite wiping out the dinosaurs. With luck a backup program might be able to restore lost files.
'nuff said
-
I just want to point out that we're not completely out of the woods.
I think we are. At least in terms of the older installer which did that nasty deletion of BackBlaze files. Could any future installer, Adobe's or anyone else's do something nasty like this? Of course. But in terms of this older, removed installer, it's a moot topic.
Lastly, anyone on a Mac running Time Machine could probably reconstruct the deleted file, or from a backup. Because again, crap happens!
Again, that's not an excuse for this Adobe bug. But it seems like time to move on; you can't download the buggy installer.
'nuff said'
-
http://www.cnet.com/how-to/how-to-access-hidden-files-to-restore-in-time-machine/
How to access hidden files to restore in Time Machine
-
According to the original article referenced here:
This caused a lot of our customers to freak out," Backblaze Marketing Manager Yev Pusin wrote in an e-mail. "The reason we saw a huge uptick from our customers is because Backblaze's .bzvol is higher up the alphabet. We tested it again by creating a hidden file with an '.a' name, and the files inside were removed as well.
I did access all invisible files on my Mac. Looked at root level sorting alphabetically I see .Adobe as the first! Kind of makes sense that Adobe's installer would try to delete it. Not sure why .bzvol was affected, it should fall below .Adobe. Anyway, using Time Machine, I went back well before this update of CC, still see .Adobe folder with two items. So I don't think I have anything to worry about (nor did I ever use Blackblaze). Anyway, one can backup such files from TM once they have ability to see the invisible files.
-
And yes, you can wait as long as you want! Just don't select Update.
That may not be entirely accurate.
I've watched this debacle from a distance and 'unloaded' ACC as soon as the bug was reported. Just did a 'Get Info' on the ACC file to find that it was updated yesterday at 09:01 (how cute : Valentine's Day!) Version 3.5.1.209.
Now I've deliberately NOT launched ACC so it must have been either Lr or Ps that 'made a call home' and that upgrade was definitely a BTS update. Have Adobe found a new way to force upgrade known 'problematic' installers or is it a consequence of ticking Preferences > Always keep CC desktop up to date ?
-
That may not be entirely accurate.
Well CC has never updated anything without my permission. On the Mac. In fact I don't have the CC menu app running although I am still notified of an update. But, nothing updates unless I tell the app to do so. If anything, folks complain, justifiably so, that they don't get timely update notifications unless they log into and out of the CC app or restart.
AFAIK, there's no mechanism that forces an update. I've always had to give permission and further, you have to type in your password on Mac to install all apps!
-
Well CC has never updated anything without my permission. On the Mac. In fact I don't have the CC menu app running although I am still notified of an update. But, nothing updates unless I tell the app to do so.
And that's exactly my setup and what happened to me, pre-bug update ( ACC notification and request permission).
So it's pretty surprising unless there was some BTS wizardry.
-
...Just did a 'Get Info' on the ACC file to find that it was updated yesterday at 09:01 ... Version 3.5.1.209...
Lucky you. I (deliberately) tried to update and the update failed (see post #30).
-
I've watched this debacle from a distance and 'unloaded' ACC as soon as the bug was reported. Just did a 'Get Info' on the ACC file to find that it was updated yesterday at 09:01 (how cute : Valentine's Day!) Version 3.5.1.209.
Date updated isn't necessarily date installed. It's possible you did get an update without your permission, especially if you've set your Mac to allow this but as I said, I've never had Adobe update anything without my permission and/or by entering my admin Password.
-
Installation of 3.5.0.209 failed. Error code 1003. "Get help" link says "uninstall and reinstall" the CC app. Tried running the CC uninstaller, the message is: "Couldn't uninstall CC for desktop. You still have CC apps installed on your computer that require it."
Try this (I had the same experience and following the instructions in these notes fixed ACC for me):
---------
Re: Creative Cloud crashes at start up
Follow below steps :
Step 1)
Click on the Finder and look for the options listed next to Apple Icon located at the top left corner of the Desktop screen and click on "Go" menu button and select "Utilities" option.
(Applications>Utiliites)
Locate Adobe Creative Cloud and Adobe Application Manager folder under Utilities window and trash both folders.
Step 2)
Trash Adobe Creative Cloud folder from Applications as well.
Step 3)
1) Right click on Finder icon and select "Go-ToFolder " option.
2) You will get a text box, type-in below command and then hit ’Return’ key.( Do not miss ~ symbol)
~/library
3)Then navigate to Application Support>Adobe.
Open Adobe folder and trash folders named AAMUpdater and OOBE.
Step 4)
1) Right click on Finder icon and select "Go-To" Folder option.
2) You will get a text box, type-in below command and then hit ’Return’ key.
/library
3)Then navigate to Application Support>Adobe.
Open Adobe folder and trash folders named AAMUpdater ,Adobe Application Manager and OOBE.
Step 5)
Click on the below link and download & run Adobe Cleaner tool :
Select the option "Adobe Application Manager for Mac OS X 10.6" and then click on "Clean up Selected" .
http://download.macromedia.com/SupportTools/Cleaner/mac/AdobeCreativeCloudCleanerTool.dmg
Step 6 )
Click on the below link and download Adobe Application Manager and install the same :
http://download.adobe.com/pub/adobe/creativesuite/cc/mac/ApplicationManager9.0_all.dmg
Once the installation process is completed, installation box will disappear, then open Application folder and locate Adobe Application manager launch icon , double click on it and update .
Once the Adobe Application Manager update is completed, it should launch Adobe Creative Cloud.
___________
-
You've just convinced me not to go any where near any of this upgrading until we are dead-certain they have a version that works properly. Life's too short for this kind of crap.
-
... Creative Cloud crashes at start up...
Ann, thanks for the tips an the effort to help. Just to clarify, my CC app did not crash at start up; it worked, telling me there is an update, just refused to install that update.
In the meantime, I resolved the issue with the tried and true Bill Gates' advice: restart the computer. Go figure.
-
Glad re-booting worked for you.
In my cases, shutting-down+reboot did nothing but following those notes and clearing out those folders (particularly the OOBE stuff) resulted in a perfect clean-up.
I was then able to install ACC 209 and have seen no further problems with OSX or with any of my CC apps (or any of my other programs for that matter).
-
In the meantime, I resolved the issue with the tried and true Bill Gates' advice: restart the computer. Go figure.
Hi Slobodan,
I had that happening to me on an early morning plane-ride from Amsterdam to our London headquarters. After a considerable delay, the captain informed us that there was a problem with one of the auxiliary Autopilot systems, and because it was quite foggy at Heathrow airport, they wanted to make sure and have all 3 (i.e. 2 backup) systems functioning properly before taking-off.
After some more delay, the captain said that they had a phone call with Boeing in Seattle, who advised to shut down all power in the airplane, and hope that all relais switches would reset as intended upon restart ... Lights went out, airco shut off, systems rebooted, and off we went.
Cheers,
Bart
-
Hey Bart,
Now that we are exchanging "war stories" about restarting, here is mine:
Lufthansa flight from Barcelona to Moscow, via Munich. As we were gaining altitude departing Munich, a huge boom was heard and felt. The plane started to try to regain balance and direction. We asked the crew why isn't the captain telling us what's going on. Their response: "He obviously has better things to do." After about 10 terribly long minutes, with people crying etc., the captain finally told us we lost one engine (duh!), but not to worry, they are trained to fly with only one left. Right, I was thinking, but what happens if the second fails? Anyway, we returned safely to Munich, I gulped a huge glass of whisky, and an hour or so later, we continued on another plane to Moscow.
But that is just an intro into the rebooting story I promised. Upon landing in Moscow, I was telling this story to my friends, when one of them said with a typical Russian laconic attitude: "That's nothing." He proceeded to tell his story: flying on a Russian Illyshin plane, not otherwise known for a great safety record, one of the engines (of four) also stopped. Then another. I don't remember if the third failed too, but long story short, the captain announced what he is going to do: to shut down all four engines and then... restart them. And he did shut it down. My friend remembered that terribly long moment when there was an absolute silence in the air, somewhere above Siberia, and then that well-known sound like when you try to restart a stalled car engine: vrrrr...vrrrr... vrrrr. Nothing. Vrrrr...vrrrr... vrrr.. vroooommm, finally! All engines came roaring back and they landed safely. Ha!
-
Hey Bart,
Now that we are exchanging "war stories" about restarting, here is mine:[...]
LOL, although you didn't at that time, I'm sure.
The benefit of Siberia is that there will probably little collateral damage if all attempts fail (and pilots are trained for emergency landings, unfortunately the plane structure may not like it), the problem with London is that it's rather busy with every 45 seconds a plane making an approach for landing, that will burn fuel fast if you're put in a holding pattern waiting another turn trying to find the runway in the fog.
Well, there you go, if everything else fails, a cold reboot may get you going again ...
Cheers,
Bart
-
LOL, although you didn't at that time, I'm sure.
The benefit of Siberia is that there will probably little collateral damage if all attempts fail (and pilots are trained for emergency landings, unfortunately the plane structure may not like it), the problem with London is that it's rather busy with every 45 seconds a plane making an approach for landing, that will burn fuel fast if you're put in a holding pattern waiting another turn trying to find the runway in the fog.
Well, there you go, if everything else fails, a cold reboot may get you going again ...
Cheers,
Bart
It's been rumioured that there was a third Wright brother, he's still waiting to land at Heathrow... ;D
-
It's been rumoured that there was a third Wright brother, he's still waiting to land at Heathrow... ;D
LOL, also no autopilot and London fog, no doubt.
Cheers,
Bart