Double-click timeout is not applied to X

Bug #55270 reported by Cruxic
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs
xorg-server (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

A while back I reached my frustration limit while using Netbeans (a Java Swing IDE). It was very difficult to select anything in my project tree because the double click rate was way to fast for me (and most users I can imagine). Changing the Double-click timeout in Ubuntu's mouse preferences dialog did nothing to fix the issue. From what I can tell this dialog only effects Gnome applications because the setting is written to ~/.gconf/desktop/gnome/peripherals/mouse/%gconf.xml

After some research I found the solution: create .Xresources in my home directory with the line
*multiClickTime: 400. After a log out things worked correctly.

The best way, it's added this parameter in the file /etc/X11/Xresources/x11-common. (see my comment of the 2007-07-26)

The mouse preferences dialog should be doing this automatically to achieve greater consistency and usability.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Unconfirmed → Rejected
Revision history for this message
Cruxic (cruxic) wrote : Re: [Bug 55270] Re: Double-click timeout is not applied to X

It's been quite a while since I submitted that report but I don't think it
is a duplicate of #28052. 28052 does deals with motion sensitivity not
click sensitivity or am I mistaken?

On 4/19/07, Sebastien Bacher <email address hidden> wrote:
>
> *** This bug is a duplicate of bug 28052 ***
> https://bugs.launchpad.net/bugs/28052
>
> Thanks for the bug report. This particular bug has already been
> reported, but feel free to report any other bugs you find.
>
> ** Changed in: control-center (Ubuntu)
> Importance: Undecided => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Rejected
>
> ** This bug has been marked a duplicate of bug 28052
> mouse sensitivity range might not be optimal
>
> --
> Double-click timeout is not applied to X
> https://bugs.launchpad.net/bugs/55270
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
hache (jacheroy) wrote :

Thanks for this solution! It's work ! I have added the parameter in the /etc/X11/Xresources/x11-common! Because, you have this problem with all swing application! for sample, if you use Mercury Messenger (write in java), any doubleclick was a crazy manipulation ...! I have change this parameter on all configurations (lap-top, desktop and server)!

Revision history for this message
hache (jacheroy) wrote :

.... sorry I forgot to say ... It's not Ubuntu problem ! because the problem is the same with Red-Hat, Suse and Linux Enterprise (the RH very from Oracle)

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Indeed, this is about double-click rate with non-gnome apps. Unmarking as a duplicate.

Changed in control-center:
assignee: desktop-bugs → nobody
status: Invalid → Confirmed
Revision history for this message
Cruxic (cruxic) wrote :

Thank you Timo for unmarking it as duplicate!

Rant:
To tell the truth I had kinda given up on it and lost faith in the Ubuntu development process. You have restored my faith to some degree. It just goes to show that care should be taken when reviewing these bug submissions. Users that actually take time to tell you what's not working are of tremendous value (most users silently abandon your software rather than telling you how to fix it.)

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Actually, the mouse capplet should change the X resource database while doing the modification. I'm not sure how to do it permanently though.

Anyway, I don't see how it's an xorg bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's not a gnome-applets bug, gnome-control-center use the gconf value and transform it to a xsetting which should work, reassigning. Does the setting work in GNOME applications? Trying with nautilus on hardy the setting is correctly used there

Changed in gnome-applets:
assignee: nobody → desktop-bugs
status: Confirmed → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!.

Changed in gnome-control-center:
status: Incomplete → Invalid
Revision history for this message
Geoffrey De Smet (ge0ffrey) wrote :

This bug is still present in Ubuntu 8.10, please reopen.

To reproduce: install any java Swing app (for example jedit or something), possibly also set java6-sun as your default java,
open the java app, open the ubuntu mouse configuration and set double click speed to 1000ms, in the java app double click on stuff and notice you have to double click within 200ms

hache (jacheroy)
description: updated
Revision history for this message
Bryce Harrington (bryce) wrote :

Hi cruxic,

Please attach the output of `lspci -vvnn` too.

[This is an automated message. If this script has reached you erroneously, please accept our apologies; any reply to this message will be sufficient to prevent it from doing further automated processing.]

Changed in xorg:
status: New → Incomplete
Revision history for this message
mindseye (aimforstars) wrote :

I'm having trouble with this too, sending requested output (even if it wasn't requested from me). Hope it helps.

The output is in a text file

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

Tried on Jaunty Jackalope 9.04 updated to 4/2 and double-click times do not seem different on jedit and terminal. I am closing the bug as fixed, but if you can provide a way to reproduce it in Jaunty please re-open it.

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

Unable to reproduce.

