** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938935
Title:
virtualbox-guest-dkms 6.1.16-dfsg-6~ubuntu1.20.04.2: virtualbox-guest
kernel module failed to
Public bug reported:
I’m trying to revive a slightly old Lenovo Z70-80. I haven’t used it for
a month or so. Then, I downloaded all the latest updates a couple of
weeks ago and something broke. The screen looks as if it's tearing many
times per second and some of the middle pixels are repeated on
Public bug reported:
Generated automatically; I have not noticed any issues.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: virtualbox-guest-dkms 6.1.16-dfsg-6~ubuntu1.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
Thanks for removing the tag, Norbert. Out of curiosity, is this still a
problem for you? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713274
Title:
zenmap uses menu package in
Public bug reported:
I use the snap version of Chromium on Kubuntu and there is no way to use
KDE's file picker in Chromium. The reason is that the option is not
available in the build provided by snap.
In the Flatpak build, if the user goes to "chrome://flags" there is an
option "Use the XDG
** Changed in: ubuntu-z-systems
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/1928780
Title:
[UBUNTU 21.04] openCryptoki: Soft token does not check if an
The kernel patch for 9710 is now in the sound subsystem tree, it should
be in linux-next sometime later today
https://mailman.alsa-project.org/pipermail/alsa-
devel/2021-August/188208.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
After auto upgrading to the new Nvidia driver, I keep getting the
"system crashed" message. The linux kernel 5.11.00-generic doesn't boot
at all with this new nvidia driver.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
I've done some more testing and built tags v5.7 and v5.7-rc2 from
source.
v5.7-rc2 seems to consistently boot without any special kernel flags
v5.7 gives me rather odd behaviour:
- When I'm first powering on the machine, v5.7 does not boot without any
special kernel flags
- If I set
Thanks for the information. So it means the ownership of the pin is incorrectly
configured by the BIOS. I can force the host_own bit to different value, please
try to install the customized kernel and give me the dmesg output.
https://people.canonical.com/~mschiu77/lp1937056/
However, even it
Hello,
For some reason, in the past week or so this bug has been freezing my
machine every couple of days or so (I’m surprised that AMD wasn’t able
to reproduce the problem yet¹). You can imagine how “pleasant” it makes
using this computer.
Today I got an interesting error in dmesg, perhaps
This bug was fixed in the package opencryptoki - 3.15.1+dfsg-0ubuntu1.2
---
opencryptoki (3.15.1+dfsg-0ubuntu1.2) hirsute-security; urgency=medium
* SECURITY UPDATE: Invalid curve attacks
- d/p/lp1928780-Add-missing-return-codes.patch: Partial cherry-pick of
master as a
This is a Focal v4 check_nrpe querying bionic NRPE v3 and should work
without spamming logs. I am seeing in syslog:
check_nrpe - - - Remote 10.1.2.3 does not support version 3/4 packets
However checks are working.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Upgrade already asked in Debian 5 months ago :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984830
This bug is critical as it makes the software totally unusable…
** Bug watch added: Debian Bug tracker #984830
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984830
--
You received
stress-ng --af-alg 0 -t 60 (a few rounds) produces:
[ 99.445636] BUG: scheduling while atomic: kthreadd/2/0x0002
[ 99.445647] Modules linked in: chacha_generic chacha_x86_64 libchacha
xxhash_generic wp512 streebog_generic sm3_generic sha3_generic rmd160
poly1305_generic poly1305_x86_64
With debugedit v5.0 things are still the same
https://launchpadlibrarian.net/551609214/buildlog_ubuntu-impish-
amd64.virtualbox_6.1.26-dfsg-2ubuntu1_BUILDING.txt.gz
the setuid bit is lost.
I guess we need to dig deeper into dh_strip activities, to see
what/where/how it is lost. Maybe it is lost
ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL
-rwsr-sr-x 1 buildd buildd 406824 Aug 4 15:51
debian/virtualbox/usr/lib/virtualbox/VBoxSDL
dh_strip --dbgsym-migration='virtualbox-dbg'
ls -latr debian/virtualbox/usr/lib/virtualbox/VBoxSDL
-rwxr-xr-x 1 buildd buildd 166208 Aug 4 15:52
** Description changed:
[Impact]
On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the failed boot from one of those
devices:
Hit any key to stop autoboot:
** Changed in: anacron (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in: anacron (Ubuntu Focal)
Status: Confirmed => Won't Fix
** Changed in: cron (Ubuntu Bionic)
Status: Confirmed => Won't Fix
** Changed in: cron (Ubuntu Focal)
Status: Confirmed => Won't
Hello Frank, or anyone else affected,
Accepted livecd-rootfs into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.664.27 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Frank, or anyone else affected,
Accepted livecd-rootfs into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.664.27 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brian, or anyone else affected,
Accepted livecd-rootfs into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.664.27 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Public bug reported:
From LP: #1779767 comment 13:
In crontab(5) in cron 3.0pl1-136ubuntu2 the manpage is now wrong. It
says:
> Several environment variables are set up automatically by the cron(8) daemon.
> […] PATH is set to "/usr/bin:/bin". HOME, SHELL, and PATH may be overridden
> by
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
stress-ng --daemon -t 60 produces:
[ 68.860977] BUG: scheduling while atomic: stress-ng/91343/0x0002
[ 68.860981] Modules linked in: nls_iso8859_1 dm_multipath scsi_dh_rdac
scsi_dh_emc scsi_dh_alua intel_rapl_msr joydev intel_rapl_common kvm_intel kvm
rapl input_leds serio_raw
and stress-ng --dup 0 produces:
[ 506.394685] BUG: scheduling while atomic: stress-ng/35875/0x0002
[ 506.394819] CPU: 0 PID: 35855 Comm: stress-ng Tainted: GW
5.13.0-1003-realtime #3-Ubuntu
[ 506.394821] i2c_i801 net_failover libahci
[ 506.394822] Hardware name: QEMU
Public bug reported:
nfsiostat.py packaged with Ubuntu nfs-common tools is throwing
TypeError's with Python3 and syntax errors with python2.
A git pull of the NFS Linux Kernel source for this file needs to occur:
Public bug reported:
[Impact]
This release contains both bug-fixes and new features and we would like to make
sure all of our supported customers have access to those improvements.
The most notable changes (besides usual bug-fixes) incoming in 0.103:
- Add YAML generator and Keyfile parser for
This bug was fixed in the package mokutil - 0.4.0-1ubuntu1
---
mokutil (0.4.0-1ubuntu1) impish; urgency=medium
* Enable building on riscv64 (LP: #1938898)
-- Heinrich Schuchardt Wed, 04 Aug
2021 14:20:13 +0200
** Changed in: mokutil (Ubuntu)
Status: New => Fix Released
Or please update pikepdf, bug was corrected in version 2.7.0 (we are at
2.16.1) :
https://github.com/pikepdf/pikepdf/blob/master/docs/release_notes.rst#v270
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://github.com/pdfarranger/pdfarranger/issues/427
** Bug watch added: github.com/pdfarranger/pdfarranger/issues #427
https://github.com/pdfarranger/pdfarranger/issues/427
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In my focal installation of Ubuntu I established that gnome-maps version
3.36.1-1 would not start. I enabled -proposed and upgraded gnome-maps to
version 3.36.1-1ubuntu1. gnome-maps now starts so marking as verified.
** Tags removed: verification-needed verification-needed-focal
** Tags added:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
+ [Impact]
+
+ On all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pikepdf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926289
Title:
Hi, same problem since a few weeks :
https://github.com/pdfarranger/pdfarranger/issues?q=only+pages+can+be+inserted
"This was probably triggered by an update of qpdf. Ubuntu will need to
update either Pikepdf or Pdf Arranger to fix this."
"1.7.1 includes a workaround"
Please packagers, update
This bug was fixed in the package neutron - 2:16.4.0-0ubuntu3~cloud0
---
neutron (2:16.4.0-0ubuntu3~cloud0) bionic-ussuri; urgency=medium
.
* New update for the Ubuntu Cloud Archive.
.
neutron (2:16.4.0-0ubuntu3) focal; urgency=medium
.
*
The verification of the Stable Release Update for neutron has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so
Public bug reported:
stress-ng --enosys 0 -t 60 causes:
[ 513.783315] BUG: scheduling while atomic: stress-ng/42082/0x0002
[ 513.783319] Modules linked in: cuse snd_seq snd_seq_device dccp_ipv4 dccp
atm chacha_generic chacha_x86_64 libchacha xxhash_generic wp512
streebog_generic
Public bug reported:
I do not know if it is a bug or not. I just installed Ubuntu 20.04 two
days ago on Aug 2, 2021 and installed the Nvidia drivers yesterday on
Aug 3, 2021 and today I keep getting this pop up saying that system
crashed. I just hit send. Do not know about why it is happening. I
Previously reported as
https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1904745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
Title:
Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are
Verified bionic-ussuri/proposed using [Test Case]
** Tags removed: verification-ussuri-needed
** Tags added: verification-ussuri-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927868
Title:
Default Comment by Bridge
** Attachment added: "opencryptoki_hirsute.debdiff"
https://bugs.launchpad.net/bugs/1928780/+attachment/5515842/+files/opencryptoki_hirsute.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also noticed just now that this kernel from the 20 track does seem to work
fine on uc20 systems:
pi-kernel5.4.0-1042.46 33120/beta
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938912
I understand this was released in net-snmpd v5.9.1 in May 2021.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912964
Title:
[Patch] Add support for digests detected from ECC certificates
To
I had been running with a USB GPS for years and recently purchased a GOOD GNSS
device, so I have not had anything on this machine that accesses the pps_api
until a few days ago.
FYI I have a Raspberry Pi with Ubuntu where the pps_api works with
raspberrypi-kernel 1:1.2010727-1 if that is of any
Upstream patch:
https://gitlab.com/gpsd/gpsd/-/commit/7f30d88d04dc62b8bd6265ad1d09d72d220f97f6
Debian patch:
https://salsa.debian.org/debian-gps-team/pkg-gpsd/-/commit/2df40c7640dcbc5cbc48969bec44932623ef243b
@maanus, That is a first iteration.
sudo add-apt-repository ppa:slashd/keepconfiguration
sudo apt-get update
Let me know the outcome.
- Eric
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815101
I pinged the security team.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928780
Title:
[UBUNTU 21.04] openCryptoki: Soft token does not check if an EC key is
valid
To manage notifications
Public bug reported:
on all pi devices we are testing (rpi3, 3b+, cm3, rpi4, etc...) when
refreshing the kernel snap to the 5.4 kernel in 18-pi (r333), it fails
to boot. Here's the serial log on the failed boot from one of those
devices:
Hit any key to stop autoboot: 0
WARNING at
The virtualbox issue is tracked at LP: #1938886
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926937
Title:
[SRU] Virtualbox new release 6.1.26
To manage notifications about this bug go to:
@Eduardo you need to provide some more information, extension pack
should be updated automatically too
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926937
Title:
[SRU] Virtualbox new release
I tend to agree with Lucas that this is a wishlist bug. As such, it's
better if we wait until upstream makes a new release and Debian picks up
this patch, which will then mean that Ubuntu will also have the patch
when the next merge is done.
I don't think we should backport this to Impish
Public bug reported:
Basically I'm hitting the issue fixed by:
https://github.com/CheetahTemplate3/cheetah3/commit/53e4c37564a48f0ad9e27fef5fa49df1d644c8c5
** Affects: cheetah (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
Thanks, Seyeong and Lucas.
Seyeong, no problem at all, and thanks for the quick follow-up! I will
wait until you have news from the customer before we proceed with the
upload.
FWIW, I can't check the patch right now because the URL is 503'ing here
(internal LP problem, most likely). But I
Public bug reported:
[Impact]
In order to follow our policy on keeping the container stack (docker.io,
containerd, and runc) up-to-date in our supported releases, let's
backport the stack in Impish to Hirsute, Focal, and Bionic.
It is also important because the new releases contain some CVE
Thanks for the update. I am marking this bug as Invalid.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938691
Title:
package
root@casual-condor:/var/lib/nova# ll .ssh/
total 28
drwxr-xr-x 2 nova root 4096 Aug 3 10:43 ./
drwxr-xr-x 10 nova nova 4096 Aug 3 10:25 ../
-rw-r--r-- 1 root root 1197 Aug 3 10:54 authorized_keys
-rw--- 1 nova root 1823 Aug 3 10:25 id_rsa
-rw-r--r-- 1 nova root 400 Aug 3 10:25
> Charms were not upgraded while this broke. We simply upgrade the
packages.
If that's the case, package maintainer script might be related? For
example,
$ grep /var/lib/nova /var/lib/dpkg/info/nova-common.postinst
--home /var/lib/nova \
chown -R nova:nova /var/lib/nova/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nova (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904580
Title:
= focal kernel verification =
ubuntu@aurorus:~$ apt show linux-image-5.4.0-81-generic | grep Recommends
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
Recommends: flash-kernel | grub-efi-arm64, initramfs-tools |
linux-initramfs-tool
ubuntu@aurorus:~$ apt show
You have been subscribed to a public bug:
Charm revision: 320
Cloud: bionic-ussuri
Permissions 0644 for '/var/lib/nova/.ssh/id_rsa' are too open.
Load key "/var/lib/nova/.ssh/id_rsa": bad permissions
nova@10.35.80.49: Permission denied (publickey).
This was preventing nova resizing:
Confirmed with hirsute/linux 5.11.0-26.28 that icmp_redirect.sh results
are as expected:
# selftests: net: icmp_redirect.sh
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Confirmed with focal/linux 5.4.0-81.91 that icmp_redirect.sh results are
as expected:
# selftests: net: icmp_redirect.sh
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
# TEST: IPv6: mtu exception plus redirect [XFAIL]
[...]
#
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1921544
Title:
[bionic] fwupd 1.2.x, 1.3.x, 1.4.x: vendor-id requirement on LVFS
causes failures
To manage notifications about
On 2021-08-04 15:11, Robie Basak wrote:
> The Focal upload is missing the fix for bug 1795483 which there's a
> task for. The Hirsute upload includes fixes for both. Accepting the
> Hirsute upload. Before I accept the Focal upload, can I think if
> this intentional? I can accept the current upload
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: fwupd-signed (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu-release-upgrader/+git/ubuntu-release-upgrader/+merge/406663
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936401
Title:
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10
Confirmed with focal/linux 5.4.0-81.91 that the following testcases from
kernel selftests net are now being run:
fib_nexthop_multiprefix.sh
fib_nexthops.sh
icmp_redirect.sh
ip6_gre_headroom.sh
route_localnet.sh
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
.
Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu
I can confirm the issue is now fixed on the 5.4 kernels.
Results with bionic/linux-oracle-5.4 5.4.0-1053.57~18.04.1:
# selftests: net: pmtu.sh
# TEST: ipv4: PMTU exceptions [ OK ]
# TEST: ipv6: PMTU exceptions [ OK ]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpasupplicant (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805625
Issue resolved with a patched kernel. Patch is here
https://bugzilla.kernel.org/show_bug.cgi?id=213579#c56.
** Bug watch added: Linux Kernel Bug Tracker #213579
https://bugzilla.kernel.org/show_bug.cgi?id=213579
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Observed on bionic:linux-aws-5.4 5.4.0-1055.58~18.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886790
Title:
lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
Hello Jim,
Did it work before with your system and got broken after a kernel
update? If yes, would you be able to identify the kernel version which
was working before? If you didn't run this use case before, would you be
able to boot with an older kernel version and check whether it works?
Issue no longer present in 90.0.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936647
Title:
right-click popups transparent after upgrade to Firefox 90
To manage notifications about this bug go
I'm unable to replicate the issue of a typical apt upgrade to the linux-
raspi -1015 kernel on hirsute server breaking boot, with either SD card
storage or a USB as the root device.
Copying things between boot partitions can be done as a temporary fix
for things, but ultimately (as discussed on
101 - 200 of 304 matches
Mail list logo
