In the guest VM, what output do you get from:
find /lib/modules -name vmwgfx.ko
?
--
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/1988488
Title:
Screen freeze at the moment of login
In the guest VM, what output do you get from:
find /lib/modules -name vmwgfx.ko
--
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/1988488
Title:
Screen freeze at the moment of login on
** Summary changed:
- test_verifier in ubuntu_bpf failed with 40 test cases on Jammy
+ test_verifier in ubuntu_bpf failed with 40 test cases on Jammy 5.15 generic
kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
That change did not help, the display still did freeze.
The content of /etc/environment was:
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
MUTTER_DEBUG_FORCE_KMS_MODE=simple
The host OS is a minimal
Tested with the latest 5.15 mainline kernel 5.15.71-051571-generic, and
this is still reproducible.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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 1991346
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
Issue caught by sut-scan, this is not a regression as we are suffering
from another build issue in the past.
+ Spotted on Jammy 5.15.0-50-generic and can be found on variants.
+
Step to reproduce:
1. Build the ubuntu_bpf test
2. Run the following in
** Description changed:
- Mobile broadband does not work after suspend on Thinkpad t460s with built-in
Sierra Wireless EM7455.
- It switches constantly on and off then. The only solution to repair the
situation is to go to Windows and switching on there.
- After check in Settings > Mobile
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430800
** Merge proposal linked:
https://code.launchpad.net/~binli/pc-enablement/+git/oem-gap-allow-list/+merge/430802
--
You received this bug notification because you are a member
Public bug reported:
I can't upgrade my ubuntu distribution because this bug
ubuntu 20.04.3 lts
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-modules-5.15.0-46-generic (not installed)
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Uname: Linux
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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
All autopkgtests for the newly accepted linux-meta-raspi-5.4 (5.4.0.1071.71)
for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
xtables-addons/unknown (arm64)
wireguard-linux-compat/unknown (arm64)
rtl8821ce/unknown (arm64)
I've been asked to prepare a summary of the current status of this bug:
- there's a grub2 security update that's been published and then pulled:
https://launchpad.net/ubuntu/+source/grub2-unsigned/2.06-2ubuntu10/+publishinghistory
This problem did not occur on 6.0.0-06rc7-generic for 2 days, even
with VA-API enabled. As I have moved on to 22.10, I will try to
downgrade to the stable 5.19 and see if the problem still exists.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Tags added: foundations-todo
--
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/1990621
Title:
PXE Boot contains wrong suggested link to ISO for live file system
Status in casper
** Tags added: foundations-todo
--
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/1990964
Title:
FTBFS on kinetic
Status in linux package in Ubuntu:
In Progress
Status in strace package
** Changed in: linux
Status: Confirmed => 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/1806437
Title:
acpi PNP0C14:02: duplicate WMI GUID
During the architectural design of the WMI subsystem an assumption was
made that there was a 1:1 mapping of WMI GUIDs (that is they're unique).
This hasn't caused MAJOR functional problems, but this was proven wrong,
as it's possible to fetch multiple BMOFs.
This change makes it so that if you
(In reply to Laurent Bonnaud from comment #18)
> Thanks a lot! I am looking forward to kernel 6.1...
Was this anything but just cosmetic? I looked at the patch and am
running it now and nothing in the dmesg has changed (nor any
functionality) except the messages aren't printed any longer.
--
Thanks a lot!
I am looking forward to kernel 6.1...
--
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/1806437
Title:
acpi PNP0C14:02: duplicate WMI GUID
This is fixed by the following commit which will be in 6.1:
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git/commit/?h=review-hans=134038b075cb1dae21623499d765973d286ac94a
--
You received this bug notification because you are a member of Kernel
Packages, which is
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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
** Also affects: linux-bluefield (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-bluefield (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification
** Description changed:
[Impact]
The kernel lrm packages have a mechanism to auto-generate transitional
packages by adding a line to 'debian/package.config' in the following
format
transitional
Example:
transitional 450-oem-20.04 450-generic amd64
When being
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 1990394
and then change the status of the bug to 'Confirmed'.
If, due to the
** Tags added: kinetic
** Package changed: ubuntu => linux (Ubuntu)
--
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/1990394
Title:
Wifi and Bluetooth with rtl8852be not working
Status
You have been subscribed to a public bug:
Realtek rtl8852be Wifi and Bluetooth not working on Kubuntu 22.04 and Ubuntu
22.10 (daily, 20.9.2022).
Works on 22.04 just by compiling it yourself as Kernel-Module.
04:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device b852
Subsystem:
linux-gkeop-5.15 is out of scope for this bug (does not exist for s390x).
To unblock the process I'll add the 'verification-done-focal' tag.
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
linux-gkeop-5.15 is out of scope for this bug (does not exist for s390x).
To unblock the process I'll add the 'verification-done-focal' tag.
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux 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/1991286
Title:
package linux-tools-5.15.0-48
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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 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 1991285
and then change the status of the bug to 'Confirmed'.
If, due to the
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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-
gkeop-5.15/5.15.0-1003.5~20.04.2 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
To me it looks like the boot-and-services sub-tests got a lot less
reliable on armhf in Focal. The previous systemd version had a higher
chance of passing those. There always was root-unittests which required
multiple attempts. But now from about 10 attempts there was one which
had root-unittests
Public bug reported:
This is a scripted bug report about ADT failures while running systemd
tests for linux/5.4.0-128.144 on focal. Whether this is caused by the
dep8 tests of the tested source or the kernel has yet to be determined.
Testing failed on:
armhf:
Public bug reported:
Bonjour,
Des paquets synaptic ne s'installent pas.
Avec Synaptic, il est difficile de savoir quoi installer alors qu'avec Ubuntu
Software, les
icones informaient tout de suite de quoi il s'agissait.
Ubuntu software ne fonctionne pas, comment faire ?
Avec mes remerciements
Public bug reported:
During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi
armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no
longer appears in /proc/asound/cards; only the Headphones output (from
the AUX socket on the board) appears.
I checked with the
yup I am also facing a bug, sometimes it does not work. Found a solution
for it just run sudo update-grub and restart the system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@xaviermd,
Thanks your feedback, the oem-sutton.newell-meta is expected, it's used
to help generate the OEM repository.
--
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/1990870
Title:
Here is what was upgraded :
Install: systemd-hwe-hwdb:amd64 (249.11.1, automatic)
Upgrade: udev:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6),
systemd-timesyncd:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6),
libpam-systemd:amd64 (249.11-0ubuntu3.4, 249.11-0ubuntu3.6),
fix released as upgrading hardware SOC and BIOS to latest. Old ADL-P will have
this issue.
revert the commits above will also fix the issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Canonical doesn't reproduce this issue because their hardware should be new.
but we need point out the commits above maybe bring some hang issue and flicker
issue for graphics.
I will close this bug since we root cause this. Thanks All
** Changed in: intel
Status: New => Fix Released
** Changed in: linux-oem-5.17 (Ubuntu)
Status: Fix Committed => Invalid
--
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/1942160
Title:
PCIE LnkCtl ASPM not enabled under
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
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/1991215
Title:
test_verifier in ubuntu_bpf failed with 40 test cases on
Anbox Cloud is affected by this too. We used shiftfs by default until
our 1.14 release in May 2022. According to the metrics we have there are
still a few users around with the 1.13 release which enables shiftfs on
ZFS.
--
You received this bug notification because you are a member of Kernel
@quanxian, we've found the patches that cause the system hang on J0
devices as following.
a8951f369fde UBUNTU: SAUCE: PCI/ASPM: Enable LTR for endpoints behind VMD
9942df2fda84 UBUNTU: SAUCE: vmd: fixup bridge ASPM by driver name instead
--
You received this bug notification because you are a
** Changed in: linux-firmware (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1990945
Title:
i915: Add GuC v70.1.1 for
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 1991220
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
1. Power on SUT and install Ubuntu 18.04.6
(ubuntu-18.04.6-live-server-amd64.iso)
2. Boot into OS then run dmesg to check if there are unexpected errors or
warnings. (=> failed, there are dpc errors in dmesg:
[1.178079] dpc: probe of :00:10.0:pcie010 failed with
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1989172
Title:
mlxbf-pmc: error when reading
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1989495
Title:
mlxbf_gige: need to clear MDIO
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield in Ubuntu.
** Changed in: linux-bluefield (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: linux-bluefield (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-bluefield 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 1991215
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
With the bpf build issue fixed (bug 1980517) on Jammy, the ubuntu_bpf
test can now be tested.
There are 40 failures discovered in test_verifier:
#21/u BPF_ATOMIC_AND without fetch FAIL
#21/p BPF_ATOMIC_AND without fetch FAIL
#22/u BPF_ATOMIC_AND with fetch FAIL
#22/p
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: Incomplete => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
@Arun, does the headset work OK on audio input/output?
--
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/1981433
Title:
[Asus Zenbook UX3402ZA] Sound doesn't work at all
Status in linux
This bug is awaiting verification that the linux-xilinx-
zynqmp/5.4.0-1018.21 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
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1988797
Title:
pcieport :00:1b.0: PCIe Bus Error: severity=Uncorrected (Non-
Fatal),
@xaviermd,
Which oem package was updated? From your logs, I found you use kubuntu
while not the OEM image. Thanks!
--
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/1990870
Title:
Cannot
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1990920
Title:
Fix resume on AMD platforms when TBT monitor is plugged
Status in HWE
86 matches
Mail list logo
