GNOME Bugzilla – Bug 733555
Crashes on Continuous after user creation dialog
Last modified: 2014-07-25 00:44:27 UTC
The steps are similar to bug 732525, but different stacktrace: Stack trace of thread 494: #0 0x00007fb731ec6582 g_type_check_instance_cast (libgobject-2.0.so.0) #1 0x000000000043b545 username_changed (gnome-initial-setup) #2 0x00007fb731ea4218 g_closure_invoke (libgobject-2.0.so.0) #3 0x00007fb731eb5e0d signal_emit_unlocked_R (libgobject-2.0.so.0) #4 0x00007fb731ebddc1 g_signal_emit_valist (libgobject-2.0.so.0) #5 0x00007fb731ebe002 g_signal_emit (libgobject-2.0.so.0) #6 0x00007fb731ea85c5 g_object_dispatch_properties_changed (libgobject-2.0.so.0) #7 0x00007fb731eaab83 g_object_notify_by_spec_internal (libgobject-2.0.so.0) #8 0x0000000000429ddb gis_account_page_local_apply (gnome-initial-setup) #9 0x0000000000412e60 gis_page_apply_begin (gnome-initial-setup) #10 0x00007fb731ea4447 _g_closure_invoke_va (libgobject-2.0.so.0) #11 0x00007fb731ebd37f g_signal_emit_valist (libgobject-2.0.so.0) #12 0x00007fb731ebe002 g_signal_emit (libgobject-2.0.so.0) #13 0x00007fb733ca07a0 gtk_button_do_release (libgtk-3.so.0) #14 0x00007fb733ca07f6 gtk_real_button_released (libgtk-3.so.0) #15 0x00007fb731ea4218 g_closure_invoke (libgobject-2.0.so.0) #16 0x00007fb731eb5627 signal_emit_unlocked_R (libgobject-2.0.so.0) #17 0x00007fb731ebddc1 g_signal_emit_valist (libgobject-2.0.so.0) #18 0x00007fb731ebe002 g_signal_emit (libgobject-2.0.so.0) #19 0x00007fb726c5dad8 ffi_call_unix64 (libffi.so.6) #20 0x00007fb726c5d529 ffi_call (libffi.so.6) #21 0x00007fb731ea4e65 g_cclosure_marshal_generic_va (libgobject-2.0.so.0) #22 0x00007fb731ea4447 _g_closure_invoke_va (libgobject-2.0.so.0) #23 0x00007fb731ebd37f g_signal_emit_valist (libgobject-2.0.so.0) #24 0x00007fb731ebe002 g_signal_emit (libgobject-2.0.so.0) #25 0x00007fb733d4bb42 gtk_gesture_multi_press_end (libgtk-3.so.0) #26 0x00007fb731ea7010 g_cclosure_marshal_VOID__BOXEDv (libgobject-2.0.so.0) #27 0x00007fb731ea4447 _g_closure_invoke_va (libgobject-2.0.so.0) #28 0x00007fb731ebd37f g_signal_emit_valist (libgobject-2.0.so.0) #29 0x00007fb731ebe002 g_signal_emit (libgobject-2.0.so.0) #30 0x00007fb733d48d9e _gtk_gesture_set_recognized (libgtk-3.so.0) #31 0x00007fb733d4a1d8 gtk_gesture_handle_event (libgtk-3.so.0) #32 0x00007fb733d4d0cf gtk_gesture_single_handle_event (libgtk-3.so.0) #33 0x00007fb733d1cc4b gtk_event_controller_handle_event (libgtk-3.so.0) #34 0x00007fb733ed124d _gtk_widget_run_controllers (libgtk-3.so.0) #35 0x00007fb733d90eae _gtk_marshal_BOOLEAN__BOXEDv (libgtk-3.so.0) #36 0x00007fb731ea4447 _g_closure_invoke_va (libgobject-2.0.so.0) #37 0x00007fb731ebd37f g_signal_emit_valist (libgobject-2.0.so.0) #38 0x00007fb731ebe002 g_signal_emit (libgobject-2.0.so.0) #39 0x00007fb733ed4cec gtk_widget_event_internal (libgtk-3.so.0) #40 0x00007fb733d8e81c propagate_event_up (libgtk-3.so.0) #41 0x00007fb733d90317 gtk_main_do_event (libgtk-3.so.0) #42 0x00007fb733932512 gdk_event_source_dispatch (libgdk-3.so.0) #43 0x00007fb731ba77e4 g_main_dispatch (libglib-2.0.so.0) #44 0x00007fb731ba7a28 g_main_context_iterate (libglib-2.0.so.0) #45 0x00007fb731ba7acc g_main_context_iteration (libglib-2.0.so.0) #46 0x00007fb73218e15c g_application_run (libgio-2.0.so.0) #47 0x0000000000411316 main (gnome-initial-setup) #48 0x00007fb730feca25 __libc_start_main (libc.so.6) #49 0x0000000000411415 _start (gnome-initial-setup) Stack trace of thread 498: #0 0x00007fb7310a718d poll (libc.so.6) #1 0x00007fb731ba79c4 g_main_context_poll (libglib-2.0.so.0) #2 0x00007fb731ba7cea g_main_loop_run (libglib-2.0.so.0) #3 0x00007fb7321c46e6 gdbus_shared_thread_func (libgio-2.0.so.0) #4 0x00007fb731bcc9b5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007fb731949f41 start_thread (libpthread.so.0) #6 0x00007fb7310b318d __clone (libc.so.6) Stack trace of thread 500: #0 0x00007fb7310a718d poll (libc.so.6) #1 0x00007fb731ba79c4 g_main_context_poll (libglib-2.0.so.0) #2 0x00007fb731ba7acc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb731ba7b09 glib_worker_main (libglib-2.0.so.0) #4 0x00007fb731bcc9b5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007fb731949f41 start_thread (libpthread.so.0) #6 0x00007fb7310b318d __clone (libc.so.6) Stack trace of thread 514: #0 0x00007fb7310a718d poll (libc.so.6) #1 0x00007fb731ba79c4 g_main_context_poll (libglib-2.0.so.0) #2 0x00007fb731ba7acc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007fb71d51508d dconf_gdbus_worker_thread (libdconfsettings.so) #4 0x00007fb731bcc9b5 g_thread_proxy (libglib-2.0.so.0) #5 0x00007fb731949f41 start_thread (libpthread.so.0) #6 0x00007fb7310b318d __clone (libc.so.6)
Sorry, a better traceback: (gdb) t a a bt
+ Trace 233861
Thread 1 (Thread 0x7fb735c79940 (LWP 494))
Can you run it under valgrind? It looks like memory corruption to me.
See also https://bugzilla.redhat.com/show_bug.cgi?id=1116478 , this happens consistently for me in F21 testing. If you reboot the system and run through g-i-s again it succeeds the second time. I'll try and run it under valgrind if I can figure out how...
the fix mclasen applied and built in Fedora as gnome-initial-setup-3.12.1-3.fc21 appears to fix my case, I forced it into an install via chroot before booting it for the first time, and g-i-s completed straight through without crashing after the username screen, first time I've seen it do that since the bug started happening. thanks.