After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 52047 - a button does not respond to mouse
a button does not respond to mouse
Status: RESOLVED FIXED
Product: gnome-session
Classification: Core
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on: 56070
Blocks:
 
 
Reported: 2001-03-12 22:55 UTC by Manuel Clos
Modified: 2006-11-07 19:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10



Description Manuel Clos 2001-03-12 22:55:33 UTC
If a button appears just under the mouse, it won't get an enter event,
and it would not respond to a "click", leaving the mouse and entering
again solves it.

Very annoying in the gnome logout window :).
Comment 1 Owen Taylor 2001-03-14 19:27:08 UTC
I don't believe this is general (try it, for example, with
testgtk), I believe it is specific to the way that the
GNOME logout screen works by grabbing the pointer and keyboard
to an off-screen invisible window, then moving the
grab back to the toplevel of the logout window when
the window is mapped. (See comments in the source code.)

You might want to try changing the owner_events field in
the first call to gdk_pointer_grab in gsm/logout.c from
FALSE to TRUE; that might possibly fix the problem.
Comment 2 Luis Villa 2002-01-28 19:36:36 UTC
Manuel: does the suggested fix (or a newer version of gsm) fix the
problem?
Comment 3 Manuel Clos 2002-01-28 19:49:16 UTC
I'm currently using gnome-core version: 1.4.0.4-ximian.11

It still happens. This is not a problem with gsm but with gtk. I
filled a bug for GTK with a demo program. The problem is that if a
widget is enabled after the mouse is over it, it doesn't seem to get
enter event.
Comment 4 Manuel Clos 2002-01-28 19:52:30 UTC
Please, see:

http://bugzilla.gnome.org/show_bug.cgi?id=56070

for more info.

Probably you want to close this bug, or even better, make it depend on
56070, so that when 56070 is closed we can come back to see if this
problem is solved.
Comment 5 Kjartan Maraas 2002-04-26 21:09:45 UTC
Adding GNOME2 keyword to make sure it's fixed there.
Comment 6 Luis Villa 2002-05-14 22:51:41 UTC
Manuel: aren't you running g2 now? is this still a problem?
Comment 7 Manuel Clos 2002-05-14 23:58:34 UTC
I still use gnome1 for daily work. I tested in gnome2 and it still
happens.

Basically this bug is: http://bugzilla.gnome.org/show_bug.cgi?id=56070

So this bug can be closed, as it is not gsm fault but gtk.

Closing bug.
Comment 8 Manuel Clos 2003-08-02 15:31:24 UTC
I closed bug 56070, but this problem is still there with gnome 2.3.3.

Reopening the bug.
Comment 9 Kjartan Maraas 2003-09-22 09:21:09 UTC
Moving this to gnome-session where it belongs. I can still reproduce
this with 2.4.0...
Comment 10 Vincent Noel 2004-07-22 14:28:41 UTC
This is still present in gnome-session 2.7
Comment 11 Ray Strode [halfline] 2006-11-07 19:43:11 UTC
So owen's proposed fix comment 1 works.

commited to both head and 2-16

2006-11-07  Ray Strode  <rstrode@redhat.com>

        Fix bug where clicking logout button doesn't work if
        mouse pointer happens to be on top of the button when
        the window is mapped (bug 52047)

        * logout.c (display_gui): set owner_events to TRUE in
         grab pointer call