debcrafters-packages team mailing list archive

[Lukas Märdian <2122556@xxxxxxxxxxxxxxxxxx>]

re #15, #12, #11: Thanks for your additional explanation! As stated,
it's a bit risky but might work out, especially if we use "block-
proposed-noble" until your internal verification is done and then maybe
do some slow phasing. But I'll leave the final decision (and discussion)
between you and the SRU team.

I did review the huge patch-series for Noble, including all of upstream
MR#1800 and it looks mostly good to me. All but 4 patches are cleanly
matching the upstream patches, the others have minor differences in
patch description of whitespace (but are not declared as "backport"). I
guess it would be OKish to upload Noble as-is, but if you'd be able to
cleanup my remarks this should allow for a smoother SRU review.

Please let me know how you want to proceed!

I've also prepared a draft MP/git-ubuntu branch, feel free to propose any changes against that branch for easier future review of your (potential) changes:
https://code.launchpad.net/~slyon/ubuntu/+source/pipewire/+git/pipewire/+merge/495139

Full range-diff of git-buildpackage patch-queue with your quilt patches applied
and the corresponding upstream range from MR#1800:
https://paste.ubuntu.com/p/5GhJ4hQMK4/

List of new quilt patches that are matching upstream ("OK") or show
slight differences ("WARN"):

UCM_updates/alsa-ucm-remove-extra-space-from-the-device.intended.patch - OK
UCM_updates/alsa-mixer-allow-to-re-attach-the-mixer-control-elem.patch - WARN
=> This seems to squash two commits from the upstream merge-proposal
   (with some random whitespace fixes in empty lines).
   Can you please either make it two clean cherry-picks or mention it's a "backport" instead of "upstream" inside the DEP-3 Origin-header and briefly explain the changes.
 2:  2afc6051c <  -:  --------- [PATCH 04/38] alsa-mixer: allow to re-attach the mixer control element
 -:  --------- >  2:  3177f41cb alsa-mixer: allow to re-attach the mixer control element
 -:  --------- >  3:  4066bbaf0 alsa-mixer: fix the re-attach code for the mixer control element

UCM_updates/alsa-mixer-extend-pa_alsa_mixer_find-with-the-subdev.patch - OK
UCM_updates/alsa-util-Add-more-standard-sample-rates.patch             - OK
UCM_updates/alsa-util-Dump-probed-rates.patch                          - OK
UCM_updates/alsa-util-Perform-format-and-rate-detection-before-s.patch - OK
UCM_updates/alsa-util-Fix-pa_alsa_get_supported_formats-fallback.patch - OK
UCM_updates/alsa-ucm-Fix-spurious-mixer-path-removal-on-initial-.patch - OK
UCM_updates/alsa-ucm-Always-create-device-conflicting-supported-.patch - OK
UCM_updates/alsa-ucm-Make-modifiers-track-conflicting-supported-.patch - OK
UCM_updates/alsa-ucm-Add-enable-disable-status-helpers-for-devic.patch - OK
UCM_updates/alsa-ucm-Set-profiles-by-their-struct-instance-not-t.patch - OK
UCM_updates/alsa-ucm-Let-profiles-know-their-associated-UCM-verb.patch - OK
UCM_updates/alsa-ucm-Stop-conflating-profile-name-with-UCM-verb-.patch - OK
UCM_updates/alsa-ucm-Make-mapping-creation-independent-from-indv.patch - OK
UCM_updates/alsa-ucm-Split-profile-creation-into-verb-and-profil.patch - OK
UCM_updates/acp-Add-idxset-comparison-and-reverse-search-operati.patch - OK
UCM_updates/alsa-ucm-Rewrite-conformant-device-group-generation-.patch - OK
UCM_updates/alsa-ucm-Fix-device-conformance-check.patch                - OK
UCM_updates/alsa-ucm-Split-out-helpers-for-device-set-name-descr.patch - OK
UCM_updates/alsa-ucm-Make-one-input-output-mapping-per-UCM-devic.patch - OK
UCM_updates/alsa-ucm-Remove-combination-port-generation-logic.patch    - OK
UCM_updates/alsa-ucm-Make-ports-store-only-one-device.patch            - OK
UCM_updates/alsa-ucm-Make-mapping-UCM-contexts-have-only-one-dev.patch - OK
UCM_updates/alsa-ucm-Make-mapping-UCM-contexts-have-only-one-mod.patch - WARN
=> nitpick: slight difference in commit message, can you make it a clean cherry-pick?
UCM_updates/alsa-ucm-Disable-old-devices-when-switching-profiles.patch - OK
UCM_updates/alsa-ucm-Create-multiple-profiles-per-verb-for-confl.patch - OK
UCM_updates/alsa-ucm-Add-enable-disable-status-helpers-for-modif.patch - OK
UCM_updates/alsa-ucm-Disable-old-modifiers-when-switching-profil.patch - OK
UCM_updates/alsa-ucm-Consider-devices-using-the-same-PCM-as-inco.patch - OK
UCM_updates/alsa-ucm-Fix-more-instances-of-profile-verb-conflati.patch - OK
UCM_updates/alsa-ucm-Check-UCM-verb-before-working-with-device-s.patch - OK
UCM_updates/alsa-ucm-Replace-port-device-UCM-context-assertion-w.patch - OK
UCM_updates/acp-Don-t-sync-hardware-volumes-while-UCM-device-is-.patch - OK
UCM_updates/acp-Disable-active-UCM-profile-before-enabling-Pro-A.patch - OK

