gtk.Button unable to be clicked after becoming sensitive

[Robert Ancell]

Hi,

I have found a bug in GTK+ in which you are unable to click buttons that have changed from insensitive to sensitive. To be able to click on them you must move the pointer outside the button and then enter it again.

I am using Ubuntu 5.10 (libgtk2.0-0 version 2.8.6-0ubuntu2.1).

Repeatable: Always

Use case: An application has buttons that become insensitive after being clicked due to a busy state machine. They become sensitive when the request is processed - if this is very fast then the user cannot click a second time without having to move the mouse outside of the button first.

Examples: Find attached a pygyk and C program that exhibit this behaviour.

This is probably related to another bug in which occurs when buttons are created under the pointer. For instance when logging out of Gnome I have become so used to moving the mouse to the OK button that when it appears it is created under the mouse pointer. You then need to move the pointer outside the button then return it to be able to click.

Thanks,
--Robert Ancell

[Robert Ancell (robert-ancell)]

Click on the button and you will be unable to click it a second time until the pointer has left the button.

[Robert Ancell (robert-ancell)]

See comments for pygtk version

[Robert Ancell (robert-ancell)]

I think this is a duplicate of Gnome bugs 56070, 327463 (and the piles of duplicate bugs they keep closing).

I don't know enough about the internals of GTK+ but the comments on Gnome Bugzilla indicate the problem may be to do with the button X window not receiving events when it is insensitive - so shouldn't it always receive events and just not act on them when the user has made it insensitive? Thus the button keeps the "sensitive" state and GDK/X keep processing events as normal.

Note about Malone/Launchpad - It is very hard to find existing bugs on main page - I want to just type in GTK+ somewhere and get a list of them.

[Daniel Holbach (dholbach)]

Thanks for your comments, your test program and the investigation you put into it. This bug was already reported as https://launchpad.net/distros/ubuntu/+source/gtk+2.0/+bug/22930

[Daniel Holbach (dholbach)]

I followed up on the other bug with a pointer to your information and will close this one as a duplicate.