So, do you still have error message when qchroot'ing ? If so, please show it here.
Yes. The error message is the one I reported in post #2. I have it either with regular Terminal applications and with FingerTerm.
By the way, I forgot to answer about the automatic update! My answer: no idea! I just installed the deb, then nothing happened, then an automatic update was available for it, through the usual Harmattan update window. I updated and then tried the commands. Is it possible that it updated to the Maemo version because of the rzr repos? I think everything happened before the package was made available in those repos.
[Edit] Well, actually now, as I seems my version of easy-chroot is "0.3.4.-0maemo0-rzr1. I uninstall it and reinstall your deb.
Yes. The error message is the one I reported in post #2. I have it either with regular Terminal applications and with FingerTerm.
By the way, I forgot to answer about the automatic update! My answer: no idea! I just installed the deb, then nothing happened, then an automatic update was available for it, through the usual Harmattan update window. I updated and then tried the commands. Is it possible that it updated to the Maemo version because of the rzr repos? I think everything happened before the package was made available in those repos.
[Edit] Well, actually now, as I seems my version of easy-chroot is "0.3.4.-0maemo0-rzr1. I uninstall it and reinstall your deb.
Yes, as you have rzr share repository enabled, the Maemo version replaced the MeeGo Harmattan one. But then rzr has fixed this version problem. Try it again and tell me whether the error message happens or not.
I've cited MeeCatalog and your "Community Share Repo" as the recommended way of installing "Easy Chroot" on MeeGo Harmattan.
rzr, could you please remove "easy-deb-chroot" (version 0.9.56-1fremantle1) from your repo ? Because a lot of people could try to install it in on Nokia N9/N950. My "easy-deb-chroot" package for MeeGo Harmattan is almost ready...
It works now. The issue was only due to the update that replaced the Meego version with the Maemo one.
Now I have to make my AZERTY bluetooth keyboard to be correctly supported, or wait until Javispredo finds a way to make the virtual keyboard work inside Debian. :]
Now I have to make my AZERTY bluetooth keyboard to be correctly supported, or wait until Javispredo finds a way to make the virtual keyboard work inside Debian. :]
Try "# synchroot" inside MeeGo (after debian is chrooted). For Maemo 5 it has solved some keyboard problems.
Works great! Unfortunately I'm stuck with VNC for now - don't have a keyboard yet .
Are you using Easy Chroot with Easy Debian using VNC server & client ? À la Android ? If so, please describe how you do it in the new "Easy Debian for MeeGo Harmattan" topic.
Are you using Easy Chroot with Easy Debian using VNC server & client ? À la Android ? If so, please describe how you do it in the new "Easy Debian for MeeGo Harmattan" topic.
No, I was merely trying to use openoffice and see how the N9 performs, using another device as VNC client and the N9 SDK VNC as server.
I'm happy to see the official easy debian release, thanks!
have tried synchroot, but i am not sure what to do to get the vkb. Is it the same as for the javispedro tips?
Which image are you using with Easy Chroot ? If it is a Debian image, look at the Easy Debian Harmattan topic. It is explained there (in section "Choosing a Debian image") what synchroot does :
"1 & 2) To physical keyboard (Bluetooth or N950's) work inside LXDE, tap the "Debian Chroot" icon, then open other X Terminal and type :
$ opensh
# synchroot
Some configuration files are now copied to the Debian image. This procedure is needed only once per image."
If you are using Easy Debian, inside LXDE the virtual keyboard should appear if you touch a text entry area. Javispedro tips concerns the language issue so all characters of the vkb work.
.