** Description changed:
- [Impact]
+ [Impact]
For sbuild users attempting to build this package locally results in pkg
build failures due to inability of sbuild to handle the build deps alternatives
when running:
- sbuild -s --source-only-changes
+ sbuild -s --source-only-changes
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux-oracle - 4.15.0-1071.79
---
linux-oracle (4.15.0-1071.79) bionic; urgency=medium
* bionic/linux-oracle: 4.15.0-1071.79 -proposed tracker (LP: #1923804)
* Disable Atari partition support for cloud kernels (LP: #1908264)
- [Config]:
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
** 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/1928019
Title:
package plymouth-theme-ubuntustudio 20.04.1 failed to install/upgrade:
installed
Public bug reported:
Unfortunately, I made the mistake of trying to add ubuntustudio packages
to a base install of Ubuntu 20.04 and there has been a problem.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: plymouth-theme-ubuntustudio 20.04.1
ProcVersionSignature: Ubuntu
** Tags removed: verification-needed verification-needed-groovy
** Tags added: verification-done verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925971
Title:
SRU bluetooth
** Changed in: pi-bluetooth (Ubuntu Focal)
Status: In Progress => 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/1921915
Title:
Bluetooth controller not detected on CM4
To
** Description changed:
[Impact]
rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. The problem happens because the daemon uses the
strtok() function which is not thread safe.
The fix from upstream removes strtok() and uses
** Changed in: libffado (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1097308
Title:
Echo Audiofire 12 not working on Ubuntu 12.10
To manage
** Changed in: libffado (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/649542
Title:
New firewire stack makes more FFADO XRUNs than old firewire stack.
To
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
@brian-murray
Re comment #38 - No I do not have another location and/or WiFi net work
available at the moment -
I will check more on this in the A.M. 11-05.2021 - I also notice difficulties
with Impish ISO's
connecting to WiFi - todays builds Xubuntu and Kubuntu - have not the time this
This issue was fixed in the openstack/neutron 17.1.2 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1884723
Title:
[OVS] multicast between VM instances on different compute nodes is
I tested the pre-built binary of the latest version of runc (by just replacing
/usr/sbin/runc) and I was able to go to 400 pods on a single test node.
This new version was released today.
```
root@node0:~# runc -v
runc version 1.0.0-rc94
spec: 1.0.2-dev
go: go1.14.15
libseccomp: 2.5.1
```
** Merge proposal linked:
https://code.launchpad.net/~ltrager/maas/+git/maas/+merge/402538
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923268
Title:
grubnet default grub.cfg should try
** Description changed:
[Impact]
* Local package build attempts on powerpc platform as well as cloud
image builds for powerpc on Xenial were affected by inability to resolve
correct golang dependencies. Allowing debian/control and package
Makefiles to ignore building and packaging
** Description changed:
[Impact]
* Local package build attempts on riscv64 platform as well as cloud
image builds for riscv64 on Hirsute were affected by inability to
resolve correct golang dependencies. Allowing debian/control and package
Makefiles to ignore building and packaging
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
Updates: the patch was not included in kernel 5.13-rc1 yet but I sent a
follow-up email and let's see how this goes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920180
Title:
Can't detect intel
** Also affects: linux-base (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-base (Ubuntu Impish)
Importance: Undecided
Assignee: dann frazier (dannf)
Status: Fix Released
** Also affects: linux-base (Ubuntu Focal)
Importance: Undecided
** Also affects: sddm (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/1915870
Title:
gnome-shell/gnome-session-check-accelerated-gl-helper crashed
Tj, from irc #ubuntu, says "I can see the problem. it's the onegrub
builds for i386 going back to 16.04 ... the updater is picking the FIRST
in the list which is for Version: 1.167+2.04-1ubuntu44"
I think this is in reference to a change in grub2: grub2-unsigned
(2.04-1ubuntu44) hirsute;
** Description changed:
efi: Failed to lookup EFI memory descriptor
is an error message generated by the kernel.
Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
+
+ [Test case]
+ Verify that 'sudo journalctl -b -1 | grep 'efi: Failed to lookup' returns no
On all target releases, I've reproduced the bug with the old logwatch
version, and verified the issue is resolved with the new logwatch
version.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-focal verification-needed-groovy verification-needed-xenial
**
Public bug reported:
If I put a hirsute guest in a reboot loop, I find it will eventually
crash:
[Bds]Booting ubuntu
FSOpen: Open '\EFI\ubuntu\shimaa64.efi' Success
[Bds] Expand
HD(15,GPT,F3395D88-1F07-48B3-AF35-4BF4BC88021F,0x800,0x31801)/\EFI\ubuntu\shimaa64.efi
->
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1114.127
---
linux-azure-4.15 (4.15.0-1114.127) bionic; urgency=medium
* bionic/linux-azure-4.15: 4.15.0-1114.127 -proposed tracker (LP:
#1923793)
* netfilter: nf_conntrack: resolve clash for matching conntracks
All autopkgtests for the newly accepted python-apt (2.1.3ubuntu1.4) for groovy
have finished running.
The following regressions have been reported in tests triggered by the package:
apt-clone/0.4.1ubuntu5 (armhf, ppc64el, amd64, s390x, arm64)
apt/2.1.10ubuntu0.3 (s390x)
salt/3001+dfsg1-2 (s390x)
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux-aws - 5.4.0-1048.50
---
linux-aws (5.4.0-1048.50) focal; urgency=medium
* focal/linux-aws: 5.4.0-1048.50 -proposed tracker (LP: #1926967)
* Focal update: v5.4.106 upstream stable release (LP: #1920246)
- [Config] aws: update abi for
This bug was fixed in the package linux-gkeop-5.4 -
5.4.0-1015.16~18.04.1
---
linux-gkeop-5.4 (5.4.0-1015.16~18.04.1) bionic; urgency=medium
* bionic/linux-gkeop-5.4: 5.4.0-1015.16~18.04.1 -proposed tracker
(LP: #1923769)
* Focal update: v5.4.106 upstream stable release (LP:
Public bug reported:
I think this might be an issue with softare-updater, honestly. But it won't
upgrade grub, giving this as an explanation:
***
PACKAGE DEPENDENCIES CANNOT BE RESOLVED
This error could be caused by required additional software packages which are
missing or not
Hello, Alex,
I don't see the attachment.
Domas
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029
Title:
ua attach command fails
To manage notifications about this bug go to:
The verification passed for focal.
* On Pi 400 **
ubuntu@ubuntu:~$ apt-cache policy bluez pi-bluetooth linux-firmware-raspi2
bluez:
Installed: 5.53-0ubuntu3
Candidate: 5.53-0ubuntu3.1
Version table:
5.53-0ubuntu3.1 500
500 http://ports.ubuntu.com/ubuntu-ports
apport information
** Tags added: apport-collected
** Description changed:
This does not seem to be related to
https://bugs.launchpad.net/ubuntu/+source/nextcloud-desktop/+bug/1923053
going by the stack trace.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package:
** Description changed:
[Impact]
rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. The problem happens because the daemon uses the
strtok() function which is not thread safe.
The fix from upstream removes strtok() and uses
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1926057/+attachment/5496215/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926057
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1926057/+attachment/5496214/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
https://bugs.launchpad.net/bugs/1926057/+attachment/5496216/+files/modified.conffile..etc.apport.crashdb.conf.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Still causing SIGSEV with 3.1.1-1ubuntu1.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926057
Title:
nextcloud crashes with SIGSEV
To manage notifications about this bug go to:
Yes, when I just plug in my hub (also without any connections), my wifi
connection get lost.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925768
Title:
Losing Wifi connection when USB-C Hub was
This issue was fixed in the openstack/neutron 16.3.2 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883089
Title:
[L3] floating IP failed to bind due to no agent gateway port(fip-ns)
To
This is a false-positive for the SRU due to the binary copy of shim 1.47
from impish to hirsute-proposed. It has already been fixed in hirsute
release, there is no change here and no need for an SRU verification.
** Changed in: shim-signed (Ubuntu Hirsute)
Status: Fix Committed => Fix
I uploaded it to this Gist:
https://gist.githubusercontent.com/atrepca/dede1e2f4b894a444d6ac0f0abeaf5dd/raw/e5877b08940773e01e5ef93596f31ede49cb69e0
/ubuntu-advantage.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
So the initramfs-tools with the fix has migrated now, the next impish
daily should have it (serial 20210511 or later). Would you be able to
test to see if that helps?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Trying again...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029
Title:
ua attach command fails
To manage notifications about this bug go to:
I can't seem to be able to attach, ok to post the full log here? It's
1342 lines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927029
Title:
ua attach command fails
To manage notifications about
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux-bluefield - 5.4.0-1011.14
---
linux-bluefield (5.4.0-1011.14) focal; urgency=medium
* focal/linux-bluefield: 5.4.0-1011.14 -proposed tracker (LP:
#1923761)
* kernel crash with stress CT offload traffic (LP: #1922672)
- netfilter:
This bug was fixed in the package linux - 5.4.0-73.82
---
linux (5.4.0-73.82) focal; urgency=medium
* focal/linux: 5.4.0-73.82 -proposed tracker (LP: #1923781)
* Packaging resync (LP: #1786013)
- update dkms package versions
* CIFS DFS entries not accessible with
This bug was fixed in the package linux-gcp - 5.4.0-1043.46
---
linux-gcp (5.4.0-1043.46) focal; urgency=medium
* focal/linux-gcp: 5.4.0-1043.46 -proposed tracker (LP: #1923765)
* Focal update: v5.4.106 upstream stable release (LP: #1920246)
- [Config] gcp: update abi for
This bug was fixed in the package linux-gke - 5.4.0-1043.45
---
linux-gke (5.4.0-1043.45) focal; urgency=medium
* focal/linux-gke: 5.4.0-1043.45 -proposed tracker (LP: #1923768)
* Focal update: v5.4.106 upstream stable release (LP: #1920246)
- [Config] gke: update abi for
This bug was fixed in the package linux-gkeop - 5.4.0-1015.16
---
linux-gkeop (5.4.0-1015.16) focal; urgency=medium
* focal/linux-gkeop: 5.4.0-1015.16 -proposed tracker (LP: #1923770)
* Focal update: v5.4.106 upstream stable release (LP: #1920246)
- [Config] gkeop: update
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
** Package changed: ubuntu => simple-scan (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927998
Title:
Jitter/noise in document scan
To manage notifications about this bug go to:
Public bug reported:
The SLURM documentation clearly states that the configurator html pages
are version specific.
The file /usr/share/doc/slurmctld/slurm-wlm-configurator.html which is
supposed to be the configuration generator for the installed version
19.05.5-1 in-fact states:
> This tool
Hi Christian,
Thanks for your response.
Do you mean disabling and enabling autostart to the old guests?
In our dev lab worked straight away after installing the first PPA you
bundled together, I didn't have to disable and enable autostart.
Kind Regards,
FRANCISCO MENCHACASALES ENGINEER |
Verified for hirsute.
** Description changed:
efi: Failed to lookup EFI memory descriptor
is an error message generated by the kernel.
Please pull in https://github.com/rhboot/shim/pull/361/files to fix it.
[Test case]
- Verify that 'sudo journalctl -b -1 | grep 'efi: Failed to
The Ubuntu Security team is +1 on disallowing purely numeric usernames,
as they are too easily confused with UIDs.
I think our preference would be to disallow leading numeric digits
entirely so that for example, 0x0 and 0o0 would be blocked as well, to
try to prevent both user and programmatic
> Can some of the testing be shortened
Well the test really does nothing other than run 'ssh' from container A
to container B before sshuttle is run and again while it's running. So
(other than timeouts) the test can't be shortened much. I think most of
the time comes from timeouts and the lxd
This bug was fixed in the package linux - 4.15.0-143.147
---
linux (4.15.0-143.147) bionic; urgency=medium
* bionic/linux: 4.15.0-143.147 -proposed tracker (LP: #1923811)
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* LRMv4: switch to signing
This bug was fixed in the package linux - 4.15.0-143.147
---
linux (4.15.0-143.147) bionic; urgency=medium
* bionic/linux: 4.15.0-143.147 -proposed tracker (LP: #1923811)
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* LRMv4: switch to signing
This bug was fixed in the package linux - 4.15.0-143.147
---
linux (4.15.0-143.147) bionic; urgency=medium
* bionic/linux: 4.15.0-143.147 -proposed tracker (LP: #1923811)
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* LRMv4: switch to signing
This bug was fixed in the package linux - 4.15.0-143.147
---
linux (4.15.0-143.147) bionic; urgency=medium
* bionic/linux: 4.15.0-143.147 -proposed tracker (LP: #1923811)
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* LRMv4: switch to signing
This bug was fixed in the package linux - 4.15.0-143.147
---
linux (4.15.0-143.147) bionic; urgency=medium
* bionic/linux: 4.15.0-143.147 -proposed tracker (LP: #1923811)
* CVE-2021-29650
- netfilter: x_tables: Use correct memory barriers.
* LRMv4: switch to signing
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
With 21.10 open, we can now let php8.0 back in (see LP: #1927264 and LP:
#1927288)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907177
Title:
Please remove php8.0 from Ubuntu 21.04
To manage
*within a release. I've also updated the information above. Let me
know what further info is needed.
** Changed in: grub2-signed (Ubuntu)
Status: Incomplete => New
** Changed in: update-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you
This was not necessary to include in the SRU of shim-signed to hirsute
(and in fact I specifically omitted the change from the upload I did to
hirsute-proposed, which got clobbered). But it also doesn't have any
impact for hirsute since -Zxz is already the default, so given that the
package has
Public bug reported:
Example failure:
http://10.246.72.9/5.4.0-1045.49-oracle/focal-linux-oracle-oracle-
amd64-5.4.0-VM.Standard2.1-ubuntu_qrt_kernel_security/ubuntu_qrt_kernel_security/results/ubuntu_qrt_kernel_security
.test-kernel-security.py/debug/ubuntu_qrt_kernel_security.test-kernel-
No refusal, just that I got this information meanwhile from FFADO
maintainer (before I got around reporting it at Debian) and it solved it
for me. So I shared that it here because perhaps it is not a bug at all.
I have also been relaying feedback from the FFADO maintainer on issues
reported at
This bug was fixed in the package linux-aws-5.4 - 5.4.0-1048.50~18.04.1
---
linux-aws-5.4 (5.4.0-1048.50~18.04.1) bionic; urgency=medium
* bionic/linux-aws-5.4: 5.4.0-1048.50~18.04.1 -proposed tracker (LP:
#1926966)
* Focal update: v5.4.106 upstream stable release (LP: #1920246)
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
This bug was fixed in the package linux-oem-5.10 - 5.10.0-1025.26
---
linux-oem-5.10 (5.10.0-1025.26) focal; urgency=medium
* focal/linux-oem-5.10: 5.10.0-1025.26 -proposed tracker (LP:
#1926155)
* Packaging resync (LP: #1786013)
- update dkms package versions
*
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
These are the relevant upstream bugs at Debian, probably all the same root
cause:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947376
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958178
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960741
** Bug watch added: Debian Bug
1 - 100 of 495 matches
Mail list logo
