Failed to install openjdk-9-jdk_9~b114-0ubuntu1 too, but on amd64. See
https://travis-ci.org/vicamo/docker-java/jobs/378539393#L2151 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770646
Title:
** 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.,
** Description changed:
Multiple places to fix:
1. device build system on xenial branch still uses vivid initrd:
1.1. no prebuilt initrd git repository available as we have for ssh
://code-review.phablet.ubuntu.com/ubuntu/initrd/ubuntu_prebuilt_initrd
and ssh://code-
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641561
Title:
make android lxc as a snap
To manage
Don't know where to land a fix for ubuntu-touch-generic-initrd.
https://launchpad.net/ubuntu/+source/initramfs-tools-ubuntu-touch ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644787
Title:
boot
Attach bootable xenial boot.img with all problems fixed.
** Attachment added: "boot.img"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-generic-initrd/+bug/1644787/+attachment/4782908/+files/boot.img
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
Multiple places to fix:
1. device build system on xenial branch still uses vivid initrd:
1.1. no prebuilt initrd git repository available as we have for ssh
://code-review.phablet.ubuntu.com/ubuntu/initrd/ubuntu_prebuilt_initrd
and ssh://code-
Public bug reported:
Multiple places to fix:
1. device build system on xenial branch still uses vivid initrd:
1.1. no prebuilt initrd git repository available as we have for ssh
://code-review.phablet.ubuntu.com/ubuntu/initrd/ubuntu_prebuilt_initrd
and ssh://code-
** 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 (
)
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/165
Title:
avila xenial+systemd port takes too long to
** 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
=> 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
Bugs, which is subscribed to Ubuntu.
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,
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:
** Changed in: lxc-android-config (Ubuntu)
Assignee: (unassigned) => Vicamo Yang (vicamo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642535
Title:
need /var/snap writable-path for sna
** 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
Bugs, which is subscribed to Ubuntu.
Filed follow-up bug 1642535.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need writable-path for snappy
To manage notifications about this bug go to:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need writable-path for snappy
To manage notifications
** Changed in: canonical-devices-system-image
Status: Fix Committed => Fix Released
** Changed in: snap-confine (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: snap-confine (Ubuntu Xenial)
Status: Fix Committed => Fix Released
** Changed in: snap-confine
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638204
Title:
install snapd in default ubuntu xenial image
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage
** Also affects: urfkill (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage
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
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
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
AppArmor is not functioning this way Hmmm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc android container to lxd
To manage notifications about this bug go to:
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.
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
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"
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.
** 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.,
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
** 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
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
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641549
Title:
migrate lxc
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641561
Title:
make
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)
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1641561
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
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:
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"
: 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
phablet@ubuntu-phablet:~$ hello-world
Hello World!
phablet@ubuntu-phablet:~$ system-image-cli -i
current build number: 76
device name: frieza_arm64
channel: ubuntu-touch/staging/ubuntu
last update: 2016-11-05 03:12:16
version version: 76
version ubuntu: 20161105
version device: 20161014.0
version
** Description changed:
[Impact]
When porting snappy to our reference device -- m10 (xenial, arm64,
kernel-3.10), execution of hello-world command from the hello-world snap
fails due to the lack of appropriate permission in apparmor. It turns
out ptrace is used between snap-confine
** Description changed:
[Impact]
- TBD
+ When porting snappy to our reference device -- m10 (xenial, arm64,
+ kernel-3.10), execution of hello-world command from the hello-world snap
+ fails due to the lack of appropriate permission in apparmor. It turns
+ out ptrace is used between
Upstream has merged this and tagged as 1.0.44 [1], so it should only be
available after that.
[1]: https://github.com/snapcore/snap-confine/commits/1.0.44/src/snap-
confine.apparmor.in
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Merge proposal: https://github.com/snapcore/snap-confine/pull/170
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633367
Title:
missing ptrace options needed by snap-confine
To manage notifications
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
Bugs, which is
Enable necessary ptrace options for both snap-confine and its helper.
** Patch added: "diff.patch"
https://bugs.launchpad.net/ubuntu/+source/snap-confine/+bug/1633367/+attachment/4760899/+files/diff.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Don't know where to send a merge proposal, so put a patch here first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633367
Title:
missing ptrace options needed by snap-confine
To manage
** 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
This, along with bug 1632272, are necessary to install/run snap hello-
world package on avila.
** Also affects: snap-confine (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All necessary changes merged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632602
Title:
no adb access under xenial+systemd user build
To manage notifications about this bug go to:
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
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
** Tags added: snappy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need writable-path for snappy
To manage notifications about this bug go to:
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632272
Title:
need writable-path for snappy
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632602
Title:
no adb access
** 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
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
** 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
** 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
** 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
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:
** 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
https://bugzilla.redhat.com/show_bug.cgi?id=925630 "Kernel support for
kexec and kprobes has landed upstream in the 4.8 kernel".
** Bug watch added: Red Hat Bugzilla #925630
https://bugzilla.redhat.com/show_bug.cgi?id=925630
--
You received this bug notification because you are a member of
As today's version 1.5.9-5ubuntu0.1, there is already arch/arm64.c
available, but it's still not included in debian/control. It does build
in my arm64 docker env, haven't tried yet.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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
** 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
** 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.
** 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
** 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
** 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
** 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:
** 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"
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
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"
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
** 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
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
** 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
Bugs, which is subscribed to
** 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627613
Title:
** Branch linked: lp:~vicamo/upstart/xenial-escape-systemd-strings
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627613
Title:
enable android adbd properly in systemd
To manage notifications
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627613
Title:
enable android adbd properly in systemd
To manage
** 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
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
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
"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
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
** 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
** 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
** 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
** 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
** Also affects: lxc-android-config (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625023
Title:
switch to systemd on ubuntu phone xenial
To
** Changed in: lxc-android-config (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1625916
Title:
android init exits at executing
1 - 100 of 169 matches
Mail list logo
