P: Completely broken Hand tool (PS24.5) Hand Tool Sticking, sticky, not seeing mouse-up

@CJButlerwhat about @Goyko survey idea?

I guess what's even more aggravating than devteam not being able to fix it quickly (or at all) is the fact that in the meantime there are new features implemented that for many of us are to be seldomly used, but hand tool, bread and butter of our daily work is broken. I also suppose that the most vocal people here are the ones that use your software to make a living, not say AI enthusiasts. Since v25 I've used these generative features once 🤷‍♂ and could have easily grab another photo and with some masking add the missing background just as quickly, but the hand tool, I use it hundred times a day. It adds insult to injury.

For what it's worth, I set up a new rig few days ago, clean machine, fresh Photoshop installation, it's there, so maybe grab something Intel based with RTX GPU, install W10 Pro 22H2, update, move the taskbar to the window's top (I remember Photoshop going bonkers back in the day with taskbar on top) and see for yourself.

And to sum it up maybe we are frustrated also because it's not the only bug that plagues your software. random clipboard problems between your apps (suggested solution - something hijacks the clipboard, not our fault, like it's the only program ever that cannot into clipboard management, seriously?), Illustrator's inability to refresh layer thumbnails properly - it's there since version 10, we're using 20 something now, quirky guides in Photoshop, artboards in Photoshop acting unexpectedly, selections stopping working everywhere but Indesign (yet), stock libraries not loading, fonts not activating on a whim, I could go on and on, but living in the world of early access apps and constant updates we are conditioned to shrug those small bugsies off and continue, but you still manage to break things big time... And all that with the recurring payment when lot of us could easily keep using CS6.

@12551929 It won't have much to do with the wacom. Because I've tested a lot of things... This is because I easily reproduced this with a mouse click while reinstalling Windows OS and only installing Photoshop. People talk about Spring Road, but I think differently. Looks like it has to do with the space bar.

But what does that really mean for us?

The bug will remain infinetley in the software?

So I am stuck with version 24.2, which by the way is the least version to run the latest version of Lumenzia on.

Just a thought:

All of us here have Adobe accounts.

So gather our email addresses and send us your survey by email, and additionally ask for our system info, that Photoshop provides.

That's the purpose of that tool anyways, providing Adobe with infos to debug the software, if there are bugs.

Then you can collect all the data from affected users/systems and find the similarities, which may lead to the solution.

BUT actively send emails out to all people here, who reportedly have this bug!

Many may have already given up on the topic and won't provide any info, if you are not proactive.

Additionally you have all the needed infos in one place (best would be a dedicated email-address at Adobe regarding this bug) and your devs can look further into it.

It may not work for most of you, but reverting to an older Wacom driver may a more or less temporary solution. Autodesk informed me a few months ago that the most recent version of the Wacom driver can render Maya more or less useless, which was the case for me. After reverting to an older tablet driver version everything was fine again. Now, after some updates of Maya AND the Wacom driver it seems to be stable. 

So, we are talking about Photoshop, not Maya!? Yes, but i've read in several forums that people could fix strange pen behavior by reverting to older Wacom drivers, for several programs. So, if everything fails for you try this solution. Should take a few minutes, and if it is not working just re-update again. And feel free to bite in your table (cheaper than eating your Wacom tablet).

Yes, I am too.  After unchecking spring loaded tools it still happens.  But, restarting Photoshop seems to resolve it for a few days and then it happens again.

I am experiencing it even with no checkmark in Spring-loaded Tool Shortcuts. 
I also have disabled Gestures, Overscroll and Flick Panning. 
The Eye Dropper tool seemed to have had adopted this bad behaviour too, at some point earlier today, at least for a moment. 
Photoshop 25.1.0. Windows 10 Pro, 22H2. 64-bit. Intel i7

Edit: nope, I can replicate the eye dropper tool sticky thing. It's not every time, but it will stick until clicking again. 
I should say, it is not as frustrating as the other sticking tools. It's just that the "ring" stays on screen, instead of just when holding down the button. 

I do appreciate your engagement on this matter @CJButler, as you're a member of the Adobe team, at least it shows to us that we're being heard. I understand the difficulties to reproduce bugs given the different environments, so I'll try to share some of my PC specs and some details as requested and I would suggest that the others colleagues do the same:

I'm using a Wacom Intuos Pro M PTH660, Adobe Photoshop version 25.1 and Windows 10 Pro version 22H2 (OS build 19045.3324 with Windows Feature Experience Pack 1000.19041.1000.0).

The bug seems to happen with mouse and wacom pen, until now I've been able to evade the bug uncheking the Edit > Preferences > Tools > Spring-loaded Tool Shortcuts, as suggested by someone on this very thread sometime ago, but I don't know if it will be a permanent fix. I saw some people saying that this bug won't happen on Windows 11 and that turning on Windows Ink on Wacom driver would solve the problem, but I didn't tested it since Windows Ink makes working on anything related to painting unbearable.

Hope that helps into futher troubleshooting.

>> I think what's grinding people's gears is that we can all reproduce this easily, every time, in every version since 24.5, on just about every platform. In fact I'd say most of use can't NOT reproduce it. It's difficult to understand why it's so evasive on your end when it's so pervasive on our end.

I totally get that. And I hope you can appreciate we're just as frustrated on the other end of the spectrum. With so many people reporting this, we don't understand why we cannot reproduce this as easily as all of you. We absolutely are not ignoring this bug.

>> Your subversion or Git checkin notices ought to have something in that timeframe that gives a clue, surely.

As far as tracking it to a specific checkin, without reproducing it and reducing it to a specific checkin, it's near impossible. There are literally thousands of check-ins to the code base between those two versions you mentioned. And there is further data that suggests it started happening at or around 24.3. Maybe earlier.  So it's not that simple. And yes, we have looked.

Our primary testing efforts are focused on Win 10 machines, both with and without Wacom devices. These are native machines, not VMs. The behavior has been reported seen on Windows 11, and in this thread at least one user says he saw it on a MBP/M1 with Mac OS 13.5.2. We have had dedicated remote sessions with people who can reproduce pretty much at will. We have seen it happen remotely with 5 engineers watching. We carefully follow the steps they show us on our machines. Nothing. And then days later we see it happen (Aha!, we say), but then it goes away. I personally saw it happen two weeks ago. And never since. At Adobe, as far as I know, we have only seen it (rarely) on Win 10 machines, never on Win 11 or Mac.

Without reliably reproducing, we will continue to have great difficulty making progress. I wish it were otherwise.

Never had a tablet, so it's not that. Our 60+ office machines are a mix of win10 and win11 and we can reproduce it on all of those, none have a tablet.