This bug was fixed in the package ubuntu-touch-session -
0.108+16.10.20160817.1-0ubuntu1
---
ubuntu-touch-session (0.108+16.10.20160817.1-0ubuntu1) yakkety; urgency=medium
[ Łukasz 'sil2100' Zemczak ]
* Modify the add_custom_to_xdg_data.sh profile.d hook to not modify
the
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start on staging (xenial) on
** Branch linked: lp:~sil2100/ubuntu-touch-
session/fix_bootability_on_xenial
** Changed in: gsettings-ubuntu-touch-schemas (Ubuntu)
Status: New => Invalid
** Changed in: canonical-devices-system-image
Status: Confirmed => In Progress
** Changed in: canonical-devices-system-image
Ok, it seems that the culprit is my quick-fix add_custom_to_xdg_data.sh
in profile.d! I tracked it down and it seems to be causing the invalid
.profile. The reason is yet unknown, but I suppose something changed and
now it was applied in a different order than on vivid. I checked the
values and it
** Changed in: ubuntu-touch-session (Ubuntu)
Assignee: (unassigned) => Łukasz Zemczak (sil2100)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start on staging
** No longer affects: unity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
To
It seems as if XDG_DATA_DIRS gets cleared out at some time (you can see
the "::" where the previous XDG_DATA_DIRS content should have been),
wonder what component could have caused this. There was no change in
ubuntu-touch-session that actually sets the .profile file.
As Pat pointed out on IRC a
The problem seems to be:
$ initctl get-env -g XDG_DATA_DIRS
/usr/share/ubuntu-touch:/usr/share/ubuntu-touch:/usr/share/ubuntu-touch:/usr/share/ubuntu-touch::/custom/usr/share/:/custom/usr/share/
Compared to a working, upgraded device:
$ initctl get-env -g XDG_DATA_DIRS
** No longer affects: glib2.0 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to 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
To
Looking at the commitlog, from the packages that could have touched
anything related to schemas, I see two package uploads happening between
image #40 (xenial working) and image #41 (xenial broken):
- gsettings-ubuntu-touch-schemas (0.0.7+16.04.20160615.1-0ubuntu1) >
gsettings-ubuntu-schemas:
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gsettings-ubuntu-touch-schemas (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Commitlog for 41 if needed.
** Attachment added: "41.commitlog"
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1604421/+attachment/4722067/+files/41.commitlog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirmed, something on vivid makes the schemas work, if you wipe or
bootstrap, glib can't find them.
glib-compile-schemas doesn't help, something else must be different
between a vivid upgrade and fresh xenial.
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
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)
I confirm Timo's findings. vivid + upgrade (with udf) works, fresh
xenial doesn't boot. Here is the diff between writable parts of the 2
installation. Left is vivid+upgrade, right is xenial.
** Patch added: "vivid-xenial.diff"
Updated to the fact that it's possible to get staging working by not
using using wipe/bootstrap.
** Summary changed:
- Unity 8 fails to start on staging (xenial) on the phone
+ Unity 8 fails to start on staging (xenial) on the phone when --wipe is used
for flashing
** Description changed:
+
I think testing flashing 40 + flashing newer without --bootstrap/--wipe
was never done.
You can try using my (still working, flashed formerly and dist-upgraded)
krillin's home directory:
https://private-fileshare.canonical.com/~tjyrinki/krillin/
Likewise I could extract pieces of / or other
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
** Changed in: canonical-devices-system-image
Status: New => Confirmed
** Changed in: canonical-devices-system-image
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I did upgrades from image 40 and finally ended up with everything
upgraded and Unity 8 still starting fine. So it seems it would tarball
related.
The 41 details: version_detail:
ubuntu=20160713,device=20160402,custom=20160713,version=41
-> custom tarball was updated from 20160623 to 20160713
->
version_detail:
ubuntu=20160623,device=20160402,custom=20160623,version=40
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start on staging (xenial) on the phone
To
@Daniel I don't think systemd is to blame, older xenial images worked.
Upstart is still in uses as well for example starting/stopping unity8
via /sbin/initctl.
It's the image 40 which is the last one that works. 41 and newer are
broken. The diff in packages between 40 and 41 is quite big:
It's something very recent. Image 40 on ubuntu staging does boot to
Unity 8. I will continue bisecting tomorrow.
That is, on my mako ubuntu-device-flash touch --channel=ubuntu-
touch/staging/ubuntu --developer-mode --password= --wipe
--revision=40 --bootstrap boots to unity8.
--
You
** Changed in: canonical-devices-system-image
Assignee: (unassigned) => Michał Sawicz (saviq)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start on staging
I give up. Everything is crashing repeatedly there and I don't know how
to control services there as upstart seems no longer used.
systemctl also doesn't seem to be working correctly. At least not like
it does on the desktop.
systemctl list-units for instance fails with:
Failed to list units: No
** Changed in: unity8 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start on staging (xenial) on the phone
To manage
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start on staging (xenial) on
Tested now also on mako, same problem. ubuntu channel,
ubuntu=20160719,device=20160402,custom=20160719,version=44
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1604421
Title:
Unity 8 fails to start
** Description changed:
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
29 matches
Mail list logo
