P: Saving copy not saving over jpg file

So much for my weekend post of "lets just get all along" But, OH LOOK, its some hard data we have here. This weekend I said we had 181 subscribed members on this thread, why, all waiting for the day someone can say its been fixed and we will have the news. Thread lost 4 subscribers since then just like I said I have thought time and time again, this back and forth isn't useful here. At this rate, I'll unsubscribe I'm sure LONG before Adobe puts out the fix. 

35 MORE messages on this, STILL?

GIVE IT UP, people. Adobe software is ancient, creaky junk that they can barely keep running. They’re using their software-rental scam to wring as much money out of moribund products as they can on the way down.

If by tomorrow you haven’t started your transition to modern software that’s actually being maintained, you’re another day behind.

The ....COPY.jpg situation makes it really tough to keep track of texture maps in Blender 3D, because as soon as the name changes, the link breaks. Side note, creating some package mocks for WalMart.com today for a client and almost sent the wrong file because I missed the word COPY.  It's getting kind of funny actually that this annoying file saving bug defines Photoshop for me now 🙂 

https://feedback.photoshop.com/users/5f5f265a6880ca11de7cc9c9

@mattrock1 Have you actually read my comments?  I think not.

I will argue that yes, DGrainger, many of your comments are of no use and you seem to use this forum as a soapbox.

@scott_cocking  Your comment amounts to an ad hominem attack, which is not allowed on this forum. Nothing that I wrote is "useless" and in fact is entirely correct. I am not sure what your particular "beef" is against me or my comments, but I advise you to either be polite and civil or take your remarks to some other place that does not mind that sort of stuff. You have actually on been on this forum for a very few months; perhaps you came here just looking for a fight!

@DGrainger Your comments are so useless, why don't you stop spilling ink. NOTHING you say is actually helpful. You aren't Adobe, so just shut up. 

Ok, but Adobe stated, that it is already fixed in 22.3:

https://helpx.adobe.com/photoshop/kb/fixed-issues.html

@2stepbay  FYI Frank is not a Adobe employee. However, you should note that several Adobe employees have in fact posted on this thread, and continue to do so. What they cannot do is to take the time to repeat over and over what they have said every time a new poster pops up. One of the problems is that this thread has become very long, so posters probably do not go back through it to discover what Adobe actually has already said. John Elzenga is correct in that Adobe IS in fact working on this issue and has every motivation they need to get it resolved as quickly as possible. He is very knowledgeable about Adobe, Adobe products, and does know whereof he speaks.  Enough "ink has been spilled" about this; it will be fixed, and it will be fixed as quickly as the programmers figure it out. They are NOT asleep at their desks!

Another poster, lora cawkins,  wrote yesterday (March 14) asserting that Adobe does not monitor this forum; that is incorrect. Read through the 16 or 17 pages of this thread and you will see that Adobe employees do, in fact, read and respond to this and do, in fact, have close contact with appropriate departments inside Adobe to urge repair of problems.