Waiting for the Activation Lock Capable check

[etrahretep]

Widgets CPU bar and System Profiler display "waiting for the Activation Lock Capable check" after a few minutes. Restarting fixes it but it returns after a few minutes. Any idea

iMac Pro 2017 Intel MacOs 15.0 B7

[locupleto]

Hello,Thanx for reporting. Questions: if you used the binary I compiled; then did you do this part of the instruction:

- sudo xattr -d com.apple.quarantine crystal_htop_x86?

[etrahretep]

Yes I did. Doing it for a second time gives me: xattr: crystal_htop_x86: No such xattr: com.apple.quarantine

[locupleto]

What os version are you running?

[etrahretep]

iMac Pro 2017 Intel MacOs 15.0 B7

[locupleto]

Oh, a beta of Sequoia… I have never tested on that. This must be is security related issue.  Google suggests you may try xattr -cr instead:From the MacOSBeta community on Redditreddit.comSent from my iPhoneOn Aug 28, 2024, at 07:52, Peter Harte @.***> wrote: iMac Pro 2017 Intel MacOs 15.0 B7

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>

[etrahretep]

That didn't do iit.

[locupleto]

That is unfortunate. Of course you could always compile the source code for my htop fork yourself if you are up to it. That would likely solve the security issue. But: If you try to execute the binary directly from the terminal, what error msg do you get then?

Den ons 28 aug. 2024 kl 09:43 skrev Peter Harte @.***>:

That didn't do iit. Scherm.afbeelding.2024-08-28.om.09.40.12.png (view on web) https://github.com/user-attachments/assets/a5df067b-17fd-4266-8c5e-72c8852c57f3 Scherm.afbeelding.2024-08-28.om.09.41.23.png (view on web) https://github.com/user-attachments/assets/518fcafc-b454-4cd4-b27d-07a8d359eedb

— Reply to this email directly, view it on GitHub https://github.com/locupleto/crystal-widgets/issues/1#issuecomment-2314563938, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6PKGQXXQVL32WZKVVD2XTZTV5OXAVCNFSM6AAAAABNEBS5ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJUGU3DGOJTHA . You are receiving this because you commented.Message ID: @.***>

-- Urban Ottosson Mail: @.***

[etrahretep]

Something different then your screenshot:

[etrahretep]

OK compiled htop from fork and renamed it to crystal_htop_x86. When run in terminal it gives correct output. The CPU bar widget gives me 8 flat stats? Strange thing is if run the old binary the tasks and stats show. Not after restart.

[etrahretep]

Pity. That didn't work. Same "waiting for the Activation Lock Capable check" after a few minutes...

[locupleto]

How very annoying. I have it installed and running flawlessly on all three of my Macs; an M1 Ultra with 14.6.1 Sonoma and a Mac Pro Trash can with Monterey 12.7.6. as well as a 2017 Intel Macbook Air also with Monterey.

As I described, the only difference between my fork and the base htop is that my binary logs some of the measurements to log files in the temp directory. If we peek into the shell scripts on my M1 Ultra, I have defined a custom /tmp directory (default /tmp). [image: Screenshot 2024-08-28 at 17.55.39.png] Therefore I will find all the continuously updating measurement files that the crystal_htop binary writes there togheter with the lock file. [image: Screenshot 2024-08-28 at 17.56.04.png]

if the binary you just compiled worked, It should write 8 htop_cpu_00N.txt files (where N = 1..8 on an eight core cpu) in the temp directory. the binary of course need to be able to write there. On my machine it looks like this:

[image: Screenshot 2024-08-28 at 17.57.28.png]

I don't have your macOS version installed do I can't really do much more at this point. I am pretty much out of ideas I'm afraid.

Den ons 28 aug. 2024 kl 12:45 skrev Peter Harte @.***>:

Pity. That didn't work. Same "waiting for the Activation Lock Capable check" after a few minutes...

— Reply to this email directly, view it on GitHub https://github.com/locupleto/crystal-widgets/issues/1#issuecomment-2314966154, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6PKGX6P2VT2VMZNIDGPITZTWSYLAVCNFSM6AAAAABNEBS5ESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJUHE3DMMJVGQ . You are receiving this because you commented.Message ID: @.***>

-- Urban Ottosson Mail: @.***

[etrahretep]

Thanks for replying! No files are written to temp using the new compiled binary. If I run the precompiled in terminal it all works instantly in Ubersicht and files are written to temp. Funny thing is the output differs from the new and pre-compiled in the terminal (former screenshots). Oh well, worth the try, I'll put it aside to use with a future M3/4 Mac. Kudo's for the amazing layout and programming. Cheers

[locupleto]

Thank you and no problem. I will be sure to carefully check if I have similar challenges when macOS Sequoia is released; fingers crossed it's a beta-problem :-)