Skip to main content
Adobe Photoshop Family

12 Messages

 • 

1.5K Points

Wed, Nov 14, 2018 4:35 PM

Solved

Photoshop 20.0.1: Most functions in Edit, Image, Layer, Select and Filter grayed out for image opened from Lightroom Classic

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.

Responses

4 Messages

 • 

144 Points

2 years ago

This reply was created from a merged topic originally titled cannot merge layers Photoshop 20.0.1.

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.






120 Messages

 • 

1.9K Points

2 years ago

This reply was created from a merged topic originally titled Sometimes menus/commands are unavailable.

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.




10 Messages

 • 

284 Points

2 years ago

This reply was created from a merged topic originally titled Commands disabled in Photoshop.

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...

Note: This conversation was created from a reply on: Photoshop: CTRL+J no longer duplicates a layer. Setting CTRL+J as keyboard shortc....

41 Messages

 • 

948 Points

2 years ago

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? 


1.8K Messages

 • 

21.6K Points

2 years ago

Of course it will be fixed. Patients grasshopper.

Author “Color Management for Photographers"

41 Messages

 • 

948 Points

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

1.8K Messages

 • 

21.6K Points

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. ;-(

Author “Color Management for Photographers"

5 Messages

 • 

144 Points

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.

1.8K Messages

 • 

21.6K Points

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. 

Author “Color Management for Photographers"

5 Messages

 • 

144 Points

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?

1.8K Messages

 • 

21.6K Points

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.

Author “Color Management for Photographers"

5 Messages

 • 

144 Points

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.

Adobe Administrator

 • 

15.4K Messages

 • 

291.4K Points

Sr. Product Manager, Adobe Digital Imaging

41 Messages

 • 

948 Points

Thank you for the links but knowing a bit more about when this issue is going to be sorted would have been much more helpful. Still, you're the first Adobe person to post here in quite a while, so thanks for that too.

Adobe Administrator

 • 

15.4K Messages

 • 

291.4K Points

Sorry, I've been out for a while with pneumonia. I can't give any exact details but it will be fixed in the next update.

Sr. Product Manager, Adobe Digital Imaging

41 Messages

 • 

948 Points

Sorry to hear that Jeffrey, I hope you are fully fit now. 

I guess the radio silence meant no-one else was available to provide information, commentary or even to shine a wee bit of light on this issue?

21 Messages

 • 

332 Points

2 years ago

This reply was created from a merged topic originally titled Cannot duplicate layer in new CC update.

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???

2 Messages

 • 

70 Points

Disable the start up page in photoshop & re open /  or Open photoshop before opening lightroom & then editing in photoshop

8 Messages

 • 

286 Points

2 years ago

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.

443 Messages

 • 

6.6K Points

2 years ago

The answer to this problem is simple: go to Preferences/General in Photoshop and tick the second option down - disable home screen. Problem solved! It's a new feature that has been added without realising it affected LR, but it is quite unnecessary so tick the box and it goes away and LR and PS work as usual.

Bob Frost

8 Messages

 • 

286 Points

Good solution, thank you Robert for sharing this tip.  I question Adobe's culture of not being forthcoming about the operational procedures of these programs.  And don't get me started on the hassle of Rush being 'not compatible' when attempting to install via Creative Cloud and the hoops to jump through to diagnose and resolve this issue [hint: required win10 update to a certain version].

5 Messages

 • 

122 Points

Awesome! Thank you, Robert, you are wonderful :) This works!! 
Yi-Chen

1.8K Messages

 • 

21.6K Points

2 years ago

It is very simple. But some people would rather vent then fix the temporary problem. 

Author “Color Management for Photographers"

76 Messages

 • 

1.2K Points

Man, you really are a child, aren't you? Sincerely, I hope you find some help with your ego problem. If you were my employee, I wouldn't want you posting on my company's forum the presented decorum. If you really are an Adobe employee, then fully agree with Jon and an internal culture change is needed.

1.8K Messages

 • 

21.6K Points

And the venting continues. 
I'm sorry the facts continue to ruin your life Geoff. 

Author “Color Management for Photographers"

