What would cause sudo to go deaf and dumb? I updated to Sierra three days ago.
I tried running a sudo command today and it just sits there like an idiot. Never even asks for a password. The day I updated to Sierra, I got notified that MailTags and GPG were incompatible, so I updated both of them. GPG still has only beta releases if you need to run on Sierra (if they don't hurry, they're going to miss Sierra entirely), so I installed that. The installation hung when "one minute to go" turned into 15+ minutes with still nothing happening. Activity Monitor showed it hung in sudo, nothing apparent under sudo (but for all I know, stuff under sudo forks its own hierarchy). I quit and retried it, with the same result; then tried uninstalling the whole thing in case the old version was hosing something up; every installation or deinstallation hung. Several HOURS later, after I thought I had terminated everything involved, a message popped up saying that either some installation or deinstallation had actually finished, and enjoy the results. So I performed one final installation and let it run overnight; it ultimately finished, or timed out and assumed it succeeded, wh atever. The point is, I don't know whether sudo was broken when GPG got there, or GPG (or something I caused by aborting it) broke sudo, or what. Anyway, is there some sort of stupid-lock that needs to be cleared to make sudo proceed again? I even went to console looking for sudo invocation entries. Console and its navigation is all changed in Sierra, and if it's still recording sudo invocations I couldn't find them. _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
