Version: unspecified (using KDE 4.8.0) OS: Linux Kubuntu 11.10 KDE 4.80 If I set mouse click interval to 800ms in system settings, KDE apps set correctly, but non-KDE apps click interval remains at default 200ms. If I Boot same system into Gnome or Unity all apps work perfectly -- no interval problems. I installed KDE on Fedora 16 and problem goes away as with Gentoo and Slackware. This only occurs on ubuntu's port of kde and is started back when KDE 3x went to 4x Reproducible: Always Steps to Reproduce: Just install kubuntu, run system settings, and set mouse double click interval to 800ms. Actual Results: KDE apps have a correct interval of 800ms as configured, but non KDE apps remain at the default 200ms interval. Expected Results: KDE apps have a correct interval of 800ms as configured, and non KDE apps also change the default 200ms interval to 800ms. I have a disability that prevents me from double clicking under 700ms. I reported this bug a long time ago 'Bug 268399 - double click select text not working', but I did not articulate the problem. Kubuntu has a bug (easily repeatable): mouse settings change mouse double click interval correctly, but the interval for non-KDE apps (firefox, chrome,etc) stays at about 200 ms. This bug has persisted through different versions probably because most people don't notice. I asked my wife to try to double click select text in Chrome on Kubuntu 11.10 and it works without fail -- I can't, but on Kate or other KDE apps I can. As a workaround I installed mousetweaks and wrote a bash script: #!/bin/bash /usr/bin/mousetweaks --dwell --dwell-time=1.2 -t 20 --ssc --ssc-time 1.2 This preforms a double click at 200ms.
See also http://www.linuxquestions.org/questions/linux-software-2/double-click-speed-with-gtk-and-thunderbird-332254/
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thanks for the report. Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!