Buttons can't be clicked after the window was set to insensitive

[JonathanTurner]

The search button will ignore a click (to perform a second search) after a
search has been performed, until the user moves away from the search button and
then moves back over it.

Steps to reproduce:

.) Click the search button, but do not move the mouse
.) Type something into the search popup and hit enter
.) After the search results come back, since the mouse is still over the search
button, click again

Results:

.) The button is still depressed and will not allow a click

Expected results:

.) The button allows the user to click again

[Michael Vogt (mvo)]

I can't reproduce this on my two hoary installs. What version of ubuntu and
synaptic do you use?

thanks,
 Michael

[JonathanTurner (probata)]

(In reply to comment #1)
> I can't reproduce this on my two hoary installs. What version of ubuntu and
> synaptic do you use?
>
> thanks,
> Michael

I've reproduced it on both of my hoary installs. Using synaptic 0.56+cvs one
from a week ago and one from today.

Make sure you don't move the mouse from being over the search button and you
only type and hit enter in the search popup. After the search finishes your
mouse will still be over the search button, and you won't be able to click.

[Michael Vogt (mvo)]

(In reply to comment #2)
> (In reply to comment #1)
> > I can't reproduce this on my two hoary installs. What version of ubuntu and
> > synaptic do you use?
>
> I've reproduced it on both of my hoary installs. Using synaptic 0.56+cvs one
> from a week ago and one from today.
>
> Make sure you don't move the mouse from being over the search button and you
> only type and hit enter in the search popup. After the search finishes your
> mouse will still be over the search button, and you won't be able to click.

Sorry still no luck. What I did was:
1. Started synaptic
2. Clicked on the Search button in the toolbar
3. entered something into the entries filed and hit <enter>
4. after the search was finished the mouse was still over the search button and
it did not moved
5. clicking again did pop-up the search field.

Do you get a different result? Or did I just not took the right steps to
reproduce the problem?

thanks,
 Michael

[JonathanTurner (probata)]

> Sorry still no luck. What I did was:
> 1. Started synaptic
> 2. Clicked on the Search button in the toolbar
> 3. entered something into the entries filed and hit <enter>
> 4. after the search was finished the mouse was still over the search button and
> it did not moved
> 5. clicking again did pop-up the search field.
>
> Do you get a different result? Or did I just not took the right steps to
> reproduce the problem?

Those are exactly the steps, only #5 doesn't work here as the button won't let
me click. Could this be a versioning issue with some of the underlying sdks/etc?

[Michael Vogt (mvo)]

(In reply to comment #2)
> (In reply to comment #1)
[..]
> Those are exactly the steps, only #5 doesn't work here as the button won't let
> me click. Could this be a versioning issue with some of the underlying sdks/etc?

I use a up-to-date hoary with the standard "human" theme. It may be interessting
to see if changing your theme to human has any effect on this bug.

[JonathanTurner (probata)]

(In reply to comment #5)
> (In reply to comment #2)
> > (In reply to comment #1)
> [..]
> > Those are exactly the steps, only #5 doesn't work here as the button won't let
> > me click. Could this be a versioning issue with some of the underlying
sdks/etc?
>
> I use a up-to-date hoary with the standard "human" theme. It may be interessting
> to see if changing your theme to human has any effect on this bug.

I'm using a standard Human theme, also. For kicks I switched it to Industrial
and half a dozen other themes but to no luck.

I'm also using the up-to-date hoary.

[reh4c (gene-hoffler)]

I've got the same problem (inability to hit search button again without "tapping" somewhere else
first). I'm using hoary array 6 on an AMD64 laptop-Gateway 7405GX with a synaptics touchpad.

[Bill Farner (terasurfer)]

Same problem here, i386, hoary. However, it happens any time synaptic is 'busy'
with something else. It seems as though the buttons are disabled (not visibly)
while another operation is executing (such as the database loading), and are
afterwards only clickable when the mouse moves onto the button (i.e. not if the
mouse is already over it).

Additional steps to reproduce:
1. Launch Synaptic.
2. Move mouse over any (active) toolbar button, before initial database loading
completes.
3. Try to click the button once loading completes.

[Michael Vogt (mvo)]

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

[Michael Vogt (mvo)]

It looks the problem is only reproducable when the focus policy
(System/Preferences/Windows) is not set to "Select windows when the mouse moves
over them". This is what I use on all my machines and that's why I wasn't able
to reproduce the problem.

It looks like a gtk/metacity problem to me, but I'll look more deeply into it
now that I can reproduce it.

[Michael Vogt (mvo)]

Just some additional data:
I can reproduce it with "metacity, icewm and xfce"

[Michael Vogt (mvo)]

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

[P (p92)]

I also have this annoying behaviour. I feel it is a general gtk problem, because qt applications do not have this behaviour. konqueror for example always allows
me to click on a button that was inactive when I put the mouse on it.

I am using breezy and ii synaptic 0.57.2-1 Graphical package manager

[Manu Cornet (lmanul)]

Same problem here, with an up-to-date breezy and synaptic 0.57.4ubuntu6

[Michael Vogt (mvo)]

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

[Michael Vogt (mvo)]

Small Test-case in pygtk to demonstrate the problem. Use metacity in "click-to-focus" mode and after the initial click a second click won't work.

[Sebastien Bacher (seb128)]

Michael, that's a duplicate of bug #22930 (http://bugzilla.gnome.org/show_bug.cgi?id=56070 upstream)