*** This bug is a duplicate of bug 1786574 ***
https://bugs.launchpad.net/bugs/1786574
The issue for me was resolved in some recent system updates on Thinkpad
X1 Carbon Gen 9. Just to let you know.
--
You received this bug notification because you are a member of Kernel
Packages, which is
[Expired for linux-hwe-5.8 (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: linux-hwe-5.8 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.8 in Ubuntu.
[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.
Hello?
--
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/1980701
Title:
Relationed with #1975444: mt7921e wifi fails to resume after suspend
Status in linux package in Ubuntu:
Confirmed
*** This bug is a security vulnerability ***
Private security bug reported:
[Impact]
When adding objects/sets/elements on the same nftables netlink batch, there can
be cross-table references. When a table is deleted, references to freed objects
may be left, leading to use-after-free
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
5.15.0-39-generic
--
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/1982479
Title:
[Medion Akoya E3223] Latest kernel breaks LCD screen
Status in linux package in Ubuntu:
Confirmed
Bug
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
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
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Kamal Mostafa
Public bug reported:
This is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1969247 because
the bug is critical and still not fixed in Ubuntu 20.04.
Problem: fallocate() called with FALLOC_FL_ZERO_RANGE flag must return
error on ZFS, but in Ubuntu 20.04 it doesn't return
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
Also, MySQL 8.0.30 was released recently in Ubuntu 20.04. This version
uses falloate() for redo files. This leads to very hard to recover
corruption after MySQL server restart.
https://bugs.mysql.com/bug.php?id=108012
Please fix this in Ubuntu 20.04 ASAP.
** Bug watch added: MySQL Bug System
Public bug reported:
[Summary]
No video output on Thunderbolt monitor.
1. Connect monitor to DUT directly
2. Connect monitor to DUT via Docking
System can detect the monitor and able to change display mode but no
output on the monitor
[Steps to reproduce]
1. Boot to OS
2. Plug an external
Please do as the kernel bot asks and collect the necessary logs for this
bug.
--
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/1981554
Title:
[Ubuntu-22.04] Video mode is not working
Public bug reported:
The 'linux-lowlatency' kernel build (incl. autopkgtest) was triggered in a
kinetic-proposed migration process (for zlib) and runs into a 'regression':
"autopkgtest for linux-lowlatency/5.19.0-1001.1: amd64: Pass, arm64: Regression
♻"
The regression is highly likely not due
> verification-needed-jammy
Juerg - which firmware landed for VCN?
> Binary files /tmp/tmpjfs7by6f/74GQKUQY8t/linux-
firmware-20220329.git681281e4/amdgpu/yellow_carp_vcn.bin and
/tmp/tmpjfs7by6f/0SroKiuHba/linux-
firmware-20220329.git681281e4/amdgpu/yellow_carp_vcn.bin differ
There was a revert
** Tags added: verification-needed-jammy
--
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/1981922
Title:
Upgrade yellow carp DMCUB firmware to fix suspend failure
Status in HWE
I'm unsure if this is really fixed in Jammy
I'm seeing flickering with 5.15.0-41 as well which seems to improve with
i915.enable_dc=0 intel_idle.max_cstate=2
cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.15.0-41-generic root=/dev/mapper/vgubuntu-root ro quiet
splash i915.enable_dc=0
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/1983111
Title:
package
Public bug reported:
Just an ordinary kernel update attempt via apt update && apt upgrade.
System is Ubuntu 22.04 Desktop, booting with systemd-boot instead of
GRUB.
The kernel update failed, most likely because of issues around the sd-
boot kernel-update utility.
ProblemType: Package
All autopkgtests for the newly accepted linux-meta-gcp-5.4 (5.4.0.1085.64) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk/17.11.10-0ubuntu0.1 (amd64)
r8168/8.045.08-2ubuntu1 (amd64)
systemd/237-3ubuntu10.53 (arm64)
Please
All autopkgtests for the newly accepted linux-meta-gkeop-5.4
(5.4.0.1050.53~18.04.47) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
kpatch/0.5.0-0ubuntu1.1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
Please visit the excuses
** Description changed:
+ [Impact]
+
To attach TFT touchscreens the pi-foundation kernel ships the fbtft
devicetree overlay along with rpi-display.
While you can attach a stand-alone TFT display just fine when only using
rpi-display to provide the drivers with hardcoded GPIO
** Changed in: linux-allwinner-5.17 (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-allwinner-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1980594
Title:
** Changed in: linux-starfive-5.17 (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-allwinner-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1980594
Title:
** Changed in: linux-starfive-5.17 (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-starfive-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1983019
Title:
Pinctrl driver
This bug is still not fixed in Ubuntu 20.04.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1969247
Title:
fallocate with FALLOC_FL_ZERO_RANGE produces zero-size files on zfs in
All autopkgtests for the newly accepted linux-meta-gke-5.4
(5.4.0.1079.85~18.04.41) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:
dpdk/17.11.10-0ubuntu0.1 (amd64)
r8168/8.045.08-2ubuntu1 (amd64)
lxc/3.0.3-0ubuntu1~18.04.1
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1043.42)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
lttng-modules/unknown (arm64)
gost-crypto/unknown (arm64)
bbswitch/unknown (arm64)
r8168/unknown (arm64)
** Changed in: linux-raspi (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1981078
Title:
[pi-kernel] Please set
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
--
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/1982627
Title:
MT7612u wireless chipset not working on
** Description changed:
+ [Impact]
+
I tried to use f_mass_storage to expose a 16TB hard drive attached to
Raspberry Pi to another computer.
On the remote computer the recognised drive has incorrect capacity and the
data is truncated.
After some debugging I noted the problem is caused
** 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1979045
Title:
misleading error prints from
** 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-bluefield in Ubuntu.
https://bugs.launchpad.net/bugs/1979264
Title:
mlx-trio module license update
This bug is awaiting verification that the linux-bluefield/5.4.0-1043.48
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-1043.48
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-1043.48
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-1043.48
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-1043.48
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-ibm/5.4.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists,
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-riscv (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-starfive-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects:
The HW (43f0/1672) of the bug reporter is not (yet) supported by
upstream.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** No longer affects: linux-firmware (Ubuntu)
** Also affects: backport-iwlwifi-dkms (Ubuntu)
Importance: Undecided
Status: New
** Changed
@harish-kp Yours is a different problem. Can you open a new bug for
that?
$ ubuntu-bug linux-firmware
--
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/1969966
Title:
No support
** Description changed:
SRU Justification:
[Impact]
This bug in bcache affects (at least) focal and jammy releases.
When Random Read I/O is started with a test like -
fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G
--ioengine=libaio --direct=1
** Description changed:
SRU Justification:
[Impact]
This bug in bcache affects (at least) focal and jammy releases.
When Random Read I/O is started with a test like -
fio --name=read_iops --directory=/home/ubuntu/bcache_mount/ --size=16G
--ioengine=libaio --direct=1
Attached is the history.log file, I think this is the one where the
upgrade happened.
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982477/+attachment/5605828/+files/history.log
--
You received this bug notification because you are a member of
** Changed in: linux-firmware (Ubuntu Kinetic)
Status: New => Fix Released
--
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/1977872
Title:
Add symlinks to enable StarFive
** Tags removed: need-duplicate-check
--
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/1983090
Title:
package linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1 failed to
Public bug reported:
i tried to uninstall this core version, but it dit not make it, the core
version doesn't change, then it show me this report message(broken).
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
ProcVersionSignature:
** Also affects: linux-starfive-5.17 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-starfive-5.17 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-starfive-5.17 (Ubuntu Jammy)
Assignee: (unassigned) => Emil Renner Berthing (esmil)
--
No success, the downgrade doesn't work either. Today morning, wrong
resolution after the wake up. It seems as if the monitor wakes up with
correct resolution if there is just a little period between sleep and
wake up. But when there's a longer period in between, it wakes up with
wrong resolution.
52 matches
Mail list logo
