Bug 678310 – Warnings about unknown listeners

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 678310 - Warnings about unknown listeners


Summary:	Warnings about unknown listeners


Status:	RESOLVED DUPLICATE of bug 678475

Product:	atk
Classification:	Platform
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	ATK maintainer(s)
QA Contact:	ATK maintainer(s)

URL:
Whiteboard:

Duplicates:	678404 (view as bug list)
Depends on:
Blocks:

Reported:	2012-06-18 11:38 UTC by Bastien Nocera
Modified:	2012-06-22 16:15 UTC

See Also:
GNOME target:	3.6
GNOME version:	---

Description Bastien Nocera 2012-06-18 11:38:51 UTC

gnome-control-center, at-spi2-atk, clutter, clutter-gtk, gtk+ from master

Running:
NO_AT_BRIDGE=1 gnome-control-center
Removes all the warnings.

(gnome-control-center:18893): Clutter-WARNING **: No listener with the specified listener id 2.

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff4d22a81 in g_logv (log_domain=0x7ffff6fe640e "Clutter", log_level=G_LOG_LEVEL_WARNING, format=0x7ffff6fe6418 "No listener with the specified listener id %d", args1=0x7fffffffd058) at gmessages.c:758
758			G_BREAKPOINT ();
(gdb) bt

+ Trace 230382

#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 atk_remove_global_event_listener
at atkutil.c line 260
#4 spi_atk_deregister_event_listeners
at event.c line 1233
#5 tally_event_reply
at bridge.c line 95
#6 get_device_events_reply
at bridge.c line 169
#7 ??
from /lib64/libdbus-1.so.3
#8 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#9 ??
from /lib64/libatspi.so.0
#10 g_main_dispatch
at gmain.c line 2539
#11 g_main_context_dispatch
at gmain.c line 3075
#12 g_main_context_iterate
at gmain.c line 3146
#13 g_main_context_iteration
at gmain.c line 3207
#14 g_application_run
at gapplication.c line 1607
#15 main
at control-center.c line 256
#0 g_logv
at gmessages.c line 758
#1 g_log
at gmessages.c line 792
#2 g_return_if_fail_warning
at gmessages.c line 801
#3 g_hash_table_remove_internal
at ghash.c line 1267
#4 g_hash_table_remove
at ghash.c line 1302
#5 cally_util_remove_key_event_listener
at ./cally/cally-util.c line 258
#6 atk_remove_key_event_listener
at atkutil.c line 304
#7 spi_atk_deregister_event_listeners
at event.c line 1240
#8 tally_event_reply
at bridge.c line 95
#9 get_device_events_reply
at bridge.c line 169
#10 ??
from /lib64/libdbus-1.so.3
#11 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#12 ??
from /lib64/libatspi.so.0
#13 g_main_dispatch
at gmain.c line 2539
#14 g_main_context_dispatch
at gmain.c line 3075
#15 g_main_context_iterate
at gmain.c line 3146
#16 g_main_context_iteration
at gmain.c line 3207
#17 g_application_run
at gapplication.c line 1607
#18 main
at control-center.c line 256
#0 g_logv
at gmessages.c line 758
#1 g_log
at gmessages.c line 792
#2 g_return_if_fail_warning
at gmessages.c line 801
#3 g_hash_table_size
at ghash.c line 1609
#4 cally_util_remove_key_event_listener
at ./cally/cally-util.c line 262
#5 atk_remove_key_event_listener
at atkutil.c line 304
#6 spi_atk_deregister_event_listeners
at event.c line 1240
#7 tally_event_reply
at bridge.c line 95
#8 get_device_events_reply
at bridge.c line 169
#9 ??
from /lib64/libdbus-1.so.3
#10 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#11 ??
from /lib64/libatspi.so.0
#12 g_main_dispatch
at gmain.c line 2539
#13 g_main_context_dispatch
at gmain.c line 3075
#14 g_main_context_iterate
at gmain.c line 3146
#15 g_main_context_iteration
at gmain.c line 3207
#16 g_application_run
at gapplication.c line 1607
#17 main
at control-center.c line 256
#0 g_logv
at gmessages.c line 758
#1 g_log
at gmessages.c line 792
#2 g_return_if_fail_warning
at gmessages.c line 801
#3 g_hash_table_destroy
at ghash.c line 1047
#4 cally_util_remove_key_event_listener
at ./cally/cally-util.c line 264
#5 atk_remove_key_event_listener
at atkutil.c line 304
#6 spi_atk_deregister_event_listeners
at event.c line 1240
#7 tally_event_reply
at bridge.c line 95
#8 get_device_events_reply
at bridge.c line 169
#9 ??
from /lib64/libdbus-1.so.3
#10 dbus_connection_dispatch
from /lib64/libdbus-1.so.3
#11 ??
from /lib64/libatspi.so.0
#12 g_main_dispatch
at gmain.c line 2539
#13 g_main_context_dispatch
at gmain.c line 3075
#14 g_main_context_iterate
at gmain.c line 3146
#15 g_main_context_iteration
at gmain.c line 3207
#16 g_application_run
at gapplication.c line 1607
#17 main
at control-center.c line 256

Continuing.

Comment 1 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-06-18 12:51:54 UTC

(In reply to comment #0)
> gnome-control-center, at-spi2-atk, clutter, clutter-gtk, gtk+ from master
> 
> Running:
> NO_AT_BRIDGE=1 gnome-control-center
> Removes all the warnings.

FWIW, if you have any AT running, like Orca, you don't have those warnings.

And something offtopic but worth to mention: it seems that the way to avoid not having events registered is deregister if you don't have any client (AT) at that moment (in this bug, the problem is that it tries to unload to the wrong AtkUtil implementation). Wondering if it would be possible to just not register to the events if no AT is listening when the bridge is initialized.

Comment 2 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-06-20 08:24:56 UTC

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

Comment 3 Alejandro Piñeiro Iglesias (IRC: infapi00) 2012-06-22 16:15:14 UTC

Bug 678475 solved all those warnings (although not with the solution I have in mind). Closing as duplicate.

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