[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Description changed: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto - 4. run lxd image create script to create the android lxd image. - - $ ./lxd-image-create.sh - - 5. create an ephemeral container for debug: - - $ lxc init -e -p android android armhf - $ lxc start armhf + 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android- + config/lxd-migration/+merge/311103 . This cause the system to + automatically import android initrd as an lxd image and to start it up + on boot. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. apply changes from https://code.launchpad.net/~vicamo/lxc-android- config/lxd-migration/+merge/311103 . This cause the system to automatically import android initrd as an lxd image and to start it up on boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641561] Re: make android lxc as a snap
Filed bug 1644787 to upgrade initrd package to xenial one. Need some hacks in initrd touch script. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641561 Title: make android lxc as a snap Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: With snapd running in current Ubuntu Touch Xenial port, we'd like to package whole android container as a snap for the final all-snap target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641561/+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
[Touch-packages] [Bug 1644445] Re: avila xenial+systemd port takes too long to boot to GUI
** Merge proposal linked: https://code.launchpad.net/~vicamo/repowerd/+git/repowerd/+merge/311694 ** Changed in: repowerd (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress ** Changed in: repowerd (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-touch-session (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/165 Title: avila xenial+systemd port takes too long to boot to GUI Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: In Progress Status in repowerd package in Ubuntu: In Progress Status in ubuntu-touch-session package in Ubuntu: In Progress Bug description: We found devices will take about 80 seconds to show the ubuntu flash UI, and after about 60 seconds to show the login UI. So it will take more than 2 minutes to boot up the system. [[1. on xenial+systemd/arm64]]: Second boot time: Without flight mode: 25s to ubuntu splash, 93s to login dialog With flight mode: 46s to ubuntu splash, 120s to login dialog Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s to login dialog. Worse cases are also observed. $ adb shell system-image-cli -i current build number: 84 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-17 03:23:16 version version: 84 version ubuntu: 20161117 version device: 20161014.0 version custom: 20161117 [[2. on vivid+upstart/armhf]]: Second boot time: Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to login dialog. However I have this only once and am never able to reproduce the same. The usual cases have almost no difference from the following two cases. All boot to splash in 10s and login dialog in around 22s. With flight mode: 9s to ubuntu splash, 19s to login dialog Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s to login dialog $ adb shell system-image-cli -i current build number: 235 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-11-19 11:56:02 version version: 235 version ubuntu: 20161119 version device: 20160809.0 version custom: 20160831--42-26-vivid [[Debug Tips]] 1. Flash xenial user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/staging/ubuntu \ --device=frieza_arm64 [--recovery-image=recovery.img] 2. Flash vivid user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \ --device=frieza [--recovery-image=recovery.img] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/165/+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
[Touch-packages] [Bug 1644445] Re: avila xenial+systemd port takes too long to boot to GUI
** Branch linked: lp:~vicamo/lxc-android-config/bug-165-fix-xenial- slow-boot ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Also affects: repowerd (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) ** Changed in: ubuntu-touch-session (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/165 Title: avila xenial+systemd port takes too long to boot to GUI Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Status in repowerd package in Ubuntu: New Status in ubuntu-touch-session package in Ubuntu: New Bug description: We found devices will take about 80 seconds to show the ubuntu flash UI, and after about 60 seconds to show the login UI. So it will take more than 2 minutes to boot up the system. [[1. on xenial+systemd/arm64]]: Second boot time: Without flight mode: 25s to ubuntu splash, 93s to login dialog With flight mode: 46s to ubuntu splash, 120s to login dialog Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s to login dialog. Worse cases are also observed. $ adb shell system-image-cli -i current build number: 84 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-17 03:23:16 version version: 84 version ubuntu: 20161117 version device: 20161014.0 version custom: 20161117 [[2. on vivid+upstart/armhf]]: Second boot time: Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to login dialog. However I have this only once and am never able to reproduce the same. The usual cases have almost no difference from the following two cases. All boot to splash in 10s and login dialog in around 22s. With flight mode: 9s to ubuntu splash, 19s to login dialog Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s to login dialog $ adb shell system-image-cli -i current build number: 235 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-11-19 11:56:02 version version: 235 version ubuntu: 20161119 version device: 20160809.0 version custom: 20160831--42-26-vivid [[Debug Tips]] 1. Flash xenial user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/staging/ubuntu \ --device=frieza_arm64 [--recovery-image=recovery.img] 2. Flash vivid user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \ --device=frieza [--recovery-image=recovery.img] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/165/+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
[Touch-packages] [Bug 1644445] Re: avila xenial+systemd port takes too long to boot to GUI
** Branch linked: lp:~vicamo/ubuntu-touch-session/bug-165-depends- on-android-target -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/165 Title: avila xenial+systemd port takes too long to boot to GUI Status in Canonical System Image: New Status in ubuntu-touch-session package in Ubuntu: New Bug description: We found devices will take about 80 seconds to show the ubuntu flash UI, and after about 60 seconds to show the login UI. So it will take more than 2 minutes to boot up the system. [[1. on xenial+systemd/arm64]]: Second boot time: Without flight mode: 25s to ubuntu splash, 93s to login dialog With flight mode: 46s to ubuntu splash, 120s to login dialog Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s to login dialog. Worse cases are also observed. $ adb shell system-image-cli -i current build number: 84 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-17 03:23:16 version version: 84 version ubuntu: 20161117 version device: 20161014.0 version custom: 20161117 [[2. on vivid+upstart/armhf]]: Second boot time: Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to login dialog. However I have this only once and am never able to reproduce the same. The usual cases have almost no difference from the following two cases. All boot to splash in 10s and login dialog in around 22s. With flight mode: 9s to ubuntu splash, 19s to login dialog Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s to login dialog $ adb shell system-image-cli -i current build number: 235 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-11-19 11:56:02 version version: 235 version ubuntu: 20161119 version device: 20160809.0 version custom: 20160831--42-26-vivid [[Debug Tips]] 1. Flash xenial user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/staging/ubuntu \ --device=frieza_arm64 [--recovery-image=recovery.img] 2. Flash vivid user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \ --device=frieza [--recovery-image=recovery.img] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/165/+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
[Touch-packages] [Bug 1643459] Re: additional writable paths for other system services
** Patch added: "0001-misc-create-var-lib-udisks2-in-post-install.patch" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1643459/+attachment/4782317/+files/0001-misc-create-var-lib-udisks2-in-post-install.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1643459 Title: additional writable paths for other system services Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: New Bug description: /var/tmp: rtkit systemd service uses PrivateTmp /var/lib/udisks2: udisks2 /var/lib/dhcp: isc-dhcp-server leases files To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643459/+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
[Touch-packages] [Bug 1643459] Re: additional writable paths for other system services
/var/lib/udisks2 has to exist after the installation so that we may bind mount it to writable /userdata partition. Don't know where to land the patch yet. ** Branch linked: lp:~vicamo/lxc-android-config/more-writable-paths ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1643459 Title: additional writable paths for other system services Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: In Progress Status in udisks2 package in Ubuntu: New Bug description: /var/tmp: rtkit systemd service uses PrivateTmp /var/lib/udisks2: udisks2 /var/lib/dhcp: isc-dhcp-server leases files To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643459/+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
[Touch-packages] [Bug 1644445] [NEW] avila xenial+systemd port takes too long to boot to GUI
Public bug reported: We found devices will take about 80 seconds to show the ubuntu flash UI, and after about 60 seconds to show the login UI. So it will take more than 2 minutes to boot up the system. [[1. on xenial+systemd/arm64]]: Second boot time: Without flight mode: 25s to ubuntu splash, 93s to login dialog With flight mode: 46s to ubuntu splash, 120s to login dialog Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s to login dialog. Worse cases are also observed. $ adb shell system-image-cli -i current build number: 84 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-17 03:23:16 version version: 84 version ubuntu: 20161117 version device: 20161014.0 version custom: 20161117 [[2. on vivid+upstart/armhf]]: Second boot time: Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to login dialog. However I have this only once and am never able to reproduce the same. The usual cases have almost no difference from the following two cases. All boot to splash in 10s and login dialog in around 22s. With flight mode: 9s to ubuntu splash, 19s to login dialog Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s to login dialog $ adb shell system-image-cli -i current build number: 235 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-11-19 11:56:02 version version: 235 version ubuntu: 20161119 version device: 20160809.0 version custom: 20160831--42-26-vivid [[Debug Tips]] 1. Flash xenial user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/staging/ubuntu \ --device=frieza_arm64 [--recovery-image=recovery.img] 2. Flash vivid user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \ --device=frieza [--recovery-image=recovery.img] ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-touch-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-session in Ubuntu. https://bugs.launchpad.net/bugs/165 Title: avila xenial+systemd port takes too long to boot to GUI Status in Canonical System Image: New Status in ubuntu-touch-session package in Ubuntu: New Bug description: We found devices will take about 80 seconds to show the ubuntu flash UI, and after about 60 seconds to show the login UI. So it will take more than 2 minutes to boot up the system. [[1. on xenial+systemd/arm64]]: Second boot time: Without flight mode: 25s to ubuntu splash, 93s to login dialog With flight mode: 46s to ubuntu splash, 120s to login dialog Without flight mode, but disable ofono completely: 84s to ubuntu splash, 143s to login dialog. Worse cases are also observed. $ adb shell system-image-cli -i current build number: 84 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-11-17 03:23:16 version version: 84 version ubuntu: 20161117 version device: 20161014.0 version custom: 20161117 [[2. on vivid+upstart/armhf]]: Second boot time: Without flight mode: The worse case I got is 78s to ubuntu splash, 92s to login dialog. However I have this only once and am never able to reproduce the same. The usual cases have almost no difference from the following two cases. All boot to splash in 10s and login dialog in around 22s. With flight mode: 9s to ubuntu splash, 19s to login dialog Without flight mode, but disable ofono completely: 9s to ubuntu splash, 21s to login dialog $ adb shell system-image-cli -i current build number: 235 device name: frieza channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en last update: 2016-11-19 11:56:02 version version: 235 version ubuntu: 20161119 version device: 20160809.0 version custom: 20160831--42-26-vivid [[Debug Tips]] 1. Flash xenial user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/staging/ubuntu \ --device=frieza_arm64 [--recovery-image=recovery.img] 2. Flash vivid user build: $ ubuntu-device-flash touch --bootstrap --wipe \ --channel=ubuntu-touch/rc-proposed/bq-aquaris-pd.en \ --device=frieza [--recovery-image=recovery.img] To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/165/+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
[Touch-packages] [Bug 1643459] [NEW] additional writable paths for other system services
Public bug reported: /var/tmp: rtkit systemd service uses PrivateTmp /var/lib/udisks2: udisks2 /var/lib/dhcp: isc-dhcp-server leases files ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1643459 Title: additional writable paths for other system services Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: /var/tmp: rtkit systemd service uses PrivateTmp /var/lib/udisks2: udisks2 /var/lib/dhcp: isc-dhcp-server leases files To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1643459/+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
[Touch-packages] [Bug 1642535] Re: need /var/snap writable-path for snappy global data
** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1642535 Title: need /var/snap writable-path for snappy global data Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: This is a follow-up for bug 1632272. From snap-confine source code[1], when running on classic distribution as we're for ubuntu-touch, some additional paths are mounted. They are /dev, /etc, /home, /root, /proc, /sys, /tmp, /var/snap, /var/lib/snapd, /var/tmp, /run, /lib/modules, /media, etc. Among them, /var/snap is necessary for lxd snap global data like pid file, daemon socket, and images. [1]: https://github.com/snapcore/snap-confine/blob/master/src/mount- support.c#L556 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642535/+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
[Touch-packages] [Bug 1632272] Re: need writable-path for snappy
It turns out we also need /var/snap for lxd snap, which writes some global data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1632272 Title: need writable-path for snappy Status in Canonical System Image: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Bug description: Snappy writes to /etc/systemd/system, /snap and /var/lib/snapd. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632272/+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
[Touch-packages] [Bug 1642535] Re: need /var/snap writable-path for snappy global data
** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~vicamo/lxc-android-config/lxd-snap-writable-path -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1642535 Title: need /var/snap writable-path for snappy global data Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: This is a follow-up for bug 1632272. From snap-confine source code[1], when running on classic distribution as we're for ubuntu-touch, some additional paths are mounted. They are /dev, /etc, /home, /root, /proc, /sys, /tmp, /var/snap, /var/lib/snapd, /var/tmp, /run, /lib/modules, /media, etc. Among them, /var/snap is necessary for lxd snap global data like pid file, daemon socket, and images. [1]: https://github.com/snapcore/snap-confine/blob/master/src/mount- support.c#L556 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1642535/+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
[Touch-packages] [Bug 1632272] Re: need writable-path for snappy
Filed follow-up bug 1642535. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1632272 Title: need writable-path for snappy Status in Canonical System Image: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Bug description: Snappy writes to /etc/systemd/system, /snap and /var/lib/snapd. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632272/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
All known issues in comment 8 addressed, so I think that's all we need for lxd porting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1638204] Re: install snapd in default ubuntu xenial image
Confirmed installed in ubuntu-touch version 1.264xenial19, or system- image rev 84. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1638204 Title: install snapd in default ubuntu xenial image Status in Canonical System Image: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Bug description: currently m10 have arm64 branch. we want to run snapd on it ! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1638204/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Also affects: urfkill (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Status in urfkill package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Update prebuilt boot.img with current kernel changes in https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 ** Attachment added: "boot.img" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4778450/+files/boot.img -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
audit namespace issue fixed in upstream https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f9441639e6319f0c0e12bd63fa2f58990af0a9d2 and https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=33faba7fa7f2288d2f8aaea95958b2c97bf9ebfb . Already included in my kernel merge proposal. ** Attachment removed: "boot.img" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777591/+files/boot.img -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Branch linked: lp:~vicamo/lxc-android-config/lxd-migration ** Branch unlinked: lp:~vicamo/lxc-android-config/lxd-writable-path -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
AppArmor is not functioning this way Hmmm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Add audit=0 to kernel command line and logd ceases to try kernel audit, and the rest of the system (lxd/snap) doesn't seem to be affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Another issue seems to relate to the kernel version again. In logcat messages I found logd restarts over and over again due to failure when sending audit netlink messages. It seems lxd fails to setup some cgroups: cgroups controllers for blkio/memory/network/pids/... not found. I/UpstartPropertyWatcher( 1833): Property changed: init.svc.logd=running E/libaudit(30123): Error sending data over the netlink socket: Unknown error -111 E/libaudit(30123): Could net set pid for audit events, error: Connection refused I/UpstartPropertyWatcher( 1833): Property changed: init.svc.logd=restarting -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
With some hacking with systemd, now lxd image boots and GUI is available. Some refinements are needed. Known issues: 1. lxc tries to write client.srt to /root/.config/lxc, which should be read-only by default. Add --force-local to every lxc command invoked fixes this issue. 2. Currently I'm launching lxd container via `lxc launch -e ...`, but it would be nice if that's somehow covered by lxd daemon. Don't know if it's possible to create an ephemeral yet autostart container in a formal way. 3. wifi/bluetooth is not available at boot because urfkill starts before the container. Need a manual restart to urfkill. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Script to generate android lxd image from /android/system/boot/android- ramdisk.img ** Attachment removed: "lxd-image-create.sh" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777635/+files/lxd-image-create.sh ** Attachment added: "lxd-image-create.sh" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777978/+files/lxd-image-create.sh ** Description changed: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. - 5. edit lxd profile manually because it doesn't currently support - setting multiple entries of "raw.lxc" config: + $ ./lxd-image-create.sh - $ lxc profile edit android - # This should bring up an editor, default nano. Use - # `update-alternatives --config editor` to choose the one you like. - # The result should be: - $ lxc profile show android - name: android - config: - raw.lxc: | - lxc.devttydir=lxc - lxc.tty=4 - lxc.cap.drop=mac_admin mac_override - lxc.aa_profile=unconfined - lxc.autodev=0 - lxc.init_cmd=/init - lxc.cgroup.devices.allow = a - lxc.mount.auto= - lxc.mount.auto=sys:rw proc:mixed cgroup:mixed - security.nesting: "true" - security.privileged: "true" - description: "" - devices: - dev_socket: - path: /dev/socket - source: /dev/socket - type: disk - - 6. create an ephemeral container for debug: + 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. $ ./lxd-image-create.sh 5. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Current status: with following three lines added to the profile, ueventd processes devices as usual. But I can't still found any daemon process with executable located in /system running. /proc/$(pidof init)/mounts shows /system and all other partitions have been correctly mounted. lxc.cgroup.devices.allow = a lxc.mount.auto= lxc.mount.auto=sys:rw proc:mixed cgroup:mixed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init lxc.cgroup.devices.allow = a lxc.mount.auto= lxc.mount.auto=sys:rw proc:mixed cgroup:mixed security.nesting: "true" security.privileged: "true" description: "" devices: dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Description changed: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init + lxc.cgroup.devices.allow = a + lxc.mount.auto= + lxc.mount.auto=sys:rw proc:mixed cgroup:mixed security.nesting: "true" security.privileged: "true" description: "" devices: - dev_binder: - path: /dev/binder - type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init lxc.cgroup.devices.allow = a lxc.mount.auto= lxc.mount.auto=sys:rw proc:mixed cgroup:mixed security.nesting: "true" security.privileged: "true" description: "" devices: dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Script to generate android lxd image from /android/system/boot/android- ramdisk.img ** Attachment added: "lxd-image-create.sh" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777635/+files/lxd-image-create.sh -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
** Branch linked: lp:~vicamo/lxc-android-config/lxd-writable-path ** Description changed: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). - $ lxd init --auto + $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 , or just use the prebuilt one in the attachments. 1. follow bug 1641505 and https://bugs.launchpad.net/canonical- devices-system-image/+bug/1641505/comments/2 to enable adbd emergency mode and disable current lxc-based android container. 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ sudo lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Prebuilt boot image with https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 applied. ** Merge proposal linked: https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 ** Description changed: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. + + [Steps to reproduce current setup] + 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 + 1. add /var/lib/lxd to writable paths + 2. install lxd, lxd-client and then reboot the device so that writable path may take effect. + 3. initialize lxd. This can take a while (2 minutes for me). + + $ lxd init --auto + + 4. run lxd image create script to create the android lxd image. + 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: + + $ lxc profile edit android + # This should bring up an editor, default nano. Use + # `update-alternatives --config editor` to choose the one you like. + # The result should be: + $ lxc profile show android + name: android + config: + raw.lxc: | + lxc.devttydir=lxc + lxc.tty=4 + lxc.cap.drop=mac_admin mac_override + lxc.aa_profile=unconfined + lxc.autodev=0 + lxc.init_cmd=/init + security.nesting: "true" + security.privileged: "true" + description: "" + devices: + dev_binder: + path: /dev/binder + type: unix-char + dev_socket: + path: /dev/socket + source: /dev/socket + type: disk + + 6. create an ephemeral container for debug: + + $ lxc init -e -p android android armhf + $ lxc start armhf ** Attachment added: "boot.img" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1641549/+attachment/4777591/+files/boot.img ** Description changed: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] - 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 - 1. add /var/lib/lxd to writable paths - 2. install lxd, lxd-client and then reboot the device so that writable path may take effect. + + 0. rebuild avila kernel with additional patches from + https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 + + 1. follow bug 1641505 and https://bugs.launchpad.net/canonical-devices- + system-image/+bug/1641505/comments/2 to enable adbd emergency mode and + disable current lxc-based android container. + + 2. add /var/lib/lxd to writable paths, install lxd and lxd-client, and + then reboot the device so that writable path may take effect. + 3. initialize lxd. This can take a while (2 minutes for me). - $ lxd init --auto + $ lxd init --auto 4. run lxd image create script to create the android lxd image. - 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: - $ lxc profile edit android - # This should bring up an editor, default nano. Use - # `update-alternatives --config editor` to choose the one you like. - # The result should be: - $ lxc profile show android - name: android - config: - raw.lxc: | - lxc.devttydir=lxc - lxc.tty=4 - lxc.cap.drop=mac_admin mac_override - lxc.aa_profile=unconfined - lxc.autodev=0 - lxc.init_cmd=/init - security.nesting: "true" - security.privileged: "true" - description: "" - devices: - dev_binder: - path: /dev/binder - type: unix-char - dev_socket: - path: /dev/socket - source: /dev/socket - type: disk + 5. edit lxd profile manually because it doesn't currently support + setting multiple entries of "raw.lxc" config: + + $ lxc profile edit android + # This should bring up an editor, default nano. Use + # `update-alternatives --config editor` to choose the one you like. + # The result should be: + $ lxc profile show android + name: android + config: + raw.lxc: | + lxc.devttydir=lxc + lxc.tty=4 + lxc.cap.drop=mac_admin mac_override + lxc.aa_profile=unconfined + lxc.autodev=0 + lxc.init_cmd=/init + security.nesting: "true" + security.privileged: "true" + description: "" + devices: + dev_binder: + path: /dev/binder + type: unix-char + dev_socket: + path: /dev/socket + source: /dev/socket +
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Again, the fundermental reason init dies is a critical core service healthd dies, so it's not really about background/foreground here. And healthd dies because it fails to open /dev/binder. It follows in lxd, ueventd is not correctly running yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. [Steps to reproduce current setup] 0. rebuild avila kernel with additional patches from https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/310849 1. add /var/lib/lxd to writable paths 2. install lxd, lxd-client and then reboot the device so that writable path may take effect. 3. initialize lxd. This can take a while (2 minutes for me). $ lxd init --auto 4. run lxd image create script to create the android lxd image. 5. edit lxd profile manually because it doesn't currently support setting multiple entries of "raw.lxc" config: $ lxc profile edit android # This should bring up an editor, default nano. Use # `update-alternatives --config editor` to choose the one you like. # The result should be: $ lxc profile show android name: android config: raw.lxc: | lxc.devttydir=lxc lxc.tty=4 lxc.cap.drop=mac_admin mac_override lxc.aa_profile=unconfined lxc.autodev=0 lxc.init_cmd=/init security.nesting: "true" security.privileged: "true" description: "" devices: dev_binder: path: /dev/binder type: unix-char dev_socket: path: /dev/socket source: /dev/socket type: disk 6. create an ephemeral container for debug: $ lxc init -e -p android android armhf $ lxc start armhf To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
With comment #1 fixed with a patched kernel, it seems we bumped into bug 1625916 again. Need to run lxc in the background. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641549] Re: migrate lxc android container to lxd
Again, avila's kernel is pretty outdated, and its user namespace support is so poor that it's actually mis-behave on a certain security related operations. In security/commoncap.c, function cap_prctl_drop, it should check `ns_capable(...)`, not just `capable(...)`. See https://github.com/lxc/lxd/issues/2039 . At lease commit 160da84 "userns: Allow PR_CAPBSET_DROP in a user namespace" has to be cherry- picked, but besides that, I also found a lot similar places to be fixed. ** Bug watch added: LXD bug tracker #2039 https://github.com/lxc/lxd/issues/2039 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641561] Re: make android lxc as a snap
http://bazaar.launchpad.net/~timo-jyrinki/+junk/uitk- gallery/view/head:/snapcraft.yaml reference for snappy content interface. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641561 Title: make android lxc as a snap Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: With snapd running in current Ubuntu Touch Xenial port, we'd like to package whole android container as a snap for the final all-snap target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641561/+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
[Touch-packages] [Bug 1641561] Re: make android lxc as a snap
With bug 1641549, we're also trying to migrate current lxc-based android container to lxd image. Snap interface to access lxd is in bug 1634880. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641561 Title: make android lxc as a snap Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: With snapd running in current Ubuntu Touch Xenial port, we'd like to package whole android container as a snap for the final all-snap target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641561/+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
[Touch-packages] [Bug 1641561] [NEW] make android lxc as a snap
Public bug reported: With snapd running in current Ubuntu Touch Xenial port, we'd like to package whole android container as a snap for the final all-snap target. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641561 Title: make android lxc as a snap Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: With snapd running in current Ubuntu Touch Xenial port, we'd like to package whole android container as a snap for the final all-snap target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641561/+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
[Touch-packages] [Bug 1641549] [NEW] migrate lxc android container to lxd
Public bug reported: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Tags: lxd systemd ** Description changed: Several things to do here: - * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function. - * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc. + * include lxd, lxd-client in default installation, + * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, + * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Tags added: lxd systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641549 Title: migrate lxc android container to lxd Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: Several things to do here: * include lxd, lxd-client in default installation, * writable path for lxd: lxd resides at /var/lib/lxd and it takes write permission to fully function, * migrate lxc tmpfs-based rootfs to lxd image, lxc configs to lxd profiles, etc., * migrate systemd service definitions, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641549/+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
[Touch-packages] [Bug 1641505] Re: support adbd emergency shell under systemd
With the two patches, one may test adbd emergency shell manually by replacing ExecStart command with `/bin/false` in either lxc-android- config or lightdm systemd service. ** Branch linked: lp:~vicamo/lxc-android-config/adbd-emergency-shell ** Changed in: android-tools (Ubuntu) Status: New => In Progress ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641505 Title: support adbd emergency shell under systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: In Progress Status in lxc-android-config package in Ubuntu: In Progress Bug description: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641505/+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
[Touch-packages] [Bug 1641505] Re: support adbd emergency shell under systemd
Patch for source package android-tools to add a systemd ExecStopPost hook /usr/lib/android-tools-adbd/start-emergency-shell for other packages. ** Patch added: "0001-Add-adbd-emergency-shell-systemd-support.patch" https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1641505/+attachment/4777092/+files/0001-Add-adbd-emergency-shell-systemd-support.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1641505 Title: support adbd emergency shell under systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641505/+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
[Touch-packages] [Bug 1641505] [NEW] support adbd emergency shell under systemd
Public bug reported: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: android-tools (Ubuntu) Importance: Undecided Assignee: Vicamo Yang (vicamo) Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Assignee: Vicamo Yang (vicamo) Status: New ** Tags: systemd ** Tags added: systemd ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: android-tools (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) ** Changed in: lxc-android-config (Ubuntu) Assignee: (unassigned) => Vicamo Yang (vicamo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1641505 Title: support adbd emergency shell under systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently adbd emergency shell is only available under upstart, so some work is needed to bring it up under systemd as well. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1641505/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev - 56. + 59. - 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to create an additional symbolic link to automatically enable adb access (bug 1632602). You can do this under recovery mode: - device# cd /ubuntu/etc/systemd/system - device# mkdir android-contai...@ro.build.type\\x3duser.target.wants - device# cd android-contai...@ro.build.type\\x3duser.target.wants - device# ln -s /lib/systemd/system/android-tools-adbd.service + 2. Go to Settings::About page to enable developer mode. - 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) - host$ adb shell - device# mkdir ubuntu - device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu - device# exit - host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . - (edit the file as mp[2] does ...) - host$ adb push upstart-local-bridge.service \ - /ubuntu/lib/systemd/system/upstart-local-bridge.service - host$ adb shell - device# sync; sync; sync - device# umount /ubuntu - device# exit - host$ adb reboot - - 3. Go to Settings::About page to enable developer mode. - - [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial - [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 - - [All Pending MPs] - - 1. lxc-android-config: - * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 + [1]: https://code.launchpad.net/~avila-private-team/avila- + private/+git/platform_manifest/+ref/xenial [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 59. 2. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila- private/+git/platform_manifest/+ref/xenial [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
There is no more work to do for systemd bring up. For snappy bring up, bug 1632272 and bug 1633367 are still open/waiting for review. ** Changed in: upstart (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Released Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 59. 2. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila- private/+git/platform_manifest/+ref/xenial [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1632260] Re: adb shell is not available under xenial+systemd, upstart-local-bridge not running
Confirmed included in version 0.230+16.04.20161011-0ubuntu1, rootfs rev59. ** Changed in: lxc-android-config (Ubuntu) Status: New => Fix Released ** Changed in: canonical-devices-system-image Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1632260 Title: adb shell is not available under xenial+systemd, upstart-local-bridge not running Status in Canonical System Image: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Bug description: It seems there is still some problems in the systemd/upstart mix environment. So far running upstart-local-bridge in foreground mode stablize this a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632260/+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
[Touch-packages] [Bug 1632602] Re: no adb access under xenial+systemd user build
All necessary changes merged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1632602 Title: no adb access under xenial+systemd user build Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Bug description: adb service under user build involves several other parties and is currently not implemented. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632602/+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
[Touch-packages] [Bug 1632602] Re: no adb access under xenial+systemd user build
Temp work-arounds have been proposed. Please keep this bug open even if they're merged later. ** Changed in: android-tools (Ubuntu) Status: New => In Progress ** Changed in: android-tools (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1632602 Title: no adb access under xenial+systemd user build Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Bug description: adb service under user build involves several other parties and is currently not implemented. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632602/+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
[Touch-packages] [Bug 1632272] Re: need writable-path for snappy
** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1632272 Title: need writable-path for snappy Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Snappy writes to /etc/systemd/system, /snap and /var/lib/snapd. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632272/+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
[Touch-packages] [Bug 1632272] Re: need writable-path for snappy
** Tags added: snappy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1632272 Title: need writable-path for snappy Status in Canonical System Image: Confirmed Status in lxc-android-config package in Ubuntu: New Bug description: Snappy writes to /etc/systemd/system, /snap and /var/lib/snapd. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632272/+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
[Touch-packages] [Bug 1632602] Re: no adb access under xenial+systemd user build
After some discussion, we can also enable "ro.debuggable=1" in user builds temporarily and revert it when all is ready. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1632602 Title: no adb access under xenial+systemd user build Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Bug description: adb service under user build involves several other parties and is currently not implemented. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632602/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 56. - 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to create an additional symbolic link to automatically enable adb access. You can do this under recovery mode: + 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to create an additional symbolic link to automatically enable adb access (bug 1632602). You can do this under recovery mode: device# cd /ubuntu/etc/systemd/system device# mkdir android-contai...@ro.build.type\\x3duser.target.wants device# cd android-contai...@ro.build.type\\x3duser.target.wants device# ln -s /lib/systemd/system/android-tools-adbd.service 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 56. 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to create an additional symbolic link to automatically enable adb access (bug 1632602). You can do this under recovery mode: device# cd /ubuntu/etc/systemd/system device# mkdir android-contai...@ro.build.type\\x3duser.target.wants device# cd android-contai...@ro.build.type\\x3duser.target.wants device# ln -s /lib/systemd/system/android-tools-adbd.service 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : h
[Touch-packages] [Bug 1632602] Re: no adb access under xenial+systemd user build
However, like what we've have for eng build, one may simply hook android-tools-adbd service to another valid property under user build, e.g. "ro.build.type=user". device# cd /ubuntu/etc/systemd/system device# mkdir android-contai...@ro.build.type\\x3duser.target.wants device# cd android-contai...@ro.build.type\\x3duser.target.wants device# ln -s /lib/systemd/system/android-tools-adbd.service Here, the folder name is "android- container@\x3d.target.wants". That backslash character is required. ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1632602 Title: no adb access under xenial+systemd user build Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Bug description: adb service under user build involves several other parties and is currently not implemented. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632602/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev - 51. + 56. + + 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to create an additional symbolic link to automatically enable adb access. You can do this under recovery mode: + device# cd /ubuntu/etc/systemd/system + device# mkdir android-contai...@ro.build.type\\x3duser.target.wants + device# cd android-contai...@ro.build.type\\x3duser.target.wants + device# ln -s /lib/systemd/system/android-tools-adbd.service 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 56. 1.1. If your system is a user build, e.g. flashed from u-d-f, you need to create an additional symbolic link to automatically enable adb access (bug 1632602). You can do this under recovery mode: device# cd /ubuntu/etc/systemd/system device# mkdir android-contai...@ro.build.type\\x3duser.target.wants device# cd android-contai...@ro.build.type\\x3duser.target.wants device# ln -s /lib/systemd/system/android-tools-adbd.service 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] - https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161005/rootfs-systemd_rev-51.tar.bz2 - md5sum: 3cf478a654509c67a3d8c097bd0de9ec - build_number: 51 - version_detail: ubuntu=20161005,device=20160919.0,custom=20161005,version=51 + https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 + md5sum: 4fc880e60fcf66857fbbeff6ce58e025 + build_number: 56 + version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161011/rootfs-systemd_rev-56.tar.bz2 md5sum: 4fc880e60fcf66857fbbeff6ce58e025 build_number: 56 version_detail: ubuntu=20161011,device=20160919.0,custom=20161011,version=56 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. - 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. + 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ - /ubuntu/lib/systemd/system/upstart-local-bridge.service + /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161005/rootfs-systemd_rev-51.tar.bz2 md5sum: 3cf478a654509c67a3d8c097bd0de9ec build_number: 51 version_detail: ubuntu=20161005,device=20160919.0,custom=20161005,version=51 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. (bug 1632260) host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] 1. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161005/rootfs-systemd_rev-51.tar.bz2 md5sum: 3cf478a654509c67a3d8c097bd0de9ec build_number: 51 version_detail: ubuntu=20161005,device=20160919.0,custom=20161005,version=51 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1632260] [NEW] adb shell is not available under xenial+systemd, upstart-local-bridge not running
Public bug reported: It seems there is still some problems in the systemd/upstart mix environment. So far running upstart-local-bridge in foreground mode stablize this a lot. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Tags: systemd ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Branch linked: lp:~vicamo/lxc-android-config/foreground-upstart- local-bridge ** Tags added: systemd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1632260 Title: adb shell is not available under xenial+systemd, upstart-local-bridge not running Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: It seems there is still some problems in the systemd/upstart mix environment. So far running upstart-local-bridge in foreground mode stablize this a lot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1632260/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. - 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) - 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. - 2.2. download latest systemd-sysv package [4]. - 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb + 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. + host$ adb shell + device# mkdir ubuntu + device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu + device# exit + host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . + (edit the file as mp[2] does ...) + host$ adb push upstart-local-bridge.service \ + /ubuntu/lib/systemd/system/upstart-local-bridge.service + host$ adb shell + device# sync; sync; sync + device# umount /ubuntu + device# exit + host$ adb reboot - 3. Install android-tools-adbd for systemd (Bug 1627613) - 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. - 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. - - 4. Recompile upstart with merge proposal [8] include and install at - least the built binary /sbin/upstart-local-bridge. - - 5. Reboot. + 3. Go to Settings::About page to enable developer mode. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial - [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ - [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch - [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ - [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb - [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ - [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch - [8]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 + [2]: https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [All Pending MPs] - 1. ubuntu-touch-meta: - * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch - 2. android-tools: - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch - 3. upstart: - * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 + 1. lxc-android-config: + * https://code.launchpad.net/~vicamo/lxc-android-config/foreground-upstart-local-bridge/+merge/308097 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161005/rootfs-systemd_rev-51.tar.bz2 md5sum: 3cf478a654509c67a3d8c097bd0de9ec build_number: 51 version_detail: ubuntu=20161005,device=20160919.0,custom=20161005,version=51 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: In Progress Status in android-tools package in Ubuntu: Fix Released Status in lxc-android-config package in Ubuntu: Fix Released Status in ubuntu-touch-meta package in Ubuntu: Fix Released Status in upstart package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Reboot into recovery mode and manually change upstart-local-bridge service type to simple. host$ adb shell device# mkdir ubuntu device# mount /dev/block/platform/mtk-msdc.0/by-name/system ubuntu device# exit host$ adb pull /ubuntu/lib/systemd/system/upstart-local-bridge.service . (edit the file as mp[2] does ...) host$ adb push upstart-local-bridge.service \ /ubuntu/lib/systemd/system/upstart-local-bridge.service host$ adb shell device# sync; sync; sync device# umount /ubuntu device# exit host$ adb reboot 3. Go to Settings::About page to enable
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Recompile upstart with merge proposal [8] include and install at least the built binary /sbin/upstart-local-bridge. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [All Pending MPs] 1. ubuntu-touch-meta: * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch 2. android-tools: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch 3. upstart: * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [Prebuilt rootfs tarball] - https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 (updated 15:55 +0800) - md5sum: 220c811b8ad7cb978d6b695679ad21fc - build_number: 49 - version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49 + https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161005/rootfs-systemd_rev-51.tar.bz2 + md5sum: 3cf478a654509c67a3d8c097bd0de9ec + build_number: 51 + version_detail: ubuntu=20161005,device=20160919.0,custom=20161005,version=51 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Recompile upstart with merge proposal [8] include and install at least the built binary /sbin/upstart-local-bridge. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.ne
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Recompile upstart with merge proposal [8] include and install at least the built binary /sbin/upstart-local-bridge. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [All Pending MPs] 1. ubuntu-touch-meta: * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch - 2. upstart: + 2. android-tools: + https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch + 3. upstart: * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 (updated 15:55 +0800) md5sum: 220c811b8ad7cb978d6b695679ad21fc build_number: 49 version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Recompile upstart with merge proposal [8] include and install at least the built binary /sbin/upstart-local-bridge. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a - working xenial+upstart avila. + working xenial+upstart avila. Following steps are based on rootfs rev + 51. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. - 4. Modify lxc-android-config package systemd service file by hand as the - merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug - 1626012, bug 1627613). - - 5. Recompile upstart with merge proposal [12] include and install at + 4. Recompile upstart with merge proposal [8] include and install at least the built binary /sbin/upstart-local-bridge. - 6. Reboot. + 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ - [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb + [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch - [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 - [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 - [10]: https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 - [11]: https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 - [12]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 + [8]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [All Pending MPs] 1. ubuntu-touch-meta: * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch - 2. lxc-android-config: - * https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 - * https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 - * https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 - * https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 - 3. upstart: + 2. upstart: * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [Prebuilt rootfs tarball] https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 (updated 15:55 +0800) md5sum: 220c811b8ad7cb978d6b695679ad21fc build_number: 49 version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. Following steps are based on rootfs rev 51. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-to
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [12] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 [10]: https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 [11]: https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 [12]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [All Pending MPs] 1. ubuntu-touch-meta: * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch 2. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 * https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 * https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 * https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 3. upstart: * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [Prebuilt rootfs tarball] - https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 - md5sum: dd185cf1c7aada1623e57319ae139c72 + https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 (updated 15:55 +0800) + md5sum: 220c811b8ad7cb978d6b695679ad21fc build_number: 49 version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the pa
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [12] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 [10]: https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 [11]: https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 [12]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 [All Pending MPs] 1. ubuntu-touch-meta: * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch 2. lxc-android-config: * https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 * https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 * https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 * https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 3. upstart: * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 + + [Prebuilt rootfs tarball] + + https://private-fileshare.canonical.com/~vicamo/avila/images/systemd/ubuntu/20161004/rootfs-systemd.tar.bz2 + build_number: 49 + version_detail: ubuntu=20161001,device=20160919.0,custom=20161001,version=49 ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [12] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-sy
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [12] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 [10]: https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 [11]: https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 [12]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 + + [All Pending MPs] + + 1. ubuntu-touch-meta: + * https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch + 2. lxc-android-config: + * https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 + * https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge/+merge/307144 + * https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable-paths/+merge/306184 + * https://code.launchpad.net/~vicamo/lxc-android-config/disable-systemd-alsa-restore/+merge/306587 + 3. upstart: + * https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9][10][11] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [12] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Attachment removed: "android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) - 3.1. Recompile it from source [6] with patch [7] applied. + 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Recompile upstart with merge proposal [10] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ - [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb + [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge [10]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the - merge proposal [8][9] does. (Bug 1625445, bug 1625916 and bug 1626012). + merge proposal [8][9] does. (Bug 1625445, bug 1625916, bug 1626012, bug + 1627613). 5. Recompile upstart with merge proposal [10] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+m
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Attachment added: "ubuntu-touch_1.264xenial17+systemd_arm64.deb" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4751598/+files/ubuntu-touch_1.264xenial17+systemd_arm64.deb ** Attachment removed: "ubuntu-touch_1.264xenial13+systemd_arm64.deb" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4743481/+files/ubuntu-touch_1.264xenial13+systemd_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Install prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9] does. (Bug 1625445, bug 1625916, bug 1626012, bug 1627613). 5. Recompile upstart with merge proposal [10] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge [10]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
Add prebuilt lxc-android-config package with mp https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local- bridge, https://code.launchpad.net/~vicamo/lxc-android-config/disable- systemd-alsa-restore/+merge/306587, https://code.launchpad.net/~vicamo /lxc-android-config/fix-systemd-service-startup/+merge/306435, https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable- paths/+merge/306184 applied. ** Attachment added: "lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751443/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
Add prebuilt package with https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001 -install-systemd-service-files.patch applied. ** Attachment added: "android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751442/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
Prebuilt package with https://code.launchpad.net/~vicamo/upstart/xenial- escape-systemd-strings applied. ** Attachment added: "upstart_1.13.2-0ubuntu21.1_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4751437/+files/upstart_1.13.2-0ubuntu21.1_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) - 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. + 3.1. Recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. - 4. Modify lxc-android-config package [8] systemd service file by hand as - the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). + 4. Modify lxc-android-config package systemd service file by hand as the + merge proposal [8][9] does. (Bug 1625445, bug 1625916 and bug 1626012). - 5. Reboot. + 5. Recompile upstart with merge proposal [10] include and install at + least the built binary /sbin/upstart-local-bridge. + + 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ - [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch - [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb - [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 + [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch + [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 + [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge + [10]: https://code.launchpad.net/~vicamo/upstart/xenial-escape-systemd-strings/+merge/307140 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Recompile upstart with merge proposal [10] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
Prebuilt upstart-local-bridge binary from version 1.13.2-0ubuntu21.1 ** Attachment added: "upstart-local-bridge" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750793/+files/upstart-local-bridge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
** Patch added: "0001-install-systemd-service-files.patch" https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. - 4. Install prebuilt lxc-android-config package [8] or just correct its - systemd service file by hand as the merge proposal [9] does. (Bug - 1625445, bug 1625916 and bug 1626012). + 4. Modify lxc-android-config package [8] systemd service file by hand as + the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. Recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Modify lxc-android-config package systemd service file by hand as the merge proposal [8][9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Recompile upstart with merge proposal [10] include and install at least the built binary /sbin/upstart-local-bridge. 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1627613/+attachment/4750792/+files/0001-install-systemd-service-files.patch [8]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 [9]: https://code.launchpad.net/~vicamo/lxc-android-config/add-upstart-local-bridge [10]: https://code.launchpad.net/~vicamo/upst
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
Patch for android-tools to enable adbd in eng build at boot. ** Branch linked: lp:~vicamo/lxc-android-config/add-upstart-local-bridge -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
** Branch linked: lp:~vicamo/upstart/xenial-escape-systemd-strings -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in upstart package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
** Description changed: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. + + TODO: document + https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. TODO: document https://wiki.canonical.com/PES/Engineering/Premium/PhoneArticles/MechanismsThatUseProperty To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Filed bug 1627613 to track adbd stuff separately. ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb - 3. Install android-tools-adbd for systemd (Bug 1625023) + 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: Confirmed Status in lxc-android-config package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1627613) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devic
[Touch-packages] [Bug 1627613] Re: enable android adbd properly in systemd
"upstart-local-bridge[930]: Unit name android-contai...@persist.sys.usb.config\x3d,adb.target is not valid." So from systemd source, the allowed unit name is: #define VALID_CHARS DIGITS LETTERS ":-_.\\" upstart-local-bridge translates the event (name,value) pair to a unit name that doesn't conform to systemd's requirement. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1627613] [NEW] enable android adbd properly in systemd
Public bug reported: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. ** Affects: canonical-devices-system-image Importance: Undecided Status: New ** Affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Tags: systemd ** Tags added: systemd ** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1627613 Title: enable android adbd properly in systemd Status in Canonical System Image: New Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Bug description: Currently android adbd has no systemd service file and the mechanism for related parts like usb state and mtp is void. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627613/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Prebuilt lxc-android-config that integrates https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable- paths/+merge/306184 for bug 1625445, https://code.launchpad.net/~vicamo /lxc-android-config/fix-systemd-service-startup/+merge/306435 for bug 1625916, and https://code.launchpad.net/~vicamo/lxc-android-config /disable-systemd-alsa-restore/+merge/306587 for bug 1626012. ** Attachment added: "lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1625023/+attachment/4746826/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug - 1625445 and bug 1625916). + 1625445, bug 1625916 and bug 1626012). - 5. Rename alsactl somewhere (Bug 1626012). - # sudo mount -o remount,rw / - # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig - # sudo ln -s /bin/true /usr/sbin/alsactl - - 6. Reboot. + 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445, bug 1625916 and bug 1626012). 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/cano
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Attachment removed: "lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb" https://bugs.launchpad.net/ubuntu/+source/lxc-android-config/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445 and bug 1625916). 5. Rename alsactl somewhere (Bug 1626012). # sudo mount -o remount,rw / # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig # sudo ln -s /bin/true /usr/sbin/alsactl 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1626012] Re: alsactl cause system reboot
** Branch linked: lp:~vicamo/lxc-android-config/disable-systemd-alsa- restore ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New ** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1626012 Title: alsactl cause system reboot Status in Canonical System Image: In Progress Status in lxc-android-config package in Ubuntu: In Progress Bug description: version: 1.1.0-0ubuntu5 (https://launchpad.net/ubuntu/xenial/+source /alsa-utils) Last few dmesg lines: [ 207.774172] -(0)[2764:alsactl.orig]AudDrv_Clk_Off, Aud_AFE_Clk_cntr:0 [ 207.784590] .(0)[2764:alsactl.orig]-AudDrv Afe_Log_Print [ 207.784862] .(0)[2764:alsactl.orig]+Audio_Ipoh_Setting_Set() [ 207.784885] .(0)[2764:alsactl.orig]AudioI2S1_Setting_Set() [ 207.784926] .(0)[2764:alsactl.orig]Afe_Anc_Set() [ 207.784931] .(0)[2764:alsactl.orig]EnAble_Anc_Path not supported in 6752!!! Audio_HP_ImpeDance_Set [ 207.784974] -(0)[2764:alsactl.orig]---AudDrv_Clk_On, Aud_AFE_Clk_cntr:0 [ 207.821943] -(0)[0:swapper/0][mt6323_pmic_eint_irq] receive interrupt [ 207.821953] -(0)[0:swapper/0][wake_up_pmic] [ 207.822001] .(0)[40:pmic_thread_kth][pmic_thread_kthread] running [ 207.822013] .(0)[40:pmic_thread_kth][INT] int_status_val_0=0x40b3 [ 207.822018] .(0)[40:pmic_thread_kth][spkl_ab_int_handler] [ 207.822026] .(0)[40:pmic_thread_kth][spkl_d_int_handler] [ 207.822035] .(0)[40:pmic_thread_kth][watchdog_int_handler] [ 207.822044] .(0)[40:pmic_thread_kth][pwrkey_int_handler] [ 207.822052] .(0)[40:pmic_thread_kth][pwrkey_int_handler] Press pwrkey [ 207.822058] .(0)[40:pmic_thread_kth]kpd: Power Key generate, pressed=1 [ 207.822091] .(0)[40:pmic_thread_kth]kpd: (pressed) HW keycode =116 using PMIC [ 207.822107] .(0)[40:pmic_thread_kth][thr_h_int_handler] [ 207.822119] .(0)[40:pmic_thread_kth][INT] int_status_val_1=0x2d40 [ 207.822124] .(0)[40:pmic_thread_kth][vsys_oc_int_handler] [ 207.822132] .(0)[40:pmic_thread_kth][PMIC] Reg[0x13c]=0xc4f9 [ 207.822141] .(0)[40:pmic_thread_kth][PMIC] Reg[0x13e]=0x936c To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626012/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] - 1. flash images built from xenial branch [1] (need manually checkout - xenial branch in kernel-3.10/ before https://code.launchpad.net/~vicamo - /avila-private/+git/platform_manifest/+merge/306441 is merged). This - should gives a working xenial+upstart avila. + 1. flash images built from xenial branch [1]. This should gives a + working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445 and bug 1625916). 5. Rename alsactl somewhere (Bug 1626012). # sudo mount -o remount,rw / # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig # sudo ln -s /bin/true /usr/sbin/alsactl 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1]. This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445 and bug 1625916). 5. Rename alsactl somewhere (Bug 1626012). # sudo mount -o remount,rw / # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig # sudo ln -s /bin/true /usr/sbin/alsactl 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https:/
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1] (need manually checkout xenial branch in kernel-3.10/ before https://code.launchpad.net/~vicamo /avila-private/+git/platform_manifest/+merge/306441 is merged). This should gives a working xenial+upstart avila. - 2. Install systemd-sysv rather than upstart-sysv + 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb - 3. Install android-tools-adbd for systemd + 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its - systemd service file by hand as the merge proposal [9] does. + systemd service file by hand as the merge proposal [9] does. (Bug + 1625445 and bug 1625916). - 5. Rename alsactl somewhere to work-around bug 1626012. + 5. Rename alsactl somewhere (Bug 1626012). # sudo mount -o remount,rw / # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig # sudo ln -s /bin/true /usr/sbin/alsactl 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1] (need manually checkout xenial branch in kernel-3.10/ before https://code.launchpad.net/~vicamo/avila- private/+git/platform_manifest/+merge/306441 is merged). This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445 and bug 1625916). 5. Rename alsactl somewhere (Bug 1626012). # sudo mount -o remount,rw / # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig # sudo ln -s /bin/true /usr/sbin/alsactl 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bug
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in lxc-android-config package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1] (need manually checkout xenial branch in kernel-3.10/ before https://code.launchpad.net/~vicamo/avila- private/+git/platform_manifest/+merge/306441 is merged). This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv (Bug 1625023) 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2. download latest systemd-sysv package [4]. 2.3. dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd (Bug 1625023) 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2. Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Install prebuilt lxc-android-config package [8] or just correct its systemd service file by hand as the merge proposal [9] does. (Bug 1625445 and bug 1625916). 5. Rename alsactl somewhere (Bug 1626012). # sudo mount -o remount,rw / # sudo mv /usr/sbin/alsactl /usr/sbin/alsactl.orig # sudo ln -s /bin/true /usr/sbin/alsactl 6. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625916] Re: android init exits at executing /system/etc/partition_permission.sh
** Changed in: lxc-android-config (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1625916 Title: android init exits at executing /system/etc/partition_permission.sh Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: In Progress Bug description: In init.mt8163.rc: on fs write /proc/bootprof "INIT:Mount_START" mount_all /fstab.mt8163 setprop ro.crypto.state unencrypted #change partition permission exec /system/etc/partition_permission.sh #change partition permissions exec /system/bin/chmod 0640 /dev/block/platform/mtk-msdc.0/by-name/boot ... In dmesg: [7.570313] .(3)[:init]init: command 'setprop ro.crypto.state unencrypted' action=fs status=0 (/init.mt8163.rc:71) [7.570358] .(3)[:init]init: argv[0]= exec [7.570375] .(3)[:init]init: argv[1]= /system/etc/partition_permission.sh then no further message is printed. lxc log says: NOTICE lxc_start - start.c:post_start:1447 - '/init' started with pid '' ... DEBUGlxc_start - start.c:signal_handler:342 - container init process exited DEBUGlxc_start - start.c:__lxc_start:1392 - unknown exit status for init: 9 DEBUGlxc_start - start.c:__lxc_start:1397 - Pushing physical nics back to host namespace DEBUGlxc_start - start.c:__lxc_start:1400 - Tearing down virtual network devices used by container INFO lxc_error - error.c:lxc_error_set_and_log:55 - child <> ended on signal (9) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625916/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] - 1. flash images built from xenial branch [1] . This should gives a - working xenial+upstart avila. + 1. flash images built from xenial branch [1] (need manually checkout + xenial branch in kernel-3.10/ before https://code.launchpad.net/~vicamo + /avila-private/+git/platform_manifest/+merge/306441 is merged). This + should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2 download latest systemd-sysv package [4]. 2.3 dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2 Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Fix android container 4.1. Install prebuilt package [8] or just correct its systemd service file by hand as the merge proposal [9] does. 4.2. fix /etc/mtab entry in /usr/lib/tmpfiles.d/debian.conf by replacing 'L+' with 'L'. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1] (need manually checkout xenial branch in kernel-3.10/ before https://code.launchpad.net/~vicamo /avila-private/+git/platform_manifest/+merge/306441 is merged). This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2 download latest systemd-sysv package [4]. 2.3 dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2 Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Fix android container 4.1. Install prebuilt package [8] or just correct its systemd service file by hand as the merge proposal [9] does. - 4.2. fix /etc/mtab entry in /usr/lib/tmpfiles.d/debian.conf by replacing 'L+' with 'L'. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 ** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1.
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Description changed: Snappy heavily rely on systemd system session and xenial has systemd by default. + + [steps to construct systemd-based avila] + + 1. flash images built from xenial branch [1] . This should gives a + working xenial+upstart avila. + + 2. Install systemd-sysv rather than upstart-sysv + 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. + 2.2 download latest systemd-sysv package [4]. + 2.3 dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb + + 3. Install android-tools-adbd for systemd + 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. + 3.2 Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. + + 4. Fix android container + 4.1. Install prebuilt package [8] or just correct its systemd service file by hand as the merge proposal [9] does. + 4.2. fix /etc/mtab entry in /usr/lib/tmpfiles.d/debian.conf by replacing 'L+' with 'L'. + + 5. Reboot. + + [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial + [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ + [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch + [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ + [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb + [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ + [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch + [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb + [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. [steps to construct systemd-based avila] 1. flash images built from xenial branch [1] . This should gives a working xenial+upstart avila. 2. Install systemd-sysv rather than upstart-sysv 2.1. rebuild latest ubuntu-touch package from source [2] with patch [3] applied. 2.2 download latest systemd-sysv package [4]. 2.3 dpkg -i ubuntu-touch_*.deb systemd-sysv_*.deb 3. Install android-tools-adbd for systemd 3.1. download prebuilt package [5] or recompile it from source [6] with patch [7] applied. 3.2 Install the package from Terminal app because it will break adb connection and interrupt the installation process leaving a very bad state of the package. 4. Fix android container 4.1. Install prebuilt package [8] or just correct its systemd service file by hand as the merge proposal [9] does. 4.2. fix /etc/mtab entry in /usr/lib/tmpfiles.d/debian.conf by replacing 'L+' with 'L'. 5. Reboot. [1]: https://code.launchpad.net/~avila-private-team/avila-private/+git/platform_manifest/+ref/xenial [2]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/u/ubuntu-touch-meta/ [3]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch [4]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/s/systemd/ [5]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb [6]: http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/pool/main/a/android-tools/ [7]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch [8]: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb [9]: https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd-service-startup/+merge/306435 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packag
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Patch used to compile android-tools with systemd support. Note this is currently a dirty hack to enable adbd unconditionally at boot. ** Patch added: "force-adbd.patch" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746154/+files/force-adbd.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Prebuilt lxc-android-config deb that contains https://code.launchpad.net/~vicamo/lxc-android-config/fix-systemd- service-startup/+merge/306435 for bug 1625916, and https://code.launchpad.net/~vicamo/lxc-android-config/systemd-writable- paths/+merge/306184 for bug 1625445. ** Attachment added: "lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4746148/+files/lxc-android-config_0.230+16.04.20160728-0ubuntu1_all.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625916] Re: android init exits at executing /system/etc/partition_permission.sh
** Branch linked: lp:~vicamo/lxc-android-config/fix-systemd-service- startup -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc-android-config in Ubuntu. https://bugs.launchpad.net/bugs/1625916 Title: android init exits at executing /system/etc/partition_permission.sh Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: In init.mt8163.rc: on fs write /proc/bootprof "INIT:Mount_START" mount_all /fstab.mt8163 setprop ro.crypto.state unencrypted #change partition permission exec /system/etc/partition_permission.sh #change partition permissions exec /system/bin/chmod 0640 /dev/block/platform/mtk-msdc.0/by-name/boot ... In dmesg: [7.570313] .(3)[:init]init: command 'setprop ro.crypto.state unencrypted' action=fs status=0 (/init.mt8163.rc:71) [7.570358] .(3)[:init]init: argv[0]= exec [7.570375] .(3)[:init]init: argv[1]= /system/etc/partition_permission.sh then no further message is printed. lxc log says: NOTICE lxc_start - start.c:post_start:1447 - '/init' started with pid '' ... DEBUGlxc_start - start.c:signal_handler:342 - container init process exited DEBUGlxc_start - start.c:__lxc_start:1392 - unknown exit status for init: 9 DEBUGlxc_start - start.c:__lxc_start:1397 - Pushing physical nics back to host namespace DEBUGlxc_start - start.c:__lxc_start:1400 - Tearing down virtual network devices used by container INFO lxc_error - error.c:lxc_error_set_and_log:55 - child <> ended on signal (9) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625916/+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
[Touch-packages] [Bug 1625916] Re: android init exits at executing /system/etc/partition_permission.sh
** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New ** No longer affects: android-tools (Ubuntu) ** Also affects: lxc-android-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to android-tools in Ubuntu. https://bugs.launchpad.net/bugs/1625916 Title: android init exits at executing /system/etc/partition_permission.sh Status in Canonical System Image: New Status in lxc-android-config package in Ubuntu: New Bug description: In init.mt8163.rc: on fs write /proc/bootprof "INIT:Mount_START" mount_all /fstab.mt8163 setprop ro.crypto.state unencrypted #change partition permission exec /system/etc/partition_permission.sh #change partition permissions exec /system/bin/chmod 0640 /dev/block/platform/mtk-msdc.0/by-name/boot ... In dmesg: [7.570313] .(3)[:init]init: command 'setprop ro.crypto.state unencrypted' action=fs status=0 (/init.mt8163.rc:71) [7.570358] .(3)[:init]init: argv[0]= exec [7.570375] .(3)[:init]init: argv[1]= /system/etc/partition_permission.sh then no further message is printed. lxc log says: NOTICE lxc_start - start.c:post_start:1447 - '/init' started with pid '' ... DEBUGlxc_start - start.c:signal_handler:342 - container init process exited DEBUGlxc_start - start.c:__lxc_start:1392 - unknown exit status for init: 9 DEBUGlxc_start - start.c:__lxc_start:1397 - Pushing physical nics back to host namespace DEBUGlxc_start - start.c:__lxc_start:1400 - Tearing down virtual network devices used by container INFO lxc_error - error.c:lxc_error_set_and_log:55 - child <> ended on signal (9) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625916/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Kernel changes in https://code.launchpad.net/~vicamo/avila/+git/kernel-3.10/+merge/306307 , maybe we need another branch for xenial+systemd? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Prebuilt adbd package that installs systemd service and starts up at early boot stage. ** Attachment added: "android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744111/+files/android-tools-adbd_5.1.1r36+git20160322-0ubuntu3.1~overlay1_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
It seems there is no repository to land changes for ubuntu-touch-mate package, so here is the patch for manual landing. ** Patch added: "ubuntu-touch-meta.patch" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+attachment/4744047/+files/0001-depends-on-systemd-sysv-instead.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Also affects: android-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in android-tools package in Ubuntu: New Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Differences between list of packages install upstart and/or systemd service files: # diff -Nu /tmp/upstart-packages.list /tmp/systemd-packages. --- /tmp/upstart-packages.list 2016-09-19 05:55:03.849426548 + +++ /tmp/systemd-packages.list 2016-09-19 05:56:15.139426552 + @@ -1,80 +1,40 @@ -account-polld -address-book-service -address-book-updater +accountsservice alsa-utils -android-tools-adbd -apparmor apport apport-noui -biometryd-bin +apt bluetooth-touch bluez -buteo-syncfw cgmanager -cgroup-lite -ciborium click -console-setup console-setup-linux cron dbus -gnome-keyring -history-service -hostname ifupdown -indicator-bluetooth -indicator-datetime -indicator-display -indicator-keyboard -indicator-location -indicator-messages -indicator-network -indicator-power -indicator-session -indicator-sound -indicator-transfer keyboard-configuration -kmod -libertine-tools -libunity-scopes1.0 lightdm lxc1 lxc-android-config -media-hub -mediascanner2.0 -mountall -mtp-server network-manager -nuntium ofono -openssh-client openssh-server -passwd -pay-service -procps +openvpn +packagekit +plymouth +policykit-1 +ppp repowerd resolvconf -rfkill +rsync rsyslog -session-migration -sync-monitor -telephony-service -tone-generator -ubuntu-app-launch -ubuntu-location-provider-here -ubuntu-location-service-bin -ubuntu-push-client -ubuntu-touch-customization-hooks +rtkit +systemd ubuntu-touch-session udev +udisks2 ufw -unity8 -unity-scope-click-departmentsdb -upstart -upstart-watchdog +upower ureadahead urfkill -url-dispatcher -usensord -util-linux whoopsie +wpasupplicant -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Append debian build version so that it doesn't confuse dpkg. ** Attachment added: "ubuntu-touch_1.264xenial13+systemd_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743481/+files/ubuntu-touch_1.264xenial13+systemd_arm64.deb ** Attachment removed: "ubuntu-touch_1.264xenial13_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743479/+files/ubuntu-touch_1.264xenial13_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
Prebuilt ubuntu-touch meta package that depends on systemd-sysv instead. ** Attachment added: "ubuntu-touch_1.264xenial13_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1625023/+attachment/4743479/+files/ubuntu-touch_1.264xenial13_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1625023] Re: switch to systemd on ubuntu phone xenial
** Also affects: ubuntu-touch-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1625023 Title: switch to systemd on ubuntu phone xenial Status in Canonical System Image: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Snappy heavily rely on systemd system session and xenial has systemd by default. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1625023/+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
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
BTW, I have location-service rebuilt for bug 1618412. The GPS works on avila. No crash found then. I think it suggests there might be some ABI change in libdbus-cpp recently, so packages linked to libdbus-cpp might need a rebuild then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: New Status in dbus-cpp package in Ubuntu: New Status in location-service package in Ubuntu: New Status in mtp package in Ubuntu: New Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+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
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
mtp-server rebuilt against latest libdbus-cpp. Verified on GNOME*, no mtp-server crash, file operations work just fine. [1]: there seems to be some unresolved issue in kio-mtp: https://bugs.kde.org/show_bug.cgi?id=318980 ** Attachment added: "mtp-server_0.0.4+16.04.20160413-0ubuntu2_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1618390/+attachment/4732673/+files/mtp-server_0.0.4+16.04.20160413-0ubuntu2_arm64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: New Status in dbus-cpp package in Ubuntu: New Status in location-service package in Ubuntu: New Status in mtp package in Ubuntu: New Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+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
[Touch-packages] [Bug 1618390] Re: dbus-cpp crash on arm64 in core::dbus::Object::get_property
libmtpserver1 rebuilt against latest libdbus-cpp. ** Attachment added: "libmtpserver1_0.0.4+16.04.20160413-0ubuntu2_arm64.deb" https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1618390/+attachment/4732672/+files/libmtpserver1_0.0.4+16.04.20160413-0ubuntu2_arm64.deb ** Bug watch added: KDE Bug Tracking System #318980 https://bugs.kde.org/show_bug.cgi?id=318980 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1618390 Title: dbus-cpp crash on arm64 in core::dbus::Object::get_property Status in Canonical System Image: New Status in dbus-cpp package in Ubuntu: New Status in location-service package in Ubuntu: New Status in mtp package in Ubuntu: New Bug description: Requests to location service cause crashes on arm64: $ system-image-cli -i current build number: 23 device name: frieza_arm64 channel: ubuntu-touch/staging/ubuntu last update: 2016-08-30 09:13:12 version version: 23 version ubuntu: 20160830 version device: 20160824.0 version custom: 20160830 Steps: * flash the above channel (remember --device frieza_arm64) * go to a scope using location * refresh == Stacktrace = #0 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:49 __val = -1 __mem = 0x29 #1 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (__val=-1, __mem=0x29) at /usr/include/c++/5/ext/atomicity.h:82 __val = -1 __mem = 0x29 #2 0x007f978d4328 in std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release() (this=0x21) at /usr/include/c++/5/bits/shared_ptr_base.h:147 #3 0x007f97922a28 in std::__shared_count<(__gnu_cxx::_Lock_policy)2>::operator=(std::__shared_count<(__gnu_cxx::_Lock_policy)2> const&) (this=this@entry=0x8b34558, __r=...) at /usr/include/c++/5/bits/shared_ptr_base.h:678 __tmp = 0x8b34ba0 #4 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr_base.h:867 property = #5 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b34550) at /usr/include/c++/5/bits/shared_ptr.h:93 property = #6 0x007f9792cc64 in core::dbus::Object::get_property() (this=0x8b342c0) at /usr/include/core/dbus/impl/object.h:162 property = #7 0x007f97931c08 in com::ubuntu::location::service::Stub::Stub(std::shared_ptr const&) (object=warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value warning: can't find linker symbol for virtual table for `std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>' value ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libubuntu-location-service3 3.0.0+16.04.20160811-0ubuntu1 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] Uname: Linux 3.10.93+ aarch64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 Date: Tue Aug 30 09:39:24 2016 SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: arm64 DistroRelease: Ubuntu 16.04 Package: mtp-server 0.0.4+16.04.20160413-0ubuntu2 [origin: LP-PPA-ci-train-ppa-service-stable-phone-overlay] PackageArchitecture: arm64 Tags: third-party-packages xenial Uname: Linux 3.10.93+ aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1618390/+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
