Comment 2 for bug 503420

I figured out it wasn't the kernel's fault but erlang's fault that this was happening because of the message during installation (via aptitude in a terminal) that noted that now that erlang was installed, it would go look for those processes that depended on it or something of the sort. I attached the fake kernel oops report anyway because more information ought to be a good thing.