Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#1024093: pipewire: Upgrade to pipewire 0.3.60-1 breaks sound

43 views
Skip to first unread message

Chris Nospam

unread,
Nov 14, 2022, 1:30:03 PM11/14/22
to
Package: pipewire
Version: 0.3.60-1
Severity: important
X-Debbugs-Cc: chri...@gmx.de

Dear Maintainer,

using pipewire 0.59-1 under debian testing (with pusleaudio package uninstalled
if this should matter) makes no problem. I have copied
/usr/share/doc/pipewire/examples/alsa.conf.d to /etc/alsa . However, after
upgrading today to pipewire 0.3.60-1 (and rebooting) sound is broken. KDE
notifications, firefox on yoputube or a aplay x.wav do not make any sound to
come out of my speakers. After downgrading again, everything seems to work fine
again.

Thanks,
Chris


-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-3-amd64 (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire depends on:
ii adduser 3.129
ii init-system-helpers 1.65.2
ii libpipewire-0.3-modules 0.3.60-1
ii pipewire-bin 0.3.60-1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

Chris Nospam

unread,
Nov 16, 2022, 6:30:03 AM11/16/22
to
I am using a kvm virtualized installation of bookworm (I did not try it yet on my bare metal installation). Below see some informations which may help. Within syslog I find no spefic entries via 'grep pipewire' which could give me a hint, but I can provide conrete log snippets if you tell what to search for.

$aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: Generic Analog [Generic Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

$ pactl list sinks
Sink #46
State: SUSPENDED
Name: alsa_output.pci-0000_00_1b.0.analog-stereo
Description: Internes Audio Analog Stereo
Driver: PipeWire
Sample Specification: s16le 2ch 48000Hz
Channel Map: front-left,front-right
Owner Module: 4294967295
Mute: no
Volume: front-left: 65536 / 100% / 0,00 dB, front-right: 65536 / 100% / 0,00 dB
balance 0,00
Base Volume: 65536 / 100% / 0,00 dB
Monitor Source: alsa_output.pci-0000_00_1b.0.analog-stereo.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE HW_MUTE_CTRL HW_VOLUME_CTRL DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "0"
alsa.card_name = "HDA Intel"
alsa.class = "generic"
alsa.device = "0"
alsa.driver_name = "snd_hda_intel"
alsa.id = "Generic Analog"
alsa.long_card_name = "HDA Intel at 0xc1940000 irq 48"
alsa.name = "Generic Analog"
alsa.resolution_bits = "16"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
api.alsa.card.longname = "HDA Intel at 0xc1940000 irq 48"
api.alsa.card.name = "HDA Intel"
api.alsa.headroom = "8192"
api.alsa.path = "front:0"
api.alsa.pcm.card = "0"
api.alsa.pcm.stream = "playback"
api.alsa.period-size = "256"
audio.channels = "2"
audio.position = "FL,FR"
card.profile.device = "3"
device.api = "alsa"
device.class = "sound"
device.id = "40"
device.profile.description = "Analog Stereo"
device.profile.name = "analog-stereo"
device.routes = "1"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "Internes Audio"
node.name = "alsa_output.pci-0000_00_1b.0.analog-stereo"
node.nick = "Generic Analog"
node.pause-on-idle = "false"
object.path = "alsa:pcm:0:front:0:playback"
priority.driver = "1009"
priority.session = "1009"
factory.id = "18"
clock.quantum-limit = "8192"
client.id = "32"
node.driver = "true"
factory.mode = "merge"
audio.adapt.follower = ""
library.name = "audioconvert/libspa-audioconvert"
object.id = "45"
object.serial = "46"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "0"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio0"
device.bus = "pci"
device.bus_path = "pci-0000:00:1b.0"
device.enum.api = "udev"
device.form_factor = "internal"
device.icon_name = "audio-card-analog-pci"
device.name = "alsa_card.pci-0000_00_1b.0"
device.nick = "HDA Intel"
device.plugged.usec = "3649773"
device.product.id = "0x293e"
device.product.name = "82801I (ICH9 Family) HD Audio Controller (QEMU Virtual Machine)"
device.subsystem = "sound"
sysfs.path = "/sys/devices/pci0000:00/0000:00:1b.0/sound/card0"
device.vendor.id = "0x8086"
device.vendor.name = "Intel Corporation"
device.string = "0"
Ports:
analog-output-lineout: Line-Ausgang (type: Line, priority: 9000, availability group: Legacy 2, availability unknown)
Active Port: analog-output-lineout
Formats:
pcm

Dylan Aïssi

unread,
Nov 16, 2022, 7:10:04 AM11/16/22
to
Hi Chris,

Le mer. 16 nov. 2022 à 12:27, Chris Nospam <chri...@gmx.de> a écrit :
>
> I am using a kvm virtualized installation of bookworm (I did not try it yet on my bare metal installation). Below see some informations which may help. Within syslog I find no spefic entries via 'grep pipewire' which could give me a hint, but I can provide conrete log snippets if you tell what to search for.
>

I think you are facing this bug:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2830

Can you check if it is really the case? If so, can you add your voice
to the upstream bug?

Thanks,
Dylan

Chris Nospam

unread,
Nov 17, 2022, 11:30:03 AM11/17/22
to
Hi Dylan,

thanks for maintaining pipewire and your hint!

Now I did the upgrade on my bare metal installation and there the problem does not show up (in contrast to the virtualized one). So it is most likely the upstream issue you have mentioned. However, it is unclear/difficult for me how to try out the in the upstream issue mentioned "pushed fix" in my vm.
As you have suggested, I have made an entry to the upstream bug report that I am probably also affected, although the issue seems to be already closed.

Chris

Dylan Aïssi

unread,
Nov 17, 2022, 11:40:03 AM11/17/22
to
Hi Chris,

Le jeu. 17 nov. 2022 à 17:21, Chris Nospam <chri...@gmx.de> a écrit :
>
> As you have suggested, I have made an entry to the upstream bug report that I am probably also affected, although the issue seems to be already closed.
>

Thanks!

I received the notification from the upstream bug while I was
preparing a patched version of the package :-).
You should be able to update your package from debian/unstable in the
next few minutes (hours?).

Best,
Dylan

Chris Nospam

unread,
Nov 18, 2022, 7:30:03 AM11/18/22
to
Hi Dylan,

indeed, version 0.3.60-2 solves the virtualization sound problem. Thanks for building the package!

All the best,
Chris

graeme vetterlein

unread,
Nov 25, 2022, 12:40:04 PM11/25/22
to

I appreciate this has been marked closed , but I'm not seeing it fixed.

This seemed such an basic bug, I'd assumed it would have been reported multiple times.

with 0.3.60-1    it played video using smplayer but not mpv , firefox youtube was choppy . When run via x2go, videos would not play at all


now with 0.3.60-3 , on native XFCE: mpv, smplayer, firefox+youtube are all choppy ... in fact I had to log out and back in to get any sound, when I tried to retest for this report.

    Via X2go:  mpv fails to play at all, smplayer is smooth,  and firefox+youtube is OK


The audio is via an HDMI connection (same settup worked fine on buster)


...I get similar effects with .mp3 audio files, but I only did a few samples.


smplayer = choppy

mpv = choppy

Parole Media Player = choppy




Probably warrants some basic tests , which I'm happy to run , given a (human) script of some kind.


XFCE desktop, HDMI connected speakers


graeme@real:~$ apt-cache rdepends pipewire
pipewire
Reverse Depends:
  wireplumber
  xdg-desktop-portal-wlr
  xdg-desktop-portal-tests
  pipewire-media-session
  sxmo-utils
  gstreamer1.0-pipewire
  pipewire-v4l2
  pipewire-tests
  pipewire-pulse
  pipewire-libcamera
  pipewire-jack
  pipewire-bin
  pipewire-bin
  pipewire-alsa
  libspa-0.2-modules
  libspa-0.2-modules
  libpipewire-0.3-modules
  libpipewire-0.3-modules
  libpipewire-0.3-0
  gnome-remote-desktop
graeme@real:~$ apt show pipewire 2> /dev/null | grep Version
Version: 0.3.60-3
graeme@real:~$ apt show wireplumber 2> /dev/null | grep Version
Version: 0.4.12-1+b1



-- System Information:
Debian Release: bookworm/sid

  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en

James Bottomley

unread,
Nov 26, 2022, 9:50:04 AM11/26/22
to
mythtv still works fine, but google-chrome (used for streaming)
doesn't. I'm still using pulseaudio with pipewire-pulse and what
pavucontrol shows me is google-chrome having difficulty connecting to
the audio output (keeps appearing and disappearing in the playback
tab).

Falling back to 0.3.58 fixes everything

James Bottomley

unread,
Dec 3, 2022, 9:50:04 AM12/3/22
to
I just tested this out with the same results as previously reported

James

Dylan Aïssi

unread,
Dec 4, 2022, 4:50:04 PM12/4/22
to
Le sam. 3 déc. 2022 à 15:45, James Bottomley
<James.B...@hansenpartnership.com> a écrit :
>
> I just tested this out with the same results as previously reported
>

Do you mean you don't have sound at all using pipewire 0.3.61 in a QEMU VM?

James Bottomley

unread,
Dec 4, 2022, 5:40:04 PM12/4/22
to
No, this is a physical system. The sound problems are only partial as
described at

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024093#45

James

Dylan Aïssi

unread,
Dec 4, 2022, 6:00:04 PM12/4/22
to
Le dim. 4 déc. 2022 à 23:28, James Bottomley
<James.B...@hansenpartnership.com> a écrit :
>
> On Sun, 2022-12-04 at 22:42 +0100, Dylan Aïssi wrote:
> > Le sam. 3 déc. 2022 à 15:45, James Bottomley
> > <James.B...@hansenpartnership.com> a écrit :
> > >
> > > I just tested this out with the same results as previously reported
> > >
> >
> > Do you mean you don't have sound at all using pipewire 0.3.61 in a
> > QEMU VM?
>
> No, this is a physical system. The sound problems are only partial as
> described at
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024093#45
>

Then your issue is absolutely not related to the initial issue of #1024093
that was about sound not working at all in a QEMU VM and that bug was fixed
in pipewire/0.3.60-2.

So please restore the state of this bug report and open your own bug report.


Dylan

James Bottomley

unread,
Dec 4, 2022, 6:20:04 PM12/4/22
to
On Sun, 2022-12-04 at 23:49 +0100, Dylan Aïssi wrote:
> Le dim. 4 déc. 2022 à 23:28, James Bottomley
>
> So please restore the state of this bug report and open your own bug
> report.

I'm not really as expert in the bug control system as debian developers
are supposed to be but I think I got this done.

James

graeme vetterlein

unread,
Jan 1, 2023, 4:30:03 PM1/1/23
to

Sorry to have cause confusion here.

I was pointed at 1024093 from elsewhere. When it seemed a good match

but was still broken I added my 2 cents wroth. I didn't spot it was a virtual environment.


Thanks to James for doing the admin of cloning the bug.


It's now just over 5 weeks from my original comment and the behaviour is unchanged.


I'll repeat my offer to run some tests, if somebody could suggest a good set.


--


Graeme



graeme vetterlein

unread,
Mar 18, 2023, 10:00:03 AM3/18/23
to

I see this is marked as the only "important" bug in pipewire.


I, for one, have had no sound for the past 4 months. Not personally critical as it's an unstable dev system, not main dev machine.  


But I'm guessing this is being targeted as the new "sound system" in Debian 12 . Is it being

worked on?  Is there a major problem?


I'm wondering if pipewire is no longer destined for "Debian 12" ?


--


Graeme



Dylan Aïssi

unread,
Mar 20, 2023, 7:10:04 AM3/20/23
to
Le sam. 18 mars 2023 à 14:51, graeme vetterlein
<graeme.r...@vetterlein.com> a écrit :
>
> I, for one, have had no sound for the past 4 months. Not personally critical as it's an unstable dev system, not main dev machine.
>

Do you have no sound at all or choppy sound like you said in [1].
Have you tried using speakers not connected via HDMI? I guess it is related
to HDMI connection, can you fill a bug on the upstream bug tracker [2]?

[1] https://bugs.debian.org/1025453#40
[2] https://gitlab.freedesktop.org/pipewire/pipewire/-/issues

graeme vetterlein

unread,
Mar 21, 2023, 3:00:06 PM3/21/23
to
Indeed it was simply choppy. I (personally) have no sound because I had
to turn it off, it was unlistenable.

I don't have other "speakers" but I plugged in a set of headphones, I
assume that's equivalent?
Anyhow sound from the headphones was fine. (tested with mpv and Lxmusic)

graeme vetterlein

unread,
Mar 21, 2023, 3:20:04 PM3/21/23
to


On 20/03/2023 11:07, Dylan Aïssi wrote:

graeme vetterlein

unread,
Mar 25, 2023, 7:50:03 AM3/25/23
to

I've switched to experimental , for : pipewire + libpipewire*

$ apt-cache policy pipewire
pipewire:
  Installed: 0.3.67-1
  Candidate: 0.3.67-1
  Version table:
 *** 0.3.67-1 800
          1 https://deb.debian.org/debian experimental/main amd64 Packages
        100 /var/lib/dpkg/status
     0.3.65-3 500
        500 http://ftp.uk.debian.org/debian unstable/main amd64 Packages
        500 http://ftp.de.debian.org/debian sid/main amd64 Packages
graeme@real:~/Documents/Remote/Bugs/22mar2023-pipewire-freedeskt>op$


So now 0.3.67-1 .. bug persists 



graeme vetterlein

unread,
Jun 27, 2023, 1:10:04 PM6/27/23
to
Having seen bookworm go to stable with this bug still present, I did
some more digging.


This comment:  https://forums.debian.net/viewtopic.php?t=150032


Points at an earlier bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867548#52


And applying their workaround, my issue disappears:


[ edit /etc/default/grub to add

GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on,igfx_off"
]


However reading the forum post, it appears they hit the issue on
upgrading to "bullseye"

I get the issue upgrading from "bullseye" to "sid (bookworm)".


Now, for me, this was very much "Monkey See, Monkey do"  I don't know
what that line added to kernel boot args does, but:


1: Maybe it's avoiding something that broken  ..or

2: It is the correct option that should be added


I either case, something is broken. It works on one release, you
upgrade, it breaks.


My initial guess would be something in the initrd generation or grub
choices is going wrong during the install process.


Could somebody move this issue to a more sensible place (package) as
it's unclear to me where the root problem lies (also tie to 867548 )

graeme vetterlein

unread,
Jun 27, 2023, 1:20:06 PM6/27/23
to

The following may be helpful:


1: I am running this on bare matal (no KVM, vmware etc)

2:

$cat /proc/cupinfo

processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 60
model name    : Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
stepping    : 3
microcode    : 0x9
cpu MHz        : 823.533
cache size    : 8192 KB
physical id    : 0
siblings    : 8
core id        : 0
cpu cores    : 4
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 13
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm cpuid_fault invpcid_single pti tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm xsaveopt dtherm ida arat pln pts
vmx flags    : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple shadow_vmcs
bugs        : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit srbds mmio_unknown
bogomips    : 6799.82
clflush size    : 64
cache_alignment    : 64
address sizes    : 39 bits physical, 48 bits virtual
power management:

processor    : 1

...elided...


graeme vetterlein

unread,
Jun 27, 2023, 1:40:04 PM6/27/23
to

Actually it looks like it's coming up on its first decade


https://bugzilla.kernel.org/show_bug.cgi?id=86311


sb7...@gmail.com

unread,
Nov 6, 2023, 10:20:04 PM11/6/23
to
I can confirm that this bug affects me in Bookworm + Pipewire with this hardware (and a DisplayPort->HDMI adapter):

================================================
System:
Host: T440s Kernel: 6.1.0-13-amd64 arch: x86_64 bits: 64 Desktop: Cinnamon
v: 5.6.8 Distro: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Laptop System: LENOVO product: 20AR006RUS v: ThinkPad T440s
Mobo: LENOVO model: 20AR006RUS v: SDK0E50510 PRO
UEFI: LENOVO v: GJETA4WW (2.54 )
date: 03/27/2020
CPU:
Info: dual core Intel Core i5-4300U [MT MCP] speed (MHz): avg: 805
min/max: 800/2900
Graphics:
Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
Device-2: Chicony Integrated Camera type: USB driver: uvcvideo
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: modesetting
unloaded: fbdev,vesa dri: crocus gpu: i915 resolution: 1366x768~60Hz
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: Mesa Intel HD Graphics 4400 (HSW
GT2)
Network:
Device-1: Intel Ethernet I218-LM driver: e1000e
Device-2: Intel Wireless 7260 driver: iwlwifi
Device-3: Intel Bluetooth wireless interface type: USB driver: btusb
================================================


I also tried the Backports 6.4 kernel with the same results.


The workaround suggested earlier in this report works:
> edit /etc/default/grub to add
> GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on,igfx_off"


This is definitely a Debian issue, because openSUSE Tumbleweed + Pipewire on this same hardware does not have this bug.
0 new messages