Hello Adeodato
On Thu, 24 Feb 2005, Adeodato Simó wrote:
* Tomas Pospisek [Wed, 23 Feb 2005 15:28:03 +0100]:
This still happens under KDE 3.3.2. I get the exactly same behaveour as described in KDE bugreport http://bugs.kde.org/show_bug.cgi?id=90073.
I read your comment, but can't reproduce with acroread here.
The crucial comment in the KDE bugreport is this one:
_ I was just able to reproduce this bug as many times as I wanted. As soon _ as I restarted klipper it went away and I could not reproduce it any _ more.
I can not reproduce the bug "from zero", that is from a fresh KDE start on, just like that. But once the bug happens, that is KDE's input "freezes", I can kill acroread to unfreeze KDE's input and from that point on reproduce the bug again and again /untill I kill klipper/ at which point the problem goes away.
Any idea how that bugreport at KDE can be reopened?
As far as KDE developers are concerned, the issue is fixed, since Qt 4.0 includes the fix (sure?) and they have a patch [1] in qt-copy that solves the issue.
[1] http://webcvs.kde.org/qt-copy/patches/0048-qclipboard_hack_80072.patch?view=markup
But you already knew this. ,-)
No, I didn't. Is this patch included in Debian? *t
-- -------------------------------------------------------- Tomas Pospisek http://sourcepole.com - Linux & Open Source Solutions --------------------------------------------------------
