Bug 350933 – Critical warning with accessibility enabled

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 350933 - Critical warning with accessibility enabled


Summary:	Critical warning with accessibility enabled


Status:	RESOLVED FIXED

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

Importance:	Normal normal
Target Milestone:	---
Assigned To:	bill.haneman
QA Contact:	bill.haneman

URL:
Whiteboard:

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

Reported:	2006-08-11 18:07 UTC by Don Scorgie
Modified:	2006-09-25 16:11 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Attachments
patch to prevent this warning/error (1.38 KB, patch) 2006-09-25 16:10 UTC, bill.haneman	committed	Details \| Review

Description Don Scorgie 2006-08-11 18:07:30 UTC

On occasion, gedit spews many critical warnings with accessibility enabled:
** (gedit:17136): CRITICAL **: get_label_from_notebook_page: assertion `GTK_IS_WIDGET (child)' failed

I haven't found a reliable way to reproduce it, but have noticed it quite often when there are no tabs open (when gaining focus, it dumps 4 or so warnings to screen.  When loosing focus, it dumps 1 warning).

Using Ubuntu Dapper

A stack-trace from breaking on g_log:

+ Trace 70255

#0 IA__g_log
at gmessages.c line 516
#1 IA__g_return_if_fail_warning
at gmessages.c line 532
#2 gail_notebook_page_get_type
from /usr/lib/gtk-2.0/modules/libgail.so
#3 gail_notebook_page_new
from /usr/lib/gtk-2.0/modules/libgail.so
#4 atk_object_get_name
from /usr/lib/libatk-1.0.so.0
#5 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#6 gnome_accessibility_module_shutdown
from /usr/lib/gtk-2.0/modules/libatk-bridge.so
#7 signal_emit_unlocked_R
at gsignal.c line 2404
#8 IA__g_signal_emit_valist
at gsignal.c line 2197
#9 IA__g_signal_emit
at gsignal.c line 2241
#10 atk_object_notify_state_change
from /usr/lib/libatk-1.0.so.0
#11 gail_widget_new
from /usr/lib/gtk-2.0/modules/libgail.so
#12 IA__g_cclosure_marshal_VOID__BOOLEAN
#13 IA__g_closure_invoke
at gclosure.c line 490
#14 signal_emit_unlocked_R
at gsignal.c line 2438
#15 IA__g_signal_emit_valist
at gsignal.c line 2197
#16 IA__g_signal_emit_by_name
at gsignal.c line 2265
#17 gail_widget_new
from /usr/lib/gtk-2.0/modules/libgail.so
#18 gail_widget_new
from /usr/lib/gtk-2.0/modules/libgail.so
#19 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#20 IA__g_closure_invoke
at gclosure.c line 490
#21 signal_emit_unlocked_R
at gsignal.c line 2508
#22 IA__g_signal_emit_valist
#23 IA__g_signal_emit
at gsignal.c line 2241
#24 gtk_widget_event_internal
at gtkwidget.c line 3751
#25 do_focus_change
at gtkwindow.c line 4629
#26 _gtk_window_set_is_active
at gtkwindow.c line 7559
#27 gtk_window_focus_in_event
at gtkwindow.c line 4651
#28 _gtk_marshal_BOOLEAN__BOXED
at gtkmarshalers.c line 83
#29 g_type_class_meta_marshal
at gclosure.c line 567
#30 IA__g_closure_invoke
at gclosure.c line 490
#31 signal_emit_unlocked_R
at gsignal.c line 2476
#32 IA__g_signal_emit_valist
#33 IA__g_signal_emit
at gsignal.c line 2241
#34 gtk_widget_event_internal
at gtkwidget.c line 3751
#35 IA__gtk_main_do_event
at gtkmain.c line 1425
#36 gdk_event_dispatch
at gdkevents-x11.c line 2291
#37 IA__g_main_context_dispatch
at gmain.c line 1916
#38 g_main_context_iterate
at gmain.c line 2547
#39 IA__g_main_loop_run
at gmain.c line 2751
#40 IA__gtk_main
at gtkmain.c line 1026
#41 main

Comment 1 Paolo Maggi 2006-08-18 16:39:40 UTC

It seems a gail or atk problem to me.

What version of gtk+ are you using?

Comment 2 Christian Persch 2006-08-27 21:36:21 UTC

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

Comment 3 bill.haneman 2006-09-25 15:24:47 UTC

the stack frames from libgail and at-spi look bad to me - probably because there are no symbols for those libs in your install.  Could you get a more complete stack trace?  The presence of gnome_accessibility_module_shutdown in the traces is very suspicious.

Comment 4 Jonathon Jongsma 2006-09-25 15:40:32 UTC

does the trace in Bug 353138 help you at all?

Comment 5 bill.haneman 2006-09-25 15:55:11 UTC

Thanks jonner, that trace may help.

Comment 6 bill.haneman 2006-09-25 16:10:55 UTC

Created attachment 73377 [details] [review]
patch to prevent this warning/error

Please let me know if this does not solve your problem. Thanks for the stack trace!