Bug#1025069: pipewire: audio broken, only says Dummy Output (on plain bookworm install)

[Hans-Christoph Steiner]

Package: pipewire
Version: 0.3.61-1
Severity: important

Dear Maintainer,

I'm running a plain, default install of bookworm that was upgraded
from bullseye. Audio output worked under bullseye, and at first under
bookworm. Then an upgrade broke the audio. Now, the only audio
device available in the GNOME Sound Settings is "Dummy Output" and it
is not possible get sound output from any of the default apps
(browsers, VLC, etc).

I can get sound output using the Pd-extended flatpak package, which
seems to directly access ALSA. That is why I filed this bug against
pipewire.

The computer is an ASUS Chromebook delbin so Linux does support
it. Here is some hopefully useful debug info:


hans@delbin:~$ pw-cli info 0
id: 0
permissions: rwxm
type: PipeWire:Interface:Core/3
cookie: 3757616015
user-name: "hans"
host-name: "delbin"
version: "0.3.61"
name: "pipewire-0"
* properties:
* config.name = "pipewire.conf"
* link.max-buffers = "16"
* core.daemon = "true"
* core.name = "pipewire-0"
* default.clock.min-quantum = "16"
* cpu.max-align = "64"
* default.clock.rate = "48000"
* default.clock.quantum = "1024"
* default.clock.max-quantum = "2048"
* default.clock.quantum-limit = "8192"
* default.video.width = "640"
* default.video.height = "480"
* default.video.rate.num = "25"
* default.video.rate.denom = "1"
* log.level = "2"
* clock.power-of-two-quantum = "true"
* mem.warn-mlock = "false"
* mem.allow-mlock = "true"
* settings.check-quantum = "false"
* settings.check-rate = "false"
* object.id = "0"
* object.serial = "0"

