This bug is awaiting verification that the linux-nvidia-
tegra/6.8.0-1001.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-noble-linux-nvidia-tegra' to
'verification-done-noble-linux-
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-38.38.1~22.04.2 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-oracle/6.8.0-1006.6
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-noble-linux-oracle' to 'verification-done-
noble-linux-oracle'. If
This bug is awaiting verification that the linux-
lowlatency/6.8.0-35.35.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-noble-linux-lowlatency' to
'verification-done-noble-linux-low
This bug is awaiting verification that the linux-ibm/6.8.0-1006.6 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-noble-linux-ibm' to 'verification-done-noble-linux-
ibm'. If the probl
This bug is awaiting verification that the linux-raspi-
realtime/6.8.0-2004.4 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-noble-linux-raspi-realtime'
to 'verification-done-noble-li
This bug is awaiting verification that the linux-gcp/6.8.0-1008.9 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-noble-linux-gcp' to 'verification-done-noble-linux-
gcp'. If the probl
This bug is awaiting verification that the linux-aws/6.8.0-1009.9 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-noble-linux-aws' to 'verification-done-noble-linux-
aws'. If the probl
This bug is awaiting verification that the linux-gke/6.8.0-1004.7 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-noble-linux-gke' to 'verification-done-noble-linux-
gke'. If the probl
This bug is awaiting verification that the linux-azure/6.8.0-1008.8
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-noble-linux-azure' to 'verification-done-noble-
linux-azure'. If the
This bug is awaiting verification that the linux-riscv/6.8.0-35.35.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-noble-linux-riscv' to 'verification-done-noble-
linux-riscv'. If th
This bug is awaiting verification that the linux-
nvidia-6.8/6.8.0-1006.6~22.04.2 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-
nvidia-6.8' to 'verification-done-jammy-l
This bug was fixed in the package gcc-11 - 11.4.0-9ubuntu1
---
gcc-11 (11.4.0-9ubuntu1) noble; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-11 (11.4.0-9) unstable; urgency=medium
* Update to git 20240412 from the gcc-11 branch.
This bug was fixed in the package gcc-12 - 12.3.0-17ubuntu1
---
gcc-12 (12.3.0-17ubuntu1) noble; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-12 (12.3.0-17) unstable; urgency=medium
* Fix typo in distro_defaults spec.
gcc-12 (12.
marked old toolchain versions as won't fix
** Changed in: gcc-9 (Ubuntu Noble)
Status: Confirmed => Won't Fix
** Changed in: gcc-10 (Ubuntu Noble)
Status: Confirmed => Won't Fix
** Changed in: gcc-11 (Ubuntu Noble)
Status: Confirmed => Won't Fix
** Changed in: llvm-toolchai
This bug was fixed in the package linux - 6.8.0-20.20
---
linux (6.8.0-20.20) noble; urgency=medium
* noble/linux: 6.8.0-20.20 -proposed tracker (LP: #2058221)
* Noble update: v6.8.1 upstream stable release (LP: #2058224)
- x86/mmio: Disable KVM mitigation when X86_FEATURE_CL
This bug was fixed in the package gcc-13 - 13.2.0-21ubuntu1
---
gcc-13 (13.2.0-21ubuntu1) noble; urgency=medium
* Merge with Debian; remaining changes:
- Build from upstream sources.
gcc-13 (13.2.0-21) unstable; urgency=medium
* Update to git 20240324 from the gcc-13 branch.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: llvm-toolchain-15 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: llvm-toolchain-16 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
T
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-12 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Aut
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-9 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Auto
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-11 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Aut
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gcc-10 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Aut
Hello, I see
https://git.launchpad.net/ubuntu/+source/gcc-13/commit/?id=6c5be2a496335c513dbe6fa85df2402cfc0f0a8b
imported the LLVM patch for Asan. There was also a similar change in
LLVM for LSan: https://github.com/llvm/llvm-
project/commit/5ffe955570a5d743bbbae204ce1b132e89fa86dc.
I was wonderin
** No longer affects: gcc-14 (Ubuntu)
** No longer affects: gcc-14 (Ubuntu Noble)
** Changed in: gcc-8 (Ubuntu Noble)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20487
** Changed in: gcc-13 (Ubuntu Noble)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Autopkgtest failures on amd64
To manage notifications about thi
** No longer affects: llvm-toolchain-17 (Ubuntu)
** No longer affects: llvm-toolchain-18 (Ubuntu)
** No longer affects: llvm-toolchain-17 (Ubuntu Noble)
** No longer affects: llvm-toolchain-18 (Ubuntu Noble)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I added llvm and gcc toolchains to the affected packages list here based
on some internet reports, not my own testing:
https://stackoverflow.com/questions/77894856/possible-bug-in-gcc-sanitizers
https://stackoverflow.com/questions/77826203/addresssanitizer-randomly-throws-sigsegv-with-no-explanati
** Also affects: llvm-toolchain-15 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: llvm-toolchain-16 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: llvm-toolchain-17 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: llvm-toolchain-
This issue might also affect 22.04 with the HWE kernel
Going from kernel 6.5.0-21 to 6.5.0-25, we're seeing the same change in
kernel parameters
On a system with kernel 6.5.0-21 I have these kernel parameters set:
vm.mmap_rnd_bits = 28
vm.mmap_rnd_compat_bits = 8
On a system with the new kernel
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: llvm-toolchain-14 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
T
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2048768
Title:
Auto
32 matches
Mail list logo
