Hello again Zhanglei.
This means that so far:
3000: BUG
3002: NO BUG
3003: NO BUG
3004: NO BUG
You can find kernel 3005 here:
https://kernel.ubuntu.com/~kmously/kernel-kmously-039f206-aRqC/
Please ensure you are running version -3005. Thank you
--
You received this bug notification because
Sorry. Like this?
for (tc = 0U; tc < self->aq_nic_cfg.tcs; tc++) {
for (i = 0U; self->aq_vecs > i; ++i) {
aq_vec = self->aq_vec[i];
if (!aq_vec)
break;
data += count;
count = aq_vec_get_sw_stats(aq_vec, tc, data);
}
}
--
You received this bug notification because you are
Thanks Zhanglei. I am building 3005 now. It should be ready in about 30
minutes. I will update again soon
--
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/1971576
Title:
SATA device hot
Public bug reported:
System info:
Description:Ubuntu 20.04.4 LTS
Release:20.04
Linux kot9ra-Air 5.17.7+ #2 SMP Fri May 13 05:27:24 BST 2022 x86_64 x86_64
x86_64 GNU/Linux
Building log:
Building for 5.17.7+
Building for architecture x86_64
Building initial module for 5.17.7+
ERROR
The following two lines shouldn't be omitted:
data += count;
count = aq_vec_get_sw_stats(aq_vec, tc, data);
--
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/1958770
Title:
Hello Kahled, Version 3004 hot plug can pass. thanks //Mao
--
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/1971576
Title:
SATA device hot plug regression on AMD EPYC (Asus) server
I have implemented your suggestion, so far no issues. I'm going to kick
off my backup now and do some more testing later.
** Patch added: "aq_nic.c.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958770/+attachment/5589366/+files/aq_nic.c.patch
--
You received this bug
** Tags added: originate-from-1969557 somerville
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17
All autopkgtests for the newly accepted linux-meta-kvm (5.15.0.1006.6) for
jammy have finished running.
The following regressions have been reported in tests triggered by the package:
oss4/4.2-build2010-5ubuntu9 (amd64)
digimend-dkms/10-4 (amd64)
rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu15
Thanks for the bug report.
This sounds like a hardware problem, most likely just new batteries are
required.
Wired mice or wireless with a dongle use the same code paths so clearly
that's working for some mice. I don't think there's any software bug
here.
** Package changed: xorg (Ubuntu) =>
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable;
You have been subscribed to a public bug:
What happens:
Wireless mouse shows up under `lsusb` list but doesn't control the
cursor.
Expected behavior:
The mouse controls the cursor.
Background:
I purchased a "Mini 2.4 GHz Wireless Optical Mini Finger Mouse Mice For
Laptop PC Computers"
Please try selecting 'Ubuntu on Xorg' on the login screen.
Please also upgrade to Ubuntu 22.04 as soon as you can.
--
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/1973143
Title:
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/1971202
Title:
[nouveau][amdgpu] Freeze in
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- [nouveau][amdgpu] Freeze
+ [nouveau][amdgpu] Freeze in 5.15.0-27.28-lowlatency (but 5.17.6 works)
--
You received this bug notification because you are a member of
You have been subscribed to a public bug:
happens with both xorg and wayland
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-lowlatency 5.15.30
Uname: Linux 5.15.0-27-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82
Hi, following up on this -
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970426/comments/9
GRUB PARAM - `i915.enable_dc=0 intel_idle.max_cstate=2` has fixed the
flicker for me.
$ uname -a
Linux home 5.15.0-30-generic #31-Ubuntu SMP Thu May 5 10:00:34 UTC 2022 x86_64
x86_64 x86_64
I think that's a bit different to the original version, which breaks out
the loop as soon as "aq_vec" evaluates to false.
So, instead of
if (aq_vec) {
...
}
Should be
if (!aq_vec)
break;
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux-gcp (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-gcp in Ubuntu.
https://bugs.launchpad.net/bugs/1964527
Title:
Enable CONFIG_UNICODE for
** Package changed: linux (Ubuntu) => joystick (Ubuntu)
** Changed in: joystick (Ubuntu)
Status: Confirmed => New
--
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/1973216
Title:
** Package changed: ubuntu => linux (Ubuntu)
** Package changed: linux (Ubuntu) => unattended-upgrades (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/1973237
Title:
WiFi
You have been subscribed to a public bug:
After an unattended upgrade (the packages upgraded listed at the end), at least
following things crashed:
- WiFi adapter - not seen by the system
- system speakers - not seen
- cannot regulate the brightness of my laptop screen
Used system:Ubuntu
Alas! I spoke to seen. The seeming "workaround" only lasted for one
boot, and after that, the ~180 seconds delay is back to stay, although
the Intel IOMMU is still disabled.
So this issue is "sporadic". Maybe even a race condition... :(
And maybe not even related to the intel-lpss driver: The
Thanks Zhanglei. This means that so far:
3000: BUG
3002: NO BUG
3003: NO BUG
We are getting closer. This is the remaining set of patches:
00501b41aaf73f (tag: test-3000, tag: fail1) s390/pci: move pseudo-MMIO to
prevent MIO overlap
14914e943b0ca5 cpufreq: Fix get_cpu_device() failure in
When the machine is booted, open a terminal and run "dmesg" to see on
what the kernel was stuck so long. In my case, it was the intel-lpss PCI
device initialization, and I fixed it by disabling the Intel IOMMU. If
you get similar results, this issue might be a duplicate of mine which I
reported
With Wayland, hibernate never works. NVIDIA 510.
Switching back to X11, and it works.
--
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/1970957
Title:
suspend problem
Status in linux
After grepping dmesg for all lines about the "00:15" devices, I found
two lines starting with "DMAR:", which made me think of another machine
running debian which had issues with DMAR: devices that were related to
the Intel IOMMU.
So I tried the workaround I knew from there:
Edit
After finding someone reporting the same issue
(https://forums.linuxmint.com/viewtopic.php?t=373747=2175201) and
reading that the machine may come alive after a while, I found that
indeed after 3 minutes the machine works. dmesg that reveals that it
seemingly was the initialization of the
Unfortunately, this command at terminal yields:
mic@mic-Aspire-E5-576G:~$ apport-collect 1973234
ERROR: The python3-launchpadlib package is not installed. This functionality is
not available.
mic@mic-Aspire-E5-576G:~$
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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 1973234
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
I would like to report the latest kernel update: 4.15.0.177.166 to my
Linux Mint 19.1 systems displayed the following problems:
1. After Update - Boot process is VERY SLOW.
2. After Update - Once desktop comes up, mouse and keyboard are disabled for
approx. 2 minutes.
3.
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 1973203
and then change the status of the bug to 'Confirmed'.
If, due to the
** 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/1973203
Title:
Kubuntu does not shut down properly
Status in linux package in Ubuntu:
You have been subscribed to a public bug:
Hello
I'm having issues with Kubuntu 22.04 on a Thinkpad X1 Carbon 4th generation.
After a clean install without encryption, when I turn off the laptop, it does
not shut down properly (some lights on my keyboard stay turned on even though
the power
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589277/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589278/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589275/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589274/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589276/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589273/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589265/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589266/+files/Lsusb.txt
--
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/1973216
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589268/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589272/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589269/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589267/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589271/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589270/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589261/+files/CRDA.txt
--
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/1973216
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589263/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589264/+files/Lspci.txt
--
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/1973216
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1973216/+attachment/5589262/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected focal
** Description changed:
What I expected to happen:
I plug in Saitek Cyborg Evo Force joystick, run ffmvforce or ffcfstress and
can adjust the force-feedback.
What happenend instead:
No force-feedback at all.
ffcfstress
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 1973216
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
What I expected to happen:
I plug in Saitek Cyborg Evo Force joystick, run ffmvforce or ffcfstress and can
adjust the force-feedback.
What happenend instead:
No force-feedback at all.
ffcfstress raises error "ERROR: device (or driver) has no constant force
feedback
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.1-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thank you @bsdz, compiles and works flawlessly since yesterday. UBSAN is
happy, performance is as expected.
@kaihengfeng, is this patch suitable for inclusion upstream?
** Patch added: "aq_nic.c.patch"
This bug was fixed in the package linux - 5.15.0-30.31
---
linux (5.15.0-30.31) jammy; urgency=medium
* jammy/linux: 5.15.0-30.31 -proposed tracker (LP: #1971685)
* Packaging resync (LP: #1786013)
- [Packaging] update variants
- debian/dkms-versions -- update from
** Changed in: linux-azure (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-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1971701
Title:
Azure: swiotlb patch needed for
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Assignee: (unassigned) => Jian Hui Lee (jianhuilee)
** Changed in: linux-intel-iotg (Ubuntu Jammy)
Importance: Undecided => Medium
--
You received this bug
Same here with my ThinkPad E460. Everything was working fine with 20.04.
--
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/1971437
Title:
linux-image-5.15.0-27-generic causes Thinkpad
https://lists.ubuntu.com/archives/kernel-team/2022-May/130246.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1973169
Title:
[Azure][CVM] Fix swiotlb_max_mapping_size() for
*** This bug is a duplicate of bug 1958191 ***
https://bugs.launchpad.net/bugs/1958191
Same here, after upgrading from 20.04 on my ThinkPad E460 which had been
working fine for years.
lshw | grep -A2 display
*-display
description: VGA compatible controller
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/1973167
Title:
Public bug reported:
SRU Justification
[Impact]
Description of problem:
When the v5.15 linux-azure kernel is used for CVM on Azure, it uses swiotlb for
bounce buffering.
We recently found an issue in swiotlb_max_mapping_size(), which is used by the
SCSI subsytem APIs, which are used by the
Public bug reported:
After updating to linux-image-4.15.0-177-generic, my machine completely
freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI
mode. The mouse pointer is frozen, the keyboard does not even respond to
CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no
Public bug reported:
This package still suggests crda to be installed whereas it was removed
from jammy already: simply remove this from debian/control as done in
[1].
[1]
https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/13612257/+listing-
archive-extra
** Affects:
** 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/1973034
Title:
linux generic fails to boot on azure arm64 instance
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
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/1970819
Title:
5.15 pc-kernel uc22 snap fails to load bluetooth
This would fail on another ARM64 node howzit-kernel as well with Jammy
5.15.0-27-generic
But without the messages from mpt3sas_cm0
dmesg output:
[ 2945.964263] LTP: starting read_all_sys (read_all -d /sys -q -r 3)
[ 2947.922462] WARNING! power/level is deprecated; use power/control instead
[
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/1973145
Title:
[ThinkPad P1 Gen 4i][Nvidia
** Summary changed:
- kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17
ARM64 "helo-kernel"
+ kernel oops triggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17
ARM64 "helo-kernel"
** Description changed:
Issue found on Jammy 5.17.0-8-generic #8~22.04.2-Ubuntu
Thanks. It kind of looks like the Nvidia driver is directly aware of the
USB-C/Thunderbolt port. So maybe it's not surprising then that the order
of connection matters.
For now that suggests the bug is somewhere between the Nvidia driver and
the kernel.
** Package changed: xorg-server (Ubuntu)
It's the external monitor which is facing issue.
On Thu, 12 May 2022, 2:05 pm Daniel van Vugt, <1973...@bugs.launchpad.net>
wrote:
> Also which monitor is displaying the wrong resolution?
>
> ** Summary changed:
>
> - monitor resolution issue
> + Wayland session limited to 1024x768
>
> **
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 1973153
and then change the status of the bug to 'Confirmed'.
If, due to the
** Summary changed:
- kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.17 ARM64
+ kernel oops tiggered by read_all_sys in ubuntu_ltp/fs on J-5.15 / J-5.17
ARM64 "helo-kernel"
** Description changed:
- Issue found on 5.17.0-8-generic #8~22.04.2-Ubuntu with ARM64 node helo-
- kernel
Hi, Alberto,
from the output below, auto-import is disabled. what this function is
used for？
# /usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n10
auto-import is disabled on classic
** Changed in: snapd (Ubuntu)
Status: Incomplete => In Progress
--
You received this
Public bug reported:
Issue found on 5.17.0-8-generic #8~22.04.2-Ubuntu with ARM64 node helo-
kernel
The read_all_sys test in fs from ubuntu_ltp will cause kernel oops and
test will timeout.
Test log:
<<>>
tag=read_all_sys stime=1652343855
cmdline="read_all -d /sys -q -r 3"
contacts=""
This bug was fixed in the package linux-firmware -
20220429.gitac21ab5d-0ubuntu1
---
linux-firmware (20220429.gitac21ab5d-0ubuntu1) kinetic; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] Drop rsync from Build-Depends
- [Packaging] Move obsolete scripts
-
This bug was fixed in the package linux-firmware -
20220429.gitac21ab5d-0ubuntu1
---
linux-firmware (20220429.gitac21ab5d-0ubuntu1) kinetic; urgency=medium
* Miscellaneous Ubuntu changes
- [Packaging] Drop rsync from Build-Depends
- [Packaging] Move obsolete scripts
-
If you are using a USB-C dock then please see bug 1970495.
Otherwise if you think the USB-C port might be wired directly to the
Nvidia GPU then please see bug 1960865.
When the bug occurs next please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the
You have been subscribed to a public bug:
The external Samsung 34" monitor connects fine with HDMI, but not on USB-C.
It worked for a short amount of time at one point early after installing Ubuntu
22.04, but not since.
No difference with disconnect / reconnect, reboot, etc.
ProblemType: Bug
** Tags added: oem-priority originate-from-1967153 somerville
--
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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if
Thanks. 5.4.0-112.126 works for me.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1956086
Title:
Also, if you have the time then please upgrade to Ubuntu 22.04. Ubuntu
21.10 will reach end-of-life in July.
https://wiki.ubuntu.com/Releases
** Summary changed:
- Wayland session limited to 1024x768
+ [impish] Wayland session limited to 1024x768
--
You received this bug notification because
Also which monitor is displaying the wrong resolution?
** Summary changed:
- monitor resolution issue
+ Wayland session limited to 1024x768
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux
You have been subscribed to a public bug:
Even though my monitor support maximum resolution, I can only set it to
1068X768.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
** Also affects: linux-oem-5.14 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Assignee: (unassigned) => koba (kobako)
** Also affects: linux-oem-5.17 (Ubuntu)
** Package changed: ubuntu => linux-signed-hwe-5.13 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1973113
Title:
package: libc6 2.31-0ubuntu9.9
Status in
You have been subscribed to a public bug:
new libc6:amd64 package pre-installation script subprocess returned
error exit status 2
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-40.45~20.04.1-generic
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/1973139
Title:
package
** Changed in: oem-priority
Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)
--
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/1969432
Title:
5.17 kernel won't load
Public bug reported:
Only a message that there was a problem discovered with the question to
report this via a bug.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-modules-extra-5.4.0-110-generic (not installed)
ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178
Uname:
Private bug reported:
Ubuntu 22.04 installation crashes on our Intel Sapphire Rapids proto server
which is targeting Telco workloads.
Attaching the console logs.
Currently, it looks like disabling VT-D option in BIOS settings helps mitigate
the issue.
Console logs indicate something is wrong
Adding more hardware: I have the same problem with a Thinkpad T460s on 22.04.
Ubuntu 21.10 worked fine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967721
Title:
Laptop never
95 matches
Mail list logo