hans@delbin ~$ sudo journalctl | grep wire
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Rejected send message, 0
matched rules; type="error", sender=":1.71" (uid=1000 pid=2238
comm="/usr/bin/wireplumber") interface="(unset)" member="(unset)" error
name="org.bluez.MediaEndpoint1.Error.NotImplemented" requested_reply="0"
destination=":1.2" (uid=0 pid=844 comm="/usr/libexec/bluetooth/bluetoothd")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Activating via systemd:
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.71'
(uid=1000 pid=2238 comm="/usr/bin/wireplumber")
Nov 26 22:53:37 delbin dbus-daemon[846]: [system] Activating via systemd:
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.71'
(uid=1000 pid=2238 comm="/usr/bin/wireplumber")
Nov 26 22:53:37 delbin wireplumber[2238]: stopped by signal: Terminated
Nov 26 22:53:37 delbin wireplumber[2238]: disconnected from pipewire
Nov 26 22:53:37 delbin systemd[2206]: wireplumber.service: Consumed 1.036s CPU time.
Nov 26 22:54:20 delbin wireplumber[1092]: Can't find xdg-portal: (null)
Nov 26 22:54:20 delbin wireplumber[1092]: found session bus but no portal
Nov 26 22:54:20 delbin pipewire-pulse[1093]: mod.rt: Can't find xdg-portal: (null)
Nov 26 22:54:20 delbin pipewire-pulse[1093]: mod.rt: found session bus but no portal
Nov 26 22:54:20 delbin pipewire[1090]: mod.rt: Can't find xdg-portal: (null)
Nov 26 22:54:20 delbin pipewire[1090]: mod.rt: found session bus but no portal
Nov 26 22:54:20 delbin dbus-daemon[845]: [system] Activating via systemd:
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service'
requested by ':1.24' (uid=116 pid=1093 comm="/usr/bin/pipewire-pulse")
Nov 26 22:54:20 delbin pipewire[1090]: mod.x11-bell: XOpenDisplay() failed
Nov 26 22:54:21 delbin wireplumber[1092]: Failed to set scheduler settings:
Operation not permitted
Nov 26 22:54:21 delbin wireplumber[1092]: SPA handle
'api.libcamera.enum.manager' could not be loaded; is it installed?
Nov 26 22:54:21 delbin wireplumber[1092]: PipeWire's libcamera SPA missing or
broken. libcamera not supported.
Nov 26 22:54:21 delbin pipewire-pulse[1205]: 536870912
Nov 26 22:54:21 delbin wireplumber[1092]: Trying to use legacy bluez5 API for LE
Audio - only A2DP will be supported. Please upgrade bluez5.
Nov 26 22:54:24 delbin NetworkManager[887]: <info> [1669499664.3297] device
(wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.
Connected to wireless network "N"
Nov 26 22:54:26 delbin wireplumber[2182]: Can't find xdg-portal: (null)
Nov 26 22:54:26 delbin wireplumber[2182]: found session bus but no portal
Nov 26 22:54:26 delbin pipewire-pulse[2183]: mod.rt: Can't find xdg-portal: (null)
Nov 26 22:54:26 delbin pipewire-pulse[2183]: mod.rt: found session bus but no portal
Nov 26 22:54:26 delbin pipewire[2180]: mod.rt: Can't find xdg-portal: (null)
Nov 26 22:54:26 delbin pipewire[2180]: mod.rt: found session bus but no portal
Nov 26 22:54:26 delbin pipewire[2180]: mod.x11-bell: XOpenDisplay() failed
Nov 26 22:54:26 delbin pipewire-pulse[2233]: 536870912
Nov 26 22:54:26 delbin wireplumber[2182]: Failed to set scheduler settings:
Operation not permitted
Nov 26 22:54:26 delbin wireplumber[2182]: SPA handle
'api.libcamera.enum.manager' could not be loaded; is it installed?
Nov 26 22:54:26 delbin wireplumber[2182]: PipeWire's libcamera SPA missing or
broken. libcamera not supported.
Nov 26 22:54:27 delbin wireplumber[2182]: Trying to use legacy bluez5 API for LE
Audio - only A2DP will be supported. Please upgrade bluez5.
Nov 26 22:54:40 delbin wireplumber[1092]: stopped by signal: Terminated
Nov 26 22:54:40 delbin wireplumber[1092]: disconnected from pipewire



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

Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
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 gstreamer1.0-pipewire:amd64 0.3.61-1
un gstreamer1.0-pulseaudio <none>
ii init-system-helpers 1.65.2
ii libpipewire-0.3-0:amd64 0.3.61-1
ii libpipewire-0.3-common 0.3.61-1
ii libpipewire-0.3-modules 0.3.61-1
ii libpipewire-0.3-modules:amd64 0.3.61-1
un libsdl1.2debian-pulseaudio <none>
ii pipewire-bin 0.3.61-1
ii pipewire-pulse 0.3.61-1
ii pipewire:amd64 0.3.61-1
un pipewire-media-session <none>
ii pulseaudio 16.1+dfsg1-2+b1
un pulseaudio-module-bluetooth <none>
ii pulseaudio-utils 16.1+dfsg1-2+b1
ii vlc-plugin-pipewire:amd64 3-2
ii wireplumber 0.4.12-1+b1

pipewire recommends no packages.

pipewire suggests no packages.

-- no debconf information

[Dylan Aïssi]

Hi,

Le mar. 29 nov. 2022 à 15:51, Hans-Christoph Steiner <ha...@eds.org> a écrit :
>
> hans@delbin ~$ sudo journalctl | grep wire

> ...

> Nov 26 22:54:40 delbin wireplumber[1092]: stopped by signal: Terminated
> Nov 26 22:54:40 delbin wireplumber[1092]: disconnected from pipewire
>

> Versions of packages pipewire depends on:

> ...
> ii pulseaudio 16.1+dfsg1-2+b1

I suspect it is a conflict between pulseaudio and pipewire-pulse and a
duplicate of
https://bugs.debian.org/1021530

Can you check if the pulseaudio service is running? If so, can you try
to disable (and mask)
pulseaudio service and socket and restart pipewire, pipewire-pulse and
wireplumber
services? These steps are describe at https://wiki.debian.org/PipeWire

If you are facing this conflict, you can also just remove the
pulseaudio package. It looks
like I really have to mark pipewire-pulse in conflict with pulseaudio.

Best,
Dylan

[Patrice Duroux]

Hi,

I think it would be a shame to come to this: package conflict.

This means that on the same system, their users must exclusively use one same
software and sometimes leaving the decision to the root users (who may also
disagree themselves).
Ideally, it would be even more powerful Debian proposal if, in such a case,
users run whatever in parallel (and without pushing the problem to the container
side). I know that it is not always possible but to consider it is a (big) plus
to me. It also facilite comparison: one time with pulseaudio, one time with
pipewire, without the installing/purging danse.

A documentation and/or a simple setting command to run that solves is a better
way to my opinion. Could a management script and making the switch be helpful?

Regards,
Patrice

[Hans-Christoph Steiner]

You can ping me on IRC (_hc) or matrix (@eighthave:matrix.org) if you want to
try it interactively. pulseaudio was not running as far as I could tell.

root@delbin:~# service pulseaudio-enable-autospawn status
○ pulseaudio-enable-autospawn.service
Loaded: masked (Reason: Unit pulseaudio-enable-autospawn.service is masked.)
Active: inactive (dead)
hans@delbin:~$ ps auxww|grep pulse
hans 68885 0.0 0.1 35168 10600 ? S<sl 20:50 0:00
/usr/bin/pipewire-pulse
hans 80426 0.0 0.0 9568 2204 pts/1 S+ 21:04 0:00 grep pulse
hans@delbin:~$ systemctl --user --now enable wireplumber.service
hans@delbin:~$ journalctl --user -u pipewire --user -u wireplumber --user -u
pipewire-pulse -f

Nov 26 22:54:26 delbin pipewire-pulse[2233]: 536870912
Nov 26 22:54:26 delbin wireplumber[2182]: Failed to set scheduler settings:
Operation not permitted
Nov 26 22:54:26 delbin wireplumber[2182]: SPA handle
'api.libcamera.enum.manager' could not be loaded; is it installed?
Nov 26 22:54:26 delbin wireplumber[2182]: PipeWire's libcamera SPA missing or
broken. libcamera not supported.
Nov 26 22:54:27 delbin wireplumber[2182]: Trying to use legacy bluez5 API for LE
Audio - only A2DP will be supported. Please upgrade bluez5.

Dec 01 20:50:55 delbin systemd[2147]: Stopping PipeWire PulseAudio...
Dec 01 20:50:55 delbin systemd[2147]: Stopped PipeWire PulseAudio.
Dec 01 20:50:55 delbin systemd[2147]: pipewire-pulse.service: Consumed 17.350s
CPU time.
Dec 01 20:50:55 delbin systemd[2147]: Started PipeWire PulseAudio.
Dec 01 20:50:55 delbin pipewire-pulse[68890]: 536870912
hans@delbin:~$ systemctl status|grep -e pipe -e wire -e pulse
│ │ └─80108 grep -e pipe -e wire -e pulse
├─pipewire-pulse.service
│ └─68885 /usr/bin/pipewire-pulse
├─pipewire.service
│ └─2180 /usr/bin/pipewire
├─wireplumber.service
│ └─2182 /usr/bin/wireplumber

[Hans-Christoph Steiner]

It looks like it is not conflicting with pulseaudio. I tried these steps and
I'm still have only "Dummy Output". I have not restarted though

hans@delbin:~$ systemctl --user daemon-reload
hans@delbin:~$ systemctl --user --now disable pulseaudio.service pulseaudio.socket
hans@delbin:~$ systemctl --user --now enable pipewire pipewire-pulse
Created symlink
/home/hans/.config/systemd/user/default.target.wants/pipewire.service →
/usr/lib/systemd/user/pipewire.service.
Created symlink
/home/hans/.config/systemd/user/sockets.target.wants/pipewire.socket →
/usr/lib/systemd/user/pipewire.socket.
Created symlink
/home/hans/.config/systemd/user/default.target.wants/pipewire-pulse.service →
/usr/lib/systemd/user/pipewire-pulse.service.
Created symlink
/home/hans/.config/systemd/user/sockets.target.wants/pipewire-pulse.socket →
/usr/lib/systemd/user/pipewire-pulse.socket.
hans@delbin:~$ LANG=C pactl info | grep '^Server Name'
Server Name: PulseAudio (on PipeWire 0.3.61)
hans@delbin:~$ $ systemctl --user --now enable wireplumber.service
bash: $: command not found

hans@delbin:~$ systemctl --user --now enable wireplumber.service

hans@delbin:~$ systemctl --user --now enable pipewire pipewire-pulse
hans@delbin:~$ systemctl --user --now start pipewire pipewire-pulse
hans@delbin:~$ systemctl --user --now restart pipewire pipewire-pulse
hans@delbin:~$ systemctl --user --now restart wireplumber.service
hans@delbin:~$

[Hans-Christoph Steiner]

I've filed a bug upstream and am working through some debugging there:
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086

[Lucas]

I had been happily using my Roland STUDIO-CAPTURE on recent kernels
with only minor changes to /etc/pulse/daemon.conf:
default-sameple-format = S24LE
default-sample-rate = 96000

After upgrading to bookworm and away from pure pulseaudio to
pipewire-pulse (on wireplumber) I only have "Dummy Output" selectable
in Gnome's Settings.
I have modified what I could from 48000 rates to 96000 in
/usr/share/pipewire, but that didn't solve it (and I can't seem to
find a global setting for sample format). Prior to that, I'd tried
setting the STUDIO-CAPTURE's own rate to 48000 Hz, without change to
Gnome Settings' "Dummy Output" option only.

