I use an "alternate invocation" bound to "sample foreground color" to quickly sample color as I paint. When you do so, an eye-dropper icon appears on the cursor. It disappears as you release your "alternate invocation" shortcut. The problem is the icon doesn't disappear sometimes (often) and you need an extra action (like trigger it again, mirror the canvas, change tool...). It might seem like nothing, but when you do, and you get stuck with the icon right after that, in a new color sampling manipulation, it becomes to feel like a burden. To reproduce: paint with a color, color sample with the alternate invocation, paint again, sample again, eventually you will get a stuck eye-dropper icon. Sometimes it keeps on happening, sometimes it takes time to pop back up... I couldn't find a specific manipulation prior to witnessing the sticky icon. I tried doing so while calling other invocations like zooming, panning, rotating. But it doesn't seem to have an impact.
PS: Please note I use the no cursor setting for my cursor. It seems it won't happen if you have another cursor option which will have a graphic representation (a dot or an icon...)
I've seen this happen even though I use the brush outline cursor, so setting to confirmed. I'm simply not sure it is really fixable, though. It's also not a regression, I've seen this before on my mac.
I think there is a mix here: brush outline is not a cursor option. I guess you mean you use "preview outline" as brush outline shape. I'm talking about the Brush Cursor Icon option (which is just above). If you put it to anything except "no cursor" you will not have the persistent eyedropper issue.
I could not make the cursor to stuck after 15min of blending colors. My cursor is set to none, and outline to brush preview. We had stuck icons with the zoom actions a while ago, and maybe I got the eyedropper icon stuck once back then.
Yes, I also sometimes struggled with reproducing and thought it was gone after this or that... sometimes it's very rare. But to tell you how much it was slowing me down, I started working with the white pixel cursor to "forget about it".
Also is it possible it is related to the ARM architecture ? I think Halla has an M1 laptop just like me.
I don't think is arch related, I'm also on arm64. The more likely reason is a signal could get lost under certain rare conditions. And reproducing those exact conditions is finicky.