Start liferea (Move ~/.liferea_1.7 before to force-create a new profile), click on any feed and click any item in the upper right pane. Reproducible: Always Steps to Reproduce: 1. Move ~/.liferea_1.7 before to force-create a new profile if it exists 2. Start liferea in a terminal 3. Click on any feed and click any item in the upper right pane 4. Segfault Actual Results: segfault Expected Results: No segfault :) amd64 testing Bug might be caused by net-libs/webkit-gtk-1.4.3-r200 (see stack trace)
Created attachment 287793 [details] stack trace
Created attachment 287795 [details] cave info liferea webkit-gtk:2
Can you reproduce this with liferea-1.8_rc1 ? I have just updated this ebuild, so you must wait some time until it's available in your mirror.
Still fails with liferea-1.8_rc1. I'll attach the new stack trace.
Created attachment 287811 [details] stack trace for liferea-1.8_rc1
Created attachment 287815 [details] cave info liferea webkit-gtk:2 after upgrading to liferea-1.8_rc1
(In reply to comment #4) > Still fails with liferea-1.8_rc1. I'll attach the new stack trace. It catches my eye the fact that even if you have specified ACCEPT_KEYWORDS=amd64 you are using ~arch webkit-gtk. I guess you're using libpng-1.5.5, and that you already have executed revdep-rebuild.
Hm. the thing about amd64 instead of ~amd64 looks like a bug. I've reported it to the paludis guys. I'm actually completely on ~amd64 with nothing masked or unmasked by me. I'm using libpng-1.5.5 and revdep-rebuild only wants to rebuild shotwell which is caused by https://bugs.gentoo.org/show_bug.cgi?id=384165
Problem occurs with liferea-1.7.1-r1 here (amd64). Segfaults with very similar stack : #0 0x00007f084aca3ffd in waitpid () from /lib64/libpthread.so.0 #1 0x00007f084aecd962 in g_on_error_stack_trace () from /usr/lib64/libglib-2.0.so.0 #2 0x00000000004332ac in ?? () #3 <signal handler called> #4 0x00007f07f44b840d in ?? () from /usr/lib64/gio/modules/libgiognutls.so #5 0x00007f07f44b91a8 in ?? () from /usr/lib64/gio/modules/libgiognutls.so #6 0x00007f07f44ba5b1 in ?? () from /usr/lib64/gio/modules/libgiognutls.so #7 0x00007f07f44bac62 in ?? () from /usr/lib64/gio/modules/libgiognutls.so #8 0x00007f084b67246c in g_io_stream_close () from /usr/lib64/libgio-2.0.so.0 #9 0x00007f084b6724a6 in ?? () from /usr/lib64/libgio-2.0.so.0 #10 0x00007f084b3dd5ca in g_object_unref () from /usr/lib64/libgobject-2.0.so.0 #11 0x00007f084ce37ed2 in ?? () from /usr/lib64/libsoup-2.4.so.1 #12 0x00007f084ce3802f in soup_socket_disconnect () from /usr/lib64/libsoup-2.4.so.1 #13 0x00007f084ce17e58 in soup_connection_disconnect () from /usr/lib64/libsoup-2.4.so.1 #14 0x00007f084ce18009 in ?? () from /usr/lib64/libsoup-2.4.so.1 #15 0x00007f084aef561b in ?? () from /usr/lib64/libglib-2.0.so.0 #16 0x00007f084aef4bc1 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #17 0x00007f084aef9258 in ?? () from /usr/lib64/libglib-2.0.so.0 #18 0x00007f084aef9765 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 #19 0x00007f084d190f07 in gtk_main () from /usr/lib64/libgtk-x11-2.0.so.0 #20 0x0000000000433b57 in main ()
Looks like this somehow solved itself, at least for me. Maybe this was a transient issue about liferea-1.7 <-> webkit-gtk-1.4.X. I'm currently using webkit-gtk-1.8.1 and everything looks fine.