What does seem to have worked (for now) is running pavucontrol and
setting the Configuration tab's STUDIO-CAPTURE Profile to MultiChannel
Output (or selecting it as the default device for the Input and Output
tabs). I haven't rebooted yet, though, and I think I'll be needing to
set it again after every boot, as after setting it, it changes Gnome
Settings' "Output Device" to nothing and is greyed out. The "Input
Device" there may be changed to "Analog Input - STUDIO-CAPTURE", but
that reverts to the "Dummy Output" and no audio.

I think it may have to do with the STUDIO-CAPTURE's many outputs, but
I'm not sure where to set that, aside from possibly creating a device
definition, which pulseaudio alone didn't require.

Here's my pactl list sinks output after pavucontrol sets it up
working, if it helps:
Sink #470
State: RUNNING
Name: alsa_output.usb-Roland_STUDIO-CAPTURE_STCP80008c08d018c010005040a0d0c4-01.multichannel-output
Description: STUDIO-CAPTURE Multichannel
Driver: PipeWire
Sample Specification: s32le 10ch 96000Hz
Channel Map: aux0,aux1,aux2,aux3,aux4,aux5,aux6,aux7,aux8,aux9
Owner Module: 4294967295
Mute: no
Volume: aux0: 65536 / 100% / 0.00 dB, aux1: 65536 / 100% / 0.00
dB, aux2: 65536 / 100% / 0.00 dB, aux3: 65536 / 100% / 0.00 dB,
aux4: 65536 / 100% / 0.00 dB, aux5: 65536 / 100% / 0.00 dB, aux6:
65536 / 100% / 0.00 dB, aux7: 65536 / 100% / 0.00 dB, aux8: 65536
/ 100% / 0.00 dB, aux9: 65536 / 100% / 0.00 dB
balance 0.00
Base Volume: 65536 / 100% / 0.00 dB
Monitor Source:
alsa_output.usb-Roland_STUDIO-CAPTURE_STCP80008c08d018c010005040a0d0c4-01.multichannel-output.monitor
Latency: 0 usec, configured 0 usec
Flags: HARDWARE DECIBEL_VOLUME LATENCY
Properties:
alsa.card = "3"
alsa.card_name = "STUDIO-CAPTURE"
alsa.class = "generic"
alsa.device = "0"
alsa.driver_name = "snd_usb_audio"
alsa.id = "USB Audio"
alsa.long_card_name = "Roland STUDIO-CAPTURE at
usb-0000:05:00.0-4, high speed"
alsa.name = "USB Audio"
alsa.resolution_bits = "32"
alsa.subclass = "generic-mix"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
api.alsa.card.longname = "Roland STUDIO-CAPTURE at
usb-0000:05:00.0-4, high speed"
api.alsa.card.name = "STUDIO-CAPTURE"
api.alsa.path = "hw:3"
api.alsa.pcm.card = "3"
api.alsa.pcm.stream = "playback"
audio.channels = "10"
audio.position = "AUX0,AUX1,AUX2,AUX3,AUX4,AUX5,AUX6,AUX7,AUX8,AUX9"
card.profile.device = "3"
device.api = "alsa"
device.class = "sound"
device.id = "43"
device.profile.description = "Multichannel"
device.profile.name = "multichannel-output"
device.routes = "0"
factory.name = "api.alsa.pcm.sink"
media.class = "Audio/Sink"
device.description = "STUDIO-CAPTURE"
node.name =
"alsa_output.usb-Roland_STUDIO-CAPTURE_STCP80008c08d018c010005040a0d0c4-01.multichannel-output"
node.nick = "STUDIO-CAPTURE"
node.pause-on-idle = "false"
object.path = "alsa:pcm:3:hw:3:playback"
priority.driver = "1000"
priority.session = "1000"
factory.id = "18"
clock.quantum-limit = "8192"
client.id = "53"
node.driver = "true"
factory.mode = "merge"
audio.adapt.follower = ""
library.name = "audioconvert/libspa-audioconvert"
object.id = "42"
object.serial = "470"
node.max-latency = "16384/96000"
api.alsa.period-size = "512"
api.alsa.period-num = "64"
api.alsa.headroom = "512"
api.acp.auto-port = "false"
api.acp.auto-profile = "false"
api.alsa.card = "3"
api.alsa.use-acp = "true"
api.dbus.ReserveDevice1 = "Audio3"
device.bus = "usb"
device.bus-id =
"usb-Roland_STUDIO-CAPTURE_STCP80008c08d018c010005040a0d0c4-01"
device.bus_path = "pci-0000:05:00.0-usb-0:4:1.1"
device.enum.api = "udev"
device.icon_name = "audio-card-analog-usb"
device.name =
"alsa_card.usb-Roland_STUDIO-CAPTURE_STCP80008c08d018c010005040a0d0c4-01"
device.nick = "STUDIO-CAPTURE"
device.plugged.usec = "19929357"
device.product.id = "0x0160"
device.product.name = "STUDIO-CAPTURE"
device.serial = "Roland_STUDIO-CAPTURE_STCP80008c08d018c010005040a0d0c4"
device.subsystem = "sound"
sysfs.path =
"/devices/pci0000:00/0000:00:0b.0/0000:05:00.0/usb5/5-4/5-4:1.1/sound/card3"
device.vendor.id = "0x0582"
device.vendor.name = "Roland Corp."
device.string = "3"
Formats:
pcm


