Version-Release number of selected component: uzbl-core-0-0.33.20120514git228bc38cbd.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: uzbl-core -n 7532-14 -s 44041708 --connect-socket /tmp/uzbltabbed_7532.socket --uri duckduckgo.com --connect-socket /home/rbarlow/.cache/uzbl/event_daemon crash_function: _mm_loadu_si128 executable: /usr/bin/uzbl-core kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _mm_loadu_si128 at /usr/lib/gcc/x86_64-redhat-linux/4.8.1/include/emmintrin.h:684 #1 load_128_unaligned at pixman-sse2.c:370 #2 sse2_blt at pixman-sse2.c:4762 #3 _pixman_implementation_blt at pixman-implementation.c:250 #4 pixman_blt at pixman.c:748 #5 draw_image_boxes at cairo-image-compositor.c:108 #6 upload_boxes at cairo-spans-compositor.c:514 #7 composite_aligned_boxes at cairo-spans-compositor.c:630 #8 clip_and_composite_boxes at cairo-spans-compositor.c:882 #10 _cairo_spans_compositor_paint at cairo-spans-compositor.c:983
Created attachment 904676 [details] File: backtrace
Created attachment 904677 [details] File: cgroup
Created attachment 904678 [details] File: core_backtrace
Created attachment 904679 [details] File: dso_list
Created attachment 904680 [details] File: environ
Created attachment 904681 [details] File: exploitable
Created attachment 904682 [details] File: limits
Created attachment 904683 [details] File: maps
Created attachment 904684 [details] File: open_fds
Created attachment 904685 [details] File: proc_pid_status
Created attachment 904686 [details] File: var_log_messages
Interesting. Looks like a problem with pixman or cairo. As a sidenote, the binary in Fedora is *really* old. I need to get a new release out the door then update Fedora's package :( . Could you try uzbl from git[1] (you'll need webkitgtk-devel)? Please try the 'next' branch and follow the upgrading documentation[2] if you have customizations. Thanks. [1]https://github.com/uzbl/uzbl [2]https://github.com/uzbl/uzbl/blob/next/UPGRADING.md
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.