i've stumbled into this same situation - empty virtual keyboard. and this has happened since doing a reflash. i have tried restoring my previous settings and also the ukeyboard package (even though the details specifically state "hardware keyboard layouts" some people seem to think it has resolved the issue for them.

background :

i had been on pr1.1. the pr1.1.1 update had seemed to work settings-about confirmed pr1.1.1 version details - but app manager said it was available for install, but only via pc.

i followed instructions in another post for atp-get upgrade, which then sugested i did a apt-get -f install. this got so far through when the device rebooted, and then rebooted again, and this became a continuous cycle.

so i flashed the pr1.1.1 uk (203) image and got it working again. all seems fine except the virtual keyboard is empty (which prior to re-flash had been fine).

So are you saying that even a reflash did not cure this problem for you?

I would like to avoid a reflash if at all possible, and if it won't help, that's all the more reason I would want to avoid it (duh!).

Can anyone else in the know confirm this? I would really like to get some solid, knowledgable advice on this, not just folks trying to be helpfu saying "reflash will fix". (No offense to anyone who has offered advice, but I remain unconvinced due to lack of more serious evidence one way or the other.)

Seriously, has this issue been reported anywhere, like in bugfixes or some other arcane places that only Linux programmers know how to access? I would appreciate a more formal discussion of this rather serious (to my mind) problem. I'm surprised how little discussion this has generated.

mine stopped working yesterday did nothing to the phone just vanished

I can confirm this.

AFAIK, and there is a new update for uKeyboard, which requires libraries available for PR 1.2, therefor it won't be available until PR1.2 will be available (no matter how many times you reflash - take it from me, I reflashed about 3 times last couple of days).

Ok for the record and for anyone interested, a reflash did solve the problem.