P: Vector tool Gradient Fill angle stuck at 0 degrees on MacOS 10.10 Yosemite

[FeedbackCommunityMember]

Photoshop CC 2014.2.2 Release. I'm having an issue where any new gradient I create defaults to 0o angle, and cannot be changed. I've tried restarting the computer, restarting Photoshop, purging all cache, and changing graphics settings. Nada.

Steps to reproduce:
• File > New
• 500x500px @ 72ppi, RGB 8 bit with Square pixels
• Select Rectangle tool, draw a box shape on-screen
• In options bar at the top, change fill type to gradient
• Gradient defaults to 0o. Any attempts to change result in the angle immediately resetting back to 0o.
• Attempt to double-click thumbnail preview in layers panel to bring up gradient modal. Changing angle here also does nothing.

This is an issue I've noticed intermittently since CS6. It's not always reproducible, and sometimes the issue goes away on its own.

I work one block away from the Adobe office in SF, happy to come in with my computer to show this in person.

[FeedbackCommunityMember]

This happens on Windows as well.

When it happens just close PS and re-open it again.

[FeedbackCommunityMember]

Just bought PS. Happening to me as well as a number of other stupid things in PS. Yeah it's sad it's still happening all this time later. Some lazy people working for adobe. But that's always been true.

[FeedbackCommunityMember]

This bug is still not fixed. Irritating not to be able to rotate the gradient.

[FeedbackCommunityMember]

1. create a shape
2. fill with gradient
3. attempt to set angle to 90 degrees

[J453]

I was able to find reproducible steps.

I'm not able to reproduce this issue on Mac in Photoshop CC 2015.1.1 but I'm am however able to reproduce this issue on Windows.

Please let me know if you're able to reproduce this issue on Mac.

[FeedbackCommunityMember]

THIS SOLVES THE ISSUE QUICKLY FOR ME:

Have 2 documents open. When you get this glitch, deselect the shape, switch to other document that's open and then come back. No clue why but this works for me.

[J453]

This was fixed in CC 2017.