IIRC the issue was gone after upgrading to xenial.
--
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/1659590
Title:
containers won't start after lxc and apparmor upgrades in
Hi Brian,
I can't help testing this new package since I'm not running Ubuntu on my
laptop anymore.
Cheers!
Alex
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1455097
Just a quick note to confirm that removing and installing previous
failing DKMS modules for kernel 4.4.0-116 as explained in comment 30,
worked wonders for our issue with vboxdrv issue and retpoline.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
python-apt-common 1.4.0~beta2 from Debian sid still has a reference to
ftp://ftp.caliu.cat/debian/.
Moreover, the upstream source repo has it too, so I guess it should be
reported upstream:
https://anonscm.debian.org/git/apt/python-apt.git/tree/data/templates/Debian.mirrors
--
You received
Running as root: strace -f -o lxc-execute.log -- lxc-execute --name test
-- echo foobar
...
3274 access("/var/lib/lxc", X_OK) = 0
3274 open("/proc/self/mountinfo", O_RDONLY) = 7
3274 fstat(7, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
3274 mmap(NULL, 4096, PROT_READ|PROT_WRITE,
This is what I get on a trusty vagrant box with latest kernel, lxc and
apparmor from trusty-updates:
root@vagrant-ubuntu-trusty-64:~# lxc-execute --name guest -- echo foobar
lxc-execute: utils.c: safe_mount: 1391 No such file or directory - Failed to
mount proc onto /proc
lxc-execute: conf.c:
lxc.conf with obfuscated IP addresses.
** Attachment added: "lxc.conf"
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+attachment/4809377/+files/lxc.conf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc
Public bug reported:
On January 19 lxc and apparmor were upgraded on our VPN servers:
2017-01-19 06:30:36 upgrade libdbus-1-3:amd64 1.6.18-0ubuntu4.4
1.6.18-0ubuntu4.5
2017-01-19 06:30:37 upgrade python3-lxc:amd64 1.0.8-0ubuntu0.4 1.0.9-0ubuntu2
2017-01-19 06:30:38 upgrade libapparmor1:amd64
After downgrading to 1.0.1f-1ubuntu2.19, "puppet cert sign ..." works
again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1626987
Title:
openssl update may have broken
Public bug reported:
After tonight's openssl update on our puppet CA server, we can no longer
sign puppet certificates:
root@sistemes:~# puppet cert sign vm-host-14.ac.upc.es
Notice: Signed certificate request for vm-host-14.ac.upc.es
Error:
root@sistemes:~# puppet ca sign vm-host-14.ac.upc.es
I moved my script to systemd, adapted it following Martin's instructions
in comment #5 and it just works as expected.
Thanks a lot :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pm-utils in Ubuntu.
On the other side I removed pm-utils from the system and there are a
couple of remaining scripts in /etc/pm/sleep.d that are worth
mentioning:
* 10_grub-common
* 10_unattended-upgrades-hibernate
Thus, those packages are also affected by this bug I guess.
** Also affects: unattended-upgrades
Public bug reported:
I added a new script in /etc/pm/sleep.d/ that worked fine before the
upgrade to vivid. I was wondering why it doesn't work and I find out
that /var/log/pm-suspend.log is empty, and pm-powersave.log too (last
logs from pm-suspend were on Apr 28, when I upgraded from utopic to
I'm posting this comment here also (did in bug #1052360 too):
FWIW, I got this issue this morning when I logged into my desktop.
In my case the problem was that installing a new kernel failed because
there wasn't enough space in /boot (I have a really tiny /boot and this
happens whenever I
FWIW, I got this issue this morning when I logged into my desktop.
In my case the problem was that installing a new kernel failed because
there wasn't enough space in /boot (I have a really tiny /boot and this
happens whenever I forget to purge old kernels).
Hope this helps!
--
You received
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1323593/+attachment/4154580/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
Note the following error in the log attached:
update-initramfs: Generating /boot/initrd.img-3.13.0-32-generic
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-3.13.0-32-generic with 1.
run-parts:
Maybe it would be better if we set this bug as invalid and I reported a
new one. Do you agree, Patrik?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1323593
18 matches
Mail list logo