lp2122556_0001-acp-sync-the-mixer-after-selecting-the-port.patch - WARN
=> nitpick: some minimal diff of whitespace in empty lines, can you make it a clean cherry-pick?

lp2122556_0002-spa-alsa-do-not-allow-setting-Route-that-is-not-in-c.patch - WARN
=> diff in patch context. Please mention it's a "backport" instead of "upstream" inside DEP-3 Origin-header and briefly explain the changes.

** Tags added: block-proposed-noble

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to pipewire in Ubuntu.
https://bugs.launchpad.net/bugs/2122556

Title:
  3.5mm microphone recognized but can’t be used as audio input

Status in OEM Priority Project:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in pipewire source package in Noble:
  New
Status in pipewire source package in Plucky:
  In Progress

Bug description:
  [ Impact ]
  Plug-in 3.5mm headset to Dell Pro 14 Premium PA14250.
  Microphone can be recognized, but it can't capture audio in g-c-c or any sound record application

  Restart pipewire can workaround the issue.
  $ systemctl --user restart pipewire

  [ Test Plan ]
  Find Dell Pro 14 Premium PA14250, plugin 3.5mm headset. Microphone can be recognized and able to record sound with applications

  [ Where problems could occur ]
  This SRU going to improve UCM handling and may affect the audio behavior.
  The large patch sets added from pipewire 1.1.83. And been landed and tested in Plucky.

  [ Other Info ]
  * Apport information
   ProblemType: Bug
   ApportVersion: 2.28.1-0ubuntu3.8
   Architecture: amd64
   CasperMD5CheckMismatches: ./casper/initrd ./casper/vmlinuz ./casper/minimal.standard.live.hotfix.manifest ./casper/minimal.standard.live.hotfix.size ./casper/minimal.standard.live.size ./casper/minimal.manifest ./casper/minimal.standard.manifest ./casper/minimal.standard.size ./casper/minimal.hotfix.size ./casper/minimal.standard.live.hotfix.squashfs ./casper/minimal.standard.hotfix.squashfs ./casper/minimal.standard.hotfix.size ./casper/minimal.hotfix.squashfs ./casper/minimal.standard.live.manifest ./casper/minimal.size ./boot/grub/grub.cfg
   CasperMD5CheckResult: fail
   DistributionChannelDescriptor:
     # This is the distribution channel descriptor for Ubuntu 24.04 for Dell
     # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
     canonical-oem-somerville-noble-oem-24.04b-next-20250317-202
   DistroRelease: Ubuntu 24.04
   InstallationDate: Installed on 2025-09-05 (6 days ago)
   InstallationMedia: Ubuntu OEM 24.04.1 LTS "Noble Numbat" - Release amd64 (20250316)
   Package: pipewire 1.0.5-1ubuntu3.1
   PackageArchitecture: amd64
   ProcEnviron:
    LANG=en_US.UTF-8
    PATH=(custom, no user)
    SHELL=/bin/bash
    TERM=xterm-256color
    XDG_RUNTIME_DIR=<set>
   ProcVersionSignature: User Name 6.14.0-29.29~24.04.1-generic 6.14.8
   Tags: noble
   Uname: Linux 6.14.0-29-generic x86_64
   UpgradeStatus: No upgrade log present (probably fresh install)
   UserGroups: adm cdrom dip lxd sudo
   _MarkForUpload: True

  * Related upstream patches
   - UCM updates
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/merge_requests/1800
   - vendor suggested fix
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/b9e130fd8c4893368613fb57ec87a0d70460f6b5
     - https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/d42bfa56b7c94afa113048529d430c811c8ba651

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2122556/+subscriptions