FreeRDP in Fedora (EPEL) is getting old. There are many new exciting features in the 1.0.x releases, as well as bugfixes. In addition, we're hitting a strange problem where freerdp brings down the RDP server infrequently and at random, as described here: http://permalink.gmane.org/gmane.network.freerdp.devel/1589 While this is really a problem with Windows and should be fixed at the server end, we're hoping that an upgraded freerdp might help as a workaround.
Yes, I will do that RSN. I haven't had time to follow it recently, but it is getting close to the top of my list now.
I have commit the update in Fedora rawhide, but building without repo conflicts requires a remmina update as well - we are waiting for that to happen. The (major) update has thus not seen any real testing yet. Remmina is however not in EPEL and there is thus no dependency problems for updating there. The only problem is that it would be a major update in a released EL, but I think it is OK considering how unknown and immature freerdp 0.8 was and how much it has improved.
freerdp-1.0.1-2.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/freerdp-1.0.1-2.el6
Package freerdp-1.0.1-2.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing freerdp-1.0.1-2.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2012-0594/freerdp-1.0.1-2.el6 then log in and leave karma (feedback).
*** Bug 800207 has been marked as a duplicate of this bug. ***
freerdp-1.0.1-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/freerdp-1.0.1-5.fc17
freerdp-1.0.1-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.
freerdp-1.0.1-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.