It never happened again (and may have been a misuse involving immortal
sudo subprocesses but I'm blurry on the details), marking invalid but
fixed released may be correct as well.
** Changed in: lxc (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are
** Changed in: bzr
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
https://bugs.launchpad.net/bugs/1451448
Title:
bzr fails to build on vivid (release) and tru
@Chris: Thanks !
I had to implement a different scheme not using nested containers but
still requiring lxc-1.1.2.
I'll give nested containers another shot asap.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on
the outer container ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
Title:
Regression: Nested LX
I run into the same issue on a vivid host while trying to start a trusty
nested container from inside a trusty container.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1436723
@Pat: Just in case, I'm on vivid and use autopkgtest 3.13, that may be
related.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on b
@Pat: Can you re-try adding '-d' to your adt-run options and share the
log ?
/tmp/autopkgtest-reboot is created by adt-run on the testbed at run
time.
I'm eager to learn how such a failure can happen and where it needs to
be fixed.
--
You received this bug notification because you are a member
Also reproduced on arale with the branch above after 25 reboots.
$ adb shell system-image-cli -i
current build number: 22
device name: arale
channel: ubuntu-touch/arale-vivid-proposed
last update: 2010-01-01 00:29:22
version version: 22
version ubuntu: 30e975dd988b3be7886017b6d46b2821da187d7b8e5e4
** Branch linked: lp:~canonical-platform-qa/unity8/1421009-hangs-on-boot
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot in Ubuntu.
https://bugs.launchpad.net/bugs/1421009
Title:
unity8 sometimes hangs on boot
St
I've created https://code.launchpad.net/~canonical-platform-
qa/unity8/1421009-hangs-on-boot/+merge/257408 to reproduce this bug.
Given the last comment above it may need to be tweaked s/30/60/ .
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whic
Re-creating the symlink with the command above was enough to fix the
issue for me.
Thanks !
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1430675
Title:
fails to set up
Public bug reported:
Encountered when trying to test that a phone image upgraded with
-proposed still boots.
According to pitti:
naming it initrd.img-touch is broken, that's not what initramfs-tools and other
tools expect
so at the very least, i-t-ubuntu-touch needs to disable the trigger someh
12 matches
Mail list logo
