Comment # 4 on bug 1077590 from Wolfgang Rosenauer

Hmm, this happened before at some point but the usual reason is not the problem
here.
We are patching browser.xul for KDE and if the KDE version is out of sync we
run into something like this. But I verified this and this does not seem to be
the case here.
I'm wondering if it affects everyone running under KDE but this is the first
report I've seen anywhere.