missing android signal was caused by double mounting of cgroup cpu, which was already mounted. Fixing that did take boot further, now lightdm becomes alive, still boot fails, and kills adb in the process...
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1551150 Title: devel-proposed - android lxc container fails to start Status in Canonical System Image: Confirmed Status in lxc package in Ubuntu: New Bug description: Last known good image: ubuntu-touch/devel-proposed/ubuntu/mako 446 ubuntu-touch/devel-proposed/ubuntu/mako 447 (and higher) and equivalent images on other devices do not boot and hang on the boot logo. From the list of changes, it could be lxc: 446: lxc 2.0.0~rc2-0ubuntu2 447: lxc 2.0.0~rc3-0ubuntu1 Latest image with 2.0.0~rc4-0ubuntu1 doesn't boot either. lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium * New upstream release (2.0.0~rc3) - Make the cgfs backend and cgns work without cgmanager - Manpage updates - Mark lxc-clone and lxc-start-ephemeral deprecated (still included) * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral lxc (2.0.0~rc2-0ubuntu3) xenial; urgency=medium * Use versioned dependencies against the various binary packages. * Update lxc-templates to depend on lxc1 not lxc. (LP: #1549136) * Move the lxcfs recommends from lxc-templates to liblxc1. * Drop cgmanager, use the cgfs backend instead. * Have liblxc1 depend on systemd | cgroup-lite for cgfs backend. Device tarballs between 446 and 447 are the same. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1551150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
