GNOME Bugzilla – Bug 371006
gtk_dialog_run - buttons cannot be clicked after dialog is closed
Last modified: 2010-06-15 15:05:25 UTC
I'm experiencing the following very annoying behavior in many gtk applications that show dialogs (message, input, etc...): Opening a dialog (with gtk_dialog_run) and closing it by a keyboard action returns the focus to the main window, but leaves the widget over which the mouse cursor is positioned in a broken state (in case of a button, it cannot be clicked). Steps to reproduce (Synaptic application) 1. click Search or press CTRL+F 2. move the mouse cursor over any of the buttons (in the toolbar or others) 3. close the search dialog with a keyboard action (press Escape). You then cannot click the button your mouse cursor is over, you have to move the cursor out and then back over the button. (can be reproduced in many gtk+ application that use dialogs) I think the gtk_dialog_run() function should send a signal to the window it returns control (focus), maybe the enter_notify signal, on finish.
We are seeing the same behavior in Wireshark for Windows (but not Unix) and are tracking it as bug number 1003 (http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1003). I have personally noticed a similar behavior in Emacs for X/Unix with the close file button ("X") at times.
I don't think it just in dialogs. Try this in synaptic... 1. Click "mark all upgrades" 2. Keep mouse over the "mark all upgrades" button. No dialog is shown, but when focus returns, you cannot click the "mark all upgrades" button again until you move the mouse out and back over the button.
This is something that I consider a very serious bug and it's been a problem for a very long time. Given that there are probably many duplicates, or probably this one is a duplicate of some other. I have experienced this bug especially when clicking through wizards (do we still call them Druids in GNOME?).
This is a duplicate of Bug 56070 – Can't click button after setting it sensitive. Can someone with power to do so mark it as such?
ping
I can't reproduce this here (GTK+ 2.20.1) What GTK+ version are you using?
Javier, If you read the bug history carefully you can see that it's already been said that this bug is a duplicate of a closed bug. It just needs to be marked as such.
Sure, the Alberto's ping confused me *** This bug has been marked as a duplicate of bug 56070 ***