This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-25.25~20.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-focal' to
'verification-done-focal'. If the problem
*** This bug is a duplicate of bug 1967817 ***
https://bugs.launchpad.net/bugs/1967817
** This bug has been marked a duplicate of bug 1967817
display problems with wayland
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I found this issue fixed after a Senel firmware update (v0.22.520, 28 Mar
2022):
https://pcsupport.lenovo.com/us/en/products/laptops-and-netbooks/thinkpad-x-series-laptops/thinkpad-x1-titanium-type-20qa-20qb/downloads/driver-list/component?name=Mouse,%20Touchpad,%20Keyboard%20and%20Pen
The
** Tags added: seg
--
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/1967702
Title:
Enable speakup kernel modules to allow the speakup screen reader to
function
Status in linux package
In /proc/bus/input/devices, the correct info is:
I: Bus=0018 Vendor=2808 Product=0101 Version=0100
N: Name="PNP0C50:00 2808:0101 Touchpad"
P: Phys=i2c-PNP0C50:00
S:
Sysfs=/devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-PNP0C50:00/0018:2808:0101.0001/input/input16
U: Uniq=
H:
I completely reinstalled Kubuntu, then ran:
sudo apt update
sudo apt upgrade
sudo apt install neofetch
I rebooted, and the Touchpad is still detected, ran neofetch:
`.:/osssso/:. mark@mark-Galago-Pro
.:oyyo:`
** Summary changed:
- Accessibility features have been disabled, modules like speakup_soft and
others are missing
+ Enable speakup kernel modules to allow the speakup screen reader to function
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Confirmed
** Changed
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/1967820
Title:
Touchpad incorrectly detected
Public bug reported:
Computer model 'galp5'.
The issue started after updating everything, including the kernel.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-39-generic 5.13.0-39.44
ProcVersionSignature: Ubuntu 5.13.0-39.44-generic 5.13.19
Uname: Linux
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/1967817
Title:
display problems with wayland
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-455 in
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/1967818
Title:
display problems with wayland
Public bug reported:
I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate
bug filed for that), so I switched to wayland. Using gnome, kde, and
ubuntu desktops under wayland is giving problems with chrome and brave
browsers. If I have a single window open, it's pretty good, but if
Public bug reported:
I upgraded from 21.10 to 22.04 pre-beta. xorg isn't working (separate
bug filed for that), so I switched to wayland. Using gnome, kde, and
ubuntu desktops under wayland is giving problems with chrome and brave
browsers. If I have a single window open, it's pretty good, but if
note that this does not happen on firefox (about a hald dozen windows
open)
--
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/1967818
Title:
display problems with wayland
Status in linux
This bug is awaiting verification that the linux-azure/5.4.0-1075.78
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' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-azure/5.4.0-1075.78
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' to 'verification-done-focal'. If the
problem still exists,
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
This bug is awaiting verification that the linux-oem-5.14/5.14.0-1033.36
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' to 'verification-done-focal'. If the
problem still
FYI - this was CC'ed into stable, and went to 5.15.y stable. Here is
the reference for it:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/acpi/power.c?h=linux-5.15.y=bc28368596436e6e81ffc48c815b8225d96121c0
--
You received this bug notification because you are
Default Comment by Bridge
** Attachment added: "proposed backport"
https://bugs.launchpad.net/bugs/1967814/+attachment/5577049/+files/backport_qemu-4.2.mbox
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux
You have been subscribed to a public bug:
== Comment: #63 - Halil Pasic - 2022-03-28 17:33:34 ==
I'm pretty confident I've figured out what is going on.
>From the guest side, the decision whether the SCSI command was completed
>successfully or not comes down to looking at the sense data.
Tried with a live medium of Ubuntu Jammy Beta. Also reproducable here.
--
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/1967188
Title:
Trackpoint not working on Thinkpad X1 tablet Gen 2
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X
Same issue with Yamaha THR5 through USB on Ubuntu Studio 20.04.1.
Disabled JACK and was able to fix the stutter. Edit in
/etc/pulse/daemon.conf for 5.13.0-37 did not fix distorted audio.
5.13.0-39 exhibiting same problem.
--
You received this bug notification because you are a member of Kernel
Same here. I have 48GB Ram and 76GB swap partition. Where did you see
the error code -16 is EBUSY?
--
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/1962359
Title:
Hibernation fails due
** Changed in: linux-azure (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux-azure (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in
** Changed in: linux-azure (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1967166
Title:
Azure: not enough RAM under
The log I attached in comment #15 is from a cold boot, but I'm seeing all four
combinations of outcomes:
cold boot -> failing
cold boot -> working
warm boot -> failing
warm boot -> working
on ~40 Focal servers with identical hardware.
(Except for a different RAID controller in three of them which
Public bug reported:
Description:Ubuntu 20.04.4 LTS
Release:20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
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/1902464
Title:
The rear panel of Lenovo P620 doesn't support
Another logs, this time the message I see during startup, for a very short
time. It takes place when laptop is attached to docking station.
I think it is related to the issue.
(there could be some typo due to wrong OCR or just normal typo; photo of
the log attached)
/dev/nvme1n1p5: clean,
I have now tested whether the issue is still resolved and it luckily is.
So both after installing a version of amdgpu-pro and also after
uninstalling this proprietary driver again, unlocking the system works
again.
Once the stable version of Ubuntu 22.04 is published, I will upgrade and
try
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
--
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/1967750
Title:
Intel: enable x86 AMX
Status in linux package in
Hi Jeff,
Original repro machine had ~1TB memory.
Previously attached log snip:
Memory: 1055972180K/1073051196K available (14339K kernel code, 2400K rwdata,
5008K rodata, 2736K init, 4964K bss, 17079016K reserved, 0K cma-reserved)
--
You received this bug notification because you are a member
@seb128, sure, attachment "log.txt" (journalctl -b 0) contains what you
request, and it was taken just after the issue. More or less, at ~17:05
I detached docking station, and after this I logged in and fresh GNOME
session appeared to my eyes. Immediately after logging in I gathered the
log.txt.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1962349
Title:
Bolt doesn't work with
The new ASUS EC sensor (asus-ec-sensors) driver might help you - see
https://www.phoronix.com/scan.php?page=news_item=Linux-5.18-HWMON for
more information.
This driver has been included in the first release candidate of the
upcoming Linux 5.18 kernel (5.18-rc1). You can download this 5.18-rc1
HI Sujith, can you tell us what server this is, and how much RAM is in
it? Just wondering.
--
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/1934620
Title:
NVIDIA A100-80GB GPU fails to
This also happens with the kernel in xubuntu-22.04-beta-desktop-
amd64.iso, so it will block me upgrading that machine to Jammy when it's
released.
Is there anything I can do to help? I'm not familiar with debugging
kernel drivers, but I'm a competent general developer, and I'm prepared
to put in
** Changed in: subiquity (Ubuntu)
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/bugs/1967562
Title:
jammy beta (220330) arm iso kernel panic during pxe boot
https://lore.kernel.org/netdev/cover.1632565508.git.leo...@nvidia.com/
It seems jammy kernel needs cf530217408e ("devlink: Notify users when objects
are accessible") from v5.16-rc1
(see link) the old devlink_register (before cf530217408e) implementation do
not publish the params so we cannot
** Description changed:
-
- on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode
+ on kernel 5.15.0-23-generic devlink cannot show/change flow steering
+ mode
[test case]
# devlink dev param show pci/:24:00.0 name flow_steering_mode
pci/:24:00.0:
-
@Paolo , thanks for verifying. Right, MAAS deployment looks good (see my
comment of "Additional Information" in the bug description) as what Dann
pointed out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@dann , I checked the grub entry prior to filing this bug. For now the
pxe server is used for the other purpose. Let me reproduce the post-
mortem information later on. Thanks for the tip!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: Incomplete
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: linux
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 1967750
and then change the status of the bug to 'Confirmed'.
If, due to the
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 1967754
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
on kernel 5.15.0-23-generic devlink cannot show/change flow steering mode
[test case]
# devlink dev param show pci/:24:00.0 name flow_steering_mode
pci/:24:00.0:
name flow_steering_mode type driver-specific
values:
(flow steering mode description
** Changed in: linux-azure (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1961329
Title:
linux-azure: Update HV support
Public bug reported:
[Impact]
Enable AMX (aka TMUL) new instructions on the 5.15 kernel.
[Test case]
Tests have been performed directly by Intel.
[Fix]
Apply the following upstream commits:
20df73756148 ("selftests/x86/amx: Update the ARCH_REQ_XCOMP_PERM test")
063452fd94d1
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/1967748
Title:
kswapd0 take 100% processor
I have a workaround for this:
UBUNTU: SAUCE: riscv: Disable VMAP_STACK since it fails with efi
When VMAP_STACK is enabled, kernel threads have their stacks in the vmalloc
region.
So when The kworker responsible for handling efi work queue (efi_call_rts)
calls
Public bug reported:
Hello
I don't know if this is normal operation or if it is possible to configure
KSWAPD0.
I installed version 22.04 (jammy) choosing encrypted ZFS partitioning in an
external disk.
The installation chose to assign the swap partition to SDC2.
On reboot, this partition does
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35
---
linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP:
#1967284)
* IPU6 camera has no function on Andrews MLK (LP: #1964983)
- SAUCE: IPU6:
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35
---
linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP:
#1967284)
* IPU6 camera has no function on Andrews MLK (LP: #1964983)
- SAUCE: IPU6:
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35
---
linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP:
#1967284)
* IPU6 camera has no function on Andrews MLK (LP: #1964983)
- SAUCE: IPU6:
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35
---
linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP:
#1967284)
* IPU6 camera has no function on Andrews MLK (LP: #1964983)
- SAUCE: IPU6:
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35
---
linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP:
#1967284)
* IPU6 camera has no function on Andrews MLK (LP: #1964983)
- SAUCE: IPU6:
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1032.35
---
linux-oem-5.14 (5.14.0-1032.35) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1032.35 -proposed tracker (LP:
#1967284)
* IPU6 camera has no function on Andrews MLK (LP: #1964983)
- SAUCE: IPU6:
Yeah, it's not a MAAS deploy issue, but a subiquity PXE install issue
(MAAS deploys this system fine).
@Tai this bit looks weird to me:
[0.00] Kernel command line: BOOT_IMAGE=/casper/vmlinuz debug
root=/dev/ram0 ramdisk_size=150 ip=dhcp
Could you add a 'journalctl -b 0 > log' to the bug after getting the
issue?
--
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/1967613
Title:
Gnome session reset after docking station
Amazon tested
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1966969
Title:
linux-aws: Xen:
Another case, but this time positive: laptop was suspended, docking
station has been disconnected, and after waking up (which took some
time, about 8s) everything was fine.
But, yesterday I've installed "displaylink-driver-5.5.0-59.151.run" and
I don't know if this changed the situation or nor.
Queued for stable trees
https://lore.kernel.org/stable/ykgzn+ugt...@kroah.com/
** Changed in: linux-riscv (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Importance: Undecided => Critical
** Changed in: ubuntu-meta (Ubuntu)
Milestone: None => ubuntu-22.04
** Tags added: rls-ff-incoming
** Tags removed: rls-ff-incoming
**
It appears the main cause of this is presently bug 1959888 when you log
in with a secondary monitor on a secondary (Nvidia) GPU. So the log
messages stop once you have that fix. Although I would still like to
understand it better because that's the second bug I've seen trigger the
same messages.
Public bug reported:
Upstream raspberrypi patchset 2022-04-04
Ported from the following raspberrypi branch:
rpi-5.15.y
from https://github.com/raspberrypi/linux.git
configs: Re-enable all GSPCA camera modules
drm/vc4: Force trigger of dlist update on margins change (#4970)
brcmfmac:
I just deployed Jammy on recht (using MAAS) and it seems fine:
...
ubuntu@recht:~$ uname -a
Linux recht 5.15.0-23-generic #23-Ubuntu SMP Fri Mar 11 14:57:40 UTC 2022
aarch64 aarch64 aarch64 GNU/Linux
ubuntu@recht:~$ lsb_release -d
Description:Ubuntu Jammy Jellyfish (development branch)
So you're saying it's a regression due to a kernel upgrade? Do you have
older oem kernels still installed to boot with to verify if they still
work?
The bug seems to be in the ethernet driver (igc).
[ 7253.607665] Call Trace:
[ 7253.607667]
[ 7253.607672] igc_get_hw_semaphore_i225+0x34/0x180
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1966497
Title:
Fix non-working MT7921 BT
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
** Also affects: linux-oem-5.17 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.17 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1967069
Title:
Enable headset mic on
** Changed in: linux-oem-5.17 (Ubuntu Jammy)
Status: In Progress => Fix Committed
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
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/1967727
Title:
Random screen blanks with
This bug was fixed in the package alsa-ucm-conf - 1.2.2-1ubuntu0.13
---
alsa-ucm-conf (1.2.2-1ubuntu0.13) focal; urgency=medium
* d/p/0035-Revert-PATCH-ucm2-USB-Audio-Add-more-support-to-Leno.patch
d/p/0036-Revert-PATCH-Add-support-for-Lenovo-ThinkStation-P62.patch
This bug was fixed in the package bolt - 0.9.1-2~ubuntu20.04.1
---
bolt (0.9.1-2~ubuntu20.04.1) focal; urgency=medium
* SRU into Ubuntu 20.04.
- Add support for integrated USB4 controllers (LP: #1962349)
-- Mario Limonciello Fri, 25 Feb 2022 16:20:33
-0600
** Changed in:
Public bug reported:
On a clean 22.04 install, the screen randomly blanks once in a while for
a couple of seconds, then comes back.
I see the following message in dmesg when it happens:
[ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
ProblemType: Bug
DistroRelease:
This is actually fixed already in 5.13.0.39.44 as shown above, but the
root cause that I'm facing is that edge-Kernel is behind non -egde:
$ rmadison -a amd64 -u ubuntu linux-image-generic-hwe-20.04-edge | grep focal
linux-image-generic-hwe-20.04-edge | 5.13.0.27.29~20.04.13 | focal-security |
The verification of the Stable Release Update for alsa-ucm-conf has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Public bug reported:
Device information for https://answers.launchpad.net/ubuntu-
certification/+question/701164
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1031-oem 5.14.0-1031.34
ProcVersionSignature: Ubuntu 5.14.0-1031.34-oem 5.14.21
Uname: Linux 5.14.0-1031-oem
The verification of the Stable Release Update for bolt has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
You have firmware files that are provided by two different packages. You
have firmware-realtek 20210818-1 installed which is not an Ubuntu
package but a Debian package. You should not install Debian packages on
an Ubuntu system.
** Changed in: linux-firmware (Ubuntu)
Status: New => Invalid
** Summary changed:
- touchscreen
+ THOMSON GEN360-4C128BK touchscreen does not work
** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)
** Summary changed:
- THOMSON GEN360-4C128BK touchscreen does not work
+ Thomson Neo 360 X (GEN360-4C128BK) touchscreen does not work
--
You
You have been subscribed to a public bug:
touchscreen does not work at any time
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
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/1967721
Title:
Laptop never resuming from
Public bug reported:
On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after
suspending the laptop, it's never possible to wake it up.
Neither keyboard nor power button work, only way is to long-press to
force poweroff and restart.
This did not happen with 21.10.
ProblemType:
99 matches
Mail list logo