76 Messages

 • 

1.2K Points

Eyeroll. As dense as they come.

Champion

 • 

783 Messages

 • 

13.6K Points

Eye roll.   Having to open Photoshop first has happened in the past and it was fixed.  This is a TEMPORARY workaround and not a big deal.  This will be fixed also.   

1.8K Messages

 • 

21.6K Points

Worse than climate change for some ;-)

Author “Color Management for Photographers"

443 Messages

 • 

6.6K Points

Robert, But you don't have to open Photoshop first! Just use the option Adobe have given you in Photoshop's Preferences as I said in a previous post. No work-arounds needed; just get rid of the new Home Screen, it is not needed to go from LR to PS!! Probably most PS users won't want it either; I didn't so turned it off immediately after install, before this effect became recorded.

Adobe will probably have recorded this bug in PS Home screen  as a 'minor bug'; that is one for which there is an easy solution. So no rush to fix it.

Bob Frost

1.3K Messages

 • 

22.5K Points

If you do find the Home screen useful, open PS first and forget about the preference. No doubt the bug will be fixed soon enough.

If you don't, then change the preference - regardless of the bug.

Champion

 • 

783 Messages

 • 

13.6K Points

Robert,  thanks for reminding me about the Home Screen preference fixing the problem.  You said your CUSTOM Home Screen did not cause a problem.  Maybe Adobe should just use yours. : )

443 Messages

 • 

6.6K Points

Just to be clear, I use a custom Workspace as my 'home screen' which necessitated turning off Adobe's Home Screen. Sorry for any confusion.

Bob Frost

1.3K Messages

 • 

22.5K Points

And I think that is important. If you don't like the Home screen just switch it off anyway. If you value aspects of the Home screen, leave the preference alone.

I get this bug all the time on my PC, and it is annoying, but it's nowhere near as catastrophic as some of the more hysterical posts make it appear. No doubt it'll be fixed soon. For now, we can just try to remember to open PS first. And yes, I often forget. But then how hard is it to say sh1t to yourself, close the document, and do Ctrl E a second time?

443 Messages

 • 

6.6K Points

Having not had this new Home Screen for the last 30 yrs of using Photoshop, I am sure I can wait a while longer to see if it has any benefits while opening LR edits.

Curious to know what aspects of it you value when editing from LR?

Bob Frost

1.3K Messages

 • 

22.5K Points

None, Bob, when sending something from LR.

However, that's not the only way one opens stuff in PS. I am not a 100% enthusiast for the Home screen (eg I'd like to add shortcuts to certain folders), though it's good to have recent photos displayed in a variety of ways. But one aspect I do like is its LR Photos panel. So when I am on another computer, I can go into my synced LR collections and open one or more photos.

596 Messages

 • 

11.3K Points

John,
I get this bug all the time on my PC, and it is annoying, but it's nowhere near as catastrophic as some of the more hysterical posts make it appear.
No, it's not a big deal (once you know the workaround). What seems more important to me is the fact that such a bug can make it to a public release. Any user calling PS from LR can observe it immediately after updating. Adobe has accustomed us since many years now to such bugs that are immediately noticeable and easy to reproduce. This should simply not happen. We are not talking about bugs that are hard to detect or that are related to unusual configurations. This obviously indicates flawed (I would rather say non-existent) testing procedures. That's the actual problem that should be fixed. We are alerting about this loss of quality since years and obviously nobody is hearing. Or nobody is actually in control.



 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

443 Messages

 • 

6.6K Points

My guess is that LR and PS are produced by different teams of engineers and testers, and people testing LR are probably not going to have access to the latest beta versions of all the other Adobe products, and vice versa. So it is easy to see how this minor bug could slip through.

Bob Frost

596 Messages

 • 

11.3K Points

and people testing LR are probably not going to have access to the latest beta versions of all the other Adobe products
That's exactly what I name a flaw in the testing procedures. Adobe is selling us a software ecosystem. It's up to them to make it consistent and to ensure code quality. I'm not paying for being a beta tester.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

1.8K Messages

 • 

21.6K Points

Beta testers for Adobe don't get paid either FWIW. 

