Sent to https://bugzilla.gnome.org/show_bug.cgi?id=721700
** Bug watch added: GNOME Bug Tracker #721700 https://bugzilla.gnome.org/show_bug.cgi?id=721700 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=721700 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1262380 Title: gtk+3.0 FTBFS on ppc64el Status in GTK+ GUI Toolkit: Unknown Status in “gtk+3.0” package in Ubuntu: Fix Released Bug description: gtk+3.0 fails to build on ppc64el with a test suite failure in the gtkbuilder tests: $ cd gtk+3.0-3.10.6/debian/build/shared/testsuite/gtk $ Xvfb -ac -noreset -screen 0 1024x768x16 :0 -nolisten tcp -auth & $ export DISPLAY=:0.0 $ ./builder /Builder/Parser: OK /Builder/Types: OK /Builder/Construct-Only Properties: OK /Builder/Children: OK /Builder/Child Properties: OK /Builder/Object Properties: OK /Builder/Notebook: OK /Builder/Domain: OK /Builder/Signal Autoconnect: Segmentation fault $ gdb shows some kind of corrupted backtrace (the calling function is test_connect_signals(), not test_gmenu()): (gdb) bt #0 0x00003fffb7deeab8 in gtk_window_get_type () at /home/buildd/stage1/gtk+3.0-3.10.6/./gtk/gtkwindow.c:552 #1 0x000000001000c8dc in signal_normal (window=<optimized out>, spec=...) at /home/buildd/stage1/gtk+3.0-3.10.6/./testsuite/gtk/builder.c:145 #2 0x00003fffb76c79b0 in g_cclosure_marshal_VOID__PARAM () from /usr/lib/powerpc64le-linux-gnu/libgobject-2.0.so.0 #3 0x000000001000c8a0 in test_gmenu () at /home/buildd/stage1/gtk+3.0-3.10.6/./testsuite/gtk/builder.c:2605 #4 0x626f3c20203e6563 in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) (gdb) A clean backtrace immediately before the segfault looks like: #0 signal_normal (window=<optimized out>, spec=...) at /home/buildd/stage1/gtk+3.0-3.10.6/./testsuite/gtk/builder.c:144 #1 0x00003fffb76c7b30 in g_cclosure_marshal_VOID__PARAM (closure=0x100997a0, return_value=<optimized out>, n_param_values=<optimized out>, param_values=0x3fffffffe630, invocation_hint=<optimized out>, marshal_data=0x0) at /build/buildd/glib2.0-2.39.2/./gobject/gmarshal.c:1042 #2 0x00003fffb76c3678 in g_closure_invoke (closure=0x100997a0, return_value=0x0, n_param_values=<optimized out>, param_values=0x3fffffffe630, invocation_hint=0x3fffffffe528) at /build/buildd/glib2.0-2.39.2/./gobject/gclosure.c:777 #3 0x00003fffb76dec78 in signal_emit_unlocked_R (node=0x1004ca20, detail=457, instance=0x10200ff0, emission_return=0x0, instance_and_params=0x3fffffffe630) at /build/buildd/glib2.0-2.39.2/./gobject/gsignal.c:3556 #4 0x00003fffb76e7fc4 in g_signal_emit_valist (instance=0x10200ff0, signal_id=<optimized out>, detail=<optimized out>, var_args=0x3fffffffe800 "\003") at /build/buildd/glib2.0-2.39.2/./gobject/gsignal.c:3312 #5 0x00003fffb76e8240 in g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.39.2/./gobject/gsignal.c:3368 #6 0x00003fffb76c9e2c in g_object_dispatch_properties_changed ( object=0x10200ff0, n_pspecs=<optimized out>, pspecs=<optimized out>) at /build/buildd/glib2.0-2.39.2/./gobject/gobject.c:1046 #7 0x00003fffb76cd864 in g_object_notify_by_spec_internal ( pspec=<optimized out>, object=0x10200ff0) at /build/buildd/glib2.0-2.39.2/./gobject/gobject.c:1140 #8 g_object_notify (object=0x10200ff0, property_name=<optimized out>) at /build/buildd/glib2.0-2.39.2/./gobject/gobject.c:1187 #9 0x00003fffb7df00d4 in gtk_window_set_title_internal (window=0x10200ff0, title=<optimized out>, update_titlebar=<optimized out>) at /home/buildd/stage1/gtk+3.0-3.10.6/./gtk/gtkwindow.c:1807 #10 0x00000000100080a8 in test_connect_signals () at /home/buildd/stage1/gtk+3.0-3.10.6/./testsuite/gtk/builder.c:260 #11 0x00003fffb7617ce8 in test_case_run (tc=0x10053a70) at /build/buildd/glib2.0-2.39.2/./glib/gtestutils.c:2088 #12 g_test_run_suite_internal (suite=0x10048ae0, path=0x3fffb769aa68 "") at /build/buildd/glib2.0-2.39.2/./glib/gtestutils.c:2148 #13 0x00003fffb7617f08 in g_test_run_suite_internal (suite=0x10048ac0, path=0x3fffb769aa68 "") at /build/buildd/glib2.0-2.39.2/./glib/gtestutils.c:2159 #14 0x00003fffb761840c in g_test_run_suite (suite=0x10048ac0) at /build/buildd/glib2.0-2.39.2/./glib/gtestutils.c:2210 #15 0x00003fffb7618480 in g_test_run () at /build/buildd/glib2.0-2.39.2/./glib/gtestutils.c:1526 #16 0x0000000010003ed4 in main (argc=1, argv=0x3ffffffff638) at /home/buildd/stage1/gtk+3.0-3.10.6/./testsuite/gtk/builder.c:2781 (gdb) Stepping through with gdb also shows signal_normal() being entered twice in response to the first gtk_window_set_title() call, even though it should only be called once. This problem was not evident in the initial bootstrap of gtk+3.0, but now is reproducible on both the launchpad builders and the porter system. It could be due to a kernel upgrade after the initial bootstrap, we're not sure. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1262380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
