RiparaCapo

This is the normal(!) behavior of RiparaCapo when it waits until the "repair_packages" process has completed.

You may not be familiar with the meaning of the spinning wait cursor. If an application takes longer than 2 seconds to process the events in its event queue (regardless of the exact cause!) the operating system displays the wait cursor whenever the cursor hovers over that application's windows (see also https://en.wikipedia.org/wiki/Spinning_pinwheel#System_usage).

However, even if you had (force) quit RiparaCapo the "repair_packages" process would have successfully completed.

Furthermore the start dialog of RiparaCapo clearly indicates "Permissions repair may take up to several minutes"; this means RiparaCapo waits until the "repair_packages" process has finished and then RiparaCapo will continue with the next dialog (to quit or to check the log file).

One thing is clear, you have no clue what you're talking about. A tip, don't download apps you don't understand;-)

Thanks for the heads up info MacParc. It would be helpful to provide that info at your website.

I just start the repair_permissions process which still exists.

It's an AppleScript running this command

/usr/libexec/repair_packages —repair —standard-pkgs —debug <Volume>

You can do it directly in Terminal, though the question remains "why"? If you run it in Terminal, you'll see pretty much all it does is restore the 'write' property on lots of printer related directories.

@ChrisB: when you save a script as run-only, it captures the state of the properties from the last run (in other words, your last exitStatus is written into the script, including your HD drive name and username). After testing, you should recompile a fresh version of the script and save it as 'run-only' without running it first to avoid that.

@softwater: Thanks for the hint. :-)