** Tags removed: originate-from-2004217 stella
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2002968
Title:
Fix flicker display problem on some panels which support PSR2
Status
See also bug 2006370
--
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/1965882
Title:
[nouveau] External monitor plugged into (secondary) Nvidia GPU is all
white (plus a little flicker)
Actually this might be a variation on bug 1965882 so please also try
adding a kernel parameter:
intel_iommu=off
I don't know if AMD CPUs will require a different parameter.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
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/2006370
Title:
[nouveau] Terribly flicking an
Thanks for the bug report.
It looks like this is probably a bug in the nouveau graphics driver, and
most likely the HDMI port is connected to your Nvidia GPU. The nouveau
driver is also logging errors which may or may not be related to this
bug.
Please open the 'Additional Drivers' app and use it
You have been subscribed to a public bug:
Hi,
I have HP15 Gaming Pavilion bought 2-3 years ago.
I had Windows 10 before (not it is the second OS due to this bug [I can't use
Ubuntu with this bug]), and Win 10 has no problems.
No solution [that I found over the internet] worked.
I have to have
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** Also affects: nvidia-graphics-drivers-525 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-510 in Ubuntu.
https://bugs.launchpad.net/bugs/1975650
Title:
Nvid
** Description changed:
Notice: I have not reproduced this bug myself, nor do I have the needed
setup to reproduce this bug. This is a bug report based on info provided
to me over IRC.
- In order for CUDA compute to work, a kernel module "nvidia-uvm" is
- necessary. This module *should* e
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
http
strace of "clinfo -l" from the machine of the affected user.
** Attachment added: "clinfo_strace.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006408/+attachment/5645158/+files/clinfo_strace.log
--
You received this bug notification because you are a member
Public bug reported:
Notice: I have not reproduced this bug myself, nor do I have the needed
setup to reproduce this bug. This is a bug report based on info provided
to me over IRC.
In order for CUDA compute to work, a kernel module "nvidia-uvm" is
necessary. This module *should* exist in the hea
I have just tried the updated version of the 20.04c package, which
provides kernel version 6.1.0-1006.6. No Improvement there. The system
still locks up as soon as I log in.
The last thing that journalctl recorded before the lock-up is:
01:32:57 Xorg: (II) Loading /usr/lib/x86_64-linux-gnu/nvidia
** Tags added: patch
--
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/2000709
Title:
net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19
Status in ubuntu-kernel-tests:
In P
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
** Description changed:
On Focal and Kinetic the fcnal-test.sh does not run because it reports
that 'nettest' command not found; skipping tests
This is due to the nettest binary not being found in the path and
skipping the tests, but it is built and exists in the net directory
where t
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow)
--
You received this bug notification becaus
** Summary changed:
- Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
+ Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Public bug reported:
* Explain the bug
Running DDOS test on tcp port 22 will trigger kernel crash.
* Brief explanation of fixes
Do not update stateful expressions if lookup is inverted
* How to test
Configuration nftables with config file below:
flush ruleset
table inet filter {
chain inpu
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 2006391
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
On Focal and Kinetic the fcnal-test.sh does not run because it reports
that 'nettest' command not found; skipping tests
This is due to the nettest binary not being found in the path and
skipping the tests, but it is built and exists in the net directory
where the tests are ru
** Changed in: ubuntu-z-systems
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Status: Confirmed => 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
Is there a message in the kernel ring buffer (dmesg) or kernel audit
log?
--
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/1991691
Title:
cannot change mount namespace
Status in Linux:
I have sent a backported patch to the mailing list:
https://lists.ubuntu.com/archives/kernel-team/2023-February/136838.html
** Patch added:
"v2-0001-selftest-net-Improve-IPV6_TCLASS-IPV6_HOPLIMIT-te.patch"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000709/+attachment/5645117/+files/
While this patchset is to fix an already landed fix since v5.19-rc1, I added it
directly into experimental kernel PPA in
https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/intermediate-kernel:
* linux-unstable version 6.2.0-9008.8+exp.49
-
https://launchpad.net/~canonical-hwe-team/+arch
** Patch added:
"0001-selftest-net-Improve-IPV6_TCLASS-IPV6_HOPLIMIT-tests.patch"
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000709/+attachment/5645116/+files/0001-selftest-net-Improve-IPV6_TCLASS-IPV6_HOPLIMIT-tests.patch
--
You received this bug notification because you are a mem
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 2006303
and then change the status of the bug to 'Confirmed'.
If, due to the nature
Public bug reported:
The following additional packages will be installed:
linux-libc-dev:i386
The following packages will be upgraded:
linux-libc-dev:i386
1 upgraded, 0 newly installed, 0 to remove and 20 not upgraded.
341 not fully installed or removed.
Need to get 0 B/1462 kB of archives.
A
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
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/1999882
Title:
[UBUNTU 20.04] KVM: s390: pv: don't allow u
For kernel v6.1 or older, it takes an additional commit 5545b7b9f294
("net: wwan: t7xx: Add NAPI support") to backport.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2006259
Title
This also requires the dummy net config (CONFIG_DUMMY) brought in as a
fix in https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1998244
--
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
While this is only planned for oem-6.0/oem-6.1 and on, mark kinetic as
WONTFIX.
** Changed in: linux (Ubuntu Kinetic)
Status: New => Won't Fix
** Changed in: linux (Ubuntu Lunar)
Status: New => Triaged
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => High
** Changed
This affects kernel >= v5.19-rc1.
** Also affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also aff
Public bug reported:
Upstream commit d10b3a695ba0 ("net: wwan: t7xx: Runtime PM") introduced
support for Runtime PM for this driver, but due to a bug in the
initialization logic the usage refcount would never reach 0, leaving the
feature unused. This patchset addresses that, together with a bug fo
I had been using the 525 Nvidia drivers successfully for several months.
Today I ran an `apt upgrade` after being away from my PC for a month,
and the upgrade caused this graphics driver issue to occur again.
I fixed it by running:
sudo apt install --reinstall nvidia-driver-525/jammy
sudo apt
Thank you Dimitri! If these will be run for the package in -proposed as
part of the validation, I'll accept the new upload from the Rejected
queue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad
Confirmed that broadcom-sta-dkms (6.30.223.271-23~22.04.1) can be
installed and built on a jammy system running the hwe-5.19 kernel:
===
Setting up broadcom-sta-dkms (6.30.223.271-23~22.04.1) ...
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 5
Confirmed that bcmwl-kernel-source
(6.30.223.271+bdcom-0ubuntu10~22.04.1) can be installed and built on a
jammy system running the hwe-5.19 kernel:
===
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu10~22.04.1) ...
Loading new bcmwl-6.30.223.271+bdcom
** No longer affects: hundredpapercuts
--
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/1460768
Title:
Unable to build kernel 3.19.0-18
Status in linux package in Ubuntu:
Confirmed
Bug
** Changed in: linux-meta-allwinner-5.17 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta-allwinner-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1994490
Title:
RISCV: segfaults after i
I've been trying to reproduce this on a few different kernels now, I can
not reproduce this with
The default 5.19 kernel that 22.10 comes with (official images, after updating).
The latest mainline 6.1.10 kernel release.
I have 2.58 snapd installed, and on both I can start slack.
I can however r
@Kai-Chuan, per requested by you, we picked up a XPS 17, the touch pad
works well under Ubuntu 22.04.
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997472/+attachment/5645064/+files/dmesg.txt
--
You received this bug notification because you are a mem
Thx Roxana, with that I'm updating the affected 'L' series to 'In
Progress', 'K' and 'J' to 'Fix Committed' and 'F' to New.
** Changed in: linux (Ubuntu Lunar)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Kinetic)
Status: Triaged => Fix Committed
** Changed in: lin
Patch is applied for both focal and jammy from upstream by Kamal:
--
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/2002256
Title:
[UBUNTU 22.04] zfcp: fix double free of FSF request when q
Thx Roxana for the update and details.
That allows me to update the affected series K, J and F here to 'Fix Committed'
too
and 'L' to 'In Progress'.
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Status: New => Fix Committed
** Changed
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: ubuntu-z-systems
Status: Confirmed => 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
The fix was merged upstream:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=a6efc42a86c0
It affects 5.18+
--
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/2000709
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Andrei Gherzan (agherzan)
** Changed in: linux (Ubuntu Kinetic)
Assign
The apparmor patch in this bug is not in the upstream kernel because the
userns mediation code it is patching is not in the upstream kernel. If
the mainline kernel ppa it is failing it will be for a different reason.
--
You received this bug notification because you are a member of Kernel
Package
Already pushed from upstream for current cycle (2023.01.30) for
kinetic and jammy
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001726
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2001570
I will push the fix for focal as well, but it will be there in the next
cycle.
--
You receiv
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Package
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin2004
--
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/2002256
Title:
[UBUNTU 22.04] zfcp: fix double free of FSF
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1011.11
---
linux-oem-6.0 (6.0.0-1011.11) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2001806)
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2003453)
* Revoke & rotate
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1011.11
---
linux-oem-6.0 (6.0.0-1011.11) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2001806)
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2003453)
* Revoke & rotate
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1011.11
---
linux-oem-6.0 (6.0.0-1011.11) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2001806)
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2003453)
* Revoke & rotate
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
This bug was fixed in the package linux-oem-6.0 - 6.0.0-1011.11
---
linux-oem-6.0 (6.0.0-1011.11) jammy; urgency=medium
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2001806)
* jammy/linux-oem-6.0: 6.0.0-1011.11 -proposed tracker (LP: #2003453)
* Revoke & rotate
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1006.6
---
linux-oem-6.1 (6.1.0-1006.6) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1006.6 -proposed tracker (LP: #2003454)
* Fix for S0i3 resume on GFX11 (LP: #2003369)
- drm/amdgpu: skip MES for S0ix as well sin
Patch is applied for both focal and jammy from upstream by Kamal:
https://bugs.launchpad.net/bugs/2002347
https://bugs.launchpad.net/bugs/2003122
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
** Tags added: originate-from-2004217 stella
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2002968
Title:
Fix flicker display problem on some panels which support PSR2
Status i
Public bug reported:
Pull request:
https://github.com/alsa-project/alsa-ucm-conf/pull/261
[Impact]
Mic mute LED doesn't work on Intel-based Dell laptops.
[Fix]
Due to recent change on how kernel creates sound LEDs, there are two captures
are registered, one from SoF and one from HDA. The SoF on
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/2004534
Title:
Lenovo IdeaPad 3 15ABA7 never
Thanks for the bug report. I can see it happening in:
[ 870.506] (II) modeset(0): Modeline "1366x768"x0.0 76.30 1366 1404 1426
1592 768 771 777 798 -hsync -vsync (47.9 kHz eP)
[ 1932.032] (II) config/udev: removing device PixArt USB Optical Mouse
[ 1932.033] (**) Option "fd" "29"
[ 1932.
70 matches
Mail list logo