And, here it is after Gnome's Settings changes it back to "Dummy
Output" by setting Input to "Analog Input - STUDIO-CAPTURE":
Sink #1105
State: RUNNING
Name: auto_null
Description: Dummy Output
Driver: PipeWire
Sample Specification: float32le 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: auto_null.monitor
Latency: 0 usec, configured 0 usec
Flags: DECIBEL_VOLUME LATENCY
Properties:
node.name = "auto_null"
device.description = "Dummy Output"
audio.rate = "48000"
audio.channels = "2"
audio.position = "FL,FR"
media.class = "Audio/Sink"
factory.name = "support.null-audio-sink"
node.virtual = "true"
monitor.channel-volumes = "true"
factory.id = "18"
clock.quantum-limit = "8192"
client.id = "69"
node.driver = "true"
factory.mode = "merge"
audio.adapt.follower = ""
library.name = "audioconvert/libspa-audioconvert"
object.id = "108"
object.serial = "1105"
Formats:
pcm


I think my cause might be different, but it matches the original subject.
Thanks for any help!

[Lucas]

Here's a correction: I shutdown and started it again, and the
pavucontrol setup was retained. So, I continued testing by running
ardour, knowing it's set to use JACK through ALSA. It played fine,
but when I quit it, I wasn't able to hear pulseaudio, nor select the
same pavucontrol profile. Luckily, there's a "Pro Audio"
Configuration in pavucontrol that works too. I retested ardour with
it and later standard pulseaudio playback, and it continues to work!
I wouldn't say this is fixed, but I consider it much improved, by
these findings, and almost tolerable.

