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 678404 - "Clutter-WARNING **: No listener with the specified listener id 2"
"Clutter-WARNING **: No listener with the specified listener id 2"
Status: RESOLVED DUPLICATE of bug 678310
Product: gtk+
Classification: Platform
Component: .General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-06-19 13:06 UTC by Guillaume Desmottes
Modified: 2012-06-20 08:28 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Guillaume Desmottes 2012-06-19 13:06:04 UTC
I just updated my jhbuild gtk+ to master and now get these errors when starting any Clutter app (like totem or empathy built with champlain).

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 2

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 3

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 4

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 5

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 6

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 7

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 8

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 9

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 10

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 11

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 12

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 13

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 14

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 15

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 16

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 17

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 18

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 19

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 20

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 21

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 22

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 23

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 24

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 25

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 26

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 27

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 28

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 29

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 30

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 31

(empathy:6933): Clutter-WARNING **: No listener with the specified listener id 32

(empathy:6933): GLib-CRITICAL **: g_hash_table_remove_internal: assertion `hash_table != NULL' failed

(empathy:6933): Clutter-WARNING **: Not able to remove listener with id 1

(empathy:6933): GLib-CRITICAL **: g_hash_table_size: assertion `hash_table != NULL' failed


Here is the trace of the first warning:


  • #0 g_logv
    at gmessages.c line 758
  • #1 g_log
    at gmessages.c line 792
  • #2 cally_util_remove_global_event_listener
    at cally/cally-util.c line 222
  • #3 cally_util_remove_global_event_listener
    at cally/cally-util.c line 192
  • #4 atk_remove_global_event_listener
    at atkutil.c line 263
  • #5 spi_atk_deregister_event_listeners
    at event.c line 1233
  • #6 tally_event_reply
    at bridge.c line 95
  • #7 get_device_events_reply
    at bridge.c line 169
  • #8 complete_pending_call_and_unlock
    at dbus-connection.c line 2308
  • #9 dbus_connection_dispatch
    at dbus-connection.c line 4593
  • #10 message_queue_dispatch
    at atspi-gmain.c line 97
  • #11 g_main_dispatch
    at gmain.c line 2539
  • #12 g_main_context_dispatch
    at gmain.c line 3075
  • #13 g_main_context_iterate
    at gmain.c line 3146
  • #14 g_main_context_iteration
    at gmain.c line 3207
  • #15 g_application_run
    at gapplication.c line 1607
  • #16 main
    at empathy.c line 845

Comment 1 Emmanuele Bassi (:ebassi) 2012-06-19 13:10:17 UTC
I think this is the result of the work in bug 675183
Comment 2 Matthias Clasen 2012-06-20 00:17:10 UTC
it is a clutter warning. 
why did you file this against gtk ?
Comment 3 Jasper St. Pierre (not reading bugmail) 2012-06-20 01:34:59 UTC
Because it happened when updating GTK+?
Comment 4 Guillaume Desmottes 2012-06-20 07:49:32 UTC
Yes and because the trace seems to point to the new a11y code in Gtk+.
If I'm wrong my bad and just re-assign the bug.
Comment 5 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-06-20 08:24:56 UTC
(In reply to comment #1)
> I think this is the result of the work in bug 675183

I don't think so. Some reasons:
  * That happened before the work on that bug
  * Most of those warnings are about global event listeners not key event listeners

And as I told Emmanuele on IRC, Bastien already found this on gnome-control-center some days ago. Closing as a duplicate.

*** This bug has been marked as a duplicate of bug 678310 ***
Comment 6 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-06-20 08:28:24 UTC
(In reply to comment #0)
> I just updated my jhbuild gtk+ to master and now get these errors when starting
> any Clutter app (like totem or empathy built with champlain).

FWIW, I don't think that this happens with any Clutter app, but with any clutter-gtk app.