** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux (Ubuntu Impish)
Importance: Undecided => Medium
*** This bug is a duplicate of bug 1956519 ***
https://bugs.launchpad.net/bugs/1956519
Hi Oliver,
I believe you are seeing the same issue in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956519
I'll take a look and put updates in that bug.
Thanks for reporting!
Matthew
** This b
*** This bug is a duplicate of bug 1956519 ***
https://bugs.launchpad.net/bugs/1956519
Hi Oliver,
I believe you are seeing the same issue in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956519
I'll take a look and put updates in that bug.
Thanks for reporting!
Matthew
** This b
Hi Thomas,
Thanks for the report. I think your issue might be related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849
Can you please try 5.13.0-22-generic and let me know if it works there?
Thanks,
Matthew
--
You received this bug notification because you are a member of Kern
Hi Thomas,
Thanks for the report. I think your issue might be related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849
Can you please try 5.13.0-22-generic and let me know if it works there?
Thanks,
Matthew
--
You received this bug notification because you are a member of Ubun
Hi @dgatwood, @Jazz. I took a look at the USB patches that landed
between 5.11.0-41-generic and 5.11.0-44-generic in the Focal HWE tree:
https://paste.ubuntu.com/p/mfJCw5XmBv/
One commit which I thought was interesting was:
commit 5caa90d5fedfcdf57a42c272896cfd0ef6b5c667
commit-upstream: 5255660
Hi @dgatwood, @Jazz. I took a look at the USB patches that landed
between 5.11.0-41-generic and 5.11.0-44-generic in the Focal HWE tree:
https://paste.ubuntu.com/p/mfJCw5XmBv/
One commit which I thought was interesting was:
commit 5caa90d5fedfcdf57a42c272896cfd0ef6b5c667
commit-upstream: 5255660
Hi Steve,
On Wed, Dec 15, 2021 at 2:36 PM Jay Vosburgh wrote:
> >It's not necessary to remove the unattended-upgrades package in order to
> >achieve this. unattended-upgrades is configurable, and it's sufficient to
> >set 'APT::Periodic::Unattended-Upgrade "0";' in
> >/etc/apt/apt.conf.d/20auto
Hi everyone.
I was testing Jammy and happened to notice that unattended-upgrades Depends on
ubuntu-server-minimal, and when removing unattended-upgrades,
ubuntu-server-minimal is removed along with it:
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
ubuntu-serv
Hi Julian,
I have tested grub 2.06-2ubuntu3 in both BIOS and EFI mode on VMs, and I
can confirm that your patches have fixed both of the issues I was
seeing.
Thanks for the quick turnaround! I will keep testing these packages, but
it all seems good under secureboot.
Thanks,
Matthew
--
You rece
Hi Julian,
I have tested grub 2.06-2ubuntu3 in both BIOS and EFI mode on VMs, and I
can confirm that your patches have fixed both of the issues I was
seeing.
Thanks for the quick turnaround! I will keep testing these packages, but
it all seems good under secureboot.
Thanks,
Matthew
--
You rece
** Description changed:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
- ubuntu-server-minimal un
** Description changed:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
- ubuntu-server-minimal un
** Description changed:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
- ubuntu-server-minimal un
Public bug reported:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
ubuntu-server-minimal unattended-upgrades
0
Public bug reported:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
ubuntu-server-minimal unattended-upgrades
0
Public bug reported:
On Impish and later, removing unattended-upgrades also removes ubuntu-
server-minimal due to ubuntu-server-minimal depending on unattended-
upgrades
$ sudo apt remove unattended-upgrades
...
The following packages will be REMOVED:
ubuntu-server-minimal unattended-upgrades
0
Hi Julian, Derk,
I have been testing grub2-2.06-2ubuntu2 in -proposed in KVM, on both
BIOS and EFI VMs, and both appear to be broken.
On BIOS, grub2 doesn't get installed automatically, so I have to
manually run "grub-install /dev/vda". When I do, I reboot into grub
2.06, and upon selecting a ker
Hi Julian, Derk,
I have been testing grub2-2.06-2ubuntu2 in -proposed in KVM, on both
BIOS and EFI VMs, and both appear to be broken.
On BIOS, grub2 doesn't get installed automatically, so I have to
manually run "grub-install /dev/vda". When I do, I reboot into grub
2.06, and upon selecting a ker
Dear IOMMU Subsystem Maintainers,
I have been debugging an issue with Nathan Langford, CC here, for some months
now, along with Alex Williamson on the linux-pci mailing list, and I just wanted
to check that we aren't also running into an IOMMU bug when enabling IRQ
remapping in the crashkernel.
N
Performing verification for Bionic.
I installed the current 4.15.0-162-generic kernel from -updates to a
host in segmaas, and brought up my Bionic VM I installed for the
reproducer. The Bionic VM has linux-crashdump configured, with nr_cpus
configured to 8:
ubuntu@bionic-vm:~$ kdump-config show
D
Performing verification for Bionic.
I installed the current 4.15.0-162-generic kernel from -updates to a
host in segmaas, and brought up my Bionic VM I installed for the
reproducer. The Bionic VM has linux-crashdump configured, with nr_cpus
configured to 8:
ubuntu@bionic-vm:~$ kdump-config show
D
Hi Snakekick,
Sergio and I have continued to attempt to reproduce, and we have modeled
our config based on yours, and we think we see the issue. ldapsearch
works, but sssd does not.
If we comment out the line below in the sssd config, then sssd starts
working.
ldap_tls_cipher_suite = ECDHE-RSA-A
Hi Rex, Snakekick,
Thanks for testing that previous test package, it was actually very
interesting to hear that it didn't work, and it came as a real surprise.
I have been working with Sergio on reproducing this locally, and as you
can see, we haven't been able to reproduce just yet.
Along with
On Wed, Oct 13, 2021 at 4:43 AM Sergio Durigan Junior
wrote:
>
> On Tuesday, October 12 2021, Christian Ehrhardt wrote:
>
> > # SSSD tls issues
> > https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1921494
> > This is worked on by @Matthew Ruffell and @Athos Ribe
*** This bug is a duplicate of bug 1945590 ***
https://bugs.launchpad.net/bugs/1945590
** This bug has been marked a duplicate of bug 1945590
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
--
You received this bug notification because you are a member of Kernel
Packa
Hi Andrea,
Chris Chu mentioned it might be caused by `-fcf-protection=none`
in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/comments/19
Maybe should try a build without that flag?
I went and added all the duplicates to this bug, there is some more
information in some of them.
T
Hi Andrea,
Chris Chu mentioned it might be caused by `-fcf-protection=none`
in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/comments/19
Maybe should try a build without that flag?
I went and added all the duplicates to this bug, there is some more
information in some of them.
T
*** This bug is a duplicate of bug 1945590 ***
https://bugs.launchpad.net/bugs/1945590
** This bug has been marked a duplicate of bug 1945590
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs,
*** This bug is a duplicate of bug 1945590 ***
https://bugs.launchpad.net/bugs/1945590
** This bug has been marked a duplicate of bug 1945590
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
--
You received this bug notification because you are a member of Kernel
Packa
*** This bug is a duplicate of bug 1945590 ***
https://bugs.launchpad.net/bugs/1945590
** This bug has been marked a duplicate of bug 1945590
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Hi Rex and Snakekick,
I have built test packages for Bionic, Focal, Hirsute and Impish, with
the below commit included:
commit da55e3e69707de416b7949d08c165c950090bbb6
From: Iker Pedrosa
Date: Wed, 3 Mar 2021 15:34:49 +0100
Subject: ldap: retry ldap_install_tls() when watchdog interruption
Link:
** Summary changed:
- ad_use_ldaps error could not start tls encryption
+ ldap_install_tls occasionally fails due to watchdog timeout when using
ad_use_ldaps with tls
** Description changed:
- New sssd.conf variable ad_use_ldaps not working. On starting sssd it
- errors with "sssd[be[13765]: Co
Impish)
Importance: Undecided => Medium
** Changed in: sssd (Ubuntu Bionic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: sssd (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: sssd (Ubuntu Hirsute)
Assignee: (
Hi Rex,
Looking closer at the logging which you provided when debug_level = 4,
the important part is:
[sss_ldap_init_sys_connect_done] (0x0020): ldap_install_tls failed:
[Connect error] [(unknown error code)]
This looks very similar to this upstream bug report:
https://github.com/SSSD/sssd/issue
*** This bug is a duplicate of bug 1942299 ***
https://bugs.launchpad.net/bugs/1942299
Hi Kenneth,
The 4.15.0-159-generic kernel has now landed in Xenial ESM, and it
contains the fix "scsi: sr: Return correct event when media event code
is 3".
If you could install that kernel and double chec
*** This bug is a duplicate of bug 1942299 ***
https://bugs.launchpad.net/bugs/1942299
Hi Kenneth,
The 4.15.0-159-generic kernel has now landed in Xenial ESM, and it
contains the fix "scsi: sr: Return correct event when media event code
is 3".
If you could install that kernel and double chec
Sorry, the list of fixed kernels should be:
Bionic 4.15.0-159-generic
Focal 5.4.0-87-generic
Hirsute 5.11.0-37-generic
Impish 5.13.0-16-generic
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fi
Hi everyone,
The kernels with the fix "scsi: sr: Return correct event when media
event code is 3" were released to -updates yesterday.
Could you please install the latest kernel update, and double check that
it fixes the issue for you?
List of new kernels:
Bionic 4.15.0-155-generic
Focal 5.4.0-8
Sorry, the list of fixed kernels should be:
Bionic 4.15.0-159-generic
Focal 5.4.0-87-generic
Hirsute 5.11.0-37-generic
Impish 5.13.0-16-generic
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Fi
Hi everyone,
The kernels with the fix "scsi: sr: Return correct event when media
event code is 3" were released to -updates yesterday.
Could you please install the latest kernel update, and double check that
it fixes the issue for you?
List of new kernels:
Bionic 4.15.0-155-generic
Focal 5.4.0-8
*** This bug is a duplicate of bug 1942299 ***
https://bugs.launchpad.net/bugs/1942299
Hi Kenneth,
Thank you for taking the time to report the issue. In the future, please
feel free to file a case through the support portal if you find a issue
that needs to be fixed urgently in ESM.
In any c
*** This bug is a duplicate of bug 1942299 ***
https://bugs.launchpad.net/bugs/1942299
Hi Kenneth,
Thank you for taking the time to report the issue. In the future, please
feel free to file a case through the support portal if you find a issue
that needs to be fixed urgently in ESM.
In any c
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
*** 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 Kernel
Packages, which is subsc
*** 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 Kernel
Packages, which is subsc
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: Confirmed
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Hirsute)
*** 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 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 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 Kernel
Packages, which is subsc
*** 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 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
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
Hi Paul,
Could you please install the libvirt packages in -proposed and verify
that it fixes the problem?
Instructions to Install (on a Focal system):
1) cat << EOF | sudo tee /etc/apt/sources.list.d/ubuntu-$(lsb_release
-cs)-proposed.list
# Enable Ubuntu proposed archive
deb http://archive.ubun
** 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 because y
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
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
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
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 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
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 Kernel
Packages
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
Bugs, wh
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
Hi Dan, Eric, Mauricio and Dariusz,
Can you please review and consider sponsoring LP #1939853 for Focal and Bionic.
https://bugs.launchpad.net/ubuntu/+source/php7.4/+bug/1939853
Test packages are available and the commits include tests which I have run and
they pass.
Yes, I will seriously start
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
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.
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 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
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
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
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
Hi Dan, Eric, Mauricio,
Could you please review and sponsor LP #1930359 which contains a straightforward
fix for glib2.0.
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1930359
The issue is straightforward to reproduce with valgrind. If you want
to reproduce
the customer issue of corrupt
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
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
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
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
**
** 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
**
** 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
**
** 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
** 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
** 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
** 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
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
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
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
701 - 800 of 1806 matches
Mail list logo