On 06/15/2011 09:52 AM, Michael Hasselmann wrote:
Hi,

could we please get some information about the release plan of MeeGo
Tablet UX? Recent images have all been broken, for instance:
* install-only boot option not working (doesn't seem to start
uxlauncher),
as stated below by you, there has been some transitional activity's that will change several little bits moving forward for 1.3. As for the images being broken specificity (install-only boot) . This is probably due to a missing line in the KS file now needed for images with install options.
 --menu="autoinst:Installation:systemd.unit=installer-shell.service"
needs to be added. For example in the netbook ks file:
lang en_US.UTF-8
keyboard us
timezone --utc America/Los_Angeles
part / --size 3000 --ondisk sda --fstype=ext3
rootpw meego
xconfig --startxonboot
bootloader --timeout=0 --append="quiet" --menu="autoinst:Installation:systemd.unit=installer-shell.service"

This should solve the issue of install-only.

* windows key not working (which makes it impossible to return to the
home screen),
* no virtual keyboard,
* …

If this is a transitional phase (say, because of systemd switch), then
it would help to know the current state and when to expect working
images again.
Which tablet images you are using will also be a factor on when images will once again be fully functional during the transition. From a systemd interest, all images generated for platforms that are IA PC like and use the kernel-adaptation-pinetrail kernel should be fully functional (as systemd work point of view) . All other are still being worked on actively.

Chris


We really need http://wiki.meego.com/Release_Engineering/Plans/1.3 (like
we had for 1.2).

regards,
Michael

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to