Comment 6 for bug 1362155

Status updated:
1) we need to track it both in release series it was found (5.1.x), and releases series that are our current focus (6.0.x).
2) marked as Iincomplete in 6.0 based on the comments above, looks like we need to clarify the impact and reproducibility of this bug.
3) marked as Won't Fix for 5.1: unless this turns out High or Critical priority, we're not going to backport a fix to 5.1.