Camden,
OtherJobEnabled is documented to be a dictionary of booleans, not a single
string.
Launchd should log an error message pointing this out and ignore the key.
Instead it crashes, which is definitely a bug! :)
The bug will be addressed in a future release; meanwhile you can work around by
> Le 26 mai 2016 à 00:05, Camden Narzt a écrit :
>
> I’m sorry, I just assumed anyone doing any dev work on OSX would already run
> homebrew.
>
> A much smaller test case with no installs so definitely a problem with
> launchd/OS X is as follows:
>
> cat < php.plist
>
> "http://www.apple.co
> On May 25, 2016, at 3:05 PM, Camden Narzt wrote:
>
> I’m sorry, I just assumed anyone doing any dev work on OSX would already run
> homebrew.
I do lots of development work on OS X. I don't run homebrew.
>
> A much smaller test case with no installs so definitely a problem with
> launchd/O
I’m sorry, I just assumed anyone doing any dev work on OSX would already run
homebrew.
A much smaller test case with no installs so definitely a problem with
launchd/OS X is as follows:
cat < php.plist
http://www.apple.com/DTDs/PropertyList-1.0.dtd";>
KeepAlive
OtherJobEnabl
> Le 24 mai 2016 à 19:52, Camden Narzt a écrit :
>
> […]
>
> This is 100% reproducible on my MacBook Pro (Retina, 15-inch, Mid 2014)
> running OS X 10.11.5 (15F34).
>
> Steps to reproduce (warning, this will almost certainly cause a kernel panic):
>
> /usr/bin/ruby -e "$(curl -fsSL
> https:/
You should attach the problematic launchd.plist to that Radar.
-damien
> On 24 May, 2016, at 16:07, Camden Narzt wrote:
>
> Radar:26456448
>
> Camden
>
>> On May 24, 2016, at 1:10 PM, Kevin Elliott wrote:
>>
>>
>>> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! wrote:
>>>
>>>
>>> On 24
Radar:26456448
Camden
> On May 24, 2016, at 1:10 PM, Kevin Elliott wrote:
>
>
>> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! wrote:
>>
>>
>> On 24 May 2016, at 18:52, Camden Narzt wrote:
>>
>>> Does anyone have any ideas about why this is happening?
>>
>> The answer to the question “
> On May 24, 2016, at 11:50 AM, Quinn The Eskimo! wrote:
>
>
> On 24 May 2016, at 18:52, Camden Narzt wrote:
>
>> Does anyone have any ideas about why this is happening?
>
> The answer to the question “Why does my system kernel panic?” is pretty much
> always “Because of a bug in the OS?”
On 24 May 2016, at 18:52, Camden Narzt wrote:
> Does anyone have any ideas about why this is happening?
The answer to the question “Why does my system kernel panic?” is pretty much
always “Because of a bug in the OS?” The system is not supposed to panic
unless you do obviously dodgy things (
