Updated to latest freerdp and winconn on Ubuntu 12.10 and now cannot log into Win7 KVM guest

Previously my setup was this:

Windows 7 Ultimate installed as a KVM guest on Ubuntu 12.10 x64 host.
On the Windows 7 KVM guest I had installed Kim Knight;s RemoteAppTool which for Win7 (Ult/Ent), Vista and Win8 implements remoteapp/remotefx support (so you don't have to use Win 2008 etc server).

RemoteAppTool site:
https://sites.google.com/site/kimknight/remoteapptool

I then:
1) enabled Remote RDP connections on the Win7 Ult and set myself as allowed.
2) used RemoteAppTool to configure Windows Explorer as a "remoteapp"
3) then log out but leave the Win7 KVM guest running and can now minimize the KVM Win7 guest window on Ubuntu

Back on Ubuntu 12.10
I used the previous (Precise ppa) WinConn and setup a desktop launcher for the Windows 7 Explorer (using the KVM Guest IP address etc).

Clicking on the Desktop Launcher DID present me with the Windows Explorer as a Remote App so I could then browse my Window s7 KVM guest and execute further apps "at will"... and each would appear on the linux desktop as a separate "window".

PROBLEM:
Because I hadn't updated FreeRDP in quite a while I thought perhaps I should because I have been waiting for CLIPBOARD to be implemented.

So I deleted the old FreeRDP ppa for Ubuntu 12.04 "precise" and then inserted the new PPA for Ubuntu 12.10 Quantal release
https://launchpad.net/~freerdp-team/+archive/freerdp

sudo add-apt-repository ppa:freerdp-team/freerdp
sudo apt-get update
sudo apt-get upgrade

# and it installed the latest freerdp for the Ubuntu 12.10 release

I did the same for WinConn:
sudo add-apt-repository ppa:realender/winconn
sudo apt-get update
sudo apt-get install winconn

# at this point I should have the latest of both WinConn & FreeRDP

I deleted my desktop launcher (to be safe in case some format changes etc)

Ran WinConn which shows it is version 0.2.14

Reconfigured the IP address etc of the Windows 7 KVM guest and the Explorer remoteapp

Then....
Tried to start Windows Explorer... everything starts off the same for the login and I see I connect, preparing desktop etc but then immediately it logs me back out and the screen clears.

So without using WinConn... I opened a Terminal and used xfreerdp itself to try to log into the Windows 7 KVM Guest and it DID WORK okay !

Then I remembered Marc-André Moreau <<email address hidden> (the freerdp developer) and the whole thread in November 2012 about how he had changed the freerdp command line structure:

        reference: http://sourceforge.net/mailarchive/message.php?msg_id=30170106

from the above email he said:

>> If in the previous syntax, you would launch a remoteapp program this way:
>>
>> xfreerdp --app --plugin rail --data "||cmd" -u username -p password -d domain hostname
>>
>> The equivalent now becomes:
>>
>> xfreerdp "/app:||cmd" /u:username@... /p:password /v:hostname

I'm filing this bug for WinConn for 2 reasons....

1) if you have not yet had time to change WinConn to match this new command line structure
2) if #1 then the WinConn website should notify users NOT to upgrade freerdp to the new version or it will break WinConn

thanks
Brian Mullan