[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2022-11-04 Thread Łukasz Zemczak
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1604421 Title:

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-19 Thread Launchpad Bug Tracker
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

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-17 Thread Łukasz Zemczak
** 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

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Andrea Azzarone
** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gsettings-ubuntu-touch-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1604421 Title: Unity 8 fails to start on staging (xenial) on the phone

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Michał Sawicz
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

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Sebastien Bacher
** No longer affects: glib2.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1604421 Title: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Łukasz Zemczak
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:

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Michał Sawicz
** 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 Desktop Bugs, which is subscribed to glib2.0

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Łukasz Zemczak
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 Desktop Bugs, which is subscribed to glib2.0 in

[Bug 1604421] Re: Unity 8 fails to start on staging (xenial) on the phone when --wipe is used for flashing

2016-08-16 Thread Michał Sawicz
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 --