Doubleclick interval not set for non kde apps

Bug #936463 reported by Jon Jacobsen
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
New
Undecided
Unassigned

Bug Description

I reported this as 'bug 294443' on kde.org, but I'm resubmittiing here because it's a ubuntu specific bug:

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.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7.1
ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
Uname: Linux 3.0.0-16-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module 280.13 Wed Jul 27 16:53:56 PDT 2011
 GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
.tmp.unity.support.test.0:

ApportVersion: 1.23-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
Date: Sun Feb 19 11:55:15 2012
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: kubuntu
GraphicsCard:
 nVidia Corporation GT520 [GeForce GT520] [10de:1040] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ZOTAC International (MCO) Ltd. Device [19da:1215]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
JockeyStatus:
 xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use)
 xorg:nvidia_current_updates - NVIDIA accelerated graphics driver (post-release updates) (Proprietary, Enabled, In use)
MachineType: Gigabyte Technology Co., Ltd. GA-990FXA-UD3
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic root=UUID=4c8397a5-e806-473d-ac64-a0d51dd01221 ro verbose vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
XorgConf:
 Section "Device"
  Identifier "Default Device"
  Option "NoLogo" "True"
 EndSection
dmi.bios.date: 10/13/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F5
dmi.board.name: GA-990FXA-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd10/13/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-990FXA-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-990FXA-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20110811.g93fc084-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110411+8378443-1

Revision history for this message
Jon Jacobsen (jonj) wrote :
affects: ubuntu → xorg (Ubuntu)
bugbot (bugbot)
affects: xorg (Ubuntu) → xserver-xorg-video-nouveau (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in xserver-xorg-video-nouveau (Ubuntu):
status: New → Confirmed
Revision history for this message
Jon Jacobsen (jonj) wrote :

As a workaround, I created ~/.gtkrc-2.0 and added 'gtk-double-click-time = 800'

Using 'backports' repository I upgraded KDE from 4.8 to 4.81. The upgrade added a theme statement and moved ~/.gtkrc-2.0 to ~/.gtkrc-2.0-kde. This broke this work around. I ran ' cp .gtkrc-2.0-kde4 .gtkrc-2.0' in my ~ and the double click speed works once again.

penalvch (penalvch)
affects: xserver-xorg-video-nouveau (Ubuntu) → kdebase (Ubuntu)
Changed in kdebase (Ubuntu):
status: Confirmed → New
Revision history for this message
Lorenzo Bettini (bettini) wrote :

This bug is still present in 14.04 for the touchpad.

Adding

gtk-double-click-time = 800

to

.gtkrc-2.0

solves the problem

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.