The issue is apparently with the displaylink-driver and evdi packages
provided by Synaptics. Judging by make.log the errors were occurring
because the evdi dkms module failed to compile, so I tried running sudo
apt remove evdi and then sudo apt install evdi-dkms, which is provided
by the noble repo
** Description changed:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originat
The fix for the Mantic kernel has already been released with linux 6.5.0-14.14:
https://launchpad.net/ubuntu/+source/linux/6.5.0-14.14
This version was promoted to -updates/-security on 2023-12-05, therefore
the bug should have been marked automatically as "Fix Released".
Assuming this was an issu
Ran AppArmor tests from the QA Regression Tests [1] and POSIX mqueue
tests from the AppArmor test suite and they all passed as expected.
georgia@sec-jammy-amd64:~/apparmor-3.0.4/tests/regression/apparmor$ uname -a
Linux sec-jammy-amd64 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC
2024
** Changed in: linux (Ubuntu Noble)
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/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.1
** Changed in: linux (Ubuntu Noble)
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/2042853
Title:
[UBUNTU 23.04] Kernel config option missing
Thx for the hint, klebers - I missed that.
With that I can also set the project entry to Fix Released and close this bug.
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Changed in: linux (Ubuntu)
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/2038587
Title:
Turning COMPAT_32BIT_TIME off on ppc64el
Status i
** Changed in: ubuntu-z-systems
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/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do
** Changed in: ubuntu-z-systems
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/2042853
Title:
[UBUNTU 23.04] Kernel config option missing for
** Changed in: ubuntu-power-systems
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/2038587
Title:
Turning COMPAT_32BIT_TIME off on ppc64el
St
Public bug reported:
Long story short there is a regression that affects the datapath of Open
vSwitch based systems starting with the 6.2 kernel which is fixed by
[0].
0:
https://patchwork.ozlabs.org/project/openvswitch/patch/20231221224311.130319-1-b...@faucet.nz/
** Affects: linux (Ubuntu)
It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)
After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.
--
You received this bug notification because you are a member of Ker
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Within stress reboot tests, iwlwifi may fail to load firmware, triggers
retries,
+ and finally makes wifi operative.
+
+ iwlwifi :05:00.0: Loaded firmware version: 83.d24e06ed.0
gl-c0-fm-c0-83.ucode
+ iwlwifi :05:00.0:
** Description changed:
Situation:
OS: Xubuntu 22.04.3
Kernel version: 6.2.0-39-generic
Network driver: r8169
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI
Express Gigabit Ethernet Controller (rev 01)
NAS model: Synology DiskStation DS223
The probl
It seems to be fixed in the new kernal 6.5.0-14-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/2046434
Title:
TPM2 Problem in 6.2.0 kernel
Status in linux package in Ubuntu:
Public bug reported:
[ Impact ]
* Ubuntu builds regular kernels without FIPS configuration enabled at compile
time
* Canonical also builds FIPS kernels with FIPS configuration enabled at
compile time, intended to only be used in FIPS mode
* Currently, due to upstream patches, this thus requi
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148054.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148056.html (lunar)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148057.html
(mantic)
* https://lists.ubuntu.com/archives/kernel-team/2
Hello, got the same issue with Ubuntu 22.04.3 LTS (GNU/Linux
5.15.0-91-generic x86_64). Also tried 5.19 kernel and got the same
problem.
Jan 7 02:28:26 cache4 systemd[1]: Starting MD array scrubbing...
Jan 7 02:28:26 cache4 root: mdcheck start checking /dev/md0
Jan 7 08:28:44 cache4 kernel: [29
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2049027
Title:
The display becomes frozen after some time when a HDMI device is
connected.
Status in
** Summary changed:
- virtualbox-dkms.0.crash VirtualBox DMKS module NOT working
+ virtualbox-dkms.0.crash VirtualBox DKMS module NOT working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bugs.lau
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Noble)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux-firmware (Ubuntu Noble)
Importance:
Public bug reported:
Upgraded using sudo apt upgrade
Description:Ubuntu 22.04.3 LTS
Release:22.04
system fails to boot - blank screen - no activity
recovery mode coaxed system to startup but error happens with nvidia
drivers
system has two monitors, one works (DVI) the second (VGA
** Summary changed:
- Add MT7925 WiFi/BT support
+ Support Mediatek MT7925 WiFi/BT
--
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/2043542
Title:
Support Mediatek MT7925 WiFi/BT
So far Wifi kernel driver will be ready since v6.7-rc1 (with fixes from
-rc7), and Bluetooth since v6.6. While linux/noble is currently at v6.6,
mark it as confirmed at this moment.
** Changed in: linux (Ubuntu Noble)
Status: New => Confirmed
** Changed in: linux-oem-6.5 (Ubuntu Jammy)
Three more fixes available in v6.7-rc4 and -rc7:
* cd607f2cbbbec wifi: mt76: fix crash with WED rx support enabled
* 695bfba7ca781 wifi: mt76: mt7925: fix typo in mt7925_init_he_caps
* 7a934b5cc3f45 wifi: mt76: mt7921: fix 6GHz disabled by the missing default
CLC config
** Also affects: linux (Ub
linux-firmware SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148065.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148066.html (noble)
** Description changed:
+ [linux-firmware SRU Justification]
+
+ [Impact]
+
+ Missing firmware for Mediatek MT792
** Description changed:
+ [Problem]
+
When running an SVA case, the following soft lockup is triggered:
-
- watchdog: BUG: soft lockup - CPU#244 stuck for 26s!
- pstate: 8349 (Nzcv daif +PAN -UAO +TCO +DIT -SSB
Public bug reported:
Some years ago I had this bug with my Lenovo X1 computers.
The problem was that a left mouse click was received, but then releasing the
button, the click was not turned off.
I used this program to test the problem:
>> sudo evtest /dev/input/event15 | grep EV_KEY
This will t
I just hit this one on my Dell Optiplex 7010 this morning after an update.
Probably not matching the kernel, I get the following:
Errors were encountered while processing:
nvidia-dkms-390
E: Sub-process /usr/bin/dpkg returned an error code (1)
And the following from the make.log:
cc1: some warnin
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubunt
Public bug reported:
Hi!
I'm new there. First: a lot of thanks for Ubuntu for all involved in this
project.
Today after /usr/bin/unattended-upgrade my laptop is unable to display on
external monitor using DisplayPort. External monitor is not visible at all in
Ubuntu displays settings.
It worke
I'm also affected by this. Here's some output from apt:
Building initial module for 6.5.0-14-generic
Error! Bad return status for module build on kernel: 6.5.0-14-generic (x86_64)
Consult /var/lib/dkms/nvidia/390.157/build/make.log for more information.
dpkg: error processing package nvidia-dkms-3
Public bug reported:
After server boots up, outbound network connectivity over wifi interface
is okay but inbound is not. Jellyfin app clients are unable to connect
to Jellyfin server running on this server. From my desktop PC I cannot
ping the ip for the wifi interface.
ProblemType: Bug
Distro
In case my hardware config is useful:
mhankins@mediabox:~$ inxi -F
System:
Host: mediabox Kernel: 6.2.0-39-generic x86_64 bits: 64 Console: pty pts/0
Distro: Ubuntu 22.04.3 LTS (Jammy Jellyfish)
Machine:
Type: Desktop System: Intel product: KBL-R MRD v: 0.1
serial:
Mobo: Intel model
** Changed in: linux-nvidia-6.5 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048815
Title:
Pull request to address TPM SPI devi
** Changed in: linux-nvidia-6.5 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-nvidia-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2048966
Title:
Fix soft lockup triggered by arm_smm
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubunt
Can confirm the issue is fixed when running 6.6.11
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2048827
Title:
[amdgpu] Mouse cursor theme is grey instead of black
Status in l
This affects me too... I run a different GPU, so I will post my DMESG
here as well:
13.349657]
[ 13.349666] UBSAN: array-index-out-of-bounds in
/build/linux-SXblTa/linux-6.5.0/drivers/gpu/drm/amd/amdgpu/../pm/p
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/2803
Importance: Unknown
Status: Unknown
** Changed in: linux-hwe-6.2 (Ubuntu)
Importance: Undecided => Low
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Triaged
** Tags added: fixed-upstream
** Summary changed:
- upstream Intel VSC firmware paths changed to intel/vsc/
+ upstream Intel VSC firmware paths moved to intel/vsc/
--
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/bug
** Changed in: linux
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2048827
Title:
[amdgpu] Mouse cursor theme is grey instead of black
St
** Also affects: linux-firmware (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-fi
For noble, bug 2042074 is still not yet accepted. Mark this as CONFIRMED
at this moment.
** Changed in: linux-firmware (Ubuntu Noble)
Status: New => Confirmed
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Jammy)
Imp
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148071.html (jammy)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ In upstream commit 5370a431 ("mei: vsc: Rework firmware image names") for
+ char-misc-next targeting v6.8, the VSC firmware paths have been change
** Description changed:
+ [kernel SRU Justification]
+
+ [Impact]
+
+ Mediatek MT7925 WiFi/Bluetooth not supported yet.
+
+ [Fix]
+
+ For WiFi, there are tons of patches to be backported from upstream
+ kernel v6.7 due to a massive refactoring was done to integrate multiple
+ mt79xx drivers in
next time we should make sure the changelog lists all the delta from Debian :)
But with the same tarball it will be easier to find it out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
Public bug reported:
After an update from 3.23 to 3.24 my audio started to sound scratchy.
I'm not really sure if the problem was already in 3.23 because I'm not
sure if I used sound. But anyway, downgrading to 3.14 fixed the problem.
My HW is identified as "Ellesmere HDMI Audio [Radeon RX 470/48
And for Jammy, it takes also:
$ git show --stat 765492b8b90e3985fe60b3cf8d386538aa38b6ac
commit 765492b8b90e3985fe60b3cf8d386538aa38b6ac (tag: iwlwifi-fw-2023-09-21)
Author: Gregory Greenman
Date: Thu Sep 21 17:02:12 2023 +0300
iwlwifi: add new FWs from core81-65 release
Add the -
This depends on bug 2028065, and pull request for linux-firmware/noble
has not yet been merged at this moment.
** Changed in: linux-firmware (Ubuntu Noble)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
SRU:
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148030.html (jammy)
* https://lists.ubuntu.com/archives/kernel-team/2024-January/148030.html
(mantic)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubun
** Changed in: linux-firmware (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Lunar)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux-firmware (Ubuntu Noble)
Status
For cycle is successful. The related log is
Dec 23 23:40:40 192-168-111-160 kernel: [0.00] Linux version
5.15.0-89-generic (buildd@bos03-amd64-016) (gcc (Ubuntu 11.4.0-1ubuntu1~22.04)
11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #99-Ubuntu SMP Mon Oct 30
20:42:41 UTC 2023 (Ubuntu 5.15
Public bug reported:
found error log like below in 105 power cycles.
Dec 23 02:09:27 192-168-111-160 root[5747]: openibd: ERROR: Failed
loading kernel module ib_umad.
Dec 23 02:09:27 192-168-111-160 root[5750]: openibd: ERROR: Failed
loading kernel module ib_ipoib.
** Affects: linux-hwe-5.15 (U
Public bug reported:
In upstream commit
https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-
misc.git/commit/?h=char-misc-
next&id=5370a431ef915b52697d25a5a32cbaf9a4cbef95 for char-misc-next
targeting v6.8, the VSC firmware paths have been changed to intel/vsc
instead of the original vsc/s
** Also affects: linux (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: New
--
You received this bug notification because you are a member of Kernel
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
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.
** Changed in: linux (Ubuntu Mantic)
Importance: Undecided => High
** Changed in: linux (Ubuntu Noble)
Importance: Undecided => Medium
--
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/
** Changed in: linux (Ubuntu Lunar)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Noble)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
You re
Thanks Steffen for raising this and bringing this to our attention.
That should obviously not have happen, kernel config changes should be
propagated to all newer Ubuntu kernel version, until explicitly dropped or
modified for any other reason.
It looks like we hit a kind of a race condition here
Can you please run 'apport-collect 2048986'?
** Tags added: kern-8891
--
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/2048986
Title:
audio problem: scratching sound. linux-firmw
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (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/2039868
T
Verified vsc firmware is identical to what we have at this moment, jammy
version 20220329.git681281e4-0ubuntu3.24.
for f in intel/vsc/*; do
f="${f##*/}";
if [ -f vsc/soc_a1_prod/$f ]; then
sum_new=$(md5sum intel/vsc/$f | awk '{print $1}');
sum_cur=$(md5sum vsc/soc_a1_prod/$f | awk '{pr
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
This bug is awaiting verification that the linux-lowlatency-
hwe-6.5/6.5.0-14.14.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.5' to 'verifica
Public bug reported:
Ubuntu 22.04.3 LTS
Release: 22.04
I've an external usb WIFI. The drivers for Linux have been compiled and
insalled in this system. Up to now I didn't get any issue with the
update of linux headers but I wonder if this is the reason for this
error.
Output of lsusb: (the adapt
SRU request submitted: https://lists.ubuntu.com/archives/kernel-
team/2024-January/148033.html
** Changed in: linux (Ubuntu Mantic)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Status: New => In Progress
--
You received this bug notification because you are a mem
Confirmed fixed in linux/5.15.0-94.104 using the itrue-mqtest-provider
and itrue-mqtest-client snaps.
Test procedure:
sudo snap install itrue-mqtest-provider itrue-mqtest-client
sudo snap connect itrue-mqtest-client:itrue-mqtest-all-perms
itrue-mqtest-provider:itrue-mqtest-all-perms
sudo snap c
I believe that having a kernel in PPA to unblock you is not very
helpful, since yI think you need that kernel signed with the usual
(prod.) signature/key (and not with a test/dev key coming from the PPA).
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu
vcarceler@zvezda:~$ lsb_release -rd
Description:Ubuntu 22.04.3 LTS
Release:22.04
vcarceler@zvezda:~$
2) The version of the package you are using, via 'apt-cache policy
pkgname
** Changed in: ubuntu-z-systems
Status: New => In Progress
--
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/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not inclu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-6.5 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-6.5 in Ubuntu.
https://bug
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
** 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/2048919
Title:
[UBUNTU 23.04] Regression: Ubuntu 23.04/23.
Public bug reported:
It is exactly this bug:
https://gitlab.freedesktop.org/drm/intel/-/issues/8685
It was fixed with that kernel commit:
commit 648d7be8ecf47b0556e32550145c70db153b16fb
Author: Ville Syrjälä
Date: Mon Dec 11 23:37:47 2023 +0200
drm/i915/dmc: Don't enable any pipe DMC eve
ell had an approved MIR but the only thing it was used for was iwd which
is not currently in main. After the MIR is approved, something in main
needs to depend on it (or add it to a main seed) and then the Archive
Admins can promote it to main.
--
You received this bug notification because you ar
Alright, thanks for looking into this!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.2 in Ubuntu.
https://bugs.launchpad.net/bugs/2048827
Title:
[amdgpu] Mouse cursor theme is grey instead of black
Status in linux-hwe-6.2
1 - 100 of 112 matches
Mail list logo
