GTK2 applications segfault with pango-1.45.1
Two GTK2 applications which I use both segfault when run under pango-1.45.1, but work find under pango-1.44.7 and earlier. Here is what coredumpctl gdb
reveals for one of them, sylpheed (the other program's backtrace is similar):
Stack trace of thread 192501:
#0 0x00007fce5f162d76 g_slice_alloc (libglib-2.0.so.0 + 0x6ed76)
#1 0x00007fce5f140e46 g_list_prepend (libglib-2.0.so.0 + 0x4ce46)
#2 0x00007fce5fdd033e n/a (libgtk-x11-2.0.so.0 + 0x12633e)
#3 0x00007fce5ff09bbe n/a (libgtk-x11-2.0.so.0 + 0x25fbbe)
#4 0x00007fce5ff09c4c n/a (libgtk-x11-2.0.so.0 + 0x25fc4c)
#5 0x00007fce5f234cb2 g_closure_invoke (libgobject-2.0.so.0 + 0x14cb2)
#6 0x00007fce5f2458ea signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x258ea)
#7 0x00007fce5f24bbdb g_signal_emit_valist (libgobject-2.0.so.0 + 0x2bbdb)
#8 0x00007fce5f24c0f2 g_signal_emit (libgobject-2.0.so.0 + 0x2c0f2)
#9 0x00007fce5ff00840 n/a (libgtk-x11-2.0.so.0 + 0x256840)
#10 0x00007fce5fc12845 n/a (libgdk-x11-2.0.so.0 + 0x20845)
#11 0x00007fce5f14596f g_main_context_dispatch (libglib-2.0.so.0 + 0x5196f)
#12 0x00007fce5f145ce8 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x51ce8)
#13 0x00007fce5f145d8f g_main_context_iteration (libglib-2.0.so.0 + 0x51d8f)
#14 0x00007fce5fde0871 gtk_main_iteration (libgtk-x11-2.0.so.0 + 0x136871)
#15 0x000000000043a2bd folderview_selection_changed (sylpheed + 0x3a2bd)
#16 0x00007fce5f234cb2 g_closure_invoke (libgobject-2.0.so.0 + 0x14cb2)
#17 0x00007fce5f245c53 signal_emit_unlocked_R.isra.0 (libgobject-2.0.so.0 + 0x25c53)
#18 0x00007fce5f24bbdb g_signal_emit_valist (libgobject-2.0.so.0 + 0x2bbdb)
#19 0x00007fce5f24c0f2 g_signal_emit (libgobject-2.0.so.0 + 0x2c0f2)
#20 0x00007fce5fed6f76 n/a (libgtk-x11-2.0.so.0 + 0x22cf76)
#21 0x00007fce5feda8e5 gtk_tree_view_set_cursor_on_cell (libgtk-x11-2.0.so.0 + 0x2308e5)
#22 0x000000000043a090 folderview_select_row (sylpheed + 0x3a090)
#23 0x000000000043f0bf folderview_set (sylpheed + 0x3f0bf)
#24 0x00000000004309a6 main (sylpheed + 0x309a6)
#25 0x00007fce5ef10e5b __libc_start_main (libc.so.6 + 0x23e5b)
#26 0x0000000000431fea _start (sylpheed + 0x31fea)
Stack trace of thread 192513:
#0 0x00007fce5eff7e9f __poll (libc.so.6 + 0x10ae9f)
#1 0x00007fce5f145c86 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x51c86)
#2 0x00007fce5f145fcb g_main_loop_run (libglib-2.0.so.0 + 0x51fcb)
#3 0x00007fce5f99e446 gdbus_shared_thread_func (libgio-2.0.so.0 + 0x10d446)
#4 0x00007fce5f16dc2d g_thread_proxy (libglib-2.0.so.0 + 0x79c2d)
#5 0x00007fce5f0da06b start_thread (libpthread.so.0 + 0x806b)
#6 0x00007fce5f00372f __clone (libc.so.6 + 0x11672f)
Stack trace of thread 192512:
#0 0x00007fce5eff7e9f __poll (libc.so.6 + 0x10ae9f)
#1 0x00007fce5f145c86 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0x51c86)
#2 0x00007fce5f145d8f g_main_context_iteration (libglib-2.0.so.0 + 0x51d8f)
#3 0x00007fce5f145de1 glib_worker_main (libglib-2.0.so.0 + 0x51de1)
#4 0x00007fce5f16dc2d g_thread_proxy (libglib-2.0.so.0 + 0x79c2d)
#5 0x00007fce5f0da06b start_thread (libpthread.so.0 + 0x806b)
#6 0x00007fce5f00372f __clone (libc.so.6 + 0x11672f)
Stack trace of thread 192514:
#0 0x00007fce5effd149 syscall (libc.so.6 + 0x110149)
#1 0x00007fce5f191052 g_cond_wait_until (libglib-2.0.so.0 + 0x9d052)
#2 0x00007fce5f117481 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x23481)
#3 0x00007fce5f16e61a g_thread_pool_thread_proxy (libglib-2.0.so.0 + 0x7a61a)
#4 0x00007fce5f16dc2d g_thread_proxy (libglib-2.0.so.0 + 0x79c2d)
#5 0x00007fce5f0da06b start_thread (libpthread.so.0 + 0x806b)
#6 0x00007fce5f00372f __clone (libc.so.6 + 0x11672f)
Stack trace of thread 192517:
#0 0x00007fce5eff7e9f __poll (libc.so.6 + 0x10ae9f)
#1 0x00007fce5c08ce92 n/a (libpulse.so.0 + 0x34e92)
#2 0x00007fce5c07ee09 pa_mainloop_poll (libpulse.so.0 + 0x26e09)
#3 0x00007fce5c07f46f pa_mainloop_iterate (libpulse.so.0 + 0x2746f)
#4 0x00007fce5c07f520 pa_mainloop_run (libpulse.so.0 + 0x27520)
#5 0x00007fce5c08cdf6 n/a (libpulse.so.0 + 0x34df6)
#6 0x00007fce564c5fc8 n/a (libpulsecommon-13.0.so + 0x53fc8)
#7 0x00007fce5f0da06b start_thread (libpthread.so.0 + 0x806b)
#8 0x00007fce5f00372f __clone (libc.so.6 + 0x11672f)
Stack trace of thread 192515:
#0 0x00007fce5effd149 syscall (libc.so.6 + 0x110149)
#1 0x00007fce5f191052 g_cond_wait_until (libglib-2.0.so.0 + 0x9d052)
#2 0x00007fce5f117481 g_async_queue_pop_intern_unlocked (libglib-2.0.so.0 + 0x23481)
#3 0x00007fce5f16e61a g_thread_pool_thread_proxy (libglib-2.0.so.0 + 0x7a61a)
#4 0x00007fce5f16dc2d g_thread_proxy (libglib-2.0.so.0 + 0x79c2d)
#5 0x00007fce5f0da06b start_thread (libpthread.so.0 + 0x806b)
#6 0x00007fce5f00372f __clone (libc.so.6 + 0x11672f)
It may of course be a GTK+2 bug revealed by pango-1.45.1 rather than a pango bug.
GTK+3 programs seem to be unaffected.