** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/1251939
Title:
Chroot fails with Cannot chroot when not started
Hi Forest,
looking at http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-
eni.html#ec2-net-utils
DHCP script
Whenever the network interface receives a new DHCP lease, this script queries
the instance metadata for Elastic IP addresses. For each Elastic IP address, it
adds a rule to the
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
It seems that you were running at least two install operations at the
same time. I am unsure which package this bug belongs, as I would say
that should not be possible, but it is not a failure of dconfig-common.
Program received signal SIGSEGV, Segmentation fault.
0x006b57d9 in gc_zval_possible_root (zv=0x351f4c8) at
/build/buildd/php5-5.3.2/Zend/zend_gc.c:143
143 GC_ZOBJ_CHECK_POSSIBLE_ROOT(zv);
(gdb) bt
#0 0x006b57d9 in gc_zval_possible_root (zv=0x351f4c8) at
On a regular trusty laptop with an SSD i did 6 boots (3 reboots and 3 cold
boots), and compared the boot.logs.
My expectation is to have no less than 6 instances of each unique boot
messages, that is not the case:
1 * Starting Bridge socket events into upstart
1 * Starting modem
** Attachment added: bootlogs.tar.gz
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1235231/+attachment/3924816/+files/bootlogs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
As a temporary work around just manually add
X11/core
to the end of /etc/.bzrignore
Yes?
(On my system, nothing else in /etc comes anywhere near the size of
/etc/X11/core. So, that's likely to be the only file tripping this error
for a while.)
--
You received this bug notification because
Hi,
I have actually adapted the files from the Amazon AMI which are working just
fine.
There is also an ansible file which tells where the files should be dropped.
You might need to adjust a few things but it should all be working
There is only a problem with this bug
Re-uploading attachment as solution
** Attachment added: Re-uploading attachment as solution
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1153626/+attachment/3925065/+files/bug_1153626.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Server
