strange behaivor by clicking buttons

Bug #441905 reported by scholli
218
This bug affects 32 people
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Medium
Ubuntu
Invalid
Low
Unassigned
gtk+2.0 (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: ubuntu-desktop

Describtion:

Nautilus: For example the zoom-buttons. Mouse is over the zoom-in-button. By clicking it's zooming in, but if you don't move the mouse, the button-border clears out. So the next click is without reaction. Only a slight moving with the mouse reactivate this button. Various buttons in nautilus haves the same strange behaivor. (go-back, go-up, etc. etc.)

Evolution: If I click on send/recive it's working as usual. But the button-border around clears out - so the next click is without effects. Only if you move the mouse a little bit you get a clickable button again.

I don't know which package is provocating it, but it's affects various programs like nautilus, evolution etc.
It's a uncomfortable bug, because the nautilus-example with the zoom you're clicking fast and continuous for reach your percent of zooming. This bug makes uncomfortable the "goes"-buttons, too. It's making a fast using of those buttons impossible.

It's important to correct it, because with Jaunty I hadn't those problems and I hadn't that cut of usability like in Karmic right now.

ProblemType: Bug
Architecture: i386
Date: Sun Oct 4 04:44:34 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: nautilus 1:2.28.0-0ubuntu4
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: nautilus
Uname: Linux 2.6.31-11-generic i686

Related branches

Revision history for this message
scholli (scholli-tz) wrote :
Revision history for this message
John Doe (jodo-deactivatedaccount) wrote :

Yes, this is extremly nasty. It occours also within Rhytmbox, while hovering over the "Next" Button. I have to move away the mouse befoure I can klick again. Stop this, please.

Revision history for this message
burli (mb-embedit) wrote :

Can confirm this. I tested it with different themes. It happens in all native GTK programs (Nautilus, gedit, Me TV...), but not in Firefox or Qt Applications

Revision history for this message
tankdriver (stoneraider-deactivatedaccount) wrote :

I can confirm this problem at the mobile-broadband setup assistance too.
suggesting to add the package "gtk2-engines" or somewhat to make things quicker.

Revision history for this message
Fred Seidemann (fred-85) wrote :

Same problem here, since I did an update this morning.

Revision history for this message
tankdriver (stoneraider-deactivatedaccount) wrote :

possible Duplicate: Bug #442077

Murat Gunes (mgunes)
Changed in gtk+2.0 (Ubuntu):
importance: Undecided → High
Revision history for this message
skillllllz (bmustafa) wrote :

I can confirm this bug. Anything we can do to help?

Revision history for this message
Dan Andreșan (danyer) wrote :

Same here with eog (Eye of Gnome), clicking Next to browse the pictures doesn't work without waggling the mouse between clicks.

Revision history for this message
Micha Moskovic (micha-mosk) wrote :

I cannot do much to resolve this issue, but I have written a simple test, a window with only a GtkButton which counts the number of clicks.
The bug is apparent in this simple case, namely clicking once works, but clicking again works only if the pointer first leaves the widget. But if I click once, then resize the window, then click again, the button reacts as expected.
You can run the test with “python test_button.py”.

Revision history for this message
Micha Moskovic (micha-mosk) wrote :

The bug also only happens when clicking with the left mouse button: tapping the touchpad on a laptop or pressing the spacebar works as expected.

Revision history for this message
Dan Andreșan (danyer) wrote :

@micha, thanks for the simple script demo-ing the problem.
I just want to make a correction. You said:
"clicking once works, but clicking again works only if the pointer first leaves the widget."

Not true here, clicking again works if I move the pointer even with 1 pixel, while still on the widget, no need to leave it and return.

Changed in ubuntu-meta (Ubuntu):
status: New → Invalid
Revision history for this message
Micha Moskovic (micha-mosk) wrote :

@dan, you’re right, no need to leave the widget, moving the pointer a bit is enough.

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Confirming the issue here too. I just spoke to mclasen on IRC and he's seen this issue too, but hasn't had a chance to work out which recent commit broke it yet, so I'll try to bisect it before I go to bed

Changed in gtk+2.0 (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Here's my full git bisect log:

git bisect start
# bad: [05ded28d7d282bed6de457edeeb3e1461ea0d0ac] Updated Japanese translation
git bisect bad 05ded28d7d282bed6de457edeeb3e1461ea0d0ac
# good: [b841251ca79c332fd9922973b2a40e1298ae7f47] 2.18.0
git bisect good b841251ca79c332fd9922973b2a40e1298ae7f47
# bad: [6fef640debbe468586ff866cbef38d7a29c452d1] Only select for button and pointer event on toplevels
git bisect bad 6fef640debbe468586ff866cbef38d7a29c452d1
# good: [06c208f8f1db10fc46ea44dc06fdd92b76467b4f] Updating Estonian translation
git bisect good 06c208f8f1db10fc46ea44dc06fdd92b76467b4f
# good: [f2d9f5a9e6d4d9d3de1510b39d9a0ce0a976a4b3] Remove unused variable
git bisect good f2d9f5a9e6d4d9d3de1510b39d9a0ce0a976a4b3
# bad: [e81501ebea4cceffce2890519807b0c243fec0a3] Sent button events don't cause passive grabs
git bisect bad e81501ebea4cceffce2890519807b0c243fec0a3
# bad: [5ebb32d1ffa23241d562fb4d5be02bc6f156b515] Extend _gdk_windowing_window_at_pointer to be able to get toplevels only
git bisect bad 5ebb32d1ffa23241d562fb4d5be02bc6f156b515
# good: [fe188a18f324f4545af857436a6060e676a1287d] Bug 596494 - New property "cursor" in 2.18's GdkWindow with wrong type?
git bisect good fe188a18f324f4545af857436a6060e676a1287d

And the bad commit:

5ebb32d1ffa23241d562fb4d5be02bc6f156b515 is first bad commit
commit 5ebb32d1ffa23241d562fb4d5be02bc6f156b515
Author: Alexander Larsson <email address hidden>
Date: Mon Sep 28 15:21:54 2009 +0200

    Extend _gdk_windowing_window_at_pointer to be able to get toplevels only

    This has two advantages:
    1) In many backends, this is faster as we can terminate the window
    hierarchy traversal earlier
    2) When used in gdkdisplay.c::get_current_toplevel() to get the
    current toplevel that has the pointer we now correctly return
    a toplevel with the pointer in it where the pointer is inside
    some foreign subwindow of a toplevel window.

    The second advantage fixes some bugs in client side event generation
    when the pointer is inside such a foreign child window.

