P: (14.3) Sonoma - WB Picker Loupe Tool is stuck after first click

grazie ma lo posso installare anche su IMAC con chip M1

I regularly dog on Microsoft for continous updates to fix issues with the Silicone chips - this issue - where I'm paying for a subscription - can barely get a support ticket and am shuffled off to a community support forum (and seemingly the bugs get bundled into this thread) - with NO REALSITIC timeframes...  Really puts it into perspective.   I do NOT store anything in Adobe - frankly do not trust them - LR (cloud) is simply an editing tool for me.  I did the support ticket (what a mess) - AI constantly wanting me to AGREE to a known bug they have a fix for...   After far too much time I finally get to the next to only be told an update is coming...   WHEN?  Day, week, MONTH????   I'm paying for something that I am now using an alternative because the VERY BASIC function of White Balance has failed...   Damn you Color-Checker for making me beleive having accurate colors matters...    And to think I call out Microsoft for their frequent updates - puts things into perspective for me.  Anyone suggest alternative - I do minor editing - dropper for the WB agaist the color-checker passport - slider here or there and that is about it.  Have used the new Denoise on occasion (high ISO/low light) - but just mainly basic stuff.  Regularly used formats - DNG (Leica), RW2 (panasonic), ARW + SR2 (sony), RAF (Fuji)...   I'm not griping about the cost of Adobe - I'm excessively disappointed in the fact that after some five or so years - I'm shelved with the - don't waste our time - watch a community board for updates BS.  I've no problem paying 100/mo - but if it breaks - I expect your to get off your A$$ and keep me - THE CUSTOMER - updated as ot your percieved resolution and timeframe to do so.  Your brilliance doesn't impress - your lack of realiability offsets anything to the contrary...

Yep. This thread is a mess. Last week I reported the fact that updating to Sonoma 14.5 introduced old and new bugs again in both Intel and M chips for LRCC 7.2. The forum admins merged that bug into this one, which dates back to Sonoma 14.3 going by the title, which essentially drowns the current bug into a sea of old reports that may have been marked as "fixed". Incredibly frustrating.

However, the pinned reply states: Note: macOS 14.5 is reported to fix the issue on Classic 13.2 but introduces a crash on LrD 7.2. 

We've been told a hundred times to wait for an update. There are no work arounds. For anyone interested, I unindtalled, reinstalled, deleted preferences, reverted to older LRCC versions and all show the same bugs under Sonoma 14.5

You are using version 7.0 from 2013. Not that it matters for this bug, but if you don't update when updates are available, then you won't get the bugs fixes that these updates bring. As has been mentioned several times, Adobe does not comment on release dates. So you'll have to accept that "the next update" is all you will get from them.

This is a combined bug thread, and like you said, the issue is resolved for Lightroom Classic with MacOS 14.5. The pinned reply by Rikk Flohr clearly states it is not resolved for Lightroom 7.2 and causes a crash. I don't think Adobe needs to explain the technical details as to why this difference, and I am sure most of us would not understand a word of it if they did.

Seems each camera brand has its own software - and there is Capture One.

Since this has been going on for some time, what is an alternative to LR? I pay ny the month and am happy to move on. Anything similar someone like to recommend? 

Adobe never comments on when a bug fix will be released. Why the next update of Lightroom is later than the usual two months is again something that would never be revealed, and the technical background of a bug is also something that is not commented on (but knowing that this bug exists only in a MacOS Sonoma 14.3 and later suggests that it is probably a change that Apple made in MacOS that was the direct cause of it). The support person could have said sorry, but in the end that was most likely all he was allowed to say and you will still have to wait for the fix.

Uh I don't know, like this is when we're going to fix it, sorry for the inconvenience. We didn't buy this software once 10 years ago. We buy it every month. It's professional software. It's not a privilege to have it work.

The bug was reported MONTHS ago. It is reasonable to expect more transparency as to why this bug exists, why it hasn't been fixed sooner, and specifically when it's expected to be fixed.