looks good, thank you
** Changed in: zfs-linux (Ubuntu Mantic)
Status: New => Fix Committed
** Changed in: zfs-linux (Ubuntu Mantic)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Kernel
Packages,
Public bug reported:
Error encountered while trying to install a Ubuntu update.
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-headers-5.15.0-78 (not installed)
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion:
Hello Ionut, or anyone else affected,
Accepted mutter into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mutter/42.9-0ubuntu4
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The purpose of the size check in u-r-u is to ensure that we don't fail
mid-upgrade due to lack of disk space on /boot.
But AIUI that's not what happened here to the bug submitter; this is an
upgrade within an Ubuntu series between individual kernel packages.
We should NOT have a check in u-r-u
Removing packages from jammy-updates:
linux-meta-azure-fde-5.19 5.19.0.1025.28~22.04.1.7 in jammy
linux-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7 in jammy
amd64
linux-cloud-tools-azure-fde-5.19-edge 5.19.0.1025.28~22.04.1.7
in jammy amd64
"@Andreas firmware-sof in Mantic is 2.2.6, which already has everything
in Acelan's merge proposal."
** Changed in: firmware-sof (Ubuntu Mantic)
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Anthony, I have no preference about 1 vs 2, I only ask that the bug (and
therefore the SRU verification process) be consistent with the upload.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.1 in Ubuntu.
Hello Bin, or anyone else affected,
Accepted linux-restricted-modules-media-fixup into jammy-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/linux-restricted-modules-media-
fixup/22.04.1 in a few hours, and then in the -proposed repository.
Please
Hello Bin, or anyone else affected,
Accepted linux-restricted-modules-media-fixup into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/linux-restricted-modules-media-
fixup/20.04.1 in a few hours, and then in the -proposed repository.
Please
It doesn't look to me like the bug description matches the contents of
the firmware-sof upload in jammy. The bug description implies a
targeted fix with possible impact only to a particular affected
platform. The debdiff of the upload includes 16 new firmware files, and
opaque changes to 16
> if one desires to use dkms from the archive, rather than prebuilt
modules that all of Ubuntu kernels ship.
I am failing to see how this is compatible with the Ubuntu SRU policy.
** Changed in: zfs-linux (Ubuntu Jammy)
Status: In Progress => Incomplete
--
You received this bug
The patch for focal is quite a bit larger than for jammy and lunar, and
I question whether it's really needed. Is this driven by user demand on
focal? Was this a problem in practice when focal was released, or has
it become a problem more recently as a result of growing memory usage by
the
Hello Ioanna, or anyone else affected,
Accepted kexec-tools into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/kexec-
tools/1:2.0.22-2ubuntu2.22.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
Hello Ioanna, or anyone else affected,
Accepted kexec-tools into lunar-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/kexec-
tools/1:2.0.22-2ubuntu3.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Removing packages from mantic:
linux-signed-kvm 6.2.0-1003.3 in mantic
linux-image-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64
Comment: kvm flavor merged into virtual; LP: #2025686
1 package successfully removed.
** Changed in: linux-signed-kvm (Ubuntu Mantic)
Removing packages from mantic:
linux-kvm 6.2.0-1003.3 in mantic
linux-buildinfo-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64
linux-headers-6.2.0-1003-kvm 6.2.0-1003.3 in mantic amd64
linux-image-unsigned-6.2.0-1003-kvm 6.2.0-1003.3 in mantic
Removing packages from mantic:
linux-meta-kvm 6.2.0.1003.4 in mantic
Comment: Obsolete source package subsumed by linux-meta; LP: #2025686
1 package successfully removed.
** Changed in: linux-meta-kvm (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received this bug
Removing packages from mantic:
linux-allwinner 5.19.0-1009.9 in mantic
linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic
amd64
linux-allwinner-headers-5.19.0-1009 5.19.0-1009.9 in mantic
arm64
linux-allwinner-headers-5.19.0-1009
Removing packages from mantic:
linux-meta-allwinner 5.19.0.1009.9 in mantic
Comment: Obsolete source package subsumed by linux-riscv; LP: #2025398
1 package successfully removed.
** Changed in: linux-meta-allwinner (Ubuntu Mantic)
Status: Triaged => Fix Released
--
You received
Hello AaronMa, or anyone else affected,
Accepted alsa-ucm-conf into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu1.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello AaronMa, or anyone else affected,
Accepted alsa-ucm-conf into lunar-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/alsa-ucm-
conf/1.2.6.3-1ubuntu9.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-35788
--
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/2023577
Title:
cls_flower: off-by-one in fl_set_geneve_opt
Status
I believe this seems to have been fixed in 5.4.0-151-generic. Changelog:
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux/linux_5.4.0-151.168/changelog
Specifically the line: "net: Remove WARN_ON_ONCE(sk->sk_forward_alloc)
from sk_stream_kill_queues()." which was ported from v5.4.234
Correction, not opening a task on the ubuntu-website project which is evidently
obsolete.
Opened a github issue instead:
https://github.com/canonical/ubuntu.com/issues/12927
** Bug watch added: github.com/canonical/ubuntu.com/issues #12927
Thank you for the patch.
I do not know what content this was intended to point to, but we should
not do Stable Release Updates of a package just to fix a broken link in
the documentation - instead, particularly since we have control over the
domain it points to, we should fix it so that the link
This bug is marked as 'in progress' for glibc in both jammy and kinetic,
but there is no glibc SRU in the kinetic queue. As the normal SRU
process is to fix bugs in later releases before earlier releases, there
needs to be some clarification about the plan here.
This is also the only one of the
I also just updated to 5.4.0-150-generic and I'm still seeing this
issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2018960
Title:
linux-image-5.4.0-149-generic
I can add to this saying that the machine I'm seeing this on is behind a
NAT (being done by another firewall device), but it does not do any NAT
itself.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
Awaiting answer to Andreas' latest question.
** Changed in: thermald (Ubuntu Focal)
Status: In Progress => Incomplete
--
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/2009676
I have the same problem except I don't appear to be on focal-proposed.
steve@xxx:/etc/apt$ apt-cache policy linux-image-5.4.0-149-generic
linux-image-5.4.0-149-generic:
Installed: 5.4.0-149.166
Candidate: 5.4.0-149.166
Version table:
*** 5.4.0-149.166 500
500 http
This issue was introduced in fce96cf04430 ("virt: Add SEV-SNP guest
driver") and thus affects 5.19 kernels and newer.
--
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/2013198
Title:
Fix
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672576/+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: "Lsusb.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672574/+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/2019261
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672575/+files/Lsusb-t.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672585/+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: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672584/+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: "UdevDb.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672583/+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: "RfKill.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672582/+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: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672579/+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/2019261/+attachment/5672578/+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: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672577/+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: "ProcModules.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672581/+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: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672580/+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/2019261/+attachment/5672573/+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: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672570/+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: "CRDA.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672569/+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/2019261
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672572/+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/2019261
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672571/+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: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/2019261/+attachment/5672568/+files/AudioDevicesInUse.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 lunar
** Description changed:
linux-generic 6.2.0.20.20 on lunar, the following messages (retrieved
from dmesg) are displayed on my console at boot:
[1.134865] blacklist: Problem blacklisting hash (-13)
[1.134925] blacklist:
Public bug reported:
linux-generic 6.2.0.20.20 on lunar, the following messages (retrieved
from dmesg) are displayed on my console at boot:
[1.134865] blacklist: Problem blacklisting hash (-13)
[1.134925] blacklist: Problem blacklisting hash (-13)
[1.134961] blacklist: Problem
** Package changed: ubiquity (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/2017599
Title:
Touchpad laggy
Status in linux package in Ubuntu:
Incomplete
** Package changed: livecd-rootfs (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/2017529
Title:
livecd-rootfs: kernel bump
Status in linux package in Ubuntu:
** Information type changed from Private Security to Public
--
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/2016827
Title:
screen breaks and freezing
Status in linux package in Ubuntu:
** Project changed: ubuntu-cdimage => 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/2016185
Title:
Kernel panic at initial boot of April 13 daily 23.04 image on
** Package changed: linux-signed-hwe-5.19 (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/2008823
Title:
/sys/kernel/boot_params/data leaks random data
Status
> I can enable that successfully from the live session but
> wireless networks are not available in network manager
This is expected if SecureBoot is enabled on your system.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware
Can someone test what 'ubuntu-drivers install' does in the lunar live
environment?
--
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/2013236
Title:
Failed to install bcmwl
Copying across relevant comment from previously-duped and now re-duped
bug:
Booted from an Ubuntu Desktop Legacy ISO, and ran "ubuntu-drivers
devices" and "ubuntu-drivers list" to get more info.
ubuntu-drivers devices:
== /sys/devices/pci:00/:00:1c.3/:24:00.0 ==
modalias :
(which makes this an ubuntu-drivers-common question)
** Package changed: broadcom-sta (Ubuntu) => ubuntu-drivers-common
(Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
Ok I'm sorry, this was a mistake on my part - I misread the PCI IDs in
the original log, or otherwise failed to line them up with what I was
seeing in modaliases. 14e4:4331 is indeed listed for bcmwl in all
series < lunar, and for broadcom-sta in lunar.
** Changed in: linux-firmware (Ubuntu)
> Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl
> was installed correctly during the install so this is a
> regression with the 6.2 kernel
The bcmwl driver SHOULD NOT have been installed on this hardware in
either 22.04 or 22.10, because the bcmwl package has no Modaliases
Marking this for broadcom-sta and linux-firmware.
If the restricted driver should be used but isn't, that's a broadcom-sta
bug.
If the in-kernel b43 driver should be used, then it's a linux-firmware
bug given the log entries about firmware loading.
--
You received this bug notification because
kernel log entries in attached syslog don't show any PCI devices which
match the modaliases for the most recent bcmwl package (which is
superseded now by broadcom-sta but has the same modaliases list).
Did you find bcmwl was installed on this hardware in previous releases?
** Changed in:
Thanks, I overlooked that this was for focal. Done now.
** Changed in: linux-meta-xilinx-zynqmp (Ubuntu)
Status: Triaged => Fix Released
** Changed in: linux-xilinx-zynqmp (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of
I see that this has already been accepted into focal and jammy, but with
'Test case: TBD' this is going to stall out as an SRU. Marking
incomplete and holding the kinetic SRU until this is addressed.
** Changed in: linux-firmware (Ubuntu Kinetic)
Status: Fix Committed => Incomplete
--
This got done, the i386 binaries got handled via the NBS process.
** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in
To proceed with this SRU, I would like to have some analysis of what
makes this an armhf-only failure. Is it to do with the fact that armhf
autopkgtests run in a container and others do not? If so, it seems to
me that a more correct fix for the test is to detect that we're running
in a container
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into jammy-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into kinetic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-1ubuntu3.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
These packages do not show up as having mismatched components.
https://people.canonical.com/~ubuntu-archive/component-mismatches-
proposed.html
They need to be seeded somewhere before we would promote these to main.
** Changed in: linux-meta-xilinx-zynqmp (Ubuntu)
Status: Triaged =>
the status does not need to be set to triaged to be in our queue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-xilinx-zynqmp in Ubuntu.
https://bugs.launchpad.net/bugs/2008672
Title:
focal linux-xilinx-zynqmp promote from
Public bug reported:
The set of binaries from nvidia-graphics-drivers-390 on i386 has been
reduced to:
libnvidia-compute-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386
libnvidia-decode-390 | 390.157-0ubuntu3 | lunar-proposed/restricted | i386
libnvidia-encode-390 |
Removing packages from lunar:
libcuda1-384 390.154-0ubuntu1 in lunar armhf
libnvidia-cfg1-390 390.154-0ubuntu1 in lunar armhf
libnvidia-compute-390 390.154-0ubuntu1 in lunar armhf
libnvidia-fbc1-390 390.154-0ubuntu1 in lunar armhf
libnvidia-gl-390
To further isolate the nature of the slowdown, we should figure out if
this is caused by disk I/O degradation, CPU frequency scaling, or
something else. Can you use the bonnie++ package to check the disk
throughput under the old and new kernels?
--
You received this bug notification because you
> 4) s390x is dropped, please RM binary on the s390x missing build on
s390x: linux-image-5.19.0-21-generic (from 5.19.0-21.21)
AIUI doing so prematurely removes the currently active linux-image
package for s390x so this would seem to be the thing we should do last,
once everything else is ready
* autopkgtest for nvidia-graphics-drivers-390/390.154-0ubuntu1: amd64:
Pass, armhf: Regression ♻
?
On zfs-linux, to confirm, by "false negative" you mean: it's broken
already in the release pocket but we failed to detect it?
linux-restricted-modules also reports unsatisfiable dependencies, and
Removing packages from jammy-proposed:
linux-bluefield 5.15.0-1011.13 in jammy
linux-bluefield-cloud-tools-common 5.15.0-1011.13 in jammy amd64
linux-bluefield-cloud-tools-common 5.15.0-1011.13 in jammy arm64
All of these CVEs related to
https://xenbits.xen.org/xsa/advisory-396.html have been addressed in
every kernel except for
- Ubuntu 20.04's linux-oem-5.14
- CVE-2022-23041 has not been addressed in the 4.15 based kernels.
--
You received this bug notification because you are a member of Kernel
The API that was failing in this test was introduced in the 4.6 kernel
series (in b844f0ecbc56 ("vfs: define kernel_copy_file_from_fd()")), so
trusty's 4.4 kernel should not be affected. The linux-azure 4.15 kernels
in trusty and xenial have the needed fix applied, are they still
affected by this
Removing packages from lunar:
bcmwl 6.30.223.271+bdcom-0ubuntu10 in lunar
bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu10 in lunar amd64
Comment: Superseded by broadcom-sta; LP: #1993718
1 package successfully removed.
** Changed in: bcmwl (Ubuntu)
Status: New =>
This has been promoted.
** Changed in: broadcom-sta (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1993718
Title:
Promote to restricted:
Removing packages from lunar:
linux-allwinner-5.17 5.17.0-1003.3 in lunar
linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar
amd64
linux-allwinner-5.17-headers-5.17.0-1003 5.17.0-1003.3 in lunar
arm64
** Changed in: linux-riscv-5.19 (Ubuntu)
Status: Fix Committed => Fix Released
** Changed in: linux-meta-riscv-5.19 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Promoting gcc-12 and cpp-12 binaries was sufficient to fix this.
** Changed in: dkms (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1998154
Because gcc-12 source is in main already, *and* is already published in
jammy-{security,updates}, it seems it is straightforward to simply
promote the binaries to solve this problem.
I'll work on this; it may take a couple of rounds to get all the
dependencies promoted.
--
You received this bug
ure: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-02-26 (27
u/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
ting the same problem online. See:
https://www.reddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: stev
nts/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
nts/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
nts/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
u/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
u/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
m/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve
u/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
u/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
ddit.com/r/Ubuntu/comments/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve
nts/x0y19l/sound_buzzing_with_22041_on_chromebook/
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: steve 1065 F pulseaudio
/dev/snd/controlC0: steve 1065 F
101 - 200 of 9258 matches
Mail list logo
