Testing the new packages now, and have not yet had any segfaults,
whereas the 4.10-1ubuntu1.10 started logging faults with a couple of
minutes of starting and very regularly (sub-minute) after that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This only seems to happen for us, on 14.04 LTS at least, if the package
'systemd' is installed rather than merely libsystemd-{daemon,login}0,
and systemd-{services,shim}. It could be that a workaround is simply to
remove the 'systemd' package, assuming it's not required for your
particular setup.
I'm still able to duplicate this bug using:
linux-image-3.13.0-78-generic (from trusty-backports)
linux-image-3.19.0-50-generic (from linux-image-generic-lts-vivid)
The LXC images failed to start under linux-image-4.2.0-28-generic, with
a kernel oops.
I also tried, in Xenial,
Public bug reported:
Happened during upgrade from Server 10.4
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: php5-cli 5.3.10-1ubuntu3.4
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date:
Public bug reported:
Happened during upgrade from Server 10.4
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: php5-cli 5.3.10-1ubuntu3.4
ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28
Uname: Linux 3.2.0-31-generic x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date:
Potentially better than copying the /usr/bin/kvm binary to
/usr/bin/kvm.real is to use dpkg-dirvert, then the shell script it's
replaced with (as per Michael R. Hines' suggestion) won't be over-
written on upgrade of the qemu-kvm package:
$ sudo dpkg-divert --add --rename --divert
Potentially better than copying the /usr/bin/kvm binary to
/usr/bin/kvm.real is to use dpkg-dirvert, then the shell script it's
replaced with (as per Michael R. Hines' suggestion) won't be over-
written on upgrade of the qemu-kvm package:
$ sudo dpkg-divert --add --rename --divert
With the above patch applied stopping individual quagga daemons removes
the routes they've created (stopping bgpd removes only routes learnt via
BGP, etc). The apparent exception is zebra - that removes all routes.
This seems like far more reasonable behaviour.
BTW, the same bug also applies to
With the above patch applied stopping individual quagga daemons removes
the routes they've created (stopping bgpd removes only routes learnt via
BGP, etc). The apparent exception is zebra - that removes all routes.
This seems like far more reasonable behaviour.
BTW, the same bug also applies to
The original 'it fails ~50% of the time' was when I was testing with my
desired setup of a 10 GB LV.
The test01 - test30 lines are from a different, and later, run to the
original more verbose excerpts.
--
vmbuilder randomly fails to install grub
https://bugs.launchpad.net/bugs/610652
You
The original 'it fails ~50% of the time' was when I was testing with my
desired setup of a 10 GB LV.
The test01 - test30 lines are from a different, and later, run to the
original more verbose excerpts.
--
vmbuilder randomly fails to install grub
https://bugs.launchpad.net/bugs/610652
You
Public bug reported:
Command line and options are identical between runs, except for the
hostname and LV (as passed to --raw)
# vmbuilder kvm ubuntu --hostname=$1 --raw=/dev/vg0/$1 -c
/etc/vmbuilder.cfg --debug -o --rootsize=8192 --swapsize=2048 --mem=512
# egrep -v ^$|^# /etc/vmbuilder.cfg
** Attachment added: Successful run
http://launchpadlibrarian.net/52610446/test01.txt
--
vmbuilder randomly fails to install grub
https://bugs.launchpad.net/bugs/610652
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in
** Attachment added: Failed run
http://launchpadlibrarian.net/52610447/test03.txt
--
vmbuilder randomly fails to install grub
https://bugs.launchpad.net/bugs/610652
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to vm-builder in ubuntu.
Seems to be related to the size and/or position of the LV on disk or
partitioning setup inside the LV. 1TB drives (software RAID 1) with LBA
enabled.
4 GB LV, 2 GB root, 2GB swap:
test01.txt:2010-07-28 13:39:00,848 DEBUG : Checking if /boot/grub/stage1
exists... yes
test02.txt:2010-07-28
Public bug reported:
Command line and options are identical between runs, except for the
hostname and LV (as passed to --raw)
# vmbuilder kvm ubuntu --hostname=$1 --raw=/dev/vg0/$1 -c
/etc/vmbuilder.cfg --debug -o --rootsize=8192 --swapsize=2048 --mem=512
# egrep -v ^$|^# /etc/vmbuilder.cfg
** Attachment added: Successful run
http://launchpadlibrarian.net/52610446/test01.txt
--
vmbuilder randomly fails to install grub
https://bugs.launchpad.net/bugs/610652
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Attachment added: Failed run
http://launchpadlibrarian.net/52610447/test03.txt
--
vmbuilder randomly fails to install grub
https://bugs.launchpad.net/bugs/610652
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Seems to be related to the size and/or position of the LV on disk or
partitioning setup inside the LV. 1TB drives (software RAID 1) with LBA
enabled.
4 GB LV, 2 GB root, 2GB swap:
test01.txt:2010-07-28 13:39:00,848 DEBUG : Checking if /boot/grub/stage1
exists... yes
test02.txt:2010-07-28
Thanks Patrick, we followed your instructions for the Dossy patch and
it's working fine now.
--
amd64 vncconfig crashes
https://bugs.launchpad.net/bugs/119982
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I'm seeing a similar problem with what I believe to be a fully patched
Hardy AMD64 install. I've tried the usual things - deleting ~/.xine,
purging/reinstalling amarok/amarok-xine/libxine1-ffmpeg etc.
amarok 2:1.4.8-0ubuntu5
amarok-xine 2:1.4.8-0ubuntu5
libxine1-ffmpeg
I'd like to second Cory Dodt's comments - this is exactly what I saw -
WEP wifi borked by some update that went in to hardy a few days ago. The
iwpriv ath0 mode 3 command also resolves for me. Deleting the wireless
network from network manager makes no difference.
I'm running hardy on a T41
22 matches
Mail list logo
