Comment 2 for bug 1081328

Interesting. I never considered the obvious possibility that this issue was first introduced in 3.82 and to be honest, I've never actually encountered it on my Ubuntu box.

This may be a total non-issue...