Author “Color Management for Photographers"

443 Messages

 • 

6.6K Points

You would have to pay an awful lot more for software without bugs; many thousands of dollars instead of a measly hundred or so!! ;)

Champion

 • 

783 Messages

 • 

13.6K Points

"A hundred or so"

I think your estimate is way low if you are talking about Lr.   Some of them are minor but there are quite a few severe bugs that have been in Lr for a LONG time that really need a fix.

596 Messages

 • 

11.3K Points

You would have to pay an awful lot more for software without bugs
Nobody is expecting bug free software and certainly not me as a former developer. What is expected from a company like Adobe is

1) proper regression testing before releasing a new version and development methodology allowing to eliminate the most obvious bugs before they hit the users. This is obviously not done.

2) proper handling of bugs when they are reported. There are bugs in LR and PS that are lasting since years (5 years, 7 years,..). This is not acceptable.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

57 Messages

 • 

1.2K Points

and some people would blithely pay more and more for a service that is getting worse and worse, and say and do nothing about it. Horses for courses. 

Adobe Administrator

 • 

746 Messages

 • 

16.5K Points

@Geoff, I'm confused as to what gave you the impression that Andrew Rodney was an Adobe employee. He isn't designated as such on this forum. If he was an employee his login would indicate as much.

Thanks,
Hannah

17 Messages

 • 

520 Points

2 years ago

This reply was created from a merged topic originally titled Compatibility issue between LR and PS?.

Whenever I start PS out of LR with Command+E in order to continue editing all tools in PS are greyed out and are not selectable. The workaround I found out is to save image in .tif format and reopen it either in PS directly or with Command+E out of LR. This happens since last upgrade. Anyone an idea what is wrong?

443 Messages

 • 

6.6K Points

Read the earlier posts for solutions.

16 Messages

 • 

334 Points

2 years ago

This reply was created from a merged topic originally titled Photoshop CC 2019 Menu Items Grayed Out.

When exporting from Lightroom Classic CC to Photoshop CC with the right-click menu item "Edit In Adobe Photoshop CC 2019" the resulting files have almost totally grayed out menu items in Photoshop, making them impossible to edit or apply filters to the files, with no ability to bring the menu items back to life. Sometimes I can open Photoshop first, before clicking the Edit In selection and this process will work properly, but not always. It seems to want to fail once before I can finagle it into working properly. It is becoming a major pain in the butt, especially when editing many files in any particular project that require Photoshop. I have seen other posts on the Internet regarding this problem, but none here so I thought I would put it up.

443 Messages

 • 

6.6K Points

Read previous posts.

38 Messages

 • 

814 Points

2 years ago

I see that today there are updates for Lr CC and Br CC. Hopefully this will address the recent issues.


Peter

38 Messages

 • 

814 Points

And the first thing I noticed when I attempted update Lr CC was this ...




I think I will turn this off for now, until I feel more comfortable turning control of applying updates over to the automated process. It is turned on by default so I cleared the check mark.

596 Messages

 • 

11.3K Points

Hopefully this will address the recent issues.
No. PS has not been updated.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

38 Messages

 • 

814 Points

and there is an update for ACR too...

38 Messages

 • 

814 Points

Well! I need to do more testing, but at a first attempt the issue between Br CC and Ps CC, whereby sending from Br to Ps left the Ps menus grayed out, appears to be fixed. Yes, I did go into Photoshop Preferences and clear the "Disable the Home Screen" setting and then closed Ps before launching Br.

Also my problem with zoom "Fit on SCreen" not zooming to fill the available space also appears to be fixed.


Thank you Adobe,
Peter

596 Messages

 • 

11.3K Points

I did exactly the same and menus were grayed out like before when opening a file from Lightroom.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.

596 Messages

 • 

11.3K Points

I don't have the problem when calling PS from Bridge. Maybe the problem is at the ACR level. In that case, the bug may or may not appear depending on the ACR settings or depending on the way Lightroom communicates with PS which is different from Bridge.

 

--
Patrick
www.ppphoto.fr
Hamburg ist der wahre Grund warum
Kompassnadeln nach Norden zeigen.