Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 72395 - double-click timeout is too long when shading unshading windows
double-click timeout is too long when shading unshading windows
Product: Red Hat Linux
Classification: Retired
Component: metacity (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Havoc Pennington
: MoveUpstream, Triaged
Depends On:
Blocks: 67218 79579
  Show dependency treegraph
Reported: 2002-08-23 10:19 EDT by Ted Clark
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-01-12 17:14:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Ted Clark 2002-08-23 10:19:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.0 (X11; Linux i686; U;) Gecko/20020408

Description of problem:
See problem description at URL above.

Ted Clark <bison@visi.com> writes:
> I've noticed that double-clicking a window titlebar to shade/unshade a
> window with metacity only works intermittently.  I'd say it fails
> about 15% of the time, rough guess.  Anyone else having this
> problem?

I think the issue is perhaps just a long double-click timeout. The
timeout in Preferences->Mouse should be used here. If I change timeout
to 0.2 seconds or so things work a lot more consistently for me.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. rapidly double-click window titlebar.

Actual Results:  Windows doesn't always shade/unshade.

Expected Results:  Window should always shade/unshade.

Additional info:
Comment 1 Havoc Pennington 2003-01-12 17:14:40 EST
Moved to http://bugzilla.gnome.org/show_bug.cgi?id=103218

Note You need to log in before you can comment on or make changes to this bug.