Comment 14 for bug 424231

After re-reading it, it seems this bug took a somewhat different direction than what the original report was due to chasing down the same symptom that was probably unlikely to cause the original problem. If the original problem is no longer happening, then that's probably ok just to keep pursuing the current line that this has taken, but if the original problem is still reproducible then we need to separate this into two separate bugs. @theguv, are you still seeing the original problem you reported in the latest images? Thanks!