[Max Dmitrichenko]

Package: pipewire-pulse
Version: 0.3.65-3
Followup-For: Bug #1025069
X-Debbugs-Cc: dmit...@gmail.com

I'm confirming this issue. After upgrade from bullseye to bookworm sound in KDE disappeared. I was
able to restore it after manually installing wireplumber.


-- System Information:
Debian Release: 12.0
APT prefers testing-security
APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pipewire-pulse depends on:
ii init-system-helpers 1.65.2
ii pipewire 0.3.65-3

Versions of packages pipewire-pulse recommends:
ii wireplumber 0.4.13-1

Versions of packages pipewire-pulse suggests:
ii libspa-0.2-bluetooth 0.3.65-3
pn pulseaudio-utils <none>

-- no debconf information

[Alban Browaeys]

Do you have jackd installed and runnning at the same time as pipewire-
pulse?
Maybe you want to try piepwire-jack instead?

Cheers,
Alban

[Lucas]

On Fri, Apr 7, 2023 at 7:57 PM Alban Browaeys <alban.b...@gmail.com> wrote:
>
> Do you have jackd installed and runnning at the same time as pipewire-
> pulse?
> Maybe you want to try piepwire-jack instead?
>
> Cheers,
> Alban
>

I appreciate the suggestion, but since I also use multiple devices
with JACK, it's only running when I want to record and use a specific
profile/device. Ardour will start it using the last used (default)
profile, but only when I've not already started JACK from qjackctl to
use another profile. I think having it always running may complicate
this setup I've grown accustomed to. Are you aware of any issues
trying to stop JACK (to use other rates and devices) when using
pipewire-jack?

