*** This bug is a duplicate of bug 1942299 ***
https://bugs.launchpad.net/bugs/1942299
** This bug has been marked a duplicate of bug 1942299
CD/DVD tray ejects on boot or waking from suspend
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
*** This bug is a duplicate of bug 1911055 ***
https://bugs.launchpad.net/bugs/1911055
This bug was discovered as duplicate - the issue persisted while the P50
was suspended & resumed while in a docking station (probably prime-
select using 'ondemand'). This is GPU driver related.
** This bug
Public bug reported:
[Impact]
On systems upgraded from Bionic to Focal, enabling FIPS via the ua tool
will fail, due to the following error:
Setting up ubuntu-fips (1.2.1) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-84-generic
Failed to copy HMAC file "/usr/lib/x86_64-linux-gnu/.libg
Public bug reported:
Ubuntu Release: Ubuntu 20.04.3 LTS
Installation Style: Minimal (selected during GUI install) (Untested against
full installation style)
Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD
Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprie
u have libvirt
installed, if this is a production machine.
6) sudo rm /etc/apt/sources.list.d/ubuntu-$(lsb_release -cs)-proposed.list
If the fixed package works as expected, we will mark the launchpad bug
as verified and fast-track the release to -updates.
Thanks,
Matthew
--
You received th
** Description changed:
- The latest libvirtd (6.0.0-0ubuntu8.13) crashes when trying to bring up
- network pools with the stacktrace below. I tracked down the problem to
- the newly added patch (lp-1892132-Add-phys_port_name-support-on-
- virPCIGetNetName.patch). Assigning *netname = firstEntry
Hi Paul,
Thank you very much for testing, we appreciate it.
I'll make sure we get this fix fast-tracked, and try get a new libvirt
build into -proposed in a couple hours, and try go for a release to
-updates in the next day or so.
Thanks,
Matthew
--
You received this bug notification be
Test packages are now available in:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1943481-test
Please note these test packages are NOT SUPPORTED by Canonical, and are
for TEST PURPOSES ONLY. ONLY install in a dedicated test environment.
Instructions to Install (on a Focal system):
1) sudo ad
Okay, after reviewing the various patches and backports, Frode's
backport was correct, it was just missing the "firstEntryName = NULL;"
line.
Attached is a debdiff with the "firstEntryName = NULL;" line restored.
Only Focal is affected, Hirsute and Impish are working correctly.
I have a test pack
** Changed in: libvirt (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1943481
Title:
libvirtd crashes when creating netw
Okay, this is what appears to have happened.
During the backport of:
commit 5b1c525b1f3608156884aed0dc5e925306c1e260
Author: Dmytro Linkin
Date: Thu Jan 21 14:15:22 2021 +0200
Subject: util: Add phys_port_name support on virPCIGetNetName
Link:
https://github.com/libvirt/libvirt/commit/5b1c525
** Also affects: libvirt (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: libvirt (Ubuntu Focal)
Importance: Undecided => Critical
** Changed in: libvirt (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member o
** Attachment added: "Current dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943370/+attachment/5524707/+files/dmesg-20210912.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Attachment added: "Dmesg for 5.8.0-59"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1943370/+attachment/5524706/+files/dmesg-Kernel-5.8.0-59-generic-20210626.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core
Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA
controller])
Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller
[17aa:3978]
Control: I/O+ Mem+ BusMaster+ S
Public bug reported:
The screen flicker started while booting into kernel image 5.8.0-63 and
seems to happen on all the newer images. Image 5.8.0-55 doesn't
flicker, and this is what is currently used.
Bug #1939296 is similar, but the GPU hang is not in my dmesg output and
versions before 5.8.0-
I took a look at the autopkgtest regression for php-luasandbox on arm64.
https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/arm64/p/php-luasandbox/20210908_213035_50d50@/log.gz
We fail on:
FAIL profiler sorting [tests/profiler-sorting.phpt]
I started a t4.medium arm64 instance on A
Fixed by replacing sddm with gdm
** Changed in: gnome-shell (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/1942425
Title:
Gnome shell crashes after lock
Public bug reported:
After locking screen and logging back in gnome shell has crashed and
there is nothing open in the sessin.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.9-0ubuntu0.20.04.2
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-g
Public bug reported:
when clicking on the 'show applications' button, all the apps show up
for about a half-second before disappearing and then being replaced by
the animation of the apps swooping in from the 'show applications'
button. not a huge deal, just a display bug.
ProblemType: Bug
Distro
Performing verification for Bionic.
I installed php7.2 and php7.2-mysql from -updates, version
7.4.3-4ubuntu2.5.
I also installed mysql and set up the database table and inserted data
into it.
$ sudo apt-cache policy php7.2 | grep Installed
Installed: 7.2.24-0ubuntu0.18.04.8
$ cat testcase.ph
Performing verification for Focal.
I installed php7.4 and php7.4-mysql from -updates, version
7.4.3-4ubuntu2.5.
I also installed mysql and set up the database table and inserted data
into it.
$ sudo apt-cache policy php7.4 | grep Installed
Installed: 7.4.3-4ubuntu2.5
$ cat testcase.php
prepa
Hi test0830,
This particular issue was fixed by AWS on their backend, it wasn't an
issue with Ubuntu at all.
If you are having similar issues, you should open a new bug or a support
ticket on AWS.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Attached is a debdiff for Bionic.
I also ran the three tests in this patch, and they all pass:
ext/mysqli/tests/bug77935.phpt
ext/mysqli/tests/ps_cursor_multiple_result_sets.phpt
ext/mysqli/tests/mysqli_stmt_get_result.phpt
https://paste.ubuntu.com/p/5422Hb6YMg/
** Patch added: "Debdiff for php
Attached is a debdiff for Focal.
I have run the three tests included in these changes, and they all
succeed:
ext/mysqli/tests/ps_cursor_multiple_result_sets.phpt
ext/mysqli/tests/bug77935.phpt
ext/mysqli/tests/mysqli_stmt_get_result.phpt
https://paste.ubuntu.com/p/ZBz9wtXcDr/
** Description cha
h of these commits landed in php 7.4.13 and 7.4.15, which means they
are already present in hirsute 7.5.16 and impish 8.0.
Both commits required backports to remove the NEWS hunk, and the second
commit needed indentation adjustments.
** Affects: php7.2 (Ubuntu)
Importance: Undecided
Status: F
Public bug reported:
There was a generated bug report. I hope it didn't get lost while I
tried to figure out login.
Just trying to do a clean install of Xubuntu 20.04 on my new System76
Gazelle laptop.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignatur
Performing verification for Bionic.
Firstly, I installed 4.15.0-151-generic from -updates, to get a baseline
for all xfstests results.
I built and ran btrfs/* from xfstests, using the following local config:
export TEST_DEV=/dev/vdc
export TEST_DIR=/mnt/test
export SCRATCH_DEV_POOL="/dev/vdd /de
Performing verification for Bionic.
I installed 4.15.0-151-generic from -updates, and added the reproducer
btrfs qcow2 image file to my VM.
From there, I mounted the filesystem and attempted to balance:
$ sudo mount /dev/vdb /mnt
$ sudo btrfs filesystem balance start --full-balance /mnt
Segmenta
Performing verification for Focal.
I will first reproduce the problem with glib2.0 2.64.6-1~ubuntu20.04.3
from -security with the libglib2.0-0 libglib2.0-bin libglib2.0-data
packages.
I deleted all existing schemas from /usr/share/glib-2.0/schemas and
replaced them with a set of schemas which rep
I am also having this issue on a fresh install of 21.04:
* Occurs when booting with a USB stick already plugged in.
* Does not occur if booted without the USB stick.
* Does not occur if booted without the USB stick, then plugged in post-boot.
--
You received this bug notification because you are
Attached is a debdiff for glib2.0 on Focal which fixes this problem.
** Patch added: "Debdiff for glib2.0 for Focal"
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1930359/+attachment/5510466/+files/lp1930359_focal.debdiff
** Tags removed: regression-update
** Tags added: sts-sponsor
** No longer affects: mutter (Ubuntu)
** No longer affects: mutter (Ubuntu Focal)
** Changed in: glib2.0 (Ubuntu)
Status: New => Fix Released
** Changed in: glib2.0 (Ubuntu Focal)
Status: New => In Progress
** Changed in: glib2.0 (Ubuntu Focal)
Importance: Undecided => High
**
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs
@brian-murray - I performed the following test.
System info:
$ uname -a
Linux linodeusw01 5.4.0-74-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1934709
[Impact]
During an automatic balance, users may encounter an error when writing
the transaction log to disk, when the log tree is being parsed, which
forces the filesystem to be remounted read-only and outputs
ve a reply.
If you read Richard's mailing list link, it mentions filesystem
corruption with missing extents. This suggests this crash might be
linked to bug 1933172, which I came across while trying to reproduce the
issue in this bug.
** Affects: linux (Ubuntu)
Importance: Undecided
S
Hi Daniel,
Yes, I am sure this is the same issue that they are experiencing there,
and I now believe the issue lies in glib, and not mutter.
When we install mutter-common, it calls the libglib2.0-0 hook to
recompile the gsettings schemas.
The customer provided me with a tarball of their
/usr/sha
Okay, the affected user has now started experiencing the issue again,
and was forced to roll mutter back on their fleet.
We managed to get some logs this time, and we have determined what is
happening.
When the user upgrades the mutter packages, particularly mutter-common,
the libglib2.0-0 hook i
The affected user cannot reproduce the issue anymore. The new mutter
packages install fine in their environment, and gdm starts every time.
They have since rolled out the new mutter packages to their fleet
without any issues.
I'm going to mark this bug as invalid, as we can't reproduce the issue
a
Confirmed in 21.04.
@Tudor, Alt+F2 r will remove the icon from the launcher until this bug
is squashed.
It appears that the icon permanence occurs when I eject using the
physical button on the drive as opposed to right-clicking and selecting
"Eject" or by running the eject command at the CLI, bot
-updates.
You may now install these kernels to your systems and enjoy fast block
discard for your Raid10 arrays.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896578
Title:
raid10
accordingly.
I wish you a trouble free rollout of these kernels to your systems.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard leads to corrupted file
lists/linux-btrfs/msg103367.html
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Bionic)
Importance: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: bionic sts
** Changed in: linux (Ubuntu)
** Attachment added: "screenshot of working gdm on AWS"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+attachment/5505412/+files/Screenshot%20from%202021-06-18%2013-40-15.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I spent some time attempting to reproduce on AWS today, using a
g4dn.xlarge instance, which has a Nvidia Tesla T4 GPU, which supports
GRID.
I installed ubuntu-desktop-minimal and rebooted, and gdm started fine
with mutter 3.36.9-0ubuntu0.20.04.1. I confirmed this by looking at the
instance screens
, and I don't have any
corruption when I fsck my disks.
If things keep looking good, the SRU cycle will complete early next
week, and the kernel will be released to -updates around the 21st of
June, give or take a few days if any CVEs turn up.
Let me know how things are going.
Thanks,
Ma
stable, and I don't have any
corruption when I fsck my disks.
If things keep looking good, the SRU cycle will complete early next
week, and the kernel will be released to -updates around the 21st of
June, give or take a few days if any CVEs turn up.
Let me know how things are going.
Thanks,
Ma
Public bug reported:
Gnome Maps simply will no longer start on Ubuntu 20.04.2. Appears to be
a javascript problem.
Output error:
js-Message: 09:44:28.056: JS WARNING:
[resource:///org/gnome/Maps/js/mapSource.js 128]: reference to undefined
property "aerial"
(org.gnome.Maps:10589): Gjs-WARNING *
I built a test package based on mutter 3.36.9-0ubuntu0.20.04.1, and
reverted the three commits introduced by LP #1905825, namely:
commit: 92834d8feceeac538299a47a8c742e155de4e6e8
From: Kai-Heng Feng
Date: Mon, 21 Dec 2020 14:34:43 +0800
Subject: renderer/native: Refactor modeset boilerplate into
hanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896578
Title:
raid10: Block discard is very slow, causing severe delays for mkfs and
fstrim operations
To manage notifications about
m still running my own testing, with my /home directory being on a Raid10
array
on a Google Cloud instance, and it has no issues.
If things keep going well, we should see a release to -updates around the 21st
of June, give or take a few days if any CVEs turn up.
Thanks,
Matthew
--
You re
Performing verification for Bionic.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home directo
Performing verification for Focal.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home director
Performing verification for Groovy.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home directo
Performing verification for Hirsute.
I'm going to do three rounds of verification.
The first is the testcase from this bug, showing block discard
performance.
The second is running through the regression reproducer from bug
1907262.
The third will be results from my testing with my /home direct
e back with the results then.
Please help test these kernels in -proposed, and let me know how they
go.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896578
Title:
raid10: Block
e back with the results then.
Please help test these kernels in -proposed, and let me know how they
go.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: disca
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929129
Title:
if cloud-init status is not done, set_installer_password will crash
To manage notifications about this bug go to:
htt
Just adding a note for Bionic users, that the commit "cifs: Set
CIFS_MOUNT_USE_PREFIX_PATH flag on setting cifs_sb->prepath." landed in
4.15.0-143-generic, causing the regression, and it has been reverted in
4.15.0-144-generic.
If you are experiencing any issues with 4.15.0-143-generic, please
upg
*** This bug is a duplicate of bug 1923670 ***
https://bugs.launchpad.net/bugs/1923670
** This bug has been marked a duplicate of bug 1923670
CIFS DFS entries not accessible with 5.4.0-71.74-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
722e0a6d1bf46a689ba4541e4377c4b0b
Ubuntu-4.15.0-144.148~25
Could you please try 4.15.0-144-generic and let me know if it fixes it
for you? It should be fixed there.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
reverted before we start digging into the point release patches from
1919143.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905825
Title:
[SRU] Disable CRTCs when system becomes
reverted before we start digging into the point release patches from
1919143.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919143
Title:
SRU mutter to 3.36.9
To manage
.
Currently looking into what landed in bug 1919143 and bug 1905825.
[Testcase]
[Where problems can occur]
** Affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Affects: mutter (Ubuntu Focal)
Importance: High
Assignee: Matthew Ruffell (mruffell)
Status: In
I gather the version number came from BCC BPF which is currently 0.20.0
https://github.com/iovisor/bcc/tags
It was a failure in dpkg in the sense that dpkg reports the library was
installed fine. To me, that would mean it is the version currently set
to be used (and if there are alternatives, thes
ii iproute2 5.10.0-4ubuntu1 amd64networking and traffic control
tools
ii libbpf0:amd64 1:0.3-2ubuntu1 amd64eBPF helper library (shared
library)
There was no bpf_object__open_file symbol present.
For reference I ran:
➜ sha256sum /usr/lib/x86_64-linux-gnu/libbpf.so.0
f07
Public bug reported:
➜ ip address
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available
(required by ip)
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available
(required by ip)
ip: /lib/x86_64-linux-gnu/libbpf.so.0: no version information available
(required b
week. I would really, really appreciate it if you
could help test the kernels when they arrive in -proposed, as I really
don't want to introduce any more regressions.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
week. I would really, really appreciate it if you
could help test the kernels when they arrive in -proposed, as I really
don't want to introduce any more regressions.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
Public bug reported:
See:
https://bugs.kde.org/show_bug.cgi?id=430862
Would it be possible to backport this fix to affected Ubuntu releases
ASAP as it's quite irritating every time you take a screenshot.
I detected it on hirsute, not sure what other releases could be
affected.
ProblemType: Bug
ently using a cloud instance with 4x NVMe disks in Raid10 as my
/home directory, and things seem okay.
I'll keep you updated on the progress of this patchset via this bug.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
y /home on a Raid10 array, and when I next
submit the patches for SRU.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard leads to corrupted file system
Performing verification for Groovy
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu6.20.10.1
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/commo
Performing verification for Hirsute
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu6.21.04.1
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/comm
Performing verification for Focal
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.3.1-5ubuntu4.2
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/common-auth:
Performing verification for Bionic
I enabled -proposed and installed libpam-modules libpam-modules-bin
libpam-runtime libpam0g version 1.1.8-3.6ubuntu2.18.04.3
>From there, I set the pam_faillock configuration in:
/etc/security/faillock.conf:
deny = 3
unlock_time = 120
and also:
/etc/pam.d/com
d it will most likely fix the problem.
Let me know if you have any more questions.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1837810
Title:
KVM: Fix zero_page reference counte
The changes mentioned around shimx64.efi above fixed this issue for me
on Lenovo ThinkPad Intel® Core™ i7-3667U CPU @ 2.00GHz × 4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924605
Title:
Grub2 m
Was able to replicate the ugly fix. removing the file got gimp working
again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893480
Title:
undefined symbols
To manage notifications about this bug g
Performing verification for Groovy.
I went and generated the ssl certificates and attempted to verify them with
the openssl version 1.1.1f-1ubuntu4.3 from -updates.
ubuntu@deep-mako:~$ sudo apt-cache policy openssl | grep Installed
Installed: 1.1.1f-1ubuntu4.3
ubuntu@deep-mako:~$ mkdir reproduc
Performing verification for Focal
Generating the ssl certificates, and reproducing the problem with version
1.1.1f-1ubuntu2.3 from -updates.
ubuntu@select-lobster:~$ sudo apt-cache policy openssl | grep Installed
Installed: 1.1.1f-1ubuntu2.3
ubuntu@select-lobster:~$ mkdir reproducer
ubuntu@sele
Attached is a debdiff for grub2-signed which issues a sed to remove the
GRUB_DISTRIBUTOR=Debian line from /etc/default/grub.d/50-cloudimg-
settings.cfg
** Patch added: "Debdiff for grub2-signed on Xenial"
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1928040/+attachment/5496305/+
** Description changed:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot
Public bug reported:
[Impact]
GCE cloud instances started with images released prior to 2020-11-11
will fail to reboot when the newest grub2 2.02~beta2-36ubuntu3.32
packages are installed from -updates.
Upon reboot, the instance drops down to a grub prompt, and ceases to
boot any further.
The o
issues at
all with the test kernels, please let me know.
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907262
Title:
raid10: discard leads to corrupted file system
To manage not
I have completed most of my regression testing, and things are still looking
good. The performance of the block discard is there, and I haven't seen any
data corruption.
In particular, I have been testing against the testcase for the regression that
occurred with the previous revision of the patch
If anyone is interested in testing, there are new re-spins of the test kernels
available in the following ppa:
https://launchpad.net/~mruffell/+archive/ubuntu/lp1896578-test
The patches used are the ones I will be submitting for SRU, and are more
or less identical to the patches in the previous t
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
bmitting the patches for tomorrow, but
if I think we need more time for testing, worst case it will slip to the
SRU cycle after, which is 3 weeks away.
I will write back tomorrow with the results of my regression testing and
if I have submitted the patches for SRU.
Thanks,
Matthew
--
Y
** Description changed:
[impact]
openssl doesn't build source properly because of a badly-constructed
patch
[test case]
$ pull-lp-source openssl groovy
...
$ cd openssl-1.1.1f/
$ quilt pop -a
...
$ dpkg-buildpackage -d -S
dpkg-buildpackage: info: source package opens
Attached is a V2 for hirsute which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494814/+files/lp1927161_hirsute_v2.debdiff
--
You received this bug notification because
Attached is a V2 for impish which correctly has d/p/ in the
debian/changelog.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494813/+files/lp1927161_impish_v2.debdiff
** Patch removed: "debdiff for openssl on hirsute
Attached is a debdiff for openssl on hirsute which fixes this problem.
** Patch added: "debdiff for openssl on hirsute"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494811/+files/lp1927161_hirsute.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for openssl on groovy, which fixes this issue, and
also bug 1926254
** Patch added: "debdiff for openssl on groovy"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494812/+files/lp1926254_lp1927161_groovy.debdiff
** Patch removed: "debdiff for
Attached is a debdiff for impish which fixes this problem.
** Patch added: "debdiff for openssl on impish"
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+attachment/5494810/+files/lp1927161_impish.debdiff
--
You received this bug notification because you are a member of Ubun
I split 'pr12272.patch' into one file per commit, and I did a diff to
ensure that there is no changes to the code:
https://paste.ubuntu.com/p/zDqqXmsM8c/
When using these split up patches "dpkg-buildpackage -d -S" completes
successfully.
--
You received this bug notification because you are a m
nassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Hirsute)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: openssl (Ubuntu Impish)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a mem
built
into the next Ubuntu kernel update. Even when they are built into the
next kernel update, I'll let you know how you can test them when they
are in -proposed, before they are officially released to -updates.
I'll write back tomorrow morning with instructions on how to install the
fresh
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/1896578
[Impact]
Block discard is very slow on Raid10, which causes common use cases
which invoke block discard, such as mkfs and fstrim operations, to take
a very long time.
For example, on a i3.8xlarge instance
401 - 500 of 19676 matches
Mail list logo
