leads me to believe the Canonical doesn't have a Xserver to SurfaceFlinger bridge in place yet. For gui applications to work they will need to be written with qt5, which has support for both Xserver and SurfaceFlinger. Hence why the new SDK that was also made public as part of the U. Touch/Tablet unveil is qt5/qml. I doubt xterm from the repositories will run as expected in this chrooted Ubuntu environment running on top of the android plumbing, but I could be wrong.
The video with Shuttleworth laying out how the phone,tablet and desktop are all going to work seemlessly so you can run phone and desktop apps side by side should be taken as the ultimate end goal, not as a current deliverable. A bit of hopeful salesmanship and visioneering to generate interest in the platform development journey.
I think a big piece of the engineering yet to be made public is Canonical's replacement for both SurfaceFlinger and Xserver. I believe Canonical employees have already made public the fact that they are working on something that is not Wayland to fill that space in their stack. A forked SurfaceFlinger perhaps? No idea. It'll be fun finding out.
All I know for sure is I look forward to watching Canonical chase Google's dominance in the mobility space by forking the crap out of Google's technology and then sending it back into the marketplace as a competitor. Popcorn at the ready. At least they aren't wasting any time, this time around. trying to claim this is just a different interpretation of the Android OS, and pretending to be working in collaboration with Google. Its nice to see them taking ownership of the differentiation story early.
Though I wish they'd stress the Unity brand more and let the Ubuntu brand slide out of product strategy usage and let it exist as a community brand. The Ubuntu brand has some baggage due to the expansive nature of the Ubuntu project and the repositories. Canonical is clearly positioning the Unity interface as the cross-formfactor hotness. But for a lot of people Ubuntu is not just Unity, its the larger project space. Community members can self-identify, and will communicate with others, as using Ubuntu even though they do not use the Unity interface. This is brand confusion that will weaken the story Canonical wants to tell to new users.
The phone and the tablet products are strictly Unity interfaces. None of the traditional linux stack UI interfaces, not even KDE active afaik, works on top of SurfaceFlinger in the way that the new qt5 based UI Canonical has put together does. Please someone correct me if I am wrong about that. But if I have my information correct, that has some very significant ramification with regard to confusion that using the Ubuntu brand is going to cause when trying to win the cross-formfactor strategy. People who think of _Ubuntu_ as the larger repository that includes alternative interfaces other than Unity are going to be confused, and are going to cause confusion in others.
Canonical would get much more mileage out of the Unity brand, as a narrowly definable brand that was associated very specifically to the common UI experience they are pushing.