One thought is: since it's unlikely that the custom tarball actually could break anything, maybe the reason why dist-upgrading works is because unity8 ran once on 40, setting the state of the system to some 'state' which seems to work with all packages upgraded. On a fresh flash of 41 it might have not worked because it was the 'first boot'.
This, of course, only makes sense if no one did tests of flashing 40, booting up and then flashing 41 without --bootstrap or --wipe (so hopefully conserving the state of the rw system). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604421 Title: Unity 8 fails to start on staging (xenial) on the phone Status in Canonical System Image: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Unity 8 fails to start on staging (=xenial + xenial-overlay) on my krillin. unity-system-compositor.log: http://paste.ubuntu.com/20035267/ - shows Opening/Closing/Opening/Closing when starting unity8. unity8.log attached. Using ubuntu-touch/staging/bq-aquaris.en channel on krillin. version_detail: ubuntu=20160719,device=20160606-ab415b2,custom=20160701-981-38-14,version=49 Crash file at http://people.ubuntu.com/~timo- jyrinki/unity8/_usr_bin_unity8.32011.crash Xenial can be flashed on the phone with eg: ubuntu-device-flash touch --channel=ubuntu-touch/staging/ubuntu --developer-mode --password=0000 --wipe --boostrap (ubuntu channel) ubuntu-device-flash touch --channel=ubuntu-touch/staging/bq-aquaris.en --developer-mode --password=0000 --wipe --recovery-image recovery-krillin.img (Bq channel) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
