** Changed in: linux (Ubuntu Focal)
Status: In Progress => Invalid
** Changed in: linux (Ubuntu Focal)
Assignee: AceLan Kao (acelankao) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
Support for simultaneous high quality input and output over Bluetooth
was only added to PulseAudio in version 15, which is introduced in
Ubuntu 21.10. Please try that: http://cdimage.ubuntu.com/daily-live/
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
**
** Also affects: linux-oem-5.13 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Assignee: (unassigned) => AceLan Kao (acelankao)
** Changed in: linux-oem-5.13
In a related way say you wanted to recover a system from a boot disk,
and copy all the data off to another disk. If you use a sequential file
copy like from tar/cp in verbose mode and watch it, eventaully it will
hang on the file triggering the issue (watch dmesg/kern.log). Once that
happens, move
@Qin,
Could you please advise how could we test this?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1929895
Title:
[EHL] Enable ISHTP
Status in intel:
Fix Committed
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: pulseaudio (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: kunpeng920/ubuntu-20.04-hwe
Status: Fix Committed => Fix Released
** Changed in: kunpeng920/ubuntu-20.04
Status: Fix Committed => Fix Released
** Changed in: kunpeng920
Status: Fix Committed => Fix Released
--
You received this bug notification because you
Attaching the output of `lshw`
sudo lshw
✔
[sudo]
Public bug reported:
System reports and error every few seconds and asks to report. I am
sending the automatically generated report, I donot have any idea on the
error.
uptime --pretty
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1945263
Title:
package linux-modules-extra-5.11.0-36-generic (not installed) failed
to
Public bug reported:
I installed Ubuntu LTS in Lenovo s145 and touchpad doesn't work. It
isn't even being detected. Only external mouse works.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.11.0-36-generic 5.11.0-36.40~20.04.1
ProcVersionSignature: Ubuntu
** Summary changed:
- [Asus X541NC] wakes up from sleep mode after 1 second
+ [Asus X541NC] wakes up from sleep mode after 1 second (unless ACPI RP03 is
disabled)
** Changed in: linux-hwe-5.11 (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
Please try this as a workaround:
MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0
in /etc/environment, and reboot.
** Summary changed:
- [i915] [Braswell] screen flashes black (mouse pointer stays visible) when
moving mouse pointer to the left edge of the screen
+ [i915] [Braswell] screen flashes black
Okay, so, after having changed the GRUB configuration, this time around,
it lasted 1 day, 4 hours, and about 45 minutes before finally
blackscreening. Also, during that time, at around 1 day and a little bit
over 2 hours in, there was a +wall message across all my terminals
saying there was a
Bug has recurred after beta installation of 21.10 (Impish). b43 firmware
reverted to version 784.2, causing significant degradation of WiFi
performance. using b43-fwcutter to load firmware version 5.100.138
(666.2) resolved the issue.
** Summary changed:
- Broken WiFi Install on Ubuntu (MATE)
So to be clear this patch revert fixes the issue being caused new, but,
if the issue already happened on your filesystem it will continue to
occur because the exception is reporting corruption on disk. I don't
currently have a good fix for this other than to move the affected files
to a directory
Public bug reported:
zdb -b has given me some very long progress estimates:
$ sudo zdb -b fst
[sudo] password for sarnold:
Traversing all blocks to verify nothing leaked ...
loading space map for vdev 0 of 1, metaslab 115 of 116 ...
4.72T completed (2659MB/s) estimated time remaining:
Test Steps:
1. In BIOS setup, enable xDCI as below :
Intel Advanced Menu -> PCH-IO Configuration -> USB Configuration-> xDCI Support
-> [Enabled]
2. Boot to OS
3. Check dmesg to see if BIOS pass pci device info as below :
[ 4.534064] pci :00:14.0: [8086:4b7d] type 00 class 0x0c0330
[
Wäre can I find this Information in Windows?
Hui Wang <1943...@bugs.launchpad.net> schrieb am Mo. 27. Sept. 2021 um
02:43:
> Under windows, does the touchpad connect to i8042/ps2 bus or i2c bus?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
if patching the PulseAudio default.pa works, then the initial issue was
probably a problem with alsa-ucm-conf not being updated in your distros.
There's no reason to use asound.state these days, it's a much better
idea to use UCM. my 2 cents.
--
You received this bug notification because you are
I don't have problems running Ubuntu 20.04 LTS with (original, non-HWE
kernel) 5.4 series kernel these days. Granted, I've probably indeed
modified the default.pa as indicated above, and have had a state file
which I've restored - but the kernel is default, and the audio works
fine without any
Same issue here from a year ago on HP Z1:
[4.556401] hp_wmi: query 0x4 returned error 0x5
[4.557900] hp_wmi: query 0xd returned error 0x5
[4.561206] hp_wmi: query 0x1b returned error 0x5
--
You received this bug notification because you are a member of Kernel
Packages, which is
apport-collect doesn't work on Ubuntu Core
** 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/1945242
Title:
Failed to
solved the bug already i cleared some things and made an update
On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote:
> Any update on this? Having issues with sound working for some time,
> than suddenly stopping with a buzzing sound. Will attempt to modify
> patch for most
Still a problem on latest 20.04 kernel, 5.11.0-36-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu.
https://bugs.launchpad.net/bugs/1939628
Title:
Fan goes full speed on resume from suspend
Thanks, Simon. I'll verify a revert from the menu after I update and
post there if things don't go well.
--
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/1906476
Title:
PANIC at
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 1945242
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
The refresh to a new kernel snap is failing in uc18 image. Something
important to remark is that the DTB's for the new kernel were installed,
but it still failed to complete the refresh to the new kernel
Steps to reproduce
I am using a rpi3 and I create an uc18 arm64 image
@#41: Dataset “rpool/ROOT/ubuntu_” sounds like bug 1894329, although
that one should have been fixed.
--
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/1906476
Title:
PANIC at
All autopkgtests for the newly accepted linux-meta (5.11.0.38.39) for hirsute
have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/247.3-3ubuntu3.6 (armhf, amd64)
initramfs-tools/0.139ubuntu3 (amd64)
Please visit the excuses page listed
I just checked old and new behavior again.
First of all it's not clear for me from where this value of 53 is taken,
according to the data in /sys/class/thermal/thermal_zone5 (THP)
trip_point_0_hyst:4000
trip_point_0_temp:-274000
trip_point_0_type:passive
trip_point_1_hyst:4000
This bug was fixed in the package linux-azure - 5.11.0-1017.18
---
linux-azure (5.11.0-1017.18) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1017.18 -proposed tracker (LP: #1944161)
* Hirsute update: upstream stable patchset 2021-08-12 (LP: #1939738)
- [Config]
This bug was fixed in the package linux-azure - 5.11.0-1017.18
---
linux-azure (5.11.0-1017.18) hirsute; urgency=medium
* hirsute/linux-azure: 5.11.0-1017.18 -proposed tracker (LP: #1944161)
* Hirsute update: upstream stable patchset 2021-08-12 (LP: #1939738)
- [Config]
I'm not sure if this is the right package
** Package changed: ubuntu => thermald (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to thermald in Ubuntu.
https://bugs.launchpad.net/bugs/1945221
Title:
CPU frequency stuck at
You have been subscribed to a public bug:
I would really like to find out why my cpu's keep reverting back to a cpu
powersave mode after I get a kernel update then reboot.
I cleaned my laptops vent but this seems to happen whenever a new kernel
is updated and installed.
@DanglingPointer (ferncasado)
gonna try #74. i really do want to understand how all this works. this
might be the most reliable option since even ppa's break.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This bug was fixed in the package zfs-linux - 2.0.6-1ubuntu2
---
zfs-linux (2.0.6-1ubuntu2) impish; urgency=medium
* Revert workaround on fill locked flag patch (LP: #1906476)
- disable 4701-enable-ARC-FILL-LOCKED-flag.patch as this
is causing zfs_node.c panics
-- Colin
If the issue doesn't affect hirsute then it should be possible to update
an impish system by chroot from hirsute media, I would think.
I've been booting up only occasionally this past week when I need to
access something, but I find that apt, or possibly initramfs, updates
seem to trigger the
Actually, I realize I may have been overconfident about that. Should it
work to fix from a chroot or is the fix in the userland tools such that
a chroot from hirsute would not help due to an issue in the userland ZFS
tools under the chroot?
--
You received this bug notification because you are a
This bug was fixed in the package zfs-linux - 2.0.6-1ubuntu2
---
zfs-linux (2.0.6-1ubuntu2) impish; urgency=medium
* Revert workaround on fill locked flag patch (LP: #1906476)
- disable 4701-enable-ARC-FILL-LOCKED-flag.patch as this
is causing zfs_node.c panics
-- Colin
More details and proposed patch for the mount bug is here:
https://lore.kernel.org/lkml/20210927154459.15976-1-vvidic@valentin-
vidic.from.hr/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The patch was merged into 5.13.0-17.17, which is currently in impish-proposed.
At some point it should promulgate to the release pocket. You can view the
status here:
https://launchpad.net/ubuntu/+source/linux
I don't know how long after that it will before it appears in images. As
a
All autopkgtests for the newly accepted linux-meta (5.4.0.89.93) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
lxc/1:4.0.6-0ubuntu1~20.04.1 (arm64)
backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, ppc64el, arm64)
Please
All autopkgtests for the newly accepted linux-meta-hwe-5.11
(5.11.0.37.41~20.04.16) for focal have finished running.
The following regressions have been reported in tests triggered by the package:
systemd/245.4-4ubuntu3.13 (s390x, ppc64el, amd64)
This bug was fixed in the package nvidia-settings -
470.57.01-0ubuntu0.21.04.2
---
nvidia-settings (470.57.01-0ubuntu0.21.04.2) hirsute; urgency=medium
* debian/patches/17_do_not_read_config_on_power_saving_mode.patch:
- Do not read config on Power Saving mode. (LP: #1943160).
This bug was fixed in the package nvidia-settings -
470.57.01-0ubuntu0.20.04.2
---
nvidia-settings (470.57.01-0ubuntu0.20.04.2) focal; urgency=medium
* debian/patches/17_do_not_read_config_on_power_saving_mode.patch:
- Do not read config on Power Saving mode. (LP: #1943160).
Thanks a lot dann.
I dont know the release process of the kernel, and when our public
images are generated by CPC.
I have to test it when is uploaded here:
https://images.maas.io/ephemeral-v3/candidate/impish/arm64/
Do you have any tip about how to be aware when this should happen?
--
You
The verification of the Stable Release Update for nvidia-settings has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
I found the following link:
https://forum.manjaro.org/t/new-install-amd-fx-6300-wont-wake-from-suspend/39471/10
Suggesting that setting TearFree on may help (RS780L)
However... I wonder if ShadowPrimary did not help.
Section "Device"
Identifier "Radeon"
Driver "radeon"
Option
Public bug reported:
[Impact]
New hardware support for AMD's Yellow Carp need five commits backported
to mesa and new firmware. This is only needed on focal, skipping
hirsute/impish (no kernel support there).
[Test plan]
Install updates, boot a YC machine and check that the desktop has full
This bug is awaiting verification that the linux/5.4.0-89.100 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, change
This bug is awaiting verification that the linux/5.4.0-89.100 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, change
Will new media be available w/ this fix in place?
I ask because running "dkms status" or any dkms command presently
triggers this bug for me, and the only way forward I can see to being
able to fix that system is new media w/ a patched kernel.
--
You received this bug notification because you
** Changed in: zfs-linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: zfs-linux (Ubuntu Focal)
Importance: Undecided => High
** Changed in: zfs-linux (Ubuntu Focal)
Assignee: (unassigned) => Colin Ian King (colin-king)
--
You received this bug notification because
** Also affects: zfs-linux (Ubuntu Focal)
Importance: Undecided
Status: New
--
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/1944417
Title:
Add support for 5.14
Status in
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
I've just installed 5.11.0-38-generic from Hirsute-proposed and I can
confirm that it works. I've also changed the tag, like the bot asked. I
hope it's OK.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
--
You received this bug notification because you are
** Description changed:
[SRU Justification]
[Impact]
Cold plugged USB device was not detected on certain PCIe USB cards
(like Inateck card connected to AM64 EVM or connected to J7200 EVM).
And also the root hub mentioned in https://bugs.launchpad.net/bugs/1939638.
Re-plugging
Issue occurs in impish as well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1926084
Title:
[hirsute] Bluetooth speakers reconnect randomly
Status in bluez package in Ubuntu:
This bug was fixed in the package linux-raspi - 5.11.0-1019.20
---
linux-raspi (5.11.0-1019.20) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1019.20 -proposed tracker (LP: #1944172)
* hirsute/linux-raspi: Upstream raspberrypi patchset 2021-08-26 (LP: #1942170)
-
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
This bug was fixed in the package linux-raspi - 5.11.0-1019.20
---
linux-raspi (5.11.0-1019.20) hirsute; urgency=medium
* hirsute/linux-raspi: 5.11.0-1019.20 -proposed tracker (LP: #1944172)
* hirsute/linux-raspi: Upstream raspberrypi patchset 2021-08-26 (LP: #1942170)
-
This bug was fixed in the package linux-aws - 5.11.0-1019.20
---
linux-aws (5.11.0-1019.20) hirsute; urgency=medium
* hirsute/linux-aws: 5.11.0-1019.20 -proposed tracker (LP: #1944158)
* linux-aws: Missing check for CONFIG_SUSPEND in amdgpu_acpi.c (LP: #1943070)
- UBUNTU
Hello Trent, or anyone else affected,
Accepted zfs-linux into impish-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/2.0.6-1ubuntu2 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
** Also affects: linux-azure-5.8 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-5.8 (Ubuntu Hirsute)
Status: New => Invalid
** Changed in: linux-azure-5.8 (Ubuntu)
Status: New => Invalid
** Changed in: linux-azure-5.8 (Ubuntu Bionic)
Status:
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 1945211
and then change the status of the bug to 'Confirmed'.
If, due to the
** Description changed:
[Impact]
- * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
+ * Ubuntu's 15.4 based shim ships a very large vendor-dbx (aka mokx)
which revokes many Ubuntu kernel hashes and 2012 signing key.
- * Kernel should import those into it's
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
** Description changed:
[Impact]
It has been brought to my attention the following:
"
We have been experiencing node lockups and degradation when testing fiber
channel fail over for multi-path PURESTORAGE drives.
Testing usually consists of either failing over the fabric or
Public bug reported:
[SRU Justification]
[Impact]
Cold plugged USB device was not detected on certain PCIe USB cards
(like Inateck card connected to AM64 EVM or connected to J7200 EVM).
And also the root hub mentioned in https://bugs.launchpad.net/bugs/1939638.
Re-plugging the USB device always
Spotted on b/linux-gke-5.4 5.4.0-1052.55~18.04.1
--
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/1934477
Title:
ubuntu_aufs_smoke_test failed on F-OEM-5.13
Status in
Understood, thanks for considering the issue. Perhaps this just needs to
be release noted, warning users it may happen and how to avoid it (i.e.
implement their own set-name config)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
This bug is awaiting verification that the linux/5.11.0-38.42 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 exists,
This bug is awaiting verification that the linux/5.11.0-38.42 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 exists,
This bug is awaiting verification that the linux/5.11.0-38.42 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 exists,
This bug is awaiting verification that the linux/5.11.0-38.42 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 exists,
** Changed in: linux-oem-5.13 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1943935
Title:
CirrusLogic/CS8409: No
A test kernel of v5.4 (kernel series where the problem has been found)
has been tested by Field Engineer and here's the outcome:
"
-Extensive testing about 4/5 failovers both HWE (v5.11) and the patched kernels
seem stable (v5.4).
Thank you this unblocks us for deployment of this cloud.
"
-
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
Install linux 5.14.8 and my system not boot.
--
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/1942684
Title:
Kernel 5.14.X / 5.13.14 fails to boot
Status in linux package in Ubuntu:
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528407/+files/PaInfo.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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528414/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528400/+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/1942684
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528411/+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: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528403/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528413/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528410/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528404/+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/1942684
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528408/+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: "acpidump.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528415/+files/acpidump.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/1942684/+attachment/5528402/+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/1942684
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528412/+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: "AlsaInfo.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528399/+files/AlsaInfo.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-v.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528406/+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: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528409/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528401/+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
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1942684/+attachment/5528405/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: vladimir 1867 F pipewire-media-
/dev/snd/controlC2: vladimir 1867 F pipewire-media-
/dev/snd/controlC0: vladimir 1867 F
** Description changed:
[Impact]
Upstream linux kernel now supports configuring built-in revoked
certificates for the .blacklist keyring.
Add support in our kernel configuration to have built-in revoked
certificates.
Revoke UEFI amd64 & arm64 2012 signing certificate.
Public bug reported:
19:59:18 INFO | START ubuntu_lxc.lxc-test-unpriv
ubuntu_lxc.lxc-test-unpriv timestamp=1632340758timeout=900 localtime=Sep
22 19:59:18
19:59:18 DEBUG| Persistent state client._record_indent now set to 2
19:59:18 DEBUG| Persistent state client.unexpected_reboot
1 - 100 of 198 matches
Mail list logo
