I added the information and a regression test to bug 12928, which has been closed because it was supposedly fixed, because I think it's the same bug. The regression test I ran points to the same patch that was identified as the problem the first time around. But someone needs to officially reopen that bug. Or, I can open a new bug for it--let me know if I should.
