GTK+ buttons not clickable if the window loses focus

*** Bug 14754 has been marked as a duplicate of this bug. ***

*** Bug 14755 has been marked as a duplicate of this bug. ***

I can confirm that this bug exists and has existed since at least 3/3/2005
hoary. For example, using Synaptic, after closing one of it's child windows
(such as just after an install), I am unable to click on the Search button if
the mouse is moved to it too soon. Th e button will be active/available, but I
must move the mouse away from it before moving the mouse back to it. Once this
is done, the rounded cornered square will appear around it, indicating that it
is ready to be pressed. (This rounded cornered square would not have appeared
prior to moving the mouse away from it). Hope this clarifies things.

this is sadly a issue with GTK, i'm trying to track it since a (pre ubuntu)
while, but the problem is that here for me this occurs only on one of 3
machines, so its not reliable reproducable.

Well, this happens 100% of the time on my PC, so if anyone needs any tests
performing - debugging enabled, etc, I'll do my best.

Happens here also. If you hover over a button before it's enabled, you have to
move it away from the button before you can click it when it becomes enabled.
Notice it mostly in synaptic.

Could it be apps that you run with gksudo?

hwdb doesnt run (and shouldnt be run) with gksudo, this is sadly a gtk issue not
an application issue

waiting for gtk 2.8

How can we be sure it is a GTK issue please? Thanks.

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

It appears that someone gave this bug the header of ...

"GTK+ buttons not clickable if the window loses focus"

 The window is still in focus and never left focus. It is the install
window and there are no other windows involved, opened, or even possible
of being opened. It is not a result of change of focus. This bug only
takes place during the installation (asking you what login, password,
time settings, what drive to install to... etc...).

Since it is during the install process... I can not take a capture
snapshot for you.

It only happens on a windows where one can accept the defaults.
Specifically - if this is a re-install then GTK+ will present suggested
defaults for the Time Setting window. My location is New York .. so when
the clickable map comes up ... if "New York" is already given as a
suggested default by GTK+ ... I need not move the mouse at all (to click
the map and select a different location) ... all I need do is click the
[Forward] button and move on to the next install screen...

BUT - because I had clicked the [Forward] button on the windows that was
before the Time Settings window - and had not moved my mouse cursor at
all - my cursor is positioned ON the [Forward] button of the Time
Setting windows... already. Clicking [Forward] now does nothing.
Broken.

I must first move my mouse cursor OFF of the [Forward] button and then
back on to the [Forward] button - before clicking it will work.

I know this is difficult to understand. Let me say it in different
words.

---------
IF (when going screen to screen during the installation steps)
      the [Forward] button is drawn under the location of the mouse
cursor...
      the mouse cursor must be moved off of the [Forward] button and
then back onto the [Forward] button or the [Forward] button will not be
clickable.
---------

-ray

On Mon, 2007-03-12 at 11:52 +0000, Laurent Bigonville wrote:

> *** This bug is a duplicate of bug 22930 ***
>
> See upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=56070
>

Jeez, Ray, don't you see this bug is marked as a dupe? Did you care to check the description for bug #22930? It says "Mouse focus doesn't return until mouse is moved off button". Doesn't its description reflect the problem?

Please be nice. He was just trying to help, and launchpad is often far from easy to navigate.

My apologies ... no, I am not familiar with the process. I am very new
to Ubuntu and Linux in general. Please don't be offended. We were all
'newbies' at some point. It is my turn to be the newbie. I will make
mistakes.

-ray

On Mon, 2007-03-12 at 19:37 +0000, Rimas Kudelis wrote:

> *** This bug is a duplicate of bug 22930 ***
>
> Jeez, Ray, don't you see this bug is marked as a dupe? Did you care to
> check the description for bug #22930? It says "Mouse focus doesn't
> return until mouse is moved off button". Doesn't its description reflect
> the problem?
>

Typing has no 'tone'. The interpretation of not-nice can be in the mind
of the reader. My description was not intended to be anything other than
nice - while trying to zero in on things (it seemed to me that the
problems was being misunderstood).

I am surprised that I have gotten two emails now where it seems my
further description was interpreted as caustic. Believe me - it was not
intended to be. It was intended to zero in better on the problem as it
seemed to me (a newbie) that it was mistakenly being thought of as a
problem of window focus.

It maybe that I misunderstand the term 'focus' as used. Focus is when
two or more windows are open and one of them is 'focus' (the active
window engaged by cursor action) ... yes?

Anyways .. my apologies to anyone who has been offended in anyway.
Misunderstandings can happen when there is no 'tone' ... this has been
one.

Thank you all for your voluntary efforts to improve Ubuntu. We are all
extremely grateful.

-ray

On Mon, 2007-03-12 at 20:17 +0000, Murray Cumming wrote:

> *** This bug is a duplicate of bug 22930 ***
>
> Please be nice. He was just trying to help, and launchpad is often far
> from easy to navigate.
>

I'm not offended, sorry for my tone. It's just that recieving long comments that make no use is sometimes annoying.

Anyways, rkaliss, good luck with Ubuntu. Here's one lesson for you: always look at "This report is a duplicate of bug #*****" header at the top of a bugreport page. The description of main bug (to which others ared duped to) often describes the problem much better than its duplicates.

Have a good day! :)

rkallis, my comment was not directed at you. Thanks for the contribution.

Thanks for your understanding and your tip is much appreciated.

-ray

On Tue, 2007-03-13 at 08:38 +0000, Rimas Kudelis wrote:

> *** This bug is a duplicate of bug 22930 ***
>
> I'm not offended, sorry for my tone. It's just that recieving long
> comments that make no use is sometimes annoying.
>
> Anyways, rkaliss, good luck with Ubuntu. Here's one lesson for you:
> always look at "This report is a duplicate of bug #*****" header at the
> top of a bugreport page. The description of main bug (to which others
> ared duped to) often describes the problem much better than its
> duplicates.
>
> Have a good day! :)
>

You *all* have my admiration and gratitude for what you do.

-ray

On Tue, 2007-03-13 at 09:03 +0000, Murray Cumming wrote:

> *** This bug is a duplicate of bug 22930 ***
>
> rkallis, my comment was not directed at you. Thanks for the
> contribution.
>