** Tags added: originate-from-1963872
--
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/1965846
Title:
Enable the mic-mute led on Dell XPS 9315
Status in HWE Next:
New
Status
** Description changed:
[Impact]
- On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state
is changed accordingly.
+ On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state
is not changed accordingly.
[Fix]
Dell's mic mute support in privacy
[Expired for linux-firmware (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
This issue can be fixed by adding the modules-extra package as a test
requirement package, however we should figure out if this is how we like
to fix, or we need to adjust the kernel config / annotations.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Hello,
the module name should be nvme-tcp.
If `modprobe nvme-tcp` is not working, please try to install the modules-extra
package:
sudo apt install linux-modules-extra-gke
Which contains the module you need.
$ dpkg -c linux-modules-extra-5.4.0-1059-gke_5.4.0-1059.62_amd64.deb | grep
nvme-tcp
Public bug reported:
[Impact]
On Dell's XPS 9315, the MIC-Mute function is working but the LED(on F4) state
is changed accordingly.
[Fix]
Dell's mic mute support in privacy mode has been upstream, but the the mic-mute
led support is still SAUCE patch which is maintained with DMI based quirk.
@Chris, could you reproduce with thermald 2.4.7? thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1940485
Title:
thermald often limits CPU frequency while on AC
Status in
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 1965843
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
I'm not entirely sure if this is a thermald issue, but on my laptop
(Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC,
is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo
frequency.
Restarting thermald (with `systemctl
Please follow the instructions in comment #2.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1962414
Title:
screen white line coming at bottom
Status in linux-hwe-5.13 package
Public bug reported:
Desde o kernel 5.4.0-77 sempre que o chrome está em excução existe um excesso
de cosumo de processamento.
Presumo que seja por causa do kernel pois ao utilizar a versão 5.4.0-77 a taxa
de processamento fica em níveis baixos.
Meu sistema:
Linux Mint 20.2 Cinnamon
versão do
This bug was fixed in the package linux - 4.15.0-173.182
---
linux (4.15.0-173.182) bionic; urgency=medium
* bionic/linux: 4.15.0-173.182 -proposed tracker (LP: #1965552)
* Pick fixup from upstream stable patchset 2022-03-04 to address cert
failure with clock jitter test on
This bug was fixed in the package linux-azure-4.15 - 4.15.0-1134.147
---
linux-azure-4.15 (4.15.0-1134.147) bionic; urgency=medium
* bionic/linux-azure-4.15: 4.15.0-1134.147 -proposed tracker (LP:
#1964222)
* linux-azure: CONFIG_FB_EFI=y (LP: #1959216)
- [Config] azure-4.15:
This bug was fixed in the package linux - 4.15.0-173.182
---
linux (4.15.0-173.182) bionic; urgency=medium
* bionic/linux: 4.15.0-173.182 -proposed tracker (LP: #1965552)
* Pick fixup from upstream stable patchset 2022-03-04 to address cert
failure with clock jitter test on
This bug was fixed in the package linux - 4.15.0-173.182
---
linux (4.15.0-173.182) bionic; urgency=medium
* bionic/linux: 4.15.0-173.182 -proposed tracker (LP: #1965552)
* Pick fixup from upstream stable patchset 2022-03-04 to address cert
failure with clock jitter test on
This bug was fixed in the package linux - 4.15.0-173.182
---
linux (4.15.0-173.182) bionic; urgency=medium
* bionic/linux: 4.15.0-173.182 -proposed tracker (LP: #1965552)
* Pick fixup from upstream stable patchset 2022-03-04 to address cert
failure with clock jitter test on
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.54-0ubuntu0.18.04.1
---
nvidia-graphics-drivers-510 (510.54-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream release (LP: #1961075):
- Fixed a bug that could cause GPU exceptions when minimizing a
I'm having this problem, too!!! Ideapad 3 15ITL05 model. I'm on Ubuntu
21.10, also.
Yes, the brightness controller in the top-right drop-down menu works,
but it's more convenient to use the F11/F12 keys.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Impish verification done:
root@impish-vm:~# uname -a
Linux impish-vm 5.13.0-38-generic #43-Ubuntu SMP Fri Mar 18 12:42:26 UTC 2022
x86_64 x86_64 x86_64 GNU/Linux
root@impish-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.13.0-35-generic 5.13.0-35.40 amd64
Focal verification done:
root@focal-vm:~# uname -r
5.4.0-106-generic
root@focal-vm:~# dpkg -l| grep linux-modules
ii linux-modules-5.4.0-104-generic 5.4.0-104.118amd64
Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP
ii linux-modules-5.4.0-106-generic
This bug is awaiting verification that the linux/5.4.0-106.120 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, change
This bug is awaiting verification that the linux/5.13.0-38.43 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.4.0-106.120 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, change
This bug is awaiting verification that the linux/5.13.0-38.43 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.4.0-106.120 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, change
This bug is awaiting verification that the linux/5.4.0-106.120 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, change
This bug is awaiting verification that the linux/5.4.0-106.120 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, change
This bug is awaiting verification that the linux/5.4.0-106.120 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, change
This bug is awaiting verification that the linux/5.13.0-38.43 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-impish' to 'verification-done-impish'. If the
problem still exists,
This bug is awaiting verification that the linux/5.13.0-38.43 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-impish' to 'verification-done-impish'. If the
problem still exists,
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Confirmed
** Also affects: linux (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Impish)
Upadting the 'affects jammy' kernel entry as well.
Since commit 'f3b7e73b2c6619884351a3a0a7468642f852b8a2' is included in jammy's
5.15 since Ubuntu-5.15.0-20.20, I'm updating the status to Fix released and
with this the projects entry, too.
** Changed in: linux (Ubuntu Jammy)
Status: Fix
I have encountered this bug, and I have found it also occurs from "Dim
Screen When Inactive".
Would you try these steps to confirm?
Steps to reproduce:
1. In: Settings > Power > Power Saving
2. Set "Dim Screen When Inactive" to "True"
3. Set "Blank Screen" to "1 minute"
4. Do nothing for 1
Meanwhile this also landed in jammy:
linux-generic | 5.15.0.23.25 | jammy
hence updating the "affects jammy" entry to Fix Released,
and with that the project entry becomes Fix Released, too.
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Released
** Changed in:
** 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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1960182
Title:
[UBUNTU 20.04] kernel: Add support for CPU-MF
** 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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959529
Title:
Hipersocket page allocation failure on Ubuntu
I found the behaviour occurring in a more specific case.
Steps to reproduce:
1. In: Settings > Power > Power Saving
2. Set "Dim Screen When Inactive" to "True"
3. Set "Blank Screen" to "1 minute"
4. Do nothing for 1 minute
5. After screen turns off completely, press any key
When the screen
I have seen the bios also in there white screen flickering is not coming
means display is alright only problem is with ubuntu . could you please
help me out of it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
This bug was fixed in the package linux-azure - 5.4.0-1073.76
---
linux-azure (5.4.0-1073.76) focal; urgency=medium
* focal/linux-azure: 5.4.0-1073.76 -proposed tracker (LP: #1964181)
* linux-azure: Missing ext4 commits (LP: #1960820)
- ext4: check for out-of-order index
This bug was fixed in the package linux-azure - 5.4.0-1073.76
---
linux-azure (5.4.0-1073.76) focal; urgency=medium
* focal/linux-azure: 5.4.0-1073.76 -proposed tracker (LP: #1964181)
* linux-azure: Missing ext4 commits (LP: #1960820)
- ext4: check for out-of-order index
This bug was fixed in the package linux-azure - 5.4.0-1073.76
---
linux-azure (5.4.0-1073.76) focal; urgency=medium
* focal/linux-azure: 5.4.0-1073.76 -proposed tracker (LP: #1964181)
* linux-azure: Missing ext4 commits (LP: #1960820)
- ext4: check for out-of-order index
This bug was fixed in the package linux-azure - 5.4.0-1073.76
---
linux-azure (5.4.0-1073.76) focal; urgency=medium
* focal/linux-azure: 5.4.0-1073.76 -proposed tracker (LP: #1964181)
* linux-azure: Missing ext4 commits (LP: #1960820)
- ext4: check for out-of-order index
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.4.0-105.119
---
linux (5.4.0-105.119) focal; urgency=medium
* CVE-2022-0847
- lib/iov_iter: initialize "flags" in new pipe_buffer
* Broken network on some AWS instances with focal/impish kernels
(LP: #1961968)
- SAUCE:
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux-raspi - 5.13.0-1022.24
---
linux-raspi (5.13.0-1022.24) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1022.24 -proposed tracker (LP: #1964955)
[ Ubuntu: 5.13.0-37.42 ]
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux-gcp - 5.13.0-1021.25
---
linux-gcp (5.13.0-1021.25) impish; urgency=medium
* impish/linux-gcp: 5.13.0-1021.25 -proposed tracker (LP: #1964951)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.54-0ubuntu0.21.10.1
---
nvidia-graphics-drivers-510 (510.54-0ubuntu0.21.10.1) impish; urgency=medium
* New upstream release (LP: #1961075):
- Fixed a bug that could cause GPU exceptions when minimizing a
This bug was fixed in the package nvidia-graphics-drivers-510 -
510.54-0ubuntu0.20.04.1
---
nvidia-graphics-drivers-510 (510.54-0ubuntu0.20.04.1) focal; urgency=medium
* New upstream release (LP: #1961075):
- Fixed a bug that could cause GPU exceptions when minimizing a
This bug was fixed in the package linux - 5.13.0-37.42
---
linux (5.13.0-37.42) impish; urgency=medium
* impish/linux: 5.13.0-37.42 -proposed tracker (LP: #1964959)
* CVE-2022-0742
- ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()
linux (5.13.0-36.41)
The verification of the Stable Release Update for nvidia-graphics-
drivers-510-server 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
Public bug reported:
..
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
** Patch added: "lp1964992-focal.debdiff"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1964992/+attachment/5571326/+files/lp1964992-focal.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
This doesn't seem to be reproducible in Bionic, marking it as fixed
accordingly.
** Changed in: zfs-linux (Ubuntu Bionic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
** 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-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1961300
Title:
linux-azure: Fix NUMA node
Hi there is white line coming at bottom of screen in both wayland and
gnome.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1962414
Title:
screen white line coming at bottom
** Tags removed: verification-needed-focal verification-needed-impish
** Tags added: verification-done-focal verification-done-impish
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
** Attachment added: "dual_external_monitor_with_dp.png"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.14/+bug/1965749/+attachment/5571266/+files/dual_external_monitor_with_dp.png
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
Hello Team,
I have a Dell XPS 15 9500 laptop with the Dell WD19S Docking station and Ubuntu
20.04 LTS.
Actually, I have many problems with external monitors. Let me explain:
The WD19S docking station has 3 outputs for monitors: 2 Display Port and
1 HDMI port.
The ideal
*** This bug is a duplicate of bug 1933179 ***
https://bugs.launchpad.net/bugs/1933179
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => Invalid
** Summary changed:
- [SRU][J/OEM-5.14] Fix the mouse cursor lag on AMD RMB
+ [SRU][OEM-5.14] Fix the mouse cursor lag on AMD RMB
** Description changed:
[Impact]
Mouse cursor lag in gnome UI.
[Fix]
Only set
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 1965747
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu Focal)
**
Public bug reported:
[Impact]
Mouse cursor lag in gnome UI.
[Fix]
Only set vblank_disable_immediate when PSR is not enabled.
[Test]
Verified on HW with touchpad/trackpoint, it works smoothly.
[Where problems could occur]
It might break display output on AMD RMB platform.
** Affects: hwe-next
Kernel 5.4.0-99-generic is now running without a fault for 40 days.
--
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/1959685
Title:
Kernel BUG with btrfs on linux 5.13
Status in linux
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Public bug reported:
http://www.bluez.org/release-of-bluez-5-64/
At least for 22.10, but maybe for 22.04 too.
** Affects: bluez (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Triaged
** Tags: needs-packaging
--
You received this bug notification
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
Works with nvidia 510 driver. So I set the issue to fixed release for
this. Is there anybody using the 470 driver who could confirm it works
there too?
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => High
** Changed in: linux (Ubuntu Jammy)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => You-Sheng
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.14 (Ubuntu Focal)
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 1964983
and then change the status of the bug to 'Confirmed'.
If, due to the
This one has been merged in the last upstream stable patch set
** No longer affects: linux (Ubuntu Impish)
** No longer affects: linux (Ubuntu Focal)
** No longer affects: linux (Ubuntu Bionic)
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
--
You received this bug
The patch has been merged in ubuntu focal:
https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/commit/?id=fa748ace5184
--
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/1951606
Title:
** No longer affects: linux (Ubuntu 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/1965723
Title:
audit: improve audit queue handling when "audit=1" on cmdline
Status in linux
Sujith, does the issue happen when "tg3" is blacklisted? Something like
"blacklist=tg3 modprobe.blacklist=tg3" in kernel parameter.
--
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/1917471
This is Fix Released for jammy, since addressed at LP#1933179.
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
1 - 100 of 103 matches
Mail list logo
