Version-Release number of selected component: rdesktop-1.8.1-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: rdesktop -ndelldozer -kde -g1200x930 -a16 -uAdministrator -pXXXXXXXXXXXXXXXXX -rdisk:agfa /tmp localhost:23389 crash_function: _IO_vfprintf_internal executable: /usr/bin/rdesktop kernel: 3.14.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 _IO_vfprintf_internal at vfprintf.c:1635 #1 buffered_vfprintf at vfprintf.c:2328 #2 _IO_vfprintf_internal at vfprintf.c:1289 #3 ___vfprintf_chk at vfprintf_chk.c:33 #4 vfprintf at /usr/include/bits/stdio2.h:127 #5 error at rdesktop.c:1361 #6 disk_create at disk.c:496 #7 rdpdr_process_irp at rdpdr.c:456 #8 sec_recv at secure.c:870 #9 rdp_recv at rdp.c:98
Created attachment 929139 [details] File: backtrace
Created attachment 929140 [details] File: cgroup
Created attachment 929141 [details] File: core_backtrace
Created attachment 929142 [details] File: dso_list
Created attachment 929143 [details] File: environ
Created attachment 929144 [details] File: exploitable
Created attachment 929145 [details] File: limits
Created attachment 929146 [details] File: maps
Created attachment 929147 [details] File: open_fds
Created attachment 929148 [details] File: proc_pid_status
Created attachment 929149 [details] File: var_log_messages
Another user experienced a similar problem: The first time I ran the app using teh credential options it crashed. I don't know for sure that the windows machine i was attempting to connect to is set up correctly. It hasn't crashed since that first time. The windows machine nver seems to see the connection, but then I actually do not know what to expect. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: rdesktop -u: marcia -o:Senior81 -n:192.168.6.198 crash_function: _IO_vfprintf_internal executable: /usr/bin/rdesktop kernel: 3.16.3-200.fc20.x86_64 package: rdesktop-1.8.1-1.fc20 reason: rdesktop killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.