Changed in xorg-server (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

Next I'd like to forward this issue upstream, but first it must be retested on latest Jaunty to make sure the issue still happens there with the latest code. ISO images are available at http://cdimages.ubuntu.com/daily/current/ - if you can reproduce it in the LiveCD environment, you shouldn't need to modify your installed system. Also please attach a fresh Xorg.0.log from this testing.

Revision history for this message
hache (jacheroy) wrote :

Hi Carlos,

I've tri to do this in a VirtualBox ... but there is a bug with the 9.04 and xorg see the bugs.launchpad.net/ubuntu :Bug #354847
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/354847

have nice day

Jean
> Date: Fri, 3 Apr 2009 03:44:38 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 55270] Re: Double-click timeout is not applied to X
>
> Next I'd like to forward this issue upstream, but first it must be
> retested on latest Jaunty to make sure the issue still happens there
> with the latest code. ISO images are available at
> http://cdimages.ubuntu.com/daily/current/ - if you can reproduce it in
> the LiveCD environment, you shouldn't need to modify your installed
> system. Also please attach a fresh Xorg.0.log from this testing.
>
> --
> Double-click timeout is not applied to X
> https://bugs.launchpad.net/bugs/55270
> You received this bug notification because you are a direct subscriber
> of the bug.

_________________________________________________________________
Sur Windows Live Ideas, découvrez en exclusivité de nouveaux services en ligne... si nouveaux qu'ils ne sont pas encore sortis officiellement sur le marché !
http://ideas.live.com

Revision history for this message
Peng (pengwg) wrote :

For jaunty with latest update as of today the bug still applies to MatlabR2008b and MatlabR2009a.
The workaround works to fix the problem.

Revision history for this message
Colin Law (colin-law) wrote :

I had this problem with jEdit on 8.10 and the workaround (*multiClickTime: 400) in /etc/X11/Xresources/X11-common worked for me. I have now updated to Karmic and the workaround no longer works. Neither did putting it in ~/.Xdefaults. I found that I had to put it in ~/.Xresources for it to work.

jEdit 4.3pre18, Sun java 1.6.0_15

Revision history for this message
mishagam (mishagam) wrote :

Double-clicking still doesn't work for ubuntu 9.10 and netbeans 6.8.
 changing in ~/.Xresources fixed it - thanks
I now believe that change in /etc/X11/Xresources/X11-common would fix it also.
I wonder why it takes several years to change this flag in mouse preferences dialog - may be because /etc/X11 changes things for ALL users and mouse preferences are presumably for ONE user?
May be, but in my opinion making double-click time same for all users is preferable to double-click not working for Java applications like Netbeans.

Revision history for this message
Onni Koskinen (onni) wrote :

The problem exists on Ubuntu 9.10 with both OpenJDK (6b16-1.6.1-3ubuntu1) and Sun Java (6-15-1).
It can be verified with the following program, which outputs "200" regardless of Ubuntu settings. The mentioned workaround can be used to change this to some other value but not to respect Ubuntu double click settings.

class Test { public static void main(String[] args) {
 System.out.println(java.awt.Toolkit.getDefaultToolkit().getDesktopProperty("awt.multiClickInterval"));
}}

Revision history for this message
André Pirard (a.pirard) wrote : Re: [Bug 55270] Java double click

I'm very surprised
- to have just met a double click not working / speed problem making
Java unusable
- to discover that that this problem was reported 4 years ago
- to read comment 1 saying that the bug has already been reported but
without saying where
- to read comment 2 denying comment 1 and lacking a comment 3
- to read users continuing to describe suffering from that problem for 4
years
- to see that the bug report has been flagged with the nice ans thankful
word 'invalid'
- to see that the bug priority is low (at least one goal is achieved)
- to notice that Cruxic has worked out what can be easily turned to a fix
- to have encountered a blatant but invalid problem that I fixed with an
invalid fix
- to lose my time and wonder if the goal is working now or waiting for
Maverick

I'm thanking Cruxic for a wonderful workaround in the Description whose
title advises not to read.

Revision history for this message
Carlos J. Hernández (carlos3.14) wrote :

André:

You seem to get surprised easily.

Lucien (lucienc2000)
Changed in gnome-control-center (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
Lucien (lucienc2000) wrote :

I still have this bug in Ubuntu 10.04 why the status changed to invalid?

Revision history for this message
Sebastien Bacher (seb128) wrote :

don't reopen bugs closed for years, open a new bug if you have a simlilar issue

Changed in gnome-control-center (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
PowerKiKi (adrien-crivelli) wrote :

I dont think the bug is any different now that it used to be 4 years ago. So the bug should stay open IMHO.

Anyway here is the new bug following this still existing issue: https://bugs.launchpad.net/ubuntu/+source/dbus-java/+bug/654526

Also, it was seen on more time in Ubuntu 11.04.

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.