Indeed, it seems like the kernel linked above breaks dockerd.
dmesg with "general protection fault" and stacktrace. all docker
commands hang.
https://pastebin.ubuntu.com/p/VRbFSmPkPs/
:(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
Perfect, no need to change tags anymore.
Now that at least 2 persons verified the bug is fixed with the -proposed
kernel, the SRU process will follow its course now and the fixed linux
will land in the archives in due time: there is a mandatory 7 days wait
time, so it should hit the archives next
For all other subscribers to this bug, now is the time to help :)
Enable -proposed on affected systems:
$ echo "deb http://archive.ubuntu.com/ubuntu/ eoan-proposed main" >>
/etc/apt/source.list
Update apt sources:
$ apt update
Install the linux kernel (and friends) from -proposed:
$ sudo apt
I can confirm that the problem is fix in the -proposed kernel
(5.3.0-52-generic).
Marking verification-done.
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Reverting the status of that bug to confirmed was a bit premature :)
My previous comment already mentions 5.3.0-51-generic not being fixed
(before it being marked fix commited).
>From IRC:
"we should get a eoan/linux kernel in -proposed at the latest by
tomorrow, when that happens an automated c
For the record, this still happens with the latest Eoan kernel
(5.3.0-51-generic).
[ 68.285097] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0
[ 68.286107] i915 :00:02.0: Resetting rcs0 for hang on rcs0
[ 76.301387] i915 :00:02.0: Resetting rcs0 for hang on rcs0
--
I have verified the SRU on our platform (Exoscale.com) for the
following:
- Xenial (19.3-41-gc4735dd3-0ubuntu1~16.04.1)
- Bionic (19.3-41-gc4735dd3-0ubuntu1~18.04.1)
- Disco (19.3-41-gc4735dd3-0ubuntu1~19.04.1)
- Eoan (19.3-41-gc4735dd3-0ubuntu1~19.10.1)
A branch to add a scripted sru template wi
** Branch linked: lp:~tribaal/livecd-rootfs/xenial-proposed-build-info-
minimal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759519
Title:
[SRU] Ensure "minimal" images have "minimal" in their
/
Public bug reported:
This is a backport to xenial for changes landed in bionic in
https://code.launchpad.net/~tribaal/livecd-rootfs/trunk-minimal-build-
info/+merge/342096
/etc/cloud/build.info is the file we write to the (image) disk where we
track build information. In the current state of thin
It seems like I cannot link the branch for some reason.
It can be found here: https://code.launchpad.net/~ubuntu-core-
dev/grub/+git/ubuntu/+ref/feature/initrd-less-boot-with-fallback
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Public bug reported:
The proposed change allows users to enable "initrd-less" boot for
kernels that support it, by setting the GRUB_FORCE_PARTUUID
configuration variable in /etc/default/grub.
In case the user sets the variable today, the initrd line will not be
written, and some kernels will boot
** Changed in: cloud-images
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1656293
Title:
OVF metadata for Ubuntu is wrong
To manage notifications about th
Public bug reported:
The bionic builds of cloud images for one of our partners fails when
installing/enabling NTP in the image during livecdrootfs build:
+ chroot mountpoint_gce systemctl --root / enable ntp.service
Synchronizing state of ntp.service with SysV service script with
/lib/systemd/sy
I have a preliminary solution to this working in ppa:tribaal/squid-deb-
proxy
Note that while it should improve the hit rate, it is also a little hard
to see it working since the existing squid logs mention the URL - not
the store ID.
Feedback welcome.
--
You received this bug notification beca
** Branch linked: lp:~tribaal/squid-deb-proxy/add-store-id-program
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1456238
Title:
Rewrite urls to mirror
To manage notifications about this bug go to:
the
apt configuration is.
Unknown mirrors (mirrors not listed in /usr/share/python-
apt/templates/*) will continue to behave as today.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Triaged => In Progress
** Changed in: squid-deb-proxy (Ubuntu)
Assignee: (unassigned) => Chris Gl
** Patch added: "debdiff_lowmem_debian_1.45_to_ubuntu_1.45.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+attachment/5037338/+files/debdiff_lowmem_debian_1.45_to_ubuntu_1.45.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
** Patch added: "debdiff_lowmem_ubuntu_1.44_to_ubuntu_1.45.debdiff"
https://bugs.launchpad.net/ubuntu/+source/lowmem/+bug/1743378/+attachment/5037339/+files/debdiff_lowmem_ubuntu_1.44_to_ubuntu_1.45.debdiff
** Changed in: lowmem (Ubuntu)
Assignee: Chris Glass (tribaal) =>
Public bug reported:
Please merge lowmem 1.45 (main) from Debian unstable (main)
** Affects: lowmem (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: lowmem (Ubuntu)
Assignee: (unassigned) => Chris Glass (tribaal)
** Changed in: lowmem (Ubuntu)
Sta
** Changed in: xenial-backports
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Title:
vagrant xenial box is not provided with vagrant/vagrant username and
This bug is now fixed in ubuntu/xenial64 v20180112.0.0.
Update your vagrant boxes:
vagrant box update
vagrant up
vagrant ssh
(notice you're "vagrant").
** Changed in: cloud-images/x-series
Status: Fix Committed => Fix Released
** Changed in: cloud-images/trunk
Status: Fix Committ
Quick update:
We would normally respin an image build right now to put this to bed
once and for all, but since we're in the middle of the Meltdown/Spectre
crisis it's best to keep the build system available for security-related
work.
The vagrant image will be built and pushed along with the rest
** Changed in: cloud-images/x-series
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Title:
vagrant xenial box is not provided with vagrant/vagrant us
The fix landed in the livecd-rootfs package, so expect to see the fix in
the ubuntu/xenial64 images very soon (next image build, or the one
after).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Looks like the failure there is due to the following commit in the linux
kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
next.git/commit/?id=c6c70f4455d1eda91065e93cc4f7eddf4499b105
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
Kernel in #27 was good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.
Kernel in #25 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.l
Kernel in #23 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.l
Kernel in #21 is bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.lau
Kernel in #19 is bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.la
Kernel in #17 is bad
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.lau
Kernel in #14 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.l
Kernel in #12 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.l
kernel in #10 is bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.la
kernel from #8 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.
kernel from #6 is bad.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.l
Kernel from #4 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.
Kernel from #2 is good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on mainline kernel 4.11+
To manage notifications about this bug go to:
https://bugs.
** Changed in: cloud-images
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627931
Title:
SHA256 checksum for ovf in xenial-server-cloudimg-amd64.ova has
Just tried with v4.15-rc7 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and the problem persists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1741887
Title:
Kubernetes test suite fails on m
Public bug reported:
The to-be-introduced 4.13 based kernel fails the kubernetes test suite
(https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-
kubernetes-e2e-gce-ubuntudev2-k8sbeta-default/15?log#log)
After rough bisecting (using kernels from http://kernel.ubuntu.com
/~kernel-p
This is when you all can help: as you can see the proposed fix landed in
-proposed: if you know how, feel free to build images yourself using the
livecd-rootfs package in -proposed.
If you would still like to help testing the change but don't know how to
build images with livecd-rootfs, please giv
It seems those bugs are not affecting the xenial release. They are
however important to tackle/investigate.
The proposed SRU changes can be tested by using the "tribaal/xenial64"
image.
The SRU process can go ahead/restart as far as I can tell.
** Description changed:
It is Vagrant convention
Verified by building cloud images using the proposed package and
ensuring the resulting artifacts were satisfactory.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a m
(verified with 2.408.25)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1701132
Title:
Please use xz instead of pxz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+s
** Description changed:
It is Vagrant convention that the default user is named "vagrant"[0],
and a whole host of scripts assume this to be the default.
The xenial box is substantially less useful to Vagrant users with the
"ubuntu" user as the default.
[0] Search for "user to SSH"
Not yet.
This is currently in the sponsorship queue, so for those not familiar
with the procedure, point 6 in
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure .
As you can see using "rmadison livecd-rootfs" another SRU for livecd-
rootfs is under way (for something unrelated to this bug), s
** Description changed:
It is Vagrant convention that the default user is named "vagrant"[0],
and a whole host of scripts assume this to be the default.
The xenial box is substantially less useful to Vagrant users with the
- "ubuntu" user as the default, and there is limited benefit to ha
Clarified the description by the original bug author.
The proposed solution for SRUing does *not* drop the ubuntu@ user, and
the ubuntu user behaves exactly the same way as with every other cloud-
image we deliver.
There is an *additional* default user (the "vagrant" user), that
conforms to the c
I've tried to reproduce this issue, unsuccessfully.
I remember being affect by it in the past, however. Could someone please
confirm:
- That it's still an issue on artful (17.10).
- What the current version of grub2 they using is, with the output of
"apt-cache policy grub2; apt-cache policy grub
** Branch linked: lp:~tribaal/livecd-rootfs/xenial-proposed-vagrant-
user-changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569237
Title:
vagrant xenial box is not provided with vagrant/vagrant
Untargetting vagrant as the bug is not in vagrant at all but in the
image creation code instead (livecd-rootfs)
** Changed in: vagrant
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Description changed:
It is Vagrant convention that the default user is named "vagrant"[0],
and a whole host of scripts assume this to be the default.
The xenial box is substantially less useful to Vagrant users with the
"ubuntu" user as the default, and there is limited benefit to ha
Built a minimized image with https://launchpad.net/ubuntu/+source
/livecd-rootfs/2.408.24 and could confirm that the changes are indeed
present and that the image boots and behaves normally.
Marking verified.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verificat
This was fixed in bionic/devel in livecd-rootfs 2.482
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731492
Title:
[SRU] Release "minimized round 2" changes to Xenial
To manage notifications about
I've successfully built new images with the livecd-rootfs in zesty-
proposed.
Marking verification-done.
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubun
Regression potential section updated.
** Description changed:
-
[Impact]
* Minimized images have their disk footprint further reduced with these
changes.
* Using minimal images can save bandwidth and system resources and we
would like to make those improvements available for
** Description changed:
- PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED
- (Description incomplete for now - will complete before subscribing the sru
team)
[Impact]
* Minimized images have their disk footprint further reduced with these
changes.
* Using minimal images can save ban
** Description changed:
PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED
(Description incomplete for now - will complete before subscribing the sru
team)
[Impact]
* Minimized images have their disk footprint further reduced with these
changes.
* Using minimal images can save ban
** Description changed:
PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED
(Description incomplete for now - will complete before subscribing the sru
team)
[Impact]
- * Minimized images have their disk footprint further reduced with these
-changes.
- * Using minimal images can save ban
Public bug reported:
PLEASE IGNORE UNTIL THIS MESSAGE IS REMOVED
(Description incomplete for now - will complete before subscribing the sru team)
[Impact]
* Minimized images have their disk footprint further reduced with these
changes.
* Using minimal images can save bandwidth and system re
Turns out I had rogue pacakges in /usr/local/lib/python2.7/dist-
pacakges.
Nothing to see here, moving along.
** Changed in: google-cloud-sdk (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Well, I can't reproduce it in a lxc either. I suppose that must be my
local environment being weird somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731019
Title:
gsutil tracebacks on artful
Public bug reported:
google-cloud-sdk 176.0.0-0ubuntu1 exits with a traceback on artful:
$ gsutil
Traceback (most recent call last):
File "/usr/bin/../lib/google-cloud-sdk/bin/bootstrapping/gsutil.py", line 12,
in
import bootstrapping
File "/usr/lib/google-cloud-sdk/bin/bootstrapping/b
*** This bug is a duplicate of bug 1258597 ***
https://bugs.launchpad.net/bugs/1258597
** This bug has been marked a duplicate of bug 1258597
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT
is set is no longer supported.
--
You received this bug notification be
*** This bug is a duplicate of bug 1624715 ***
https://bugs.launchpad.net/bugs/1624715
** This bug has been marked a duplicate of bug 1624715
rpc.statd not started automatically
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
A bug has been filed upstream here:
https://bugs.freedesktop.org/show_bug.cgi?id=103351
** Bug watch added: freedesktop.org Bugzilla #103351
https://bugs.freedesktop.org/show_bug.cgi?id=103351
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
For the record since I forgot to comment previously: kernel in #21
(mainline kernel with suspicious patch reverted) does boot fine with
nouveau.
(However just reverting it will probably cause other regressions)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just tested 4.15-rc5 and the problem still persists.
A (bit painful) workaround if you don't have a choice:
- Boot liveCD, enable "expert mode" (F6 at boot menu"
- Edit the boot line to have "blacklist=nouveau
modprobe.blacklist=nouveau" BOTH before AND after the "--" at the end of
the line. T
Blacklisting nouveau allows a full boot (at a very low screen
resolution, obviously).
Kernel at #16 fails to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723619
Title:
Ubuntu Desktop ISO fa
The kernel at #14 fails to boot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau on a displayport
To manage notifications about this bug g
As discussed on IRC kaihengfeng and I will sync up tomorrow and bissect
the problem together.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouve
Tested all mainline kernels I could find for 4.13-rc*:
- 4.13-rc1: DisplayPort setup boots. Login screen appears. Choosing the
default option (wayland) results in broken desktop
(https://photos.app.goo.gl/xisx9EgTKTFoLXmJ3). Choosing the xorg
fallback works perfectly.
- 4.13-rc2: DisplayPort setu
I've done further testing as you suggested. Here's a breakdown of my
findings:
I tested the following kernel versions on 4k + displayport (installed
from launchpad librarian, with their matching -extra package and an
"update-grub"):
- 4.12.0-12: Boots. System seems to crash after a few seconds on
Switching the faulty system to using HDMI + 1080p succeeded. Updating
bug description.
** Summary changed:
- Ubuntu Desktop ISO fails to boot with nouveau
+ Ubuntu Desktop ISO fails to boot with nouveau on a displayport
** Description changed:
On the latest daily artful image (/current as of
Another machine (GTX950m on an integrated screen) boots as well.
>From my limited understanding of the error message in the screenshot -
perhaps the problem is that the screen is connected to displayport (the
GT 640 uses HDMI).
The failing system has a 4k screen connected to displayport.
--
You
I cannot run apport-collect because the livecd doesn't boot :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723619
Title:
Ubuntu Desktop ISO fails to boot with nouveau
To manage notifications abo
The livecd boots fine on another machine of mine with a nvidia GT 640
(so, an older generation), fromt eh same daily and same image burn.
I am out of extra hardware to try this on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Public bug reported:
On the latest daily artful image (/current as of 2017-01-14), the
following occurs on a system with nVidia graphics (on my system, a
GTX970): https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2
Steps to reproduce:
- Download latest daily image, check checksums, burn to USB
- Boot fro
More investigation is needed. The path *does* fix the problem, but in a
way that feels like it is a side effect.
Sorry, I should have commented on this bug before.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
An even better fix for your configuration is to change the dropdown to
"verify name exactly", and then remove the "CN=" part of the field if
you previously had one in your subject match.
Example:
"/CN=example.com" becomes "example.com"
--
You received this bug notification because you are a mem
For people suffering from this, a clean workaround is to change the VPN
configuration as follows:
- Edit your VPN connection
- "VPN" tab
- "Advanced"
- "TLS Authentication" tab
- Change the "Server certificate check" to something that is *not* "verify
subject partially".
In my case, "Don't verif
I *think* the root of the issue is that the assumption in debian/rules
# we do not want to run the init script in the postinst/prerm, its
# really only useful on shutdown, see Debian bug #645919
dh_installinit $@ --no-start -- stop 10 0 6 .
is wrong.
It is not only usefu
This debdiff should fix the problem.
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1606600/+attachment/4826417/+files/unattended-debdiff.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Xenial debdiff
** Patch added: "Xenial debdiff"
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4784081/+files/xenial.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
Yakkety debdiff
** Patch added: "Yakkety debdiff"
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4784079/+files/yakkety.deb.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
I re-ran the outlined test-sequence without adding the juju-stable PPA
(like I originally did) to make sure this bug is not a side-effect of
the PPA.
It is not. It is reproducible on vanilla distro as outlined in the
description.
** Description changed:
[Impact]
* The python Juju client
** Description changed:
- Package affected: python-jujuclient 0.50.5-0ubuntu1 (on Xenial)
+ [Impact]
- The python Juju client cannot make SSL connections to the server
- anymore, because TLS v1 was deprecated.
+ * The python Juju client cannot make SSL connections to the server anymore,
becau
** Description changed:
Package affected: python-jujuclient 0.50.5-0ubuntu1 (on Xenial)
The python Juju client cannot make SSL connections to the server
anymore, because TLS v1 was deprecated.
Switching to TLS v1.2 fixes the problem entirely.
Example failure: http://pastebin.ubu
Once this gets into zesty I shall open another bug for the SRU into
yakkety and xenial.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644153
Title:
SSL handshake fails on xenial, yakkety, zesty
To
** Summary changed:
- SSL handshake fails on xenial
+ SSL handshake fails on xenial, yakkety, zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644153
Title:
SSL handshake fails on xenial, yakke
Debdiff against the current Ubuntu release (zesty)'s version.
** Patch added: "python-jujuclient-debdiff.diff"
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4782000/+files/python-jujuclient-debdiff.diff
--
You received this bug notification because you are a member of
(for what it's worth, the systems we use have ppa:juju/stable installed,
so adding the fix to that PPA would unblock many users already)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1644153
Title:
Patch against the Xenial package.
** Attachment added: "switch-to-tls12"
https://bugs.launchpad.net/python-jujuclient/+bug/1644153/+attachment/4781989/+files/switch-to-tls12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
(sorry for the shallow bug report - I intended to fill it up some more
but it fell through the cracks)
Specific units are:
plymouth-read-write.service
plymouth-quit.service
plymouth-quit-wait.service
Measured time spent in these: between 100 and 300ms (depending on I/O, I
assume). It's a modest
Public bug reported:
A few systemd units are started despite plymouth itself not running
(nospash is set in cmdline for instance).
This results in boot times slightly longer than necessary for those
systems.
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You r
For the record, the branch patching grub2 is:
https://code.launchpad.net/~tribaal/ubuntu/+source/grub2/+git/grub2/+ref
/add-partuuid-override
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640878
Titl
cyphermox uploaded patched packages to ppa:cyphermox/grub .
Steps to assert this works are as follows:
- Boot a Yakkety EC2 image
(https://console.aws.amazon.com/ec2/home?region=eu-central-1#launchAmi=ami-b87881d7)
- Login
- sudo apt-add-repository ppa:cyphermox/grub; sudo apt update; sudo apt-u
initrd.
Suggestion:
Allow grub2 to create configuration files without an "initrd" line and
passing PARTUUID as root= entry by adding configuration knobs.
** Affects: grub2 (Ubuntu)
Importance: High
Assignee: Chris Glass (tribaal)
Status: Triaged
--
You receive
Could somebody summarize that the instructions to get this working on
wily are? Thanks a lot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1383184
Title:
Atheros Qualcomm Killer N1525 Wireless-AC [1
1 - 100 of 169 matches
Mail list logo