Thanks,
Lucas

[Lucas]

I should have let you know when I created it, but I still have no feedback from a bug report I wrote to the pipewire developers: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3131.

I guessed it was a "port detection" issue after reading this response on the original poster's bug report: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1831991

--

Protect your digital freedom and privacy, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm
On a related note, also see https://www.fsf.org/campaigns/surveillance

[Alban Browaeys]

Le dimanche 09 avril 2023 à 15:03 -0500, Lucas a écrit :

I should have let you know when I created it, but I still have no feedback from a bug report I wrote to the pipewire developers: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3131.

"Multichannel Output" Profile disappeared after I ran JACK (ardour), and I only see again now on a fresh startup.

Do you mean it disappeared from pavucontrol when you run JACK from ardour ?

What I meant is that you cannot run pipewire and jackd at the same time ? I cannot work as one will prevent the other from accessing the ALSA sound device.

If you want to run JACK application whne running pipewire you can only do so by pipewire-jackd and disabling jackd. 

This is not a pipewire bug. jackd also cannot work if the sound device is already taken by an alsa program or any other daemon plugging to the alsa interface (pipewire, pulseaudio), it could work because for one pulseaudio aut suspend itself from time to time so the alsa sound device is free when so. But then when pulseaudio will resume and your jackd daemon is holding on the alsa sound device pulseaudio will not work. This is not supported (for pulseaudio you could use the pasuspend tool, still it is  hack).

Also:

Gnome Settings Output Device contains nothing to select, while Input allows "Analog Input - STUDIO-CAPTURE" and "STUDIO-CAPTURE Pro". The only way to have output audio working is to use pavucontrol and select either of the STUDIO-CAPTURE Profile Configurations "Multichannel Output", or "Pro Audio".  

and:

That "Multichannel Output" Profile disappeared after I ran JACK (ardour), and I only see again now on a fresh startup.

seems to be two different issue. You should report both in two diffrent bug report else it the bug report will get confusing soon.

My reply was about the second issue (which to me look like a normal behavior).

For the first one, I am a bit confused. You mean that even in pavucontrol if you do not switch to the STUDIO-CAPTURE Profile Configurations "Multichannel Output", or "Pro Audio" you cannot set a sound output device?

If you bug report upstream you could try to run pipewire built from source (you just have to stop pipewire related systemd user services, ie systemctl --user stop pipewire.service, etc).

Also there is a newer pipewire version 0.3.76 in Debian rc-buggy (experimental).

I guessed it was a "port detection" issue after reading this response on the original poster's bug report: https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1831991

