Performing verification for Focal.
I set up a Jammy VM to be the nfs server, using the instructions in the
SRU template.
$ sudo cat /proc/fs/nfsd/versions
-2 -3 +4 -4.0 +4.1 +4.2
4.0 is not allowed, but 4.1 and 4.2 are.
I then started a fresh Focal VM, and installed nfs-common
Hi everyone,
@angros47, yes, this issue looks to be what you are experiencing here.
https://bugs.archlinux.org/task/80064 mentions that the issue was
introduced in:
commit aa3998dbeb3abce63653b7f6d4542e7dcd022590
Author: Damien Le Moal
Date: Sat Aug 26 09:43:39 2023 +0900
Subject: ata:
Reviews from Senior Kernel Team Members:
ACK 1
https://lists.ubuntu.com/archives/kernel-team/2024-February/149051.html
ACK 2
https://lists.ubuntu.com/archives/kernel-team/2024-February/149061.html
Applied
https://lists.ubuntu.com/archives/kernel-team/2024-February/149119.html
Will let you know
I have been running the test packages on AWS with the reproducer running
for 20 days now, and they are still running great. The change to direct
IO really does fix this issue, and my testing has removed any and all
concerns of causing a regression.
Previously focal wouldn't last more than 20
Submitted the patch as SRU to mantic. Noble will pick it up when the
kernel team pulls in 6.8-rc5.
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149042.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/149043.html
--
You received this bug
** Description changed:
+ BugLink: https://bugs.launchpad.net/bugs/2049634
+
[Impact]
Upon installing the 6.5 HWE kernel on Jammy, users with a custom wsize
set will see data destruction when copying files from their systems onto
- a cifs smb 1.0 mount.
+ a cifs smb mount.
wsize
Hi R. Diez,
The patch was merged upstream in 6.8-rc5:
commit 4860abb91f3d7fbaf8147d54782149bb1fc45892
Author: Steve French
Date: Tue Feb 6 16:34:22 2024 -0600
Subject: smb: Fix regression in writes when non-standard maximum write size
negotiated
Link:
Cover letter:
https://lists.ubuntu.com/archives/kernel-team/2024-February/148896.html
Patch:
https://lists.ubuntu.com/archives/kernel-team/2024-February/148897.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
could cause it
to page fault and subsequently crash, resulting in downtime.
The only workaround will be to disable all profiling tools until a fix
is available.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: linux (Ubuntu Mantic)
Importance: Medium
I tried on a random lab machine with 2x HP MM0500GBKAK disks.
With 6.5.0-18-generic:
Before:
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
Hi R. Diez,
Steve posted a new patch [1] that also rounds the wsize down when specified on
the mount command line, just as we wanted:
[1] https://lore.kernel.org/linux-
cifs/CAH2r5mvPz2CUyKDZv_9fYGu=9L=3uime7xajgbbu+if8ch8...@mail.gmail.com/
I tested it, and it works great.
$ sudo mount -t
Hi everyone,
Would it be possible if you could try 6.8-rc4 mainline to see if the
issue is fixed there?
https://kernel.ubuntu.com/mainline/v6.8-rc4/
$ wget
https://kernel.ubuntu.com/mainline/v6.8-rc4/amd64/linux-headers-6.8.0-060800rc4-generic_6.8.0-060800rc4.202402112032_amd64.deb
$ wget
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed-hwe-6.5 (Ubuntu)
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
--
You
*** This bug is a duplicate of bug 2053041 ***
https://bugs.launchpad.net/bugs/2053041
Hi Alex, please come over to bug 2053041 and we can try figure this out.
Thanks!
** This bug has been marked a duplicate of bug 2053041
Issue when shutting down computer: internal hard drive is not shut
** Description changed:
- Release: 22.04.3 LTS
- coreutils 8.32-4.1ubuntu1
+ [Impact]
- ls triggers unwanted mounts of autofs filesystems
+ Issuing a 'ls -l' or a 'stat' on an autofs share when you have set
+ --ghost in the auto.master file, or browse_mode=yes in autofs.conf will
+ lead to the
Hi R. Diez,
You have probably been following the chatter on the upstream mailing list
discussion. I initially thought the patch didn't fix the issue, as when I mount
with wsize=16850, the issue still occurs [1], but it seems that the intent of
the patch is to only correct when the server
Attached is a debdiff that solves this issue on Jammy.
** Patch added: "Debdiff for coreutils on Jammy"
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2033892/+attachment/5745181/+files/lp2033892_jammy.debdiff
--
You received this bug notification because you are a member of
signee: (unassigned) => Matthew Ruffell (mruffell)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2033892
Title:
ls -l triggers mount of autofs shares when --ghost option i
Hi Andrea,
I'm having some trouble with this bug, particularly on jammy-hwe.
You see, is_rust_module.sh seems to have returned again.
I see you removed it in 4f2dbd4037a697c6d96eb3d8867253e2c8d6f8d0 (ubuntu-mantic)
but if you look at 0eec6d2a63d86ac94dc8fa7c56820a0972ccbe1f (ubuntu-mantic),
** Summary changed:
- smb1: wsize blocks of bytes followed with binary zeros on copy, destroying
data
+ smb: wsize blocks of bytes followed with binary zeros on copy, destroying data
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
The cifs-netfs refactor in development seems to fix the issue:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-
fs.git/log/?h=cifs-netfs
Specifically:
commit 34efb2a814f1882ddb4a518c2e8a54db119fd0d8
Author: David Howells
Date: Fri Oct 6 18:29:59 2023 +0100
Subject: cifs: Cut
I have bisected the issue, and found the commit that introduces the
problem:
commit d08089f649a0cfb2099c8551ac47eef0cc23fdf2
Author: David Howells
Date: Mon Jan 24 21:13:24 2022 +
Subject: cifs: Change the I/O paths to use an iterator rather than a page list
Link:
Hi Milan,
Once an Ubuntu series is finalised and released, it is essentially frozen
for stability reasons.
There are certain circumstances when packages are updated, which is set out
in the Stable Release Updates process:
https://wiki.ubuntu.com/StableReleaseUpdates
This normally involves
Hi Krister,
Fascinating. I'm in New Zealand, so I use ap-southeast-2 in Sydney,
Australia for all my instances, and I never gave it any thought that
this could depend on how busy EBS is on the availability zone.
I'll move my instances to us-west-2.
Thanks,
Matthew
--
You received this bug
linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => High
** Changed in: linux (Ubuntu Mantic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) =&g
Hi Krister,
I have finally seen this occur in real life with my own two eyes!
You are absolutely correct, the 4-retry doesn't seem to be sufficient
sometimes.
The reproducer works on Focal and previous in about 20 minutes, so its
easy to see the issue trigger on Focal. But Focal and previous
Hi Eugene,
Can you try the latest 6.8-rc1 and let us know if it works there? Then
we can see if we just need to backport a patch to 6.5, or talk to the
upstream maintainers instead.
https://kernel.ubuntu.com/mainline/v6.8-rc1/
Thanks,
Matthew
--
You received this bug notification because you
Exactly 3900 bytes long? That sure is strange. Do you think I would be
able to reproduce if I set up a smb1.0 mount, make a bunch of text files
with random content, take their sha256 checksums, copy to the smb1.0
share, then re-compute the sha256 checksums to see if they match?
I would probably
Hi Craig.
Excellent work tracking down the mailing list discussion. From what I can see is
that actual memory allocation and free still works as intended, it is just
accounting that becomes incorrect, making your system work correctly, just with
wrong numbers displayed in your metrics.
** No longer affects: linux-meta (Ubuntu)
** No longer affects: linux-meta-hwe-6.5 (Ubuntu)
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Mantic)
Hi rdiez,
Yes, this was fixed in 6.2.0-32-generic, as it included the commit you
mentioned in your description.
commit e5e1411ee7e612335d8e9d6fd7379401dee54f28
Author: Paulo Alcantara
Date: Tue May 23 17:38:38 2023 -0300
cifs: fix smb1 mount regression
BugLink:
*** This bug is a duplicate of bug 2033732 ***
https://bugs.launchpad.net/bugs/2033732
** This bug has been marked a duplicate of bug 2033732
SMB 1 broken in kernel linux-generic-hwe-22.04 (version 6.2.0-31)
--
You received this bug notification because you are a member of Kernel
Hi Krister,
I apologise for the delay. The main issue I have been having with
testing is that it reproduces significantly faster on some releases than
others, and I still haven't managed to reproduce once on some releases.
I'll set up some fresh reproducers now, and leave them running.
If you
Attached is a patch for noble that solves this issue.
** Patch added: "Debdiff for e2fsprogs on noble"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5738302/+files/lp2036467_noble.debdiff
--
You received this bug notification because you are a member of Ubuntu
Attached is a V2 patch for mantic with a different version number, due
to it no longer being the devel release.
** Patch removed: "Debdiff for e2fsprogs on mantic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707893/+files/lp2036467_mantic.debdiff
** Patch
You can file a bug just like you did. If you happen to do a bit more
debugging, then making sure it gets assigned to the correct package
helps.
For the kernel, always just file a new bug, unless someone has the same
issue as you and you can find the bug via google or the all bugs
category on the
Great, so the fix works as intended. 5.15.0-91-generic should be
released to -updates this week hopefully.
I don't think the CPC team builds any cloud images with -proposed
enabled. I asked around, and I'll let you know if there does happen to
be some images built.
For the meantime you could
Hi Daniel,
Thanks for reporting. I had a look into the followup commit you
mentioned:
~/Work/kernel/ubuntu-jammy$ git log --grep "virtio-net: set queues after
driver_ok" origin/master-next
commit c6c83b9055f44bcb2bc2fae32323c0a1510c7656
Author: Jason Wang
Date: Wed Aug 9 23:12:56 2023 -0400
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Attached is a debdiff that resolves the issue on Focal. Version 5.
** Patch added: "Debdiff for tracker-miners on Focal v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725476/+files/lp1779890_focal_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on Jammy. Version 5.
** Patch added: "Debdiff for tracker-miners on Jammy v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725475/+files/lp1779890_jammy_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on lunar. Version 5.
** Patch added: "Debdiff for tracker-miners on Lunar v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725474/+files/lp1779890_lunar_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on mantic. Version 5.
** Patch added: "Debdiff for tracker-miners on Mantic v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725473/+files/lp1779890_mantic_v5.debdiff
--
You received this bug
Attached is a debdiff that resolves this issue on debian unstable /
noble.
** Patch removed: "Debdiff for tracker-miners on Focal V3"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679384/+files/lp1779890_focal_v3.debdiff
** Patch removed: "Debdiff
Attached is a debdiff that resolves the issue on Jammy. Version 5.
** Patch added: "Debdiff for tracker-miners on Jammy v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725475/+files/lp1779890_jammy_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on Focal. Version 5.
** Patch added: "Debdiff for tracker-miners on Focal v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725476/+files/lp1779890_focal_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on lunar. Version 5.
** Patch added: "Debdiff for tracker-miners on Lunar v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725474/+files/lp1779890_lunar_v5.debdiff
--
You received this bug notification
Attached is a debdiff that resolves the issue on mantic. Version 5.
** Patch added: "Debdiff for tracker-miners on Mantic v5"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5725473/+files/lp1779890_mantic_v5.debdiff
--
You received this bug
Attached is a debdiff that resolves this issue on debian unstable /
noble.
** Patch removed: "Debdiff for tracker-miners on Focal V3"
https://bugs.launchpad.net/ubuntu/noble/+source/tracker-miners/+bug/1779890/+attachment/5679384/+files/lp1779890_focal_v3.debdiff
** Patch removed: "Debdiff
(justdenis) => Matthew Ruffell (mruffell)
** Changed in: gvfs (Ubuntu Mantic)
Importance: Unknown => Undecided
** Changed in: gvfs (Ubuntu Mantic)
Status: Confirmed => Invalid
** Changed in: gvfs (Ubuntu Noble)
Importance: Unknown => Undecided
** Changed in: gvfs (
(justdenis) => Matthew Ruffell (mruffell)
** Changed in: gvfs (Ubuntu Mantic)
Importance: Unknown => Undecided
** Changed in: gvfs (Ubuntu Mantic)
Status: Confirmed => Invalid
** Changed in: gvfs (Ubuntu Noble)
Importance: Unknown => Undecided
** Changed in: gvfs (
Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
https://gitlab.gnome.org/GNOME/glib/-/issues/3185
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0
Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
https://gitlab.gnome.org/GNOME/glib/-/issues/3185
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Upstream bug: https://gitlab.gnome.org/GNOME/glib/-/issues/3185
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3185
https://gitlab.gnome.org/GNOME/glib/-/issues/3185
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attempting to
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when
** Also affects: glib2.0 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044420
Title:
gtkpod segfaults when attempting to
Hi icaria36,
Your configuration boots to nouveau instead of the nvidia driver when
you boot into -lowlatency. As seen in the below Xserver logs:
...
Nov 17 11:59:24 quiet /usr/libexec/gdm-x-session[4036]: (==) Matched nouveau as
autoconfigured driver 0
...
Nov 17 11:59:24 quiet
Hi Heiko,
I had a look at the changes between 5.15.0-86-generic and
5.15.0-88-generic, and there are the following cifs commits:
ubuntu-jammy $ git log --grep "cifs" --oneline Ub
untu-5.15.0-86.96..Ubuntu-5.15.0-88.98
c92787866aa8 cifs: if deferred close is disabled then close files immediately
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-signed (Ubuntu)
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Tags added: seg
--
You received this bug notification because you are a member of Kernel
Performing verification for Jammy. I checked out the
Ubuntu-5.15.0-90.100 git tag from the source repository on an arm64
system, and made sure that pahole was removed. I completed a build and
looked at the build log, and there were no more pahole warnings.
Marking verified for jammy.
** Tags
Hi everyone,
This is a wayland related bug, and a known issue upstream:
https://bugs.launchpad.net/mixxx/+bug/1850729
https://github.com/mixxxdj/mixxx/issues/9787
It seems the waveform code is incompatible with the QtWayland platform
plugin change, which is mentioned on their troubleshooting
Hi everyone,
This is a wayland related bug, and a known issue upstream:
https://bugs.launchpad.net/mixxx/+bug/1850729
https://github.com/mixxxdj/mixxx/issues/9787
It seems the waveform code is incompatible with the QtWayland platform
plugin change, which is mentioned on their troubleshooting
Performing verification for Jammy. David Thompson has tested the Ubuntu-
bluefield-5.15.0-1029.31 git tag on a arm64 system, and built a kernel
successfully, with no more pahole warnings occurring.
Marking verified for linux-bluefield.
** Tags removed: verification-needed-jammy-linux-bluefield
Hi Ray,
I can see the difference:
diff --git a/dmesg_working.log b/dmesg_broken.log
index 79e34be..de76884 100644
--- a/dmesg_working.log
+++ b/dmesg_broken.log
@@ -59,7 +59,7 @@ reserve setup_data: [mem
0xfee0-0xfee00fff] reserved
-efi: ACPI=0xba282000 ACPI 2.0=0xba282000
Hi Zoltan,
The bisect route would be standard debian packages. You would just wget
the packages, dpkg -i them, reboot into it, suspend, resume, remove
kernel, and report back with the result. Then I would build you the next
one.
I'll have a closer look through the commits in 5.15.0-78 to
Hi Zoltan,
There is about 1400 commits between 5.15.0-78 (good) and 5.15.0-82
(bad):
$ git log --oneline Ubuntu-5.15.0-78.85..Ubuntu-5.15.0-82.91 | wc -l
1379
Are you interested in helping us with a kernel bisect? I would build you
kernels halfway between each good and bad kernel until we land
Hi Ray,
Your dmesg log shows 16gb of usable memory.
[0.159452] Memory: 16117124K/16648596K available (20480K kernel
code, 4152K rwdata, 12720K rodata, 4764K init, 17540K bss, 531212K
reserved, 0K cma-reserved)
Could you please wait until you happen to get a boot where you get less
memory
** Description changed:
[Impact]
This is a long running bug plaguing cloud-images, where on a rare
occasion resize2fs would fail and the image would not resize to fit the
entire disk.
Online resizes would fail due to a superblock checksum mismatch, where
the superblock in memory
** Description changed:
[Impact]
This is a long running bug plaguing cloud-images, where on a rare
occasion resize2fs would fail and the image would not resize to fit the
entire disk.
Online resizes would fail due to a superblock checksum mismatch, where
the superblock in memory
@juliank I'm just doing a little bit more testing for the moment, as I
really want to make sure this isn't going to cause any issues in the
cloud images. It would be nice to have this bug fixed though, I have
seen a few cases related to it over the years.
I'll ask my SEG colleagues for help with
** Summary changed:
- superblock checksum mismatch in resize2fs
+ Resizing cloud-images occasionally fails due to superblock checksum mismatch
in resize2fs
** Description changed:
- Hi,
- We run ext4 on EBS volumes on EC2. During provisioning, cloud-init will
occasionally report that
Attached is a debdiff for e2fsprogs on trusty which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on trusty"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707900/+files/lp2036467_trusty.debdiff
--
You received this bug notification because you are
Attached is a debdiff for e2fsprogs on xenial which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on xenial"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707899/+files/lp2036467_xenial.debdiff
--
You received this bug notification because you are
Attached is a debdiff for e2fsprogs on bionic which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on bionic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707898/+files/lp2036467_bionic.debdiff
--
You received this bug notification because you are
Attached is a debdiff for e2fsprogs on focal which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on focal"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707896/+files/lp2036467_focal.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for e2fsprogs on jammy which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on jammy"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707895/+files/lp2036467_jammy.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for e2fsprogs on lunar which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on lunar"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707894/+files/lp2036467_lunar.debdiff
--
You received this bug notification because you are a
Attached is a debdiff for e2fsprogs on mantic which fixes this issue.
** Patch added: "Debdiff for e2fsprogs on mantic"
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2036467/+attachment/5707893/+files/lp2036467_mantic.debdiff
--
You received this bug notification because you are
n: e2fsprogs (Ubuntu Mantic)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: e2fsprogs (Ubuntu Lunar)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: e2fsprogs (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
**
Patches have been submitted to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-September/144570.html
https://lists.ubuntu.com/archives/kernel-team/2023-September/144571.html
--
You received this bug notification because you are a member of Kernel
Packages, which
luefield (Ubuntu Jammy)
Status: Triaged => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Matthew Ruffel
On Wed, 27 Sept 2023 at 06:11, John Chittum wrote:
>
> Could we add "Keeping the last run"
Yes please! Can we add keeping the last successful run, as well as the
last current run? If the current run fails, its nice to be able to
compare to a previous successful run.
>
> That way you delete, but
Hi Daniel,
The two CVEs you mention, CVE-2023-27522 and CVE-2023-25690, have already
been
addressed in Ubuntu, and have been since March.
https://ubuntu.com/security/CVE-2023-27522
https://ubuntu.com/security/CVE-2023-25690
For 22.04, these were both fixed in apache2 2.4.52-1ubuntu4.4:
** Also affects: gvfs (Ubuntu Mantic)
Importance: Unknown
Status: New
** Also affects: tracker-miners (Ubuntu Mantic)
Importance: High
Assignee: Denison Barbosa (justdenis)
Status: Fix Released
--
You received this bug notification because you are a member of Ubuntu
Hi everyone,
The term "regression" is a slight overstatement for Kinetic, as login
fails with the version in -updates as well, due to it not supporting the
"-" in the domain name.
With 0.9.2 in kinetic -updates:
ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from
server:
t this bug.
> What is the priority for this customer, any deadline?
>
> Thanks.
>
> JB
>
> On Mon, Jul 3, 2023 at 9:03 AM Matthew Ruffell
> wrote:
>>
>> Hi,
>>
>> I know discussions are still ongoing about the adsys 0.12.0 SRU, but I
>> have
Hi,
I know discussions are still ongoing about the adsys 0.12.0 SRU, but I
have a user who wishes to have LP #2020834 [1] fixed, which high
priority.
[1] https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/2020834
Would it be possible to potentially reject 0.12.0 from jammy
-unapproved, we get
** Description changed:
[Impact]
It is common that domain names contain the '-' character, as in "test-
example.com", and adsys versions 0.9.2 and below cannot parse these
correctly, leading to the error:
ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from
** Description changed:
BugLink: https://bugs.launchpad.net/bugs/2023955
[Impact]
Due to fips for jammy not being available yet, users with requirements
to be fips certified or fips compliant have to use focal, and many are
finding certain hardware devices do not work on their
Attached is a v4 for Jammy that updates the version to ubuntu0.1 in both
d/changelog and d/tracker-extract.postinst
** Patch added: "Debdiff for tracker-miners on Jammy V4"
Attached is a v4 for Jammy that updates the version to ubuntu0.1 in both
d/changelog and d/tracker-extract.postinst
** Patch added: "Debdiff for tracker-miners on Jammy V4"
: Medium
Assignee: Matthew Ruffell (mruffell)
Status: In Progress
** Tags: sts
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Focal)
Status:
Attached is a V3 debdiff for Mantic that fixes this issue
** Patch added: "Debdiff for tracker-miners on Mantic V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679388/+files/lp1779890_mantic_v3.debdiff
--
You received this bug notification because you
Attached is a V3 debdiff for Lunar that fixes this issue
** Patch added: "Debdiff for tracker-miners on Lunar V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679387/+files/lp1779890_lunar_v3.debdiff
--
You received this bug notification because you are
Attached is a V3 debdiff for Mantic that fixes this issue
** Patch added: "Debdiff for tracker-miners on Mantic V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679388/+files/lp1779890_mantic_v3.debdiff
--
You received this bug notification because you
Attached is a V3 debdiff for Kinetic that fixes this issue
** Patch added: "Debdiff for tracker-miners on Kinetic V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679386/+files/lp1779890_kinetic_v3.debdiff
--
You received this bug notification because
Attached is a V3 debdiff for Lunar that fixes this issue
** Patch added: "Debdiff for tracker-miners on Lunar V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679387/+files/lp1779890_lunar_v3.debdiff
--
You received this bug notification because you are
Attached is a V3 debdiff for Jammy that fixes this issue
** Patch added: "Debdiff for tracker-miners on Jammy V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679385/+files/lp1779890_jammy_v3.debdiff
--
You received this bug notification because you are
Attached is a V3 debdiff for Kinetic that fixes this issue
** Patch added: "Debdiff for tracker-miners on Kinetic V3"
https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1779890/+attachment/5679386/+files/lp1779890_kinetic_v3.debdiff
--
You received this bug notification because
101 - 200 of 2037 matches
Mail list logo
