Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Łukasz Zemczak | ||
gsettings-ubuntu-touch-schemas (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
ubuntu-touch-session (Ubuntu) |
Fix Released
|
Critical
|
Łukasz Zemczak | ||
unity8 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
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-
unity8.log attached.
Using ubuntu-
Crash file at http://
Xenial can be flashed on the phone with eg:
ubuntu-device-flash touch --channel=
(ubuntu channel)
ubuntu-device-flash touch --channel=
(Bq channel)
Related branches
- Timo Jyrinki: Approve
-
Diff: 8 lines (+1/-1)1 file modifiedetc/profile.d/add_custom_to_xdg_data.sh (+1/-1)
description: | updated |
Changed in unity8 (Ubuntu): | |
assignee: | nobody → Daniel d'Andrada (dandrader) |
Changed in unity8 (Ubuntu): | |
status: | New → In Progress |
Changed in canonical-devices-system-image: | |
assignee: | nobody → Michał Sawicz (saviq) |
Changed in canonical-devices-system-image: | |
status: | New → Confirmed |
importance: | Undecided → Critical |
no longer affects: | glib2.0 (Ubuntu) |
no longer affects: | unity (Ubuntu) |
Changed in ubuntu-touch-session (Ubuntu): | |
assignee: | nobody → Łukasz Zemczak (sil2100) |
Changed in gsettings-ubuntu-touch-schemas (Ubuntu): | |
status: | New → Invalid |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
assignee: | Michał Sawicz (saviq) → Łukasz Zemczak (sil2100) |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Committed |
Changed in canonical-devices-system-image: | |
status: | Fix Committed → Fix Released |
Tested now also on mako, same problem. ubuntu channel, ubuntu= 20160719, device= 20160402, custom= 20160719, version= 44