:040000 040000 0bf878a4bdc90edc26e1fabca17810153eab556d 3b77b97a97805a1fe60cee79033e1a7fec10bdb6 M gdk

Revision history for this message
Murat Gunes (mgunes) wrote :

Moving to "Triaged" as per Chris' comment.

Changed in gtk+2.0 (Ubuntu):
status: Confirmed → Triaged
affects: ubuntu-meta (Ubuntu) → ubuntu
Changed in ubuntu:
importance: Undecided → Medium
importance: Medium → Low
summary: - [Karmic] strange behaivor by clicking buttons
+ strange behaivor by clicking buttons
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This is fixed upstream now

Changed in gtk+2.0 (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
skillllllz (bmustafa) wrote :

Yay!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gtk+2.0 - 2.18.1-1ubuntu1

---------------
gtk+2.0 (2.18.1-1ubuntu1) karmic; urgency=low

  * debian/patches/091_git_change_fix_coordinates_issue.patch:
    - git change fixing coordinate issues leading to multiple clicks on a button
      not working until moving the cursors (lp: #441905)

 -- Sebastien Bacher <email address hidden> Mon, 05 Oct 2009 15:08:51 +0200

Changed in gtk+2.0 (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
scholli (scholli-tz) wrote :

Thanks for everybody. This was solved fast and the usability is muchhhh better now. Thanks

Revision history for this message
Dale Trombley (buzzmandt) wrote :

this is still happening for me, what's worse is I'm running kubuntu
happens in kpatience and even in wine playing diablo 2

should i start a new bug under kubuntu?

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

If it's happening in kpatience and wine, then it's completely unrelated to this issue

Revision history for this message
Sergey Sedov (serg-sedov) wrote :

After latest updates it works well for me (Gnome apps).

Revision history for this message
RJ Moore (urgemore) wrote :

I just updated my Dell Latitude D600 from Ubuntu 9.04 to 9.10 a couple days ago, and this problem has manifested. Clicks, while they do affect the visual state of buttons, etc., aren't acted on until I move the mouse. This also happens on links in firefox (3.5.4), and even sometimes when I hit <Enter> on the keyboard to activate an 'OK' button (noticed while playing nethack, tile mode, in wine). None of these problems were experienced in 9.0.4.

Changed in gtk+2.0 (Ubuntu):
status: Fix Released → Fix Committed
status: Fix Committed → Fix Released
Changed in gtk:
importance: Unknown → Medium
status: Unknown → Fix Released
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.