Could you provide the same debug logs as this bug reporter did?

loginctl user-status | grep State

lsof /dev/snd/*

fuser -v /dev/snd/*

aplay -l

journalctl --user -b --unit pipewire.service




and maybe also 

journalctl --user -b --unit pipewire-pulse.service

pipewire --version

and why not the output when running gnome-control-center from a terminal:

gnome-control-center --verbose sound

Still could you try with pipewire-jack instead of jackd (even if you prefer to run jackd only while running a jack application.

Cheers

Alban

[Alban Browaeys]

Also could you also give the wireplumber log 

https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3086#note_1829660

Cheers,

Alban

[Lucas]

On Tue, 11 Apr 2023 14:30:38 +0200 Alban Browaeys
<alban.b...@gmail.com> wrote:
> Do you mean it disappeared from pavucontrol when you run JACK from
> ardour ?

Yes, that particular output option from pavucontrol disappeared after
running ardour, and then closing it (Gnome settings shows an empty
unselectable output). After ardour is closed, jack automatically is
too, and pavucontrol once again displays STUDIO CAPTURE in
Configuration.

> What I meant is that you cannot run pipewire and jackd at the same time
> ? I cannot work as one will prevent the other from accessing the ALSA
> sound device.
> If you want to run JACK application whne running pipewire you can only
> do so by pipewire-jackd and disabling jackd.
> This is not a pipewire bug. jackd also cannot work if the sound device
> is already taken by an alsa program or any other daemon plugging to the
> alsa interface (pipewire, pulseaudio), it could work because for one
> pulseaudio aut suspend itself from time to time so the alsa sound
> device is free when so. But then when pulseaudio will resume and your
> jackd daemon is holding on the alsa sound device pulseaudio will not
> work. This is not supported (for pulseaudio you could use the pasuspend
> tool, still it is hack).

Yes, I know this should be the case, but pulseaudio seems to be
graceful enough without me suspending it to run ardour's jack. When
I'm done with that, I also don't have to stop suspending pulseaudio.

>
> Also:
> Gnome Settings Output Device contains nothing to select, while Input
> allows "Analog Input - STUDIO-CAPTURE" and "STUDIO-CAPTURE Pro". The
> only way to have output audio working is to use pavucontrol and select
> either of the STUDIO-CAPTURE Profile Configurations "Multichannel
> Output", or "Pro Audio".
> and:
> That "Multichannel Output" Profile disappeared after I ran JACK
> (ardour), and I only see again now on a fresh startup.
> seems to be two different issue. You should report both in two diffrent
> bug report else it the bug report will get confusing soon.
> My reply was about the second issue (which to me look like a normal
> behavior).
>
>
> For the first one, I am a bit confused. You mean that even in
> pavucontrol if you do not switch to the STUDIO-CAPTURE Profile
> Configurations "Multichannel Output", or "Pro Audio" you cannot set a
> sound output device?

Not quite. It wasn't disabled before I set pavucontrol's
configuration, but all that was selectable in Gnome settings for
output was a Dummy Audio option, or something to that effect.

> If you bug report upstream you could try to run pipewire built from
> source (you just have to stop pipewire related systemd user services,
> ie systemctl --user stop pipewire.service, etc).
> Also there is a newer pipewire version 0.3.76 in Debian rc-buggy
> (experimental).

I might revisit this after reading up on how to pin experimental for
that one package, but for now I'll work on adding the other debugging
information you suggested, to the bug report.

Thanks for the suggestions!

[Lucas]

On Tue, 11 Apr 2023 14:30:38 +0200 Alban Browaeys
<alban.b...@gmail.com> wrote:

> Still could you try with pipewire-jack instead of jackd (even if you
> prefer to run jackd only while running a jack application.

Okay, I just installed it. I had to start ardour with this command,
to get sound working on it:
$ pw-jack -s 96000 ardour

It didn't change Gnome Settings, but it did retain pavucontrol's
configuration the entire time jack was running, which is a very neat
trick, but doesn't seem worth having ardour see a difference in the
device, nor modifying ardour's command. I've never needed ardour and
pulseaudio running at the same time, and it doesn't seem to help the
port detection issue with Gnome Settings.