Hello, I had the same problem with kdelibs 3.2.3-1. However, I have been using unofficial QT 3.3.2 (sid has 3.2.3-2 as of writing) packages from http://bignachos.com/~nelson/debian/ for a while now. So I have to rebuild kdelibs against QT 3.3.2, otherwise, I wouldn't be able to compile any KDE app because of conflicting QT versions. That's what I did with kdelibs 3.2.3-1 today. And the bug has been gone after upgrade to the rebuilt kdelibs 3.2.3-1
I have tested some other combinations of different versions of QT and kdelibs. Here it is the summary when the bug is triggered and when it's not: QT 3.2.3-2 (sid's) + kdelibs 3.2.3-1 (sid's) = the bug IS triggered QT 3.3.2-1 (unofficial) + kdelibs 3.2.3-1 (sid's) = the bug IS triggered QT 3.3.2-1 (unofficial) + kdelibs 3.2.3-1 (rebuilt) = the bug is NOT triggered Thus it sounds like an issue with sid's QT or kdelibs as of version 3.2.3 began to use a QT 3.3.x specific feature...