FS#32229 - [midori] segfaults on copy image for jpg links
Attached to Project:
Community Packages
Opened by Raphael Groner (k0Do) - Friday, 26 October 2012, 16:22 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 30 October 2012, 23:08 GMT
Opened by Raphael Groner (k0Do) - Friday, 26 October 2012, 16:22 GMT
Last edited by Alexander F. Rødseth (xyproto) - Tuesday, 30 October 2012, 23:08 GMT
|
Details
Description:
Already reported to Manjaro. I report as a security issue cause I don't know the real cause, maybe it's a System thing. A possible reason for a fix could be a downgrade to GTK+ 2.24.11 that works for the developers. Upstream has no other idea so far. Some pic links to test with: https://lh4.googleusercontent.com/-yxrHiuC7oHw/AAAAAAAAAAI/AAAAAAAAOqA/VKZtMS5mhIE/s250-c-k/photo.jpg http://fbcdn-sphotos-c-a.akamaihd.net/hphotos-ak-ash4/307988_296155057157558_2097852588_n.jpg Program received signal SIGSEGV, Segmentation fault. 0xb57dec80 in __memcpy_ssse3 () from /usr/lib/libc.so.6 (gdb) bt #0 0xb57dec80 in __memcpy_ssse3 () from /usr/lib/libc.so.6 #1 0xb782158c in ?? () from /usr/lib/libgio-2.0.so.0 #2 0xb781bc7e in g_input_stream_read () from /usr/lib/libgio-2.0.so.0 #3 0xb77ac596 in ?? () from /usr/lib/libgdk_pixbuf-2.0.so.0 #4 0xb77ae06b in gdk_pixbuf_new_from_stream () from /usr/lib/libgdk_pixbuf-2.0.so.0 #5 0x080aaf8b in ?? () #6 0xb7c57bed in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #7 0xb7b07c88 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #8 0xb7f7e616 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #9 0xb7f90105 in ?? () from /usr/lib/libgobject-2.0.so.0 #10 0xb7f982f6 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #11 0xb7f988f5 in g_signal_emit_by_name () from /usr/lib/libgobject-2.0.so.0 #12 0xb7b76186 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #13 0xb7b77c04 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #14 0xb7b05b42 in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #15 0xb7f7d4ad in ?? () from /usr/lib/libgobject-2.0.so.0 #16 0xb7f7e616 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #17 0xb7f8fdd0 in ?? () from /usr/lib/libgobject-2.0.so.0 #18 0xb7f98031 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #19 0xb7f98473 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #20 0xb7c3ccfb in ?? () from /usr/lib/libgtk-x11-2.0.so.0 #21 0xb7b04214 in gtk_main_do_event () from /usr/lib/libgtk-x11-2.0.so.0 ---Type <return> to continue, or q <return> to quit--- #22 0xb79773a8 in ?? () from /usr/lib/libgdk-x11-2.0.so.0 #23 0xb7ebe733 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb7ebead0 in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb7ebef2b in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #26 0xb7b02d80 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #27 0x0806bef9 in main () Additional info: * package version(s) gtk2 2.24.13-1 glib2 2.32.4-1 cairo 1.12.2-3 libsoup 2.38.1-1 midori 0.4.7-2 - Also tried with midori-git from AUR. * config and/or log files etc. Steps to reproduce: 1. open a .jpg suffixed image url directly in the address bar 2. choose "copy image" from the context menu crash |
This task depends upon
Closed by Alexander F. Rødseth (xyproto)
Tuesday, 30 October 2012, 23:08 GMT
Reason for closing: Upstream
Additional comments about closing: Applied patch, for now.
Tuesday, 30 October 2012, 23:08 GMT
Reason for closing: Upstream
Additional comments about closing: Applied patch, for now.
Comment by Raphael Groner (k0Do) -
Sunday, 28 October 2012, 16:46 GMT
Comment by Raphael Groner (k0Do) -
Sunday, 28 October 2012, 18:43 GMT
Comment by
Alexander F. Rødseth (xyproto) -
Tuesday, 30 October 2012, 21:15 GMT
Comment by
Alexander F. Rødseth (xyproto) -
Tuesday, 30 October 2012, 21:18 GMT
Comment by
Alexander F. Rødseth (xyproto) -
Tuesday, 30 October 2012, 23:07 GMT
Upstream (<MonkeyofDoom>, <pfor> and
<kalikiana>) are aware and promised to provide a patch in
git.
https://bugs.launchpad.net/midori/+bug/1072412
FWIW This works fine with the git version of midori compiled for
gtk3, version 0.4.6-417-ge3a7159, on 64-bit.
I can confirm this bug. I'm able to reproduce it. Will apply the
patch while waiting for a new upstream release.
The patch didn't apply cleanly, but it worked. Updating the
package. Will remove the patch once upstream has a new release.