Thanks Brad, I just saw that this has been in -proposed for a bit on bionic,
missed that originally when looking for the file
https://packages.ubuntu.com/search?searchon=contents=libperf-jvmti.so=exactfilename=bionic-updates=any
We'll keep our eyes peeled for the release.
--
You received this
** Also affects: linux-aws (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761379
Title:
[18.04/18.10] File libperf-jvmti.so is missing in
Can anyone comment as to whether or not this will be considered for
kernels beyond -generic and -hwe? Specifically for aws, aws-hwe, and
aws-edge kernels?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using a Thinkpad T480s and while my Elantech touchpad was mostly
functional upon moving to 18.10 two-finger right-click and three-finger
middle-click stopped working. `libinput list-devices` showed 'none' for
a couple of features like 'Click methods.'
The same fixes above worked for me (both
We encountered an instance that had a nvme failure very early on in boot
today. I've updated our internal Canonical case as well as our Amazon
case on this, but posting relevant details here as well for consistency:
# uname -a
Linux XXX 4.4.0-1069-aws #79-Ubuntu SMP Mon Sep 24 15:01:41 UTC 2018
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2433
and
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/kernel/sysctl.c#n2446
are the source(s) of the noise
Looking at nearby functions like proc_dointvec_ibrs_ctrl
Also, to call it out again, this appears to affect Trusty's LTS kernel,
too (it's not clear how one marks a bug as such from the Launchpad UI)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755627
For the sake of completeness on this one, I installed the following
mainline packages on an AWS m5.large instance running 16.04.3 w/
4.4.0-112-generic
- linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb
-
It's worth noting, too, that this does not happen on Bionic @ 4.15
(using Ubuntu 4.15.0-1001.1-aws 4.15.3) but it does happen on Trusty
(using Ubuntu 3.13.0-143.192-generic 3.13.11-ckt39)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
We do not use apport and this is easily reproducible. If there is any
pointed information I can provide beyond what I've already submitted,
please let me know.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
Since at least kernel 4.4.0-116, every invocation of `sysctl -a` results
in kernel logs similar to the following:
% sysctl -a &>/dev/null; dmesg -T | tail -8
[Wed Mar 14 00:06:36 2018] sysctl_ibrs_enabled = 0, sysctl_ibpb_enabled = 0
[Wed Mar 14 00:06:36 2018] use_ibrs = 4,
It looks like this was fixed upstream and it would be fantastic if this
could make it into Bionic before anything is frozen.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752722
Title:
systemd 237
This does not appear to affect Artful and systemd 234. Example session:
~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.10
DISTRIB_CODENAME=artful
DISTRIB_DESCRIPTION="Ubuntu 17.10"
~# uname -a
Linux ip-100-65-137-86 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC
2018
Public bug reported:
Raised this upstream:
https://github.com/systemd/systemd/issues/8328
In short, in systemd 237 as it ships with Bionic, if a unit has a drop-
in present but has been masked, systemctl is-enabled and systemctl list-
unit-files report incorrect state, showing the units as
Seeing the same on Xenial when using linux-hwe-edge
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679768
Title:
Docker
If at all possible, I'd love to see this fix backported to Xenial. Given
that the bug appears to have existed as long as the sysv-generator has,
the biggest risk is to those who may be erroneously depending on the
incorrect behavior (whether explicitly or otherwise).
I've attached a very basic
Public bug reported:
See the bug raised here:
https://github.com/systemd/systemd/issues/4762
and fixed upstream here:
https://github.com/systemd/systemd/commit/e932f5407ef5ad05d25d7dfefa4cda0fe81cc346
In short, given a sysv-init script with valid LSB headers, one of which defines
We encountered the same and were able to overcome it by force-downgrading
python3.4, python3.4-minimal, libpython3.4-stdlib, and libpython3.4-minimal to
the current version available in the repositories with
apt-get install -y \
python3.4=3.4.0-2ubuntu1.1 \
python3.4-minimal=3.4.0-2ubuntu1.1
@Viktor, I believe that patch was later reverted and a new one was
issued to fix
https://lkml.org/lkml/2014/4/10/174
https://lkml.org/lkml/2014/4/8/173
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
FWIW, we ran into the same messages and in researching, I came across this page
https://silenteh.com/sysadmin/2013/08/08/amazon-ec2-xennet-skb-rides-the-rocket.html
which suggests disabling TCP offload functionality using
ethtool -K eth0 rx off tx off sg off tso off ufo off gso off gro off lro off
Public bug reported:
httpie has a dependency on requests 0.10.1 but 1.0. Raring ships
with requests 1.1.0. The httpie deb doesn't declare a dependency on any
specific version of requests, so everything installs clean.
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=13.04
21 matches
Mail list logo
