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 441266 - Extra focus event being fired by gnome-panel
Extra focus event being fired by gnome-panel
Status: RESOLVED DUPLICATE of bug 308632
Product: gnome-panel
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks: 374749
 
 
Reported: 2007-05-25 19:20 UTC by Luiz Rocha
Modified: 2007-09-02 14:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Luiz Rocha 2007-05-25 19:20:57 UTC 
There is an extra state-changed event being fired from gnome-panel, when pressing a taskbar menu item (System, Places, Applications) after clicking or drag-n-dropping an app icon to the taskbar.

Steps to reproduce:
  1. drag any icon (like, f-spot or dia) to the top panel in any place
     or press an existing one,
  2. go straight to Places menu and pressed it.

Among the events fired by gnome-panel, there is a state-changed event that shouldn't be there:

object:state-changed:focused(1, 0, None)
  source: [push button | Dia Diagram Editor
 Edit your Diagrams]
  application: [application | gnome-panel]

Checking the gnome-panel code, I found no calls to atk_object_notify_state_change.

Found this investigating bug # 374749.
Comment 1 Li Yuan 2007-08-17 06:27:41 UTC 
I can see this. But at the same time you may find that when you click the "Place" menu, the first icon (probably Dia Diagram Editor) shows the focus indicator. This means something happens in GUI. So probably gnome-panel's bug.
Comment 2 Li Yuan 2007-08-17 06:29:49 UTC 
Transfer to gnome-panel to see if they have any idea about this.
Comment 3 Vincent Untz 2007-09-02 14:45:47 UTC 
That's a known panel bug that has been here for ages. Help to fix it is welcome.

*** This bug has been marked as a duplicate of 308632 ***