P: Most functions in Edit, Image, Layer, Select and Filter grayed out for image opened from LrC

[KR Seals]

Win 10 1803, LR  8.0, I7 8700k, 64GB ram Control keys inop. Most functions in Edit, Image, Layer, Select anf Filter grayed out. Images opened directly into PS all ok. Reset prefs no help.

[defaultmsvffwly4u5u]

Photoshop CC 2019 - and I'm sorry/not sorry to say ctrl+J doesn't work, quick selection tool doesn't work, cntrl+d doesn't work, ctrl+0 doesn't work and that's just for starters: get it together Adobe

[FeedbackCommunityMember]

installed version 2019 and the menu structure gives 80% of the functions disabled. What do I do?

[geoffdeck]

After the latest update, the adjustment layers no longer work. When any adjust layer button is pressed, all it does is bring up the properties dialog. I have had to switch back to last years PS in order to use adjustment layers.

[alex12353456789]

In Lightroom I select a photo and click "Edit in Photoshop CC 2019". After that I create layers in Photoshop and work with them, but I cannot merge layers. Ctrl+Shift+E or Ctrl+Shift+Alt+E does not work, right-click menu is inactive too. Drop-down lists menu "Layer", "Select", "Image" and "Filter" are not active.
My OS: Win10 Pro 1809
Solved by deleting CC2019 (ver 20.0.1) and installing CC2018 (ver 19.1.7). Photoshop CC2018 is stable.

[Samoreen]

Jeffrey,

Very frankly, more than 3 weeks needed to fix this ? I can't believe it. And once again, how is it possible that such an obvious bug could go undetected on its way to an official release. As the product manager, you should now be aware that something is wrong in your testing procedures. Since a long time. There are so many bugs that are so obvious that they should never hit the users if decent testing was done. I suspect that the only testing that is done is done by the developers themselves, which is the worst approach to testing that I can imagine.

[geoffdeck]

I mean maybe we as a community need to find a way to calculate loss of production hours, find a lawyer, and do a class action lawsuit. While we might get Jack shit out of the deal, maybe then Adobe will take testing more seriously since there would be a clear show if consequences. I mean just between Photoshop and LR alone, there are probably enough of these instances to make some sort of case.

[TheDigitalDog]

