linux-image-6.5.0-1027-oem is still broken.
However linux-generic-hwe-22.04 6.8.0-40.40~22.04.3 (from proposed)
seems to work.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/206935
kernel 118 - the problem is not fixed !!!
I hope 119 fix this this long time problem!
Please understand: when this problems longer time exists, then linux
(ejemplo Mint) are not better as Windows !!! So you go backwards! This
cant been!
I can only use the kernal 106/107 on 3 machines with all di
Hello Frank, or anyone else affected,
Accepted glibc into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.39-0ubuntu8.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
Hello Frank, or anyone else affected,
Accepted glibc into noble-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/glibc/2.39-0ubuntu8.3
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.u
** Changed in: linux
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978133
Title:
System freeze followed by kernel panic or blank screen
Statu
Same issue here.
Ubuntu 24.04 6.8.0-40-generic
Hardware info: https://linux-hardware.org/?probe=968548e225
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2059738
Title:
Kernel 6.8 - Shu
Same here on Lenovo Ideapad Pro 5 with Core Ultra 9 185H CPU.
Tested on 6.8, 6.10 and 6.11-RC1 kernel image.
...
[ 26.776070] RIP: 0010:print_ddi_port+0x3cc/0x460 [i915]
...
[ 26.776202] Call Trace:
[ 26.776204]
[ 26.776205] ? show_regs+0x6c/0x80
[ 26.776211] ? __warn+0x88/0x140
[ 2
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076428
Title:
Enable CONFIG_EXFAT_FS in s390x too
St
the failing autopkg tests are now down to two packages:
- software-properties (all architectures)
this is unrelated to the dpkg upload, it also fails for
all other packages triggering this test in -proposed.
- libxmlada (armhf)
This is expected, needs updates for the 64bit time_t chang
the failing autopkg tests are now down to two packages:
- software-properties (all architectures)
this is unrelated to the dpkg upload, it also fails for
all other packages triggering this test in -proposed.
- libxmlada (armhf)
This is expected, needs updates for the 64bit time_t chang
** Changed in: linux (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832782
Title:
Backport VMW_PVRDMA PPN64 patch
Status in linux package in
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-40.40.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verifica
@ Detlef Bracker:
I understand your frustration.
But, it should be acknowledged that the developers' have promptly responded and
committed the appropriate changes in a reasonable amount of time.
Kernel version 5.15.0-119 should fix the issue and be available in the official
repositories (presuma
@Detlef:
There are a number of workarounds to address this problem while waiting for the
long-term fix in the -119 kernel.
You can change your grub configuration to either boot an older kernel by
default, or to add randomize_kstack_offset=off to the kernel command line (see
comment #85).
Alterna
I tested the linux-image-6.8.0-40-generic kernel on Ubuntu noble.
It fixed the bcache errors, but graphics were unusable, I had to revert
to linux-image-6.8.0-39-generic to get GDM on Wayland working (I haven't
tested GDM on Xorg).
--
You received this bug notification because you are a member o
focal:linux-bluefield kernel has CONFIG_SOUND set to 'n' so this bug
doesn't affect it.
** Tags removed: verification-needed-focal-linux-bluefield
** Tags added: verification-done-focal-linux-bluefield
--
You received this bug notification because you are a member of Kernel
Packages, which is su
This bug is awaiting verification that the linux/5.15.0-121.131 kernel
in -proposed solves the problem. Please test the kernel and update this
bug with the results. If the problem is solved, change the tag
'verification-needed-jammy-linux' to 'verification-done-jammy-linux'. If
the problem still ex
Just tried the 6.8.0-40-generic kernel and it seems to be fixed
(installed automatically via sudo apt upgrade).
Not sure if the other display-related issues are fixed though, such as
the one mentioned here: https://bugs.launchpad.net/ubuntu/+source/linux-
oem-6.5/+bug/2070096
We saw the above iss
Public bug reported:
It was disabled by mistake due to a missing dependency.
Commit "ubsan: Restore dependency on ARCH_HAS_UBSAN" was applied without
"ubsan: Remove CONFIG_UBSAN_SANITIZE_ALL", resulting in CONFIG_UBSAN being
dependant on a config option that does not exist.
Fix this by cherry-p
I can see this now builds correctly for riscv64, and I was able to
install it on a local VM. Basic testing looks good, so I'm marking this
one as verified.
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages,
*** This bug is a duplicate of bug 2066126 ***
https://bugs.launchpad.net/bugs/2066126
** This bug has been marked a duplicate of bug 2066126
[nvidia] Whole screen pans with cursor movement
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
** Description changed:
[Impact]
The 6.8 HWE kernel requires firmware that is not (yet) provided by
linux-firmware in Jammy. This obviously results in non-functional HW
components.
[Fix]
- Add missing firmware blobs.
+ Add missing firmware blobs and links.
[Test Case]
-
** Description changed:
[Impact]
The 6.8 HWE kernel requires firmware that is not (yet) provided by
linux-firmware in Jammy. This obviously results in non-functional HW
components.
[Fix]
Add missing firmware blobs and links.
[Test Case]
- Ideally: Verify that the 6.8 k
This bug is awaiting verification that the linux-
hwe-6.8/6.8.0-41.41~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.8' to 'verification-done-jammy-linux-hw
** Changed in: linux-firmware (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2073525
Title:
[SRU]QAT: Add 402xx (CPM2.0c) firmware fo
I logged in with 'Ubuntu on Xorg' selected. There is no artefact when
locking/unlocking the screen, or when changing refresh rates. The list
of refresh rates is shorter, containing only 59.88, 100, 110, & 120Hz;
seemingly in agreement with the edid data.
--
You received this bug notification beca
** Changed in: linux-gke (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gke in Ubuntu.
https://bugs.launchpad.net/bugs/2076439
Title:
Compile NVMe module as built-in on a
You have been subscribed to a public bug:
### System information
Type | Version/Name
--- | ---
Distribution Name | Ubuntu
Distribution Version| 24.04
Kernel Version | 6.8.0-39-generic
Architecture| amd64
OpenZFS Version | zfs-2.2.2-0ubuntu9
### Describe the problem you're observin
** Package changed: ubuntu => zfs-linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076663
Title:
No way to access snapshots within the .zfs/snapshot virtual folder
fr
I can reproduce this on Fedora 40, which likely indicates that it's an
upstream bug.
Workaround: disable c-states in BIOS.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1978133
Title:
** No longer affects: linux-firmware (Ubuntu)
** No longer affects: linux-firmware (Ubuntu Oracular)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2073924
Title:
[SRU][HPE 24.
Ian
My apologies, I conflated this with another bug and I am sorting this
out now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076675
Title:
[SRU][HPE 24.04] Intel FVL NIC FW flash
Public bug reported:
[Impact]
Description of problem:
Within 24.04 an intel FVL Idea adapter flash fails through a FW smart
component RPM install. The flash successfully completes on the
firmware(NVM) and fails on the firmware(ROM). The process takes roughly
thirty minutes and still fails.
Follo
All autopkgtests for the newly accepted linux-meta (5.15.0.121.121) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
apparmor-profiles-extra/unknown (s390x)
diffoscope/205 (amd64, arm64, armhf, ppc64el, s390x)
evdi/unknown (s390x)
fw
This bug was fixed in the package linux-raspi - 6.8.0-1009.10
---
linux-raspi (6.8.0-1009.10) noble; urgency=medium
* noble/linux-raspi: 6.8.0-1009.10 -proposed tracker (LP: #2072191)
* BTF support missing from kernel (LP: #2065829)
- [Config] raspi: Set DEBUG_INFO_BTF=y
[
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-nvidia-tegra-igx
--
You received this bug notification because you are a member of Kernel
Packag
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-nvidia-tegra-igx
--
You received this bug notification because you are a member of Kernel
Packag
Doesn't affect nvidia-tegra kernel use cases
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-nvidia-tegra-igx
--
You received this bug notifica
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-nvidia-tegra-igx
--
You received this bug notification because you are a member of Kernel
Packag
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-nvidia-tegra-igx
--
You received this bug notification because you are a member of Kernel
Packag
Doesn't affect tegra kernels
** Tags removed: verification-needed-jammy-linux-nvidia-tegra
verification-needed-jammy-linux-nvidia-tegra-igx
** Tags added: verification-done-jammy-linux-nvidia-tegra
verification-done-jammy-linux-nvidia-tegra-igx
--
You received this bug notification because you
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076576
** Changed in: autopkgtest (Debian)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2056461
Title:
autopkgtest-virt-qemu on noble images somet
Possibly related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076576
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076483
Title:
Failure to Suspend after Upgrade to Kernel 5.
Possibly related:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076483
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076576
Title:
5.15.0-118: NFS causes suspend to fail
Statu
You have been subscribed to a public bug:
I have a Lenovo Slim 7 ProX 14ARH7 (not the Yoga one).
The touchscreen works after turning it on or rebooting but not after
sleeping.
I made a reddit thread asking for a solution and we solved the issue by
reloading the hid-multitouch driver after wake u
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076681
Title:
Touchscreen doesn't work after suspending laptop
Status in linux package in Ub
OK it sounds like Mutter is calculating an incorrect display timing.
I'm surprised the list of refresh rates is shorter because historically
Xorg has had more.
** No longer affects: linux (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
--
You received this bug notifica
@Theis, do you have time for testing the kernel in comment #19?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2073676
Title:
after update of kernel HDMI audio is not working
Status in
Test Update:
1. Latest 24.04 just show the two messages in a separately dark screen, not in
UEFI rendered any more.
2. 24.10 is on going, after verifying it, update our test results here.
Thanks,
--Xavier
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
SRU verification for oem-6.11-noble:
[Impact]
There are two issues with Realtek RTL8851BE/RTL8852BE:
Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working due
to the firmware download fail
Issue 2: With RTL8851BE and "Control WLAN radio" (in BIOS setti
[Expired for firmware-sof (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: firmware-sof (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to firmware-sof in Ubuntu.
https://
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
Setting up linux-image-6.8.0-40-generic (6.8.0-40.40) ...
Segmentation fault (core dumped)
dpkg: error processing package linux-image-6.8.0-40-generic (--configure):
installed linux-image-6.8.0-40-generic package post-installation script
subprocess returned error exit status 139
--
You received
[12497.285105] DOM Worker[20504]: segfault at 45fb740 ip 7f9b32d72115
sp 7f9b213fe090 error 4 in libxul.so[7f9b326a5000+57c5000] likely on CPU 6
(core 2, socket 0)
[12497.285122] Code: 86 ee fa ff ff 4c 89 64 24 28 49 8b 02 48 8b 40 18 48 8d
0d 8d ed ff ff 48 39 c8 0f 85 a9 09 00 00
You have been subscribed to a public bug:
SRU verification for oem-6.11-noble:
[Impact]
There are two issues with Realtek RTL8851BE/RTL8852BE:
Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working due
to the firmware download fail
Issue 2: With RTL8851BE and "Control WLAN
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
*** This bug is a duplicate of bug 2068107 ***
https://bugs.launchpad.net/bugs/2068107
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2068107, so it is being marked as such. Please look
** Package changed: linux-oem-6.11 (Ubuntu) => linux-hwe-6.8 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2076861
Title:
rtw89: Support hardware rfkill and reset IDMEM
Check the *.sources files in /etc/apt/sources.list.d/ for any that are
disabled and re-enable them if you want them back.
$ grep '^Enabled' /etc/apt/sources.list.d/*.sources
Also check any *.list.distUpgrade files in the same directory that you
might want to reenable.
In any case, this is not a
You have been subscribed to a public bug:
I installed it the first time, while it was still in the development edition.
After the April release the system often had boot issues, the first boot failed
and the second boot succeeded. Two weeks ago all boots failed except the boots
in the alternat
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => En-Wei Wu (rickywu)
--
You received this bug notification because you are a member of Kernel
P
Sounds like a bug in the guest driver (vmwgfx) in that case. Although
some quick googling for:
"vmwgfx seems to be running on an unsupported hypervisor"
reveals it can be storage related too. I guess because the hypervisor
uses similar mechanisms for sharing storage as it does for communicating
** Description changed:
SRU verification for oem-6.11-noble:
[Impact]
There are two issues with Realtek RTL8851BE/RTL8852BE:
Issue 1: After reboot from UEFI HTTPs boot, RTL8851BE wifi were not working
due to the firmware download fail
Issue 2: With RTL8851BE and "Control WLAN radi
** Changed in: libcamera (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2037642
Title:
[FFe] Raspberry Pi 5 support
Status in Release
83 matches
Mail list logo
