Now that KDE 3.2 has moved to Sarge/testing this bug has found a whole new audience. I've just encountered it for the first time. On reading the report log for this bug I am uncertain what it's status is. Is a fix waiting on action from kde developers or is it a debian packaging problem? Regards, David Nebauer.