Verified that the GAP/CONN/CPUP/BV-05-C could pass on 5.15.0-102.112
kernel using the following procedure:
1. On PTS, switch to the LE-only dongle
2. On the IUT, run bluetoothctl
3. On PTS, start the test case.
4. On the IUT, in the bluetoothctl shell, start scanning by entering "scan on".
5. Whe
--- Comment From david_pa...@uk.ibm.com 2024-03-11 03:51 EDT---
Has there been any further progress on this issue from the Linux NFS
development team ?
The AIX NFS development team will not progress the problem from their
side until they understand why the BAD_SEQID errors has been return
** Changed in: linux (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
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/2056403
Title:
Mantic update: upstream stable patchset 202
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in:
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35
---
linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090)
* Jammy update: v6.1.78 upstream stable release (LP: #2054541)
- ext4: regenerate budd
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35
---
linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090)
* Jammy update: v6.1.78 upstream stable release (LP: #2054541)
- ext4: regenerate budd
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35
---
linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090)
* Jammy update: v6.1.78 upstream stable release (LP: #2054541)
- ext4: regenerate budd
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35
---
linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090)
* Jammy update: v6.1.78 upstream stable release (LP: #2054541)
- ext4: regenerate budd
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35
---
linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090)
* Jammy update: v6.1.78 upstream stable release (LP: #2054541)
- ext4: regenerate budd
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1035.35
---
linux-oem-6.1 (6.1.0-1035.35) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1035.35 -proposed tracker (LP: #2052090)
* Jammy update: v6.1.78 upstream stable release (LP: #2054541)
- ext4: regenerate budd
Public bug reported:
The problem occurs with the 5.15.0-102 kernel but not with 5.15.0-100.
The issue seems to be identical to the problem reported for 6.7.0 here:
https://bbs.archlinux.org/viewtopic.php?id=292203
On the page linked above is says a patch was submitted 2024-01-26 and
the problem
** Summary changed:
- quando uso un dispositivo usb mi si cancella l input del touchpad ho provato
con molti metodi ma niente /when I use a USB device the touchpad input is
canceled I have tried many methods but nothing
+ mi si cancella l input del touchpad ho provato con molti metodi ma niente
Public bug reported:
Ubuntu Release: 24.04 Noble Numbat (development branch)
Package: linux-image-6.8.0-11-generic
Version: 6.8.0-11.11
What was expected:
An image to be displayed on the screen of the laptop free from corruption.
What happened instead:
When booting using the specified kernel, th
** Changed in: ubuntu
Status: New => Invalid
** Package changed: linux (Ubuntu) => linux-raspi (Ubuntu)
** Tags added: kern-9639
--
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/2056
** Attachment added: "dmesg running kernel 6.8.0-11"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056748/+attachment/5754804/+files/dmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launch
** Description changed:
Ubuntu Release: 24.04 Noble Numbat (development branch)
Package: linux-image-6.8.0-11-generic
Version: 6.8.0-11.11
What was expected:
- An image to be displayed on the screen of the laptop free from corruption.
+ An image to be displayed on the integrated screen
Hello again Daniel,
Thank you very again much for your help and again, my apologies for being
unable to reply to your sooner.
I have found recently that my laptop, the Lenovo V145-15AST has stopped
suffering from a flickering screen. I have used the laptop extensively for
normal work and the pro
Ok, running 6.8.
uname -r
6.8.0-060800rc7-generic
--
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/2054121
Title:
Random Freezing
Status in linux package in Ubuntu:
New
Bug descriptio
Public bug reported:
Since booting in 6.5.0-25-generic some kworker thread were stuck. This
problem with iwlwifi was new. Booting back in 6.5.0-21-generic solved
the problem.
This was a suspicious new error:
```
kernel: iwlwifi :3b:00.0: Error sending MCC_UPDATE_CMD: time out after
2000ms.
Note that similar to the older gcc and upstream sanitizer bugs, this
problem may be caused by some kernel API now returning a slightly
different result, so it could be debatable whether the issue should be
fixed in ThreadSanitizer, or in the kernel itself.
--
You received this bug notification be
Public bug reported:
We updated a number of (amd64) machines from linux-
image-6.5.0-21-generic (6.5.0-21.21~22.04.1) to linux-
image-6.5.0-25-generic (6.5.0-25.25~22.04.1), and this caused
ThreadSanitizer-instrumented programs to immediately exit with an error
similar to:
FATAL: ThreadSanitizer:
** Description changed:
Intro:
==
- When hit a kernel warning when using openvswitch kernel module. Digging into
the source code, we found it's due to the code snippet
- if (WARN_ON(i.cmd >= family->resv_start_op &&
-(i.doit.validate || i.dumpit.validate)))
-
One other note, I only get the "unexpected memory mapping" error on
amd64. On arm64 machines with 6.5.0-25.25~22.04.1, ThreadSanitizer works
without issues.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
ht
Yes, it seems so!
--
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/2053041
Title:
Issue when shutting down computer: internal hard drive is not shut
down properly
Status in linux packag
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for
This bug was fixed in the package linux-firmware -
20230919.git3672ccab-0ubuntu2.9
---
linux-firmware (20230919.git3672ccab-0ubuntu2.9) mantic; urgency=medium
* Update firmware for MT7921 in order to fix Framework 13 AMD 7040 (LP:
#2049220)
- linux-firmware: update firmware for
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privile
even though this wasn't able to get verified with the mantic kernel,
I've gone ahead and released it as the update should not break anything
--
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.ne
marking the kernel task as fixed since noble has 6.8 now.
** Changed in: linux (Ubuntu Noble)
Status: New => Fix Released
--
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/2049
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Mantic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmw
This bug is awaiting verification that the linux/5.4.0-175.195 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still exi
This bug is awaiting verification that the linux/5.4.0-175.195 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still exi
This bug is awaiting verification that the linux/5.4.0-175.195 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-focal-linux' to 'verification-done-focal-linux'. If
the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
This bug is awaiting verification that the linux/6.5.0-27.28 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-mantic-linux' to 'verification-done-mantic-linux'.
If the problem still exi
--- Comment From jldo...@us.ibm.com 2024-03-11 14:00 EDT---
Thank you Frank for providing a test kernel! I have installed the test kernel
and everything appears to be working smoothly.
---
root@neop91:/home/neo# mkvterm --id 2
vterm for partition 2 is active. Press Control+] to exit.
IBM
You might want to try passing the various i8042 controller module linux
parameters (i8042.nomux=1, i8042.kbdreset=1, i8042.reset=1) and also
i8042.nopnp as told by your dmesg:
[ 0.602905] i8042: PNP: PS/2 appears to have AUX port disabled, if this
is incorrect please boot with i8042.nopnp
note t
@Rafael.lopez,
Many apologies, I did not see this reply. I will test immediately and
let you know.
Thanks for doing this!
~Noah
--
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/2016040
T
@rafael.lopez,
Sorry, hopefully last thing: can you actually back port this to 6.5? I
should be able to test that on another system
--
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/2016
@rafael.lopez,
Turns out I cannot test this. They system I have is Debian 11.9 and
dpkg doesn't support zstd :(
--
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/2016040
Title:
Creating b
You have been subscribed to a public bug:
After the latest update my Wifi is facing problems in turning on and
off. If i try to turn in off from setting Linux hangs and doesnt respond
so i have to force shutdown.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1
** Package changed: ubuntu-release-upgrader (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/2056784
Title:
I am facing this problem since last update
Status in
Public bug reported:
Hi, I purchased this adapter: https://www.amazon.co.uk/Maxuni-Bluetooth-
Computer-Receiver-Keyboard/dp/B0BQ3964FP
It doesn't currently work on Linux due to a firmware bug.
The fixes are documented on the web:
https://www.linuxcompatible.org/story/xanmod-linux-kernel-618-rel
You have been subscribed to a public bug:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent across reboots.
It does not manifest on 6.5.0-21, neither on 5.15.0-100.
Another peculiarity is that right clicking on the right
Public bug reported:
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
Kernel info: Linux gman-Laptop-13-AMD-Ryzen-7040Series 6.8.0-11-generic
#11-Ubuntu SMP PREEMPT_DYNAMIC Wed Feb 14 00:29:05 UTC 2024 x86_64
x86_64 x86_64 GNU/Linux
Hardware: AMD Framework 13
Expec
Public bug reported:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent across reboots.
It does not manifest on 6.5.0-21, neither on 5.15.0-100.
Another peculiarity is that right clicking on the right side and lower
side
** Attachment added: "Screenshot from 2024-03-11 21-29-22 6.5.0-25.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754916/+files/Screenshot%20from%202024-03-11%2021-29-22%206.5.0-25.png
--
You received this bug notification because you are a member of Kernel
Pac
** Attachment added: "Right-click 6.5.0-25.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754919/+files/Right-click%206.5.0-25.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https:/
** Attachment added: "Screenshot from 2024-03-11 21-24-02 6.5.0-21.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754917/+files/Screenshot%20from%202024-03-11%2021-24-02%206.5.0-21.png
--
You received this bug notification because you are a member of Kernel
Pac
** Attachment added: "Screenshot from 2024-03-11 21-41-30 5.15.0-100.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2056804/+attachment/5754918/+files/Screenshot%20from%202024-03-11%2021-41-30%205.15.0-100.png
--
You received this bug notification because you are a member of Kernel
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754934/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754935/+files/IwConfig.txt
--
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/20
apport information
** Tags added: apport-collected jammy
** Description changed:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent across reboots.
It does not manifest on 6.5.0-21, neither on 5.15.0-100.
Anot
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754938/+files/Lsusb.txt
--
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/2056804
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754937/+files/Lspci-vt.txt
--
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/20
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754936/+files/Lspci.txt
--
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/2056804
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754940/+files/Lsusb-v.txt
--
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/2056
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754941/+files/PaInfo.txt
--
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/2056804
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754939/+files/Lsusb-t.txt
--
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/2056
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754943/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754942/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754944/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754947/+files/PulseList.txt
--
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/
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754946/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754945/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754950/+files/acpidump.txt
** Description changed:
After updating to 6.5.0-25, I am experiencing a very peculiar form of
screen corruption. It has been persistent and consistent ac
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754949/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2056804/+attachment/5754948/+files/UdevDb.txt
--
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/2056804
This bug was fixed in the package linux-nvidia-tegra-igx-modules -
5.15.0-1009.9
---
linux-nvidia-tegra-igx-modules (5.15.0-1009.9) jammy; urgency=medium
* Master version: 5.15.0-1009.9
* Add headers package for IGX out-of-tree modules (LP: #2054483)
- [Packaging] Add out-of-
This bug was fixed in the package linux-nvidia-tegra-igx-modules-signed
- 5.15.0-1009.9
---
linux-nvidia-tegra-igx-modules-signed (5.15.0-1009.9) jammy; urgency=medium
* Master version: 5.15.0-1009.9
* Add headers package for IGX out-of-tree modules (LP: #2054483)
- [Packagin
This bug was fixed in the package linux-nvidia-tegra-igx - 5.15.0-1009.9
---
linux-nvidia-tegra-igx (5.15.0-1009.9) jammy; urgency=medium
* jammy/linux-nvidia-tegra-igx: 5.15.0-1009.9 -proposed tracker (LP:
#2054476)
[ Ubuntu: 5.15.0-1022.22 ]
* jammy/linux-nvidia-tegra: 5.15.
This bug was fixed in the package linux-nvidia-tegra - 5.15.0-1022.22
---
linux-nvidia-tegra (5.15.0-1022.22) jammy; urgency=medium
* jammy/linux-nvidia-tegra: 5.15.0-1022.22 -proposed tracker (LP:
#2053284)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update f
** Changed in: linux-nvidia-tegra-igx (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu.
https://bugs.launchpad.net/bugs/2054483
Title:
Add headers pac
Public bug reported:
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* ring gfx timeout, signaled seq=211055, emitted seq=211057
Mar 11 18:30:07 garrett-desktop kernel: [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* Process information: process armcord pid 14844 thre
** Attachment added: "look_at_this_journalctl_from_previous_boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2057155/+attachment/5754997/+files/look_at_this_journalctl_from_previous_boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which
Here is another post, it's a unresolved issue
https://bbs.archlinux.org/viewtopic.php?id=280693&p=2
--
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/2056800
Title:
Bluetooth adapt
All autopkgtests for the newly accepted linux-meta (6.5.0.27.27) for mantic
have finished running.
The following regressions have been reported in tests triggered by the package:
apparmor/4.0.0~alpha2-0ubuntu5 (arm64, armhf, ppc64el, s390x)
casper/1.486 (amd64)
Please visit the excuses page lis
I think the fix was included in 5.15.149 upstream;
https://lwn.net/Articles/963359/
Input: atkbd - skip ATKBD_CMD_SETLEDS when skipping ATKBD_CMD_GETID
The kernel team have just pulled in 5.15.148, and haven't started on
149. They will likely get to it in the next week or so.
Thanks,
Matthew
-
It seems there was an update to 'linux-hwe-6.5' a couple of days ago so
we were likely already tracking the correct component.
** Changed in: linux-hwe-6.5 (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Quoted from AMD proposed fix in https://lore.kernel.org/amd-
gfx/46657fa4-630e-47a5-a339-242ecd5ba...@amd.com/T/#m94e3b7d292e359f3d656babe3ccdbf7fc6daab6f
> The monitor shipped with the Framework 16 supports VRR [1], but it's not
> being advertised.
>
> This is because the de
The proposed v1 patch still has review comments to be addressed. Stay
tuned.
** Changed in: linux (Ubuntu Noble)
Status: New => 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/
Public bug reported:
[Impact]
The screen brightness is unable to adjust on BOE panel DPN#R6FD8
[Fix]
AMD provides a patch which is included in v6.8-rc7 to fix this issue
b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP
To avoid conflicts, pull in another panel quirk
3d71a8726e05
** Description changed:
[Impact]
The screen brightness is unable to adjust on BOE panel DPN#R6FD8
[Fix]
AMD provides a patch which is included in v6.8-rc7 to fix this issue
b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP
+
+ To avoid conflicts, pull in another panel
** Description changed:
[Impact]
The screen brightness is unable to adjust on BOE panel DPN#R6FD8
[Fix]
AMD provides a patch which is included in v6.8-rc7 to fix this issue
b7cdccc6a849 drm/amd/display: Add monitor patch for specific eDP
- To avoid conflicts, pull in another panel
1 - 100 of 104 matches
Mail list logo
