Version-Release number of selected component: ucview-0.33-6.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/ucview crash_function: __memcpy_sse2_unaligned executable: /usr/bin/ucview kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:40 #1 memcpy at /usr/include/bits/string3.h:51 #2 unicapgtk_video_display_set_pause at unicapgtk_video_display.c:1026 #7 _gtk_action_emit_activate at gtkaction.c:795 #8 gtk_action_activate at gtkaction.c:826 #9 button_clicked at gtktoolbutton.c:771 #14 gtk_button_clicked at gtkbutton.c:1115 #15 gtk_toggle_button_released at gtktogglebutton.c:485 #16 _g_closure_invoke_va at gclosure.c:840 #19 gtk_button_button_release at gtkbutton.c:1604
Created attachment 912657 [details] File: backtrace
Created attachment 912658 [details] File: cgroup
Created attachment 912659 [details] File: core_backtrace
Created attachment 912660 [details] File: dso_list
Created attachment 912661 [details] File: environ
Created attachment 912662 [details] File: limits
Created attachment 912663 [details] File: maps
Created attachment 912664 [details] File: open_fds
Created attachment 912665 [details] File: proc_pid_status
Created attachment 912666 [details] File: var_log_messages
Created attachment 912667 [details] File: exploitable
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.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.