If it helps at all, I also have my laptop connected to a Samsung monitor
via a USB Type C port which it receives the video and charging signal.
As this article also mentions:
https://gitlab.freedesktop.org/drm/amd/-/issues/2282
--
You received this bug notification because you are a member of
All autopkgtests for the newly accepted linux-restricted-modules (5.19.0-37.38)
for kinetic have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.1 (i386)
Please visit the excuses page listed
Kernel 5.19.0-3035-generic x86_64 has good behavior.
I have not seen the artifacts with this version while performing the
typical workflow that normally caused it to manifest.
https://people.canonical.com/~khfeng/lp2002986-2/
--
You received this bug notification because you are a member of
broadcom-sta-dkms can be found on the ISO pool on both lunar-desktop and
lunar-desktop-legacy. In the live session, "ubuntu-drivers install"
reports that "All the available drivers are already installed", but
broadcom-sta-dkms isn't installed. "ubuntu-drivers debug" reports
broadcom-sta-dkms as
** Also affects: broadcom-sta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to broadcom-sta in Ubuntu.
https://bugs.launchpad.net/bugs/2008142
Title:
bcmwl driver not installed
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.1
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 pulseaudio into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-1ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
This bug is awaiting verification that the linux/5.19.0-37.38 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-kinetic' to 'verification-done-kinetic'. If the
problem still exists,
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
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Your bug report is more likely to get attention if it is made in
English, since this is the language understood by the majority of Ubuntu
developers. Additionally, please only mark a bug as "security" if it
shows
** Description changed:
- I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
- It appears to be an issue with graphics as I can access a console and
- login. I am able boot with 5.19.0-32-generic. I am using nvidia
- drivers.
+ I updated software this morning and on reboot
--
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)
Status in linux
All autopkgtests for the newly accepted linux-restricted-modules-gcp
(5.4.0-1102.111) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386)
Please visit the excuses page
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 2009226
and then change the status of the bug to 'Confirmed'.
If, due to the
I am not running in problematic update but I have attached sudo lspci
-vnvn > lspci-vnvn.log
** Attachment added: "output of sudo lspci -vnvn > lspci-vnvn.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+attachment/5651446/+files/lspci-vnvn.log
--
You received this bug
Public bug reported:
I update this morning and ubuntu kernel 5.19.0-35 gives black screen.
It appears to be an issue with graphics as I can access a console and
login. I am able boot with 5.19.0-32-generic. I am using nvidia
drivers.
** Affects: linux (Ubuntu)
Importance: Undecided
Public bug reported:
Sorry, just found a crash dialog sitting behind other windows
ProblemType: Package
DistroRelease: Ubuntu 22.10
Package: nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1
Uname: Linux 6.1.14-x64v2-xanmod1 x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion:
Public bug reported:
Erro nos ajsutes de brilho e som pelo teclado, erro na inicialização em
tabelas ACPI sobre backlight PCOO.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-bluefield/5.4.0-1059.65
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-bluefield/5.4.0-1059.65
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-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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-oem-6.1/6.1.0-1008.8
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,
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency
(5.15.0-68.75) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:
nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386)
Please visit the excuses page
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-hwe-5.19 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu.
Here are the binary dump of the smbios type 9 for one of the slots, as
well as the decoded information and the appropriate section in the spec.
I have also attached a copy of the spec in a previous comment.
--
You received this bug notification because you are a member of Kernel
Packages, which
** Attachment added: "dmidecode-3.png"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651414/+files/dmidecode-3.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
** Attachment added: "dmidecode-2.png"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651413/+files/dmidecode-2.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
** Attachment added: "dmidecode-1.png"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651412/+files/dmidecode-1.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
HI Mauricio,
The following command did not work : sudo apt install --allow-downgrades
dmidecode/jammy-updates
I was able to download and install dmidecode 3.4 to my jammy instance. I
checked the version with dmidecode --v and it stated 3.4.
I uploaded my updates bios with slot information, slot
** Tags added: oem-priority originate-from-2006667 stella
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2009164
Title:
Fix screen that remains blank forever after it gets
** Also affects: linux-raspi (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-raspi (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
** Also affects:
Public bug reported:
[Impact]
Once screen is locked under gnome-shell, the screen never wakes up and
remains in blank forever.
[Fix]
"drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma
LUT operations in atomic context, so userspace can no longer misuse libdrm.
"drm/i915:
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/2009163
Title:
package
Public bug reported:
doing apt update and got this.
ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: linux-headers-6.1.0-16-generic 6.1.0-16.16
ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
Uname: Linux 5.19.0-21-generic aarch64
NonfreeKernelModules: prl_fs_freeze prl_fs
Public bug reported:
can not open software
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libnvidia-compute-418-server (not installed)
ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85
Uname: Linux 5.15.0-67-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
This is a completely different problem. Please open a new bug by running
'ubuntu-bug linux-firmware'.
--
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/1969966
Title:
No support for Intel
** Tags added: patch
--
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/2009142
Title:
nvidia-dkms-390 FTBS with linux 6.2
Status in nvidia-graphics-drivers-390
Hello everyone
I was also getting the following error:
```
Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2)
```
I have noticed that the `ibt-19-0-3.sfi` file is not present on the
system. As I was unable to find it anywhere on the Internet, I did the
following:
```
All autopkgtests for the newly accepted linux-meta-gcp (5.15.0.1031.26) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, arm64)
Please visit the excuses page listed below and
Please can you check if there is a crash file in /var/crash and if so share this
and ideally the entire /var/log folder (or at least /var/log/installer)? Thx.
We don't have a 32Gbit FCP adapter to test with.
** Package changed: linux (Ubuntu) => subiquity (Ubuntu)
** Also affects:
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2004146
Title:
Lunar update: v6.1.7 upstream
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2004147
Title:
Lunar update: v6.1.8 upstream
** Changed in: linux-oem-6.1 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
https://bugs.launchpad.net/bugs/2007583
Title:
Jammy update: v6.1.10 upstream stable
** Changed in: linux-oem-6.1 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-oem-6.1 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: New => Triaged
--
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/2009142
Title:
nvidia-dkms-390
debdiff in attatch allows to build nvidia-dkms-390 with linux 6.2.
** Patch added: "nvidia-390-support-linux-6.2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5651284/+files/nvidia-390-support-linux-6.2.debdiff
--
You received this
This might go a little bumpy. Normally the hwe-5.19 kernel is updated
when the kinetic one is. But states here likely do not follow
automatically.
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.19 (Ubuntu Kinetic)
Importance:
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/2009063
Title:
Inconsistent autopkgtest failures in xdp-tools lunar
Default Comment by Bridge
** Attachment added: "host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer"
https://bugs.launchpad.net/bugs/2009141/+attachment/5651277/+files/host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer.txt
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug
Public bug reported:
[Impact]
nvidia-dkms-390 fails to build with linux 6.2:
/var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error:
‘struct drm_mode_config’ has no member named ‘fb_base’
244 | dev->mode_config.fb_base = 0;
| ^
[Fix]
You have been subscribed to a public bug:
Bug Description:
Installation of Ubuntu 22.04 on s390x failed with an unknown error just after
having successfully activated a zfcp HBA with Fibre-Channel-attached SCSI disks.
I do see 0.0.100d successfully being online and having paths attached:
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 2009063
and then change the status of the bug to 'Confirmed'.
If, due to the
** Attachment added: "pactl-list-5.19.0-35"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651269/+files/pactl-list-5.19.0-35
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "pactl-list-5.19.0-32"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651268/+files/pactl-list-5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Attachment added: "dmesg-5.19.0-35"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651267/+files/dmesg-5.19.0-35
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in
** Attachment added: "dmesg-5.19.0-32"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651266/+files/dmesg-5.19.0-32
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.19 in
Public bug reported:
After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of
the kernel, I found my HDMI audio output device had disappeared.
Reverting to the -32 release caused it to appear again (hence why I'm
filing the bug against the kernel rather than pulseaudio). I'm
** Attachment added: "apport-bug output as per linux kernel bug procedure
requirements"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+attachment/5651265/+files/2009063.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Note that for the log references where the autopkgtest runs using a 6.1
kernel, there appears to be a regression in the kernel. I can reproduce
those locally and the problem goes away when upgrading to a mainline
6.2.0-060200.202302191831 kernel.
** Also affects: linux (Ubuntu)
Importance:
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009044
Title:
Fix AMDGPU: kernel: RIP:
** Changed in: linux (Ubuntu Lunar)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: New => In Progress
**
@Laurent
so far, uvcvideo patch seems fine & working.
which kernel version will "officially" include UVC Quanta 0408:4035 ?
BR
Giuliano
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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 2009114
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug was fixed in the package xdp-tools - 1.3.0-2ubuntu2
---
xdp-tools (1.3.0-2ubuntu2) lunar; urgency=medium
* d/p/lp-2008214-ppc64le-build-failure.patch: Resolve FTBFS for ppc64le on
Ubuntu (LP: #2008214).
-- Frode Nordahl Thu, 23 Feb 2023
14:02:56 +0100
** Changed
Didn't see this "udpgso_bench_tx: sendmsg: Connection refused" issue on
5.15.0-68.75
** 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.
Didn't see this "udpgso_bench_tx: sendmsg: Connection refused" issue on
5.4.0-145.162
** 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.
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 2009065
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped
It makes no sense to run apport-collect 2009065 in this case :)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Package changed: linux (Ubuntu) => linux-hwe-5.19 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is
Also included in https://launchpad.net/~canonical-hwe-
team/+archive/ubuntu/linux-firmware-staging version
20220329.git681281e4-0ubuntu3.10+exp.65.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
SRU: https://lists.ubuntu.com/archives/kernel-
team/2023-March/137477.html (linux-firmware/jammy)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and
+ -73 firmware are supported bug missing. On one user reported
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: 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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in
** Also affects: linux-firmware (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: oem-somerville-tentacool-meta (Ubuntu Lunar)
Importance: Undecided
Assignee: Kai-Chuan Hsieh (kchsieh)
Status: New
** Also affects: linux-firmware (Ubuntu Jammy)
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
You have been subscribed to a public bug:
lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC
2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua
97 matches
Mail list logo
