Bug 746691 – Warning closing gedit

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 746691 - Warning closing gedit


Summary:	Warning closing gedit


Status:	RESOLVED FIXED

Product:	gedit
Classification:	Applications
Component:	general
Version:	unspecified
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Gedit maintainers
QA Contact:	Gedit maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2015-03-24 14:51 UTC by Ignacio Casal Quinteiro (nacho)
Modified:	2015-03-25 08:46 UTC

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

Description Ignacio Casal Quinteiro (nacho) 2015-03-24 14:51:23 UTC

Getting this warning when closing gedit.

(gedit:6031): Gtk-WARNING **: Given child of type 'GtkOverlay' not found in GtkStack
[New Thread 0x7fffd1917700 (LWP 6046)]
[New Thread 0x7fffd2158700 (LWP 6045)]
[New Thread 0x7fffd317b700 (LWP 6043)]
[New Thread 0x7fffdeacb700 (LWP 6038)]

Program received signal SIGTRAP, Trace/breakpoint trap.
0x00007ffff46eb4cb in _g_log_abort (breakpoint=1) at gmessages.c:315
315	    G_BREAKPOINT ();
(gdb) bt

+ Trace 234882

#0 g_logv
at gmessages.c line 315
#1 g_logv
at gmessages.c line 1041
#2 g_log
at gmessages.c line 1079
#6 <emit signal ??? on instance 0xee81e0 [GtkNotebook]>
at gsignal.c line 3361
#7 gtk_notebook_switch_page
at gtknotebook.c line 6824
#8 gtk_notebook_set_current_page
at gtknotebook.c line 7393
#9 on_child_changed
#13 <emit signal notify:visible-child on instance 0xec16e0 [GtkStack]>
at gsignal.c line 3361
#14 g_object_dispatch_properties_changed
at gobject.c line 1056
#15 g_object_notify_by_pspec
at gobject.c line 1149
#16 g_object_notify_by_pspec
at gobject.c line 1259
#17 set_visible_child
at gtkstack.c line 1096
#18 gtk_stack_remove
at gtkstack.c line 1251
#22 <emit signal ??? on instance 0xec16e0 [GtkStack]>
at gsignal.c line 3361
#23 gtk_container_remove
at gtkcontainer.c line 1733
#24 ffi_call_unix64
#25 ffi_call
#26 pygi_invoke_c_callable
#27 pygi_function_cache_invoke
#28 _callable_info_call
#29 PyObject_Call
#30 PyEval_EvalFrameEx
#31 PyEval_EvalCodeEx
#32 function_call
#33 PyObject_Call
#34 PyEval_CallObjectWithKeywords
#35 _pygi_closure_handle
#36 ffi_closure_unix64_inner
#37 ffi_closure_unix64
#41 <emit signal ??? on instance 0xfb4210 [PeasExtensionSet]>
at gsignal.c line 3361
#42 remove_extension_item
#43 peas_extension_set_dispose
#44 g_object_unref
at gobject.c line 3137
#45 gedit_window_dispose
#46 g_object_run_dispose
at gobject.c line 1076
#50 <emit signal ??? on instance 0xe9b770 [GSimpleAction]>
at gsignal.c line 3361
#51 g_simple_action_activate
at gsimpleaction.c line 225
#52 gtk_action_muxer_activate_action
at gtkactionmuxer.c line 411
#53 gtk_application_activate_accel
at gtkapplication.c line 301
#54 gtk_application_activate_accel
at gtkapplication.c line 1553
#55 gtk_window_activate_key
at gtkwindow.c line 11319
#56 gedit_window_key_press_event
#57 _gtk_marshal_BOOLEAN__BOXEDv
at gtkmarshalers.c line 130
#58 _g_closure_invoke_va
at gclosure.c line 831
#59 g_signal_emit_valist
at gsignal.c line 3214
#60 g_signal_emit
at gsignal.c line 3361
#61 gtk_widget_event_internal
at gtkwidget.c line 7787
#62 propagate_event
at gtkmain.c line 2515
#63 gtk_main_do_event
at gtkmain.c line 1756
#64 gdk_event_source_dispatch
at gdkeventsource.c line 364
#65 g_main_context_dispatch
at gmain.c line 3122
#66 g_main_context_dispatch
at gmain.c line 3737
#67 g_main_context_iterate
at gmain.c line 3808
#68 g_main_context_iteration
at gmain.c line 3869
#69 g_application_run
at gapplication.c line 2308
#70 main

Comment 1 Matthias Clasen 2015-03-25 01:56:43 UTC

I think the crucial frame here is:

+ Trace 234886

#9 on_child_changed

which is on your side

Comment 2 Ignacio Casal Quinteiro (nacho) 2015-03-25 08:11:34 UTC

Matthias I am not so sure that it is a gedit issue. For what I can see this happens when we try to set the visible child on the stack when the stack is not realized, even though the widget is already added to the stack.

Comment 3 Ignacio Casal Quinteiro (nacho) 2015-03-25 08:46:10 UTC

Fixed. https://git.gnome.org/browse/gedit/commit/?id=f982a19e72e8b615cd19b0758e5173df38ff32e6