Originally Posted by knc1
Post in the JBPatch thread on that one, it sounds like a JBPatch problem.
No, it's not.
Well, it might be. You can determine that by uninstalling JBPatch, seeing if the problem goes away, reinstalling JBPatch, seeing if the problem reappears. If, and only if, all of that is true, then it might be a problem involving JBPatch. But I honestly don't see why it would.