You clearly haven't read the EULA you agreed upon to use this product; do so! And perhaps many others.
What software products do you use ( you don't own of course) that is 100% bug free?
Oh, you use LR as a part of your profession?
Class action; Ridiculous!

[ivframes]

Sometimes when I select JPG images in LR Classic and import them in the PS, menus and commands do not work.

Steps to reproduce:

1. Select JPG images in LRC
2. Right click on them choosing "Edit in PS CC2019"
3. LRC asking whether to use the adjustments - choose YES
4. PS freshly starting.
5. Menus are blank and keyboard shortcuts like CTRL M do not work at all

As shown in the gif (it's animated gif, please click on the image if it's not moving for you). Notice blank menus.

[visler]

I have some problem alike this. When i open a photo via lightroom, I cant duplicate the layers in photoshop cc, not using ctrl - j or the menus (all is greyed out).

If i open the image via camera raw in PS , all is ok.

Windows (10 home)  and photoshop is both installed yesterday...

[parkylondon]

Okay Adobe, the problem has been identified, it is repeatable, demonstrable and we're now wondering when you're going to, you know, FIX IT?

Continued radio silence does NOT help your fan base defend you, you know? 

[TheDigitalDog]

Of course it will be fixed. Patients grasshopper.

[parkylondon]

Three weeks without an update? My patience is running a bit thin

[TheDigitalDog]

It's running thin because you have really no idea how software development function.
Bug has to be internally verified on different hardware and differing OS versions. Bug has to be fixed and testing the same way. Beta has to be released for the same testing. Installer has to be updated as do web sites. Documentation has to be updated. One bug alone is rarely updated too. As an actual Adobe software developer and alpha/beta for them, since 1992, I actually understand how this work takes place. And now you kind of do. Relax! When it's done, it's done.
Then there will be other bugs in every software program and the bitching and moaning can start all over again. ;-(

[dougsooley]

I just opened an image in the newly update PSCC and there is NO OPTION to duplicate the layer?? It opned from LRCC as a locked background. I unlocked it and CTL-J does not work, Duplicate option is greyed out on both a right click and from the layer dropdown?? The layer says it is Layer 0 and there is NO OPTION to duplicate. WTF???

[jimf89590773]

OK, then how about some release notes that document the problems found so far and workarounds if available?  I get that this isn't a showstopper, but proactively telling your install base what they can expect would go a long way.

[TheDigitalDog]

Release notes are provided with an actual release. 
The temporary fix is found here and elsewhere on the web in various forums. That's one reason Adobe and other's host such forums. 

[geoffdeck]

Actually, not really. EULAs do not protect a company from everything, much like how wavers don't really protect doctors. Such suits are currently open against both Symantec and Oracle. Additionally, there are bugs and continuous bugs, and just plain negligence. I do work in the development world, I work with testers on a daily basis, software architects, et cetera, and when this many bugs exist and continue to get past testing and dev, people are reprimanded or fired.

And yes, I use LR, as do a large portion of photographers, Are you saying its not professional software? Care to keep making brown nosing Adobe arguments?

[TheDigitalDog]

The EULA which you still haven't read does protect Adobe from the so called and absolutely silly idea of a class action but by all means, waste your time venting and going down that rabbit hole, while the fix is already known and a software update will come soon. 

That you use LR to do a larger portion of photography doesn't answer the question, even if you are not a hobbyist, as I suspect you are, you don't have a leg to stand on with this bug legally and a quick but through read of the contract you agreed to, just to access the software, would show. I'm not saying it's not professional software whatsoever, it is, I'm saying you're probably not a professional user of that software but that's moot if and when you read the contract with Adobe you agreed upon to then launch the software. 
Have you not figured out how to bypass this bug? A bug that will, in time, be fixed?
Again, do tell us what software products you use, professionally or as a hobby that is 100% bug free. Of course, you cannot. 
Enough said. 

[jimf89590773]

Which then forces Adobe's users to hunt down every bug and new "feature" as they encounter them.  Any wonder that many feel like they're your beta testers?

BTW, I know what RN's are.  I've helped write them.  They're a list of non-compliant functions you know of from testing (along with changed behaviors).  What I'm proposing is that rather than a static document, a live list of what has been found post release be published.  Surely that list is being kept internally (I would hope).  The volume of posts on this topic alone should be informing someone that a better way to communicate that information needs to be found.

Think of it this way; How would you make an informed decision to upgrade if the only way to know, is to scan multiple forum posts which may or may not be labeled with the release ID and which may or may not be user error?

[TheDigitalDog]

I am a beta (and alpha) tester <g>
I've written Release Notes too. For an Adobe PS Automate plug-in. 

I make informed decisions by informing myself and that means research. Adobe in fact provides numerous methods of informing users; blogs (stay tuned.... can't say more but keep an eye on em), on their actual web site, in their UtoU forums and within their own software.

[geoffdeck]

I mean you seem like someone who just likes to hear themselves talk but you really have a vague understanding of U.S. law when it comes to software. Also, no I am a professional based on the salary paid to do the work I do. Also, just because you request something doesn't mean I have to give it to you. You really just seem like yet another internet troll. And if you don't mean to be, I suggest altering your language. 

Also, you speak upon Adobe's behalf out of faith? Because from what I see you have no affiliation with them. So you speak as if you know but have no real connection? Kind of confused on your angle of discussion here. 

And no, nothing is bug free, but at the same point, I don't have recurring issues that Adobe seems to be having with products like Word, Capture One, Davinci Resolve, Solid Works, Blender, Excel, Madcap Flare, et ceteral, all which I use on an almost daily basis. But please, continue to berate because you really don't know any better.
Enough said. 

[TheDigitalDog]

>>I mean you seem like someone who just likes to hear themselves talk but you really have a vague understanding of U.S. law when it comes to software.
The facts bud:
https://labs.adobe.com/technologies/eula/lightroom.html
8. LIMITATION OF LIABILITY. EXCEPT FOR THE EXCLUSIVE REMEDY SET FORTH ABOVE AND AS OTHERWISE PROVIDED IN SECTION 14, IN NO EVENT WILL ADOBE OR ITS AFFILIATES OR SUPPLIERS BE LIABLE TO YOU FOR ANY LOSS, DAMAGES, CLAIMS OR COSTS WHATSOEVER INCLUDING ANY CONSEQUENTIAL, INDIRECT OR INCIDENTAL DAMAGES, ANY LOST PROFITS OR LOST SAVINGS, ANY DAMAGES RESULTING FROM BUSINESS INTERRUPTION, PERSONAL INJURY OR FAILURE TO MEET ANY DUTY OF CARE, OR CLAIMS BY A THIRD PARTY, EVEN IF AN ADOBE REPRESENTATIVE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH LOSS, DAMAGES, CLAIMS OR COSTS. THE FOREGOING LIMITATIONS AND EXCLUSIONS APPLY TO THE EXTENT PERMITTED BY APPLICABLE LAW IN YOUR JURISDICTION. ADOBE'S AGGREGATE LIABILITY AND THAT OF ITS AFFILIATES AND SUPPLIERS UNDER OR IN CONNECTION WITH THIS AGREEMENT WILL BE LIMITED TO THE AMOUNT PAID FOR THE SOFTWARE, IF ANY. THIS LIMITATION WILL APPLY EVEN IN THE EVENT OF A FUNDAMENTAL OR MATERIAL BREACH OR A BREACH OF THE FUNDAMENTAL OR MATERIAL TERMS OF THIS AGREEMENT. Nothing contained in this agreement limits Adobe's liability to you in the event of death or personal injury resulting from Adobe's negligence or for the tort of deceit (fraud). Adobe is acting on behalf of its affiliates and suppliers for the purpose of disclaiming, excluding and limiting obligations, warranties and liability, but in no other respects and for no other purpose. For further information, please see the jurisdiction specific information at the end of this agreement, if any, or contact the Adobe Customer Support Department.

[TheDigitalDog]

>> Because from what I see you have no affiliation with them.

You're not looking, and thus not seeing. 

Geoff Decker:
>>I mean maybe we as a community need to find a way to calculate loss of production hours, find a lawyer, and do a class action lawsuit.<<

Class action; Ridiculous!

[jimf89590773]

Thanks for reinforcing my critique.  I shouldn't have to look all over the Adobe universe to find that information.  It's one thing to post links all over that point back to one source of truth, and it's another to have that information spread all over in bits and pieces like some easter egg hunt.  The winner gets an informed decision on to install an upgrade.  The losers spend hours searching, well, everywhere and potentially getting bad advice in the process.

[defaultmsvffwly4u5u]

Let's cut the name calling and encourage Adobe to become a quality, reliable, supplier of imaging software which works out of the box hassle free.  A change of internal culture is what is needed and wanted.