[Pkg-utopia-maintainers] Processing of pipewire_0.3.58-1_source.changes

pipewire_0.3.58-1_source.changes uploaded successfully to localhost along with the files: pipewire_0.3.58-1.dsc pipewire_0.3.58.orig.tar.bz2 pipewire_0.3.58-1.debian.tar.xz pipewire_0.3.58-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

[Pkg-utopia-maintainers] pipewire_0.3.58-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 16 Sep 2022 15:41:31 +0200 Source: pipewire Architecture: source Version: 0.3.58-1 Distribution: unstable Urgency: medium Maintainer: Utopia Maintenance Team Changed-By: Dylan Aïssi Closes: 998220 1011035

[Pkg-utopia-maintainers] Bug#1011399: marked as done (pipewire: create pipewire group with rlimits for rtprio/priority/memlock)

Your message dated Fri, 16 Sep 2022 14:36:19 + with message-id and subject line Bug#1011399: fixed in pipewire 0.3.58-1 has caused the Debian Bug report #1011399, regarding pipewire: create pipewire group with rlimits for rtprio/priority/memlock to be marked as done. This means that you

[Pkg-utopia-maintainers] Bug#1013276: marked as done (Alsa clients using the wrong plugin if pulseaudio is installed)

Your message dated Fri, 16 Sep 2022 14:36:19 + with message-id and subject line Bug#1013276: fixed in pipewire 0.3.58-1 has caused the Debian Bug report #1013276, regarding Alsa clients using the wrong plugin if pulseaudio is installed to be marked as done. This means that you claim that the

[Pkg-utopia-maintainers] Bug#1011035: marked as done (pipewire: should pipewire depend/recommend libspa-0.2-bluetooth?)

Your message dated Fri, 16 Sep 2022 14:36:19 + with message-id and subject line Bug#1011035: fixed in pipewire 0.3.58-1 has caused the Debian Bug report #1011035, regarding pipewire: should pipewire depend/recommend libspa-0.2-bluetooth? to be marked as done. This means that you claim that

[Pkg-utopia-maintainers] Bug#1019888: marked as done (pipewire 0.3.57-1: no/crackling sound if pavucontrol is open, 0.3.56-1 is fine)

Your message dated Fri, 16 Sep 2022 14:36:19 + with message-id and subject line Bug#1019888: fixed in pipewire 0.3.58-1 has caused the Debian Bug report #1019888, regarding pipewire 0.3.57-1: no/crackling sound if pavucontrol is open, 0.3.56-1 is fine to be marked as done. This means that

[Pkg-utopia-maintainers] Bug#998220: marked as done (pipewire: libspa-0.2-bluetooth not installed)

Your message dated Fri, 16 Sep 2022 14:36:19 + with message-id and subject line Bug#998220: fixed in pipewire 0.3.58-1 has caused the Debian Bug report #998220, regarding pipewire: libspa-0.2-bluetooth not installed to be marked as done. This means that you claim that the problem has been

[Pkg-utopia-maintainers] Bug#1019944: wireplumber: Upgradeing to 0.4.11-5 breaks restoring the target of a stream if it is not the default stream

Hi, with the help of NiklvsKoesikovs from the pipewire irc channel we came to the conclusion that the order in which pipewire-pulse and wireplumber are started matter. pipewire-pulse has to be startet AFTER wireplumber. Please add this to the systemd service file. Thanks Matthias

[Pkg-utopia-maintainers] Bug#1019944: wireplumber: Upgradeing to 0.4.11-5 breaks restoring the target of a stream if it is not the default stream

Package: wireplumber Version: 0.4.11-3 Severity: important X-Debbugs-Cc: m...@familie-heinz.name Hi, after upgrade wireplumber from 0.4.11-3 to 0.4.11-5 it fails to somehow realize what the target of the last stream was, if it was not the default device. pavucontrol just reports it as "Unknown

[Pkg-utopia-maintainers] Bug#995486: pipewire: crash when -media-session connects

On Mon, Sep 12, 2022 at 04:45:36PM +0200, Dylan Aïssi wrote: > Le sam. 2 oct. 2021 à 01:21, Adam Borowski a écrit : > > Upon startup, pipewire crashes for me. After poking around, it turns out > > it's not the startup of pipewire itself, but pipewire-media-session connects > > to the main part