Comment 4 for bug 419564

Yep, you're right. Unfortunately, I am (so far) unable to reproduce this bug, and noone else has reported the same problem. Do you think it might be related to the reporter using debian unstable?