how to revert to the cssu hildon-desktop if we've tried to patch it with other HDs?

You'd need to remove any pinning (from /etc/apt/preferences) for hildon-desktop, then a simple "apt-get install --reinstall hildon-desktop" should do the job (assuming you've not added external repositories with higher-versioned hildon-desktop packages - if you have then you'd need to either remove these repositories or pin the CSSU version of hildon-desktop).

@Rob1n

erm... went to xterm

root
Package: hildon-desktop
Pin: release a=unstable
Pin-Priority: 600

doesn't work?

tried to run:
root
cd /etc/apt/preferences

couldn't find... could only get up to cd /etc/apt

/etc/apt/preferences isn't a directory, it's a file - you need to create/edit the file (as root) and add (probably - I've not tested this):

are there any hopes of getting a portrait virtual key board something that's like the one in the Opera browser? i really like the way it has been handled.

P.S.
I did not enjoy using FastSMS or FastSMSevo so this request. Sorry but personal preferences!

so lets invent wheel again! Have you formulated your suggestions and ideas to fastsms developer.He might actually listen.

I'm getting the PC suite message, yet I have 61 MB free on my rootfs, what could possibly cause this?

One or more existing packages installed on your phone could be conflicting with the CSSU.

NOT A BUG. i apologize if i sound a bit brash, but this thread is becoming overwhelmed with people who clearly should not be TESTING these packages. that's right, this, as stated in the disclaimer, is for people who want to TEST potentially unstable packages, not for people who can bother doing any research into what they are doing. this thread had become absolutely littered with complaints about non-issues like, "ohhh...my ctrl + backspace doesn't work anymore..." over and over again, and by the way the answer to this can be found on pages 7, 16, and 18, or in Matan's documentation found at: http://my.svgalib.org/repo/Modified_Hildon_Desktop.html. please keep your comments, questions, and suggestions to issues of relevance so the developers don't have to wade through pagers of mindless banter in order to get actual constructive feedback on their already difficult work. if you can't be troubled with troubleshooting, don't test developmental software. be patient, cool your jets, when all the kinks are worked out and it's n00b friendly i promise you the developers aren't going to keep it to themselves.

Any idea on how to find the culprit besides having to uninstall everything?