Open GoogleCodeExporter opened 9 years ago
This probably isn't fixable. managedsoftwareupdate is being run as a launchd
agent that runs in the loginwindow context; in other words, the
managedsoftwareupdate job is loaded (and possibly run) when the loginwindow is
started. If the Keyboard Assistant is running, I'm guessing the loginwindow is
not running (not even "behind" the Keyboard Assistant) and therefore
managedsoftwareupdate _cannot_ run.
-Greg
Original comment by gregnea...@mac.com
on 15 Nov 2010 at 11:08
I logged in via ssh and noted that it was indeed running in the background. I
only noticed because I tried running managedsoftwareupdate --auto via ARD on it
and it returned an error saying it was already running.
Original comment by Nate.Wa...@gmail.com
on 15 Nov 2010 at 11:11
I just tried a variation on this, and loginwindow is definitely running, but
the attempt to launch MSU.app is failing with a kLSUnknownErr (-10810) which
makes it feel like the OS is causing the attempted launch to fail...
Original comment by gregnea...@mac.com
on 16 Nov 2010 at 12:09
I don't doubt the OS is causing the issue. I noticed it today and had never
even thought of using a non-apple keyboard. If it is something that cannot be
fixed via munki, it is no biggy, I just thought it was a rather interesting
occurance. In all honestly, anyone who is using OS X with non-Apple keyboards
should have the prefs that the wizard creates already present on the
image/machine build to prevent that popup from occuring. Having that wizard
pop up in the first place would be rather messy on a standard image.
Original comment by Nate.Wa...@gmail.com
on 16 Nov 2010 at 12:13
Original issue reported on code.google.com by
Nate.Wa...@gmail.com
on 15 Nov 2010 at 10:59