** Bug watch removed: github.com/xbmc/xbmc/issues #19479
https://github.com/xbmc/xbmc/issues/19479
--
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/1949262
Title:
Power Savings doesn't
I run Ubuntu Budgie 21.10. Since two days before turning off display
after idle went well (DPMS mode).
Since yesterday turning off display doesn't work anymore. The display
goes black for a second but then it comes back again. However, the
screen is frozen (no repainting) as long as I use the desk
All autopkgtests for the newly accepted linux-meta-azure (5.11.0.1022.23) for
hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64)
Please visit the excuses page listed below and investigate the
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/postfix/+git/postfix/+merge/412054
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
re
** Changed in: juju
Milestone: 2.9.19 => 2.9.20
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1944080
Title:
[fan-network] Race-condition between "apt update" and dhcp request
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1047.82) for
focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/unknown (arm64)
dpdk/19.11.10-0ubuntu0.20.04.1 (arm64)
Please visit the excuses page listed below and
For those who are interested to discover driver improvements provided
for Linux 5.11.
https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.11-DRM-Pull
https://kernelnewbies.org/Linux_5.11
I am surprised that there are not more problems without news Intel
drivers update with the change to L
This bug is awaiting verification that the linux-azure/5.11.0-1022.23
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-hirsute' to 'verification-done-hirsute'. If the
problem still exis
This bug is awaiting verification that the linux-azure/5.11.0-1022.23
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-hirsute' to 'verification-done-hirsute'. If the
problem still exis
** Changed in: ubuntu-release-notes
Status: New => Won't Fix
--
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/1850540
Title:
multi-zone raid0 corruption
Status in Release Notes for
** Description changed:
+ SRU Justification
- 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
+
** Description changed:
+ SRU Justification
- 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
+
** Description changed:
+ SRU Justification
- 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
+
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from
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
** Also affects: initramfs-tools (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-firmware (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-firmware (Ubuntu Focal)
Assignee: (unassigned) => Juerg Haefliger (juergh)
** Changed i
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1932423
Title:
Focal update: v5.10.43 upstream stable r
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1932393
Title:
Focal update: v5.10.42 upstream stable r
** Changed in: linux-oem-5.10 (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1932424
Title:
Focal update: v5.10.44 upstream stable r
works on Thinkpad E15-Gen2 AMD (KDE Neon)
cedric@E15-Gen2:~$ uname -a
Linux E15-Gen2 5.13.0-22-generic #22+arighi2020+1 SMP Wed Nov 10 15:41:33
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
trackpoint & trackpad activated
--
You received this bug notification because you are a member of Kernel
P
** No longer affects: linux-oem-5.14 (Ubuntu Impish)
** No longer affects: linux-oem-5.13 (Ubuntu Hirsute)
** No longer affects: linux-oem-5.13 (Ubuntu Impish)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
htt
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
** Changed in: linux (Ubuntu Jammy)
Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza)
--
You received this bug notification because you are a member of Kernel
Packages
While waiting for the next LTS version of Ubuntu I was able to fix the
mic issue on 20.04 by installing pipewire (followed this guide
https://askubuntu.com/questions/1330395/newly-installed-
ubuntu-20-04-bluetooth-headset-sound-and-mic-not-working/1340889#1340889
except I installed wireplumber inst
** Changed in: qemu (Ubuntu Focal)
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1944104
Title:
nested vm on vm not running
Status in linux-oe
** Changed in: linux-oem-5.13 (Ubuntu Hirsute)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939473
Title:
mute/micmute LEDs no functio
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1943915
Title:
IPU6 daemon+v4l2loopback is required to enable
** Also affects: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
http
** Also affects: qemu (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-oem-5.13 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are
** Changed in: linux-meta-oem-5.6 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
P
I guess this is a wontfix at this point, we have oem-5.14
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/193
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1934479
Title:
chacha.bidir in tls from ubuntu_kernel_se
** Changed in: linux-oem-5.14 (Ubuntu)
Status: Confirmed => Fix Released
--
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/1945046
Title:
ZFS related tests are failing with
** Changed in: linux-oem-5.14 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.10 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.10 (Ubuntu Impish)
Status: New =
** Changed in: linux-oem-5.14 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu Impish)
Status: New => Invali
** Also affects: linux-oem-5.14 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.14 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
http
let's just focus on stock linux for this
** Changed in: linux-oem-5.10 (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-meta-oem-5.6 (Ubuntu)
Status: New => Invalid
** Changed in: linux-oem-5.13 (Ubuntu)
Status: New => Won't Fix
** Changed in: linux-oem-5.14 (Ubuntu)
Just enabled impish-proposed, applied upgrades, and 5.13.0-22 is there,
rtw89 working well. No more requirement for extra dkms out-of-tree,
that's quite cool.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https:
@binli
There is a bug report by @superm already and most likely I have the same issue.
Should I fill a new bug or maybe we could reopen #1934014
(https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1934014) ?
@superm1
>>@xalt7x: Suggest that you adopt linux-oem-20.04d package which back
This bug was fixed in the package linux-raspi - 5.13.0-1010.12
---
linux-raspi (5.13.0-1010.12) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1010.12 -proposed tracker (LP: #1950142)
* [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
5.13.0-1010.11-raspi (
This bug was fixed in the package linux-raspi - 5.13.0-1010.12
---
linux-raspi (5.13.0-1010.12) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1010.12 -proposed tracker (LP: #1950142)
* [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
5.13.0-1010.11-raspi (
This bug was fixed in the package linux-raspi - 5.13.0-1010.12
---
linux-raspi (5.13.0-1010.12) impish; urgency=medium
* impish/linux-raspi: 5.13.0-1010.12 -proposed tracker (LP: #1950142)
* [Impish] Unable to boot rpi3b and cm3+ after upgrade to kernel
5.13.0-1010.11-raspi (
All autopkgtests for the newly accepted linux-meta-aws-5.4 (5.4.0.1060.43) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
lxc/3.0.3-0ubuntu1~18.04.1 (amd64)
kpatch/0.5.0-0ubuntu1.1 (amd64)
Please visit the excuses page listed be
This appears to be triggered by commit
4f73581836f031611b281c8c6017202f36afbf6b, the change is reported as a
bug in the 5.13 kernel as well and appears to have been brought into the
5.11 HWE kernel.
https://bugzilla.kernel.org/show_bug.cgi?id=214455
--
You received this bug notification because
Thank you Christian,
I think I managed to repair my system.
Here is how I did, if it can help others.
By the way, Jonas, it is impossible to remove broken files/folders, so the
strategy I suggest is to destroy the dataset and restore it from a backup,
while running from a bootable media.
One can
very interesting article ! more informative thanks for sharing..
http://www.forerunsoftwaresolutions.com/";>Software Training Institute
in Chennai
http://www.forerunsoftwaresolutions.com/adobe-experience-manager-training-course-in-chennai.php";>Best
AEM Training Institute In Chennai
http://www.fo
This bug was fixed in the package linux-raspi - 5.11.0-1022.24
---
linux-raspi (5.11.0-1022.24) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1022.24 -proposed tracker (LP: #1950141)
* [Hirsute]Unable to boot rpi2, rpi3, rpi3b+, rpi3a+, and cm3+ after upgrade
to kerne
Same problem here with Ubuntu 20.04 on a Dell XPS 15 9500, but in my
case it was triggered by update from kernel 5.11.0-38-generic to
5.11.0-40-generic.
Apt history shows the update as occurring last Friday morning, and the
next time I rebooted (the day after) the WiFi module stopped working,
mess
Narrowed it down a bit.
4.19.208-1 does not exhibit any battery drain issues when sleeping sometime
before powering off.
- 0% in 7 hours (97% -> 97%)
- 0% in 5 hours (100% -> 100%)
5.4.150-1 does.
- 54% in 10 hours (91% -> 37%)
- >34% in 12 hours (34% -> Dead)
Could someone else with th
Still there on first generation Lenovo ThinkPad T14 AMD (Ryzen 7 PRO
4750U based) running 5.14.17-301.fc35.x86_64:
Nov 16 15:16:15 fedora kernel: acpi PNP0C14:01: duplicate WMI GUID
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00)
Nov 16 15:16:15 fedora kernel: acpi PNP0C14
I check the situation in the different git trees (upstream and the ones
for the relevant Ubuntu releases) and the outcome is:
The commit a3e03bc1368c ("KVM: s390: index kvm->arch.idle_mask by
vcpu_idx") is upstream since v5.15-rc1, hence jammy does not need to be
patched, since it's target kernel
51 matches
Mail list logo
