Version-Release number of selected component: freerdp-1.0.2-6.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: xfreerdp -g 1650x950 -k 0x00000409 -d europe -u cz-admin-mh -p ********** -D -X 94372413 -a 16 --plugin rdpdr --data disk media /home/michal -- -x l --ignore-certificate --plugin cliprdr -t 3389 de-s-0177155.de.abb.com crash_function: fatal_handler executable: /usr/bin/xfreerdp kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 fatal_handler at /usr/src/debug/freerdp-1.0.2/libfreerdp-utils/signal.c:52 #3 __memcpy_sse2_unaligned at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:39 #4 memcpy at /usr/include/bits/string3.h:51 #5 xf_cliprdr_get_requested_data at /usr/src/debug/freerdp-1.0.2/client/X11/xf_cliprdr.c:763 #6 xf_cliprdr_process_property_notify at /usr/src/debug/freerdp-1.0.2/client/X11/xf_cliprdr.c:1212 #7 xf_event_PropertyNotify at /usr/src/debug/freerdp-1.0.2/client/X11/xf_event.c:564 #8 xf_event_process at /usr/src/debug/freerdp-1.0.2/client/X11/xf_event.c:757 #9 xf_check_fds at /usr/src/debug/freerdp-1.0.2/client/X11/xfreerdp.c:270 #10 xfreerdp_run at /usr/src/debug/freerdp-1.0.2/client/X11/xfreerdp.c:1059 #11 thread_func at /usr/src/debug/freerdp-1.0.2/client/X11/xfreerdp.c:1091
Created attachment 878328 [details] File: backtrace
Created attachment 878329 [details] File: cgroup
Created attachment 878330 [details] File: core_backtrace
Created attachment 878331 [details] File: dso_list
Created attachment 878332 [details] File: environ
Created attachment 878333 [details] File: limits
Created attachment 878334 [details] File: maps
Created attachment 878335 [details] File: open_fds
Created attachment 878336 [details] File: proc_pid_status
Created attachment 878337 [details] File: var_log_messages
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.
Another user experienced a similar problem: Had a large XML text (about 2.7 MiB/74770 lines) left in the global clipboard when switching to the RDP session window. Unable to reproduce with random text up to 4.7 MiB/82000 lines. Can't share the XML due to possibly sensitive data. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: xfreerdp -T DRECKSTOOLS --plugin cliprdr -g 1915x1022 -u lup@<domain> -p ************ <rdphost>:3389 crash_function: fatal_handler executable: /usr/bin/xfreerdp kernel: 3.19.8-100.fc20.x86_64 package: freerdp-1.0.2-6.fc20 reason: xfreerdp killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.