The unity8 crash seems to be a glib fatal error:
"No GSettings schemas are installed on the system"
Also supporting this:
$ gsettings list-schemas
No schemas installed
This could also explain why it works on upgrade, if vivid finds and
prepares the schemas fine.
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Incomplete
--
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 when --wipe is
used for flashing
Status in Canonical System Image:
Confirmed
Status in unity8 package in Ubuntu:
Incomplete
Bug description:
Update: this only happens when --wipe (or --bootstrap) is used for
flashing. It is possible to get functional xenial/staging running by
doing non-destructive flash update from rc-proposed.
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
