Dell Precision 5560 is managed by oem-somerville-pidgey-meta.
Dell XPS 13 9310 is managed by oem-somerville-bulbasaur-meta.
You can simply purge those Debian packages and then reboot the system to use
the generic kernel.
`sudo apt-get purge oem-somerville-pidgey-meta` or `sudo apt-get purge
Encountered error while installing available upgrade for bcmwl package:
dpkg: error processing package bcmwl-kernel-source (--configure):
installed bcmwl-kernel-source package post-installation script subprocess
returned error exit status 10
Errors were encountered while processing:
SRU submitted, thanks
https://lists.ubuntu.com/archives/kernel-team/2023-January/136392.html
** Description changed:
[Impact]
The commit in 5.17.0.1026.27 introduce an regression that leads to the panel
of ThinkPad L14 Gen 3 becomes blank after bootup
224dffc89a957 drm/amdgpu: make sure
Install alsa-ucm-conf version 1.2.6.3-1ubuntu1.3 on HP ZBook Studio G9
laptop, the mic default turned on.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
https://bugs.launchpad.net/bugs/2001896
Title:
Install alsa-ucm-conf version 1.2.6.3-1ubuntu4 on HP ZBook Studio G9
laptop, the mic default turned on.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done verification-done-jammy
verification-done-kinetic
--
You received
Install alsa-ucm-conf version 1.2.6.3-1ubuntu4 on HP ZBook Studio G9
laptop, the mic mute led turned on after press the key.
** Tags removed: verification-needed verification-needed-jammy
verification-needed-kinetic
** Tags added: verification-done verification-done-jammy
Install alsa-ucm-conf version 1.2.6.3-1ubuntu1.3 on HP ZBook Studio G9
laptop, the mic mute led turned on after press the key.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to alsa-ucm-conf in Ubuntu.
Public bug reported:
When upgrading from 5.11.0-44 to any 5.13 or 5.15.0-5x kernel, loading
the amdgpu module causes a kernel panic on boot. If I uninstall the
linux-modules-extra package or blacklist the amdgpu module in
modprobe.d, then I am able to boot. The kernel panic messages scroll a
bit
OK so you may or may not be commenting on the right bug. Assuming you
are, we'll just ask you to test the proposed fix when it is built...
** Description changed:
[ Impact ]
Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
Probably other headphone types would be
That's probably not as good as sticking to nouveau because it will fall
back to software rendering instead. But the third and best option is to
install an Nvidia driver using the 'Additional Drivers' app.
--
You received this bug notification because you are a member of Kernel
Packages, which is
A fix has been proposed for Lunar.
https://lists.ubuntu.com/archives/kernel-team/2023-January/136387.html
Since the Config management has change between series, a similar
patch/fix needs to be added for Kinetic and Jammy.
--
You received this bug notification because you are a member of Kernel
** Tags added: nightlight
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1995783
Title:
Nightlight fails after suspend
Status in mutter package in Ubuntu:
New
** Changed in: linux-kvm (Ubuntu Lunar)
Status: New => Confirmed
** Changed in: linux-kvm (Ubuntu Kinetic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in Ubuntu.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
SRU Justification:
- Impact:
+ [Impact]
Ice driver does not support E823 in 5.4. This was introduced in 5.7, but is
part of the Ice Lake D platform which is otherwise supported in 5.4. One of
the hardware vendors has requested that we update Ice in 5.4 to
** Summary changed:
- Update ice driver to support E823 devices
+ [SRU}Update ice driver to support E823 devices
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Michael Reed (mreed8855)
**
@acelankao: Thanks very much! Confirmed that your test kernel fixes the
screen blanking problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/2002467
Title:
ThinkPad L14 Gen
** Description changed:
SRU Justification:
[Impact]
Request to include below mpi3mr driver bug fix patches in Ubuntu
22.04.1(5.15 kernel). These patches got accepted by the upstream and
please find the corresponding commit IDs as below:
ed567615f7ec scsi: mpi3mr: Fix build
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 2003267
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: intel
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/2003267
A backup (rsync) ran again and crashed:
[16096.851781] usb 2-1: reset SuperSpeed USB device number 3 using xhci_hcd
[16096.875912] usb 2-1: LPM exit latency is zeroed, disabling LPM.
[20421.689261] perf: interrupt took too long (6260 > 6216), lowering
kernel.perf_event_max_sample_rate to 31750
This change was made by a bot.
** 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/2003270
Title:
No WiFi networks found in
Were these git commands useful?
--
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/1998643
Title:
smartpqi: Update 22.04 driver to latest kernel.org
Status in linux package in Ubuntu:
Public bug reported:
When I turn on the laptop, the WiFi is connected, few seconds later it
disconnects and can't find any WiFi network in visible networks list.
Description:Ubuntu 22.04.1 LTS
Release:22.04
I can't use WiFi for this problem.
ProblemType: Bug
DistroRelease: Ubuntu
** Description changed:
18272 03:33:07 DEBUG| Persistent state client._record_indent
now set to 2
- 18273 03:33:07 DEBUG| Persistent state
client.unexpected_reboot now set to
('ubuntu_kernel_selftests.net:fib_nexthop_nongw.sh',
** Description changed:
+ SRU Justification:
+
+ [Impact]
+
Request to include below mpi3mr driver bug fix patches in Ubuntu
22.04.1(5.15 kernel). These patches got accepted by the upstream and
please find the corresponding commit IDs as below:
ed567615f7ec scsi: mpi3mr: Fix build
** Also affects: linux-kvm (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-kvm (Ubuntu Kinetic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-kvm in
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.78.01-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-525 (525.78.01-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #2001703).
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.78.01-0ubuntu0.22.04.1
---
nvidia-graphics-drivers-525 (525.78.01-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2001703).
* debian/additional_card_ids,
debian/additional_runtimepm_ids:
This bug was fixed in the package nvidia-graphics-drivers-525 -
525.78.01-0ubuntu0.22.10.1
---
nvidia-graphics-drivers-525 (525.78.01-0ubuntu0.22.10.1) kinetic; urgency=medium
* New upstream release (LP: #2001703).
* debian/additional_card_ids,
This change was made by a bot.
** 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/2003244
Title:
Epson ET-2760 Scanner not
Uploading updated dmesg.
External monitor was connected to USB-C at 47s, system sleep at 58s, monitor
unplugged at 64s, system wake-up at 68s.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002206/+attachment/5642326/+files/dmesg.txt
--
You received
Public bug reported:
xsane 0.999, no devices available
simple scan 3.28.0, no scanner available
ET-2760 is connected by USB and powered on waiting for commands.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-202-generic 4.15.0-202.213
ProcVersionSignature: Ubuntu
Removing "pci=nommconf" results in "Enabling HDA controller" no longer
being logged. However, the freezing is still there.
Is there any kernel debug flag that I can set to help debug this
further?
--
You received this bug notification because you are a member of Kernel
Packages, which is
I have blacklisted this now using:
sudo vim /etc/modprobe.d/blacklist-nouveau.conf
adding:
blacklist nouveau
options nouveau modeset=0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hello Kai-Chuan, or anyone else affected,
Accepted alsa-ucm-conf into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Kai-Heng, or anyone else affected,
Accepted alsa-ucm-conf into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu1.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Kai-Chuan, or anyone else affected,
Accepted alsa-ucm-conf into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Kai-Heng, or anyone else affected,
Accepted alsa-ucm-conf into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
I'm seeing this as well. Some information that may help. I found the
problem with 5.4.0-137. I found that when looking at tcpdump on the
guest and the bridge I can see ARP requests on both interfaces. On the
guest I can see it responding to the ARP request, however I don't see
the ARP response on
** Summary changed:
- [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
+ [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG)
support
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Happens the same to my laptop: Ubuntu 22.04, Samsung NVME AMD 5700U...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1888018
Title:
nvme0 does not resume from standby
Status in
$lsb_release -rd
Description:Ubuntu 22.04.1 LTS
Release:22.04
$ uname -a
Linux ciampix-lap2022 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC
2023 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
IIRC I tried to install it from source back then, but had missing build
dependencies (or versions) which were not in the package repositories. I
could be wrong, though.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
Hmm, currently when connecting it via blueman it automatically connects with
the last used profile.
I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it
seems to have A2DP there.
But as soon as I change my Mic Input Device to my headphones it changes to
"Headset Head
I have exactly the same problem. The "knock knock" sound on Windows
occurs when you come back to Windows after having boot on Linux. If you
reboot twice on Windows, the sound go back to normal.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete
fixed the version as -1ubuntu6~22.04.1 because it can't be bigger than
in newer releases
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
** Changed in: zfs-linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: zfs-linux (Ubuntu Jammy)
Status: New => In
cted error while running command.
Command: ['unshare', '--fork', '--pid', '--', 'chroot', '/target',
'efibootmgr', '-v']
Exit code: 2
Reason: -
Stdout: ''
Stderr: EFI variables are not supported on this system.
** Affects: subiquity (Ubuntu)
Importance: Un
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy
--
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/1993315
This change was made by a bot.
** 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/2003203
Title:
Bluetooth dont work
Status
This device 0489:e0e1 is not supported by Linux kernel yet.
A patch to drivers/bluetooth/btusb.c is needed to add this specific
device.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
На ноутбуке Honor magicbook 14 не работает блютуз. Когда я включаю его, ничего
не происходит.
Также замечу, что присутсвует проблема с Wifi, поскольку подключается не ко
всем точкам доступа (На некоторых точках доступа происходит подключение, но
интернет отсутсвует).
And I with 5.14.0-1056-oem
Several process cannot get stopped including systemd -- also sd_[something]
I get an injunction to do:
echo 0 > /proc/sys/kernel/hung_task_timeout_secs
but I understand it is only to silence the warning...
--
You received this bug notification because you are a member
Thank's Kai-Heng Feng.
I know that but if I upgrade ubuntu it could brick MacBook boot and i will
never boot again (without hardware repair).
But your proposal give me an idea: kernel upgrade without system upgrade.
So, I look for and install newer kernel and it works !!!
(sudo dpkg -i *.deb)
Rafael, I can't seem to find a way to reproduce the bug with the
headphones I do have. Can you outline the steps (and the model of
headphones) you are using?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
This change was made by a bot.
** 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/2003181
Title:
Touchpad not detected
Status
Public bug reported:
Just removed my W10 OS and installed Ubuntu, but touchpas is not working
at all. I hva to use a mouse.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-43-generic 5.15.0-43.46
ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39
Uname: Linux
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
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/1996071
Title:
[UBUNTU 20.04] boot: Add s390x secure
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-aws/5.15.0-1029.33
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' to 'verification-done-jammy'. If the
problem still exists,
debdiff in attach (that doesn't change anything, it's basically a resync
of the same version in kinetic, recompiled with the jammy toolchain).
With this applied I was able to successfully run ubuntu_zfs_smoke_test
and ubuntu_zfs_stress both on 5.15 and 5.19.
** Patch added:
Public bug reported:
[Impact]
zfs-dkms fails to build on jammy with the latest linux hwe 5.19:
*** ZFS Version: zfs-2.1.4-0ubuntu0.1
*** Compatible Kernels: 3.10 - 5.17
[Test case]
$ sudo apt install zfs-dkms
[Fix]
The most reliable fix is probably to move to the same version that is
76 matches
Mail list logo
