pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2023-09-22T13:55:52Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3501Crash in pipewire-pulse2023-09-22T13:55:52ZsaivertCrash in pipewire-pulseI just experienced a random crash out of the blue today and am posting the crash dump here for analysis.
```plaintext
coredumpctl gdb /usr/bin/pipewire
PID: 6503 (pipewire-pulse)
UID: 1000 (saivert)
GID...I just experienced a random crash out of the blue today and am posting the crash dump here for analysis.
```plaintext
coredumpctl gdb /usr/bin/pipewire
PID: 6503 (pipewire-pulse)
UID: 1000 (saivert)
GID: 1000 (saivert)
Signal: 11 (SEGV)
Timestamp: Sun 2023-09-10 10:45:01 CEST (4min 45s ago)
Command Line: /usr/bin/pipewire-pulse
Executable: /usr/bin/pipewire
Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
Unit: user@1000.service
User Unit: pipewire-pulse.service
Slice: user-1000.slice
Owner UID: 1000 (saivert)
Boot ID: 2442c1939a1f4abeb6a6541ffa736aa9
Machine ID: 1cfb1b6d3c3c4479af84316e39bda99a
Hostname: fedora
Storage: /var/lib/systemd/coredump/core.pipewire-pulse.1000.2442c1939a1f4abeb6a6541ffa736aa9.6503.1694335501000000.zst (present)
Size on Disk: 30.7M
Package: pipewire/0.3.78-1.fc38
build-id: 034593ccc5658d964c6c38d09623a0946c4817a7
Message: Process 6503 (pipewire-pulse) of user 1000 dumped core.
Module libspa-audiomixer.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libspa-audioconvert.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-module-fallback-sink.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libblkid.so.1 from rpm util-linux-2.38.1-4.fc38.x86_64
Module libpcre2-8.so.0 from rpm pcre2-10.42-1.fc38.1.x86_64
Module libffi.so.8 from rpm libffi-3.4.4-2.fc38.x86_64
Module libselinux.so.1 from rpm libselinux-3.5-1.fc38.x86_64
Module libmount.so.1 from rpm util-linux-2.38.1-4.fc38.x86_64
Module libz.so.1 from rpm zlib-1.2.13-3.fc38.x86_64
Module libgmodule-2.0.so.0 from rpm glib2-2.76.4-3.fc38.x86_64
Module libglib-2.0.so.0 from rpm glib2-2.76.4-3.fc38.x86_64
Module libgobject-2.0.so.0 from rpm glib2-2.76.4-3.fc38.x86_64
Module libgio-2.0.so.0 from rpm glib2-2.76.4-3.fc38.x86_64
Module libavahi-client.so.3 from rpm avahi-0.8-22.fc38.x86_64
Module libavahi-common.so.3 from rpm avahi-0.8-22.fc38.x86_64
Module libpipewire-module-protocol-pulse.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-module-metadata.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-module-adapter.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-module-client-node.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-module-protocol-native.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-module-rt.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libdbus-1.so.3 from rpm dbus-1.14.8-1.fc38.x86_64
Module libspa-dbus.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module liblz4.so.1 from rpm lz4-1.9.4-2.fc38.x86_64
Module libzstd.so.1 from rpm zstd-1.5.5-1.fc38.x86_64
Module liblzma.so.5 from rpm xz-5.4.1-1.fc38.x86_64
Module libcap.so.2 from rpm libcap-2.48-6.fc38.x86_64
Module libsystemd.so.0 from rpm systemd-253.7-1.fc38.x86_64
Module libspa-journal.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libspa-support.so from rpm pipewire-0.3.78-1.fc38.x86_64
Module libpipewire-0.3.so.0 from rpm pipewire-0.3.78-1.fc38.x86_64
Module pipewire from rpm pipewire-0.3.78-1.fc38.x86_64
Stack trace of thread 6510:
#0 0x00007fa59c6a3745 impl_node_process.lto_priv.1 (libspa-audiomixer.so + 0xc745)
#1 0x00007fa5ab950a4a node_on_fd_events.lto_priv.0 (libpipewire-0.3.so.0 + 0x65a4a)
#2 0x00007fa5ab6cdce6 loop_iterate (libspa-support.so + 0x8ce6)
#3 0x00007fa5ab932e83 do_loop (libpipewire-0.3.so.0 + 0x47e83)
#4 0x00007fa5ab799907 start_thread (libc.so.6 + 0x8c907)
#5 0x00007fa5ab81f774 __clone (libc.so.6 + 0x112774)
Stack trace of thread 6505:
#0 0x00007fa5ab81fc72 epoll_wait (libc.so.6 + 0x112c72)
#1 0x00007fa5ab6db768 impl_pollfd_wait (libspa-support.so + 0x16768)
#2 0x00007fa5ab6cdc29 loop_iterate (libspa-support.so + 0x8c29)
#3 0x00007fa5ab976007 do_loop (libpipewire-0.3.so.0 + 0x8b007)
#4 0x00007fa5ab799907 start_thread (libc.so.6 + 0x8c907)
#5 0x00007fa5ab81f774 __clone (libc.so.6 + 0x112774)
Stack trace of thread 6503:
#0 0x00007fa5ab80e0fa read (libc.so.6 + 0x1010fa)
#1 0x00007fa5ab6db207 impl_eventfd_read (libspa-support.so + 0x16207)
#2 0x00007fa5ab6ce8fa loop_invoke (libspa-support.so + 0x98fa)
#3 0x00007fa5ab953982 node_deactivate.lto_priv.0 (libpipewire-0.3.so.0 + 0x68982)
#4 0x00007fa5ab9572c0 idle_node.lto_priv.0 (libpipewire-0.3.so.0 + 0x6c2c0)
#5 0x00007fa5ab9621c8 pw_impl_node_set_state (libpipewire-0.3.so.0 + 0x771c8)
#6 0x00007fa59d54b952 client_node_command (libpipewire-module-client-node.so + 0x11952)
#7 0x00007fa59d55af34 client_node_demarshal_command.lto_priv.0 (libpipewire-module-client-node.so + 0x20f34)
#8 0x00007fa597fcaa91 process_remote (libpipewire-module-protocol-native.so + 0x15a91)
#9 0x00007fa597fcb278 on_remote_data (libpipewire-module-protocol-native.so + 0x16278)
#10 0x00007fa5ab6cdce6 loop_iterate (libspa-support.so + 0x8ce6)
#11 0x00007fa5ab95155b pw_main_loop_run (libpipewire-0.3.so.0 + 0x6655b)
#12 0x000055759111a606 main (pipewire + 0x1606)
#13 0x00007fa5ab734b4a __libc_start_call_main (libc.so.6 + 0x27b4a)
#14 0x00007fa5ab734c0b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x27c0b)
#15 0x000055759111a7a5 _start (pipewire + 0x17a5)
ELF object binary architecture: AMD x86-64
GNU gdb (GDB) Fedora Linux 13.2-3.fc38
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/pipewire...
This GDB supports auto-downloading debuginfo from the following URLs:
<https://debuginfod.fedoraproject.org/>
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Reading symbols from /home/saivert/.cache/debuginfod_client/034593ccc5658d964c6c38d09623a0946c4817a7/debuginfo...
warning: Can't open file /memfd:pipewire-memfd:flags=0x0000000f,type=2,size=65664 (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:pipewire-memfd:flags=0x0000000f,type=2,size=2312 (deleted) during file-backed mapping note processing
warning: Can't open file /memfd:pipewire-memfd:flags=0x0000000f,type=2,size=4096 (deleted) during file-backed mapping note processing
[New LWP 6510]
[New LWP 6505]
[New LWP 6503]
--Type <RET> for more, q to quit, c to continue without paging--c
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/pipewire-pulse'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 impl_node_process (object=0x557596163928) at ../spa/plugins/audiomixer/mixer-dsp.c:721
721 inio->status = SPA_STATUS_NEED_DATA;
[Current thread is 1 (Thread 0x7fa59cf8a6c0 (LWP 6510))]
(gdb) bt
#0 impl_node_process (object=0x557596163928) at ../spa/plugins/audiomixer/mixer-dsp.c:721
#1 0x00007fa5ab950a4a in process_node (data=0x5575960e8470) at ../src/pipewire/impl-node.c:1234
#2 node_on_fd_events (source=<optimized out>) at ../src/pipewire/impl-node.c:1310
#3 0x00007fa5ab6cdce6 in loop_iterate (object=0x5575916b3328, timeout=<optimized out>) at ../spa/plugins/support/loop.c:483
#4 0x00007fa5ab932e83 in do_loop (user_data=0x5575916b31c0) at ../src/pipewire/data-loop.c:65
#5 0x00007fa5ab799907 in start_thread (arg=<optimized out>) at pthread_create.c:444
#6 0x00007fa5ab81f774 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
(gdb) bt full
#0 impl_node_process (object=0x557596163928) at ../spa/plugins/audiomixer/mixer-dsp.c:721
inport = <optimized out>
inb = <optimized out>
bd = 0x557593b59b88
offs = <optimized out>
inio = 0x7fa59d49c000
this = 0x557596163928
outport = 0x557596164b00
outio = 0x557594dbcae0
n_buffers = 1
i = 0
maxsize = <optimized out>
buffers = 0x557596165c80
outb = <optimized out>
datas = 0x557596166c80
__func__ = "impl_node_process"
#1 0x00007fa5ab950a4a in process_node (data=0x5575960e8470) at ../src/pipewire/impl-node.c:1234
_f = <optimized out>
_n = <optimized out>
this = 0x5575960e8470
a = 0x7fa59d49e000
status = <optimized out>
p = 0x557594dbc560
data_system = 0x5575916b3290
nsec = <optimized out>
cmd = 1
this = 0x5575960e8470
__func__ = "node_on_fd_events"
#2 node_on_fd_events (source=<optimized out>) at ../src/pipewire/impl-node.c:1310
cmd = 1
this = 0x5575960e8470
__func__ = "node_on_fd_events"
#3 0x00007fa5ab6cdce6 in loop_iterate (object=0x5575916b3328, timeout=<optimized out>) at ../spa/plugins/support/loop.c:483
--Type <RET> for more, q to quit, c to continue without paging--q
Quit
(gdb) list
716
717 if (!SPA_FLAG_IS_SET(bd->chunk->flags, SPA_CHUNK_FLAG_EMPTY)) {
718 datas[n_buffers] = SPA_PTROFF(bd->data, offs, void);
719 buffers[n_buffers++] = inb;
720 }
721 inio->status = SPA_STATUS_NEED_DATA;
722 }
723
724 outb = dequeue_buffer(this, outport);
725 if (SPA_UNLIKELY(outb == NULL)) {
(gdb)
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3500two bluetooth speakers, bad stereo2024-03-16T16:48:28Zpromeneurtwo bluetooth speakers, bad stereo<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
<!-- If you can, test also with Pulseaudio and list `pulseaudio --version`. -->
- PipeWire version (`pipewire --version`): 0.3...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
<!-- If you can, test also with Pulseaudio and list `pulseaudio --version`. -->
- PipeWire version (`pipewire --version`): 0.3.79
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): openSUSE Tumbleweed
- Desktop Environment: KDE 23.08.0
- Kernel version (`uname -r`): 6.4.12
- BlueZ version (`bluetoothctl --version`): 5.69
- `lsusb`:
```
# paste the output of "lsusb" here
```
Bus 002 Device 002: ID 0bda:0321 Realtek Semiconductor Corp. USB3.0 Card Reader
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 005: ID 04d9:1702 Holtek Semiconductor, Inc. Keyboard LKS02
Bus 001 Device 004: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
Bus 001 Device 003: ID 046d:08e5 Logitech, Inc. C920 PRO HD Webcam
Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 001 Device 006: ID 8087:0032 Intel Corp. AX210 Bluetooth
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bluetooth devices:
```
# paste the output of "bluetoothctl devices" here
```
Device 7C:ED:C6:B8:7C:78 Droite
Device 7C:ED:C6:AF:FE:1B Gauche
Device 44:3D:54:50:B3:A3 Echo Dot-2K3
Device F0:2F:74:7C:FC:8F La magicienne
Device 40:45:DA:55:D4:FA Le prophète
Device 0C:E0:E4:9E:7C:C7 PLT_BBTSENSE
Device 00:1E:7C:39:7D:25 Philips SHQ7300
Device B4:74:43:FE:CE:78 La légende noire
Device 90:06:28:B6:B1:B6 Le surfeur d'argent
## Description of Problem:
I get two amazon echo pop connected separately to the PC via Bluetooth.
I create a virtual sound output device with these statements:
*************************************************************************************
create a virtual stereo device named "bluetooth_stereo"
pactl load-module module-null-sink media.class=Audio/Sink sink_name=bluetooth_stereo channel_map=stereo
link the left channel of the PC to the left channel of the left Echo Pop (named "Gauche" as a bluetooth device)
pw-link bluetooth_stereo:monitor_FL bluez_output.<mac_address_1>:playback_FL
link the left channel of the PC to the right channel of the left Echo Pop (named "Gauche" as a bluetooth device)
pw-link bluetooth_stereo:monitor_FL bluez_output.<mac_address_1>:playback_FR
link the right channel of the PC to the right channel of the right Echo Pop (named "Droite" as a bluetooth device)
pw-link bluetooth_stereo:monitor_FR bluez_output.<mac_address_2>:playback_FR
link the right channel of the PC to the left channel of the right Echo Pop (named "Droite" as a bluetooth device)
pw-link bluetooth_stereo:monitor_FR bluez_output.<mac_address_2>:playback_FL
*************************************************************************************
see the helvum diagram
![virtual_bluetooth_stereo](/uploads/fd325a05fd11dcabffd113d98f602804/virtual_bluetooth_stereo.png)
## How Reproducible:
### Steps to Reproduce:
1. play a video with VLC or Chrome (YouTube)
2.
3.
### Actual Results:
you get randomly:
- cracks
- only left channel
- only right channel
- a good stereo
### Expected Results:
you get always a good stereo
I will send logshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/34952 echo pop, not the same codecs2023-09-10T10:29:11Zpromeneur2 echo pop, not the same codecsMy PC gets an Intel AX210 (Bluetooth 5.3)
openSUSE Tumbleweed, KDE 23.08.0, pipewire 0.3.79
Two same Amazon Echo Pop connected at the same time to the PC via Bluetooth.
Surprisingly, one uses SBC and the other one uses SBC-XQ.
I can't...My PC gets an Intel AX210 (Bluetooth 5.3)
openSUSE Tumbleweed, KDE 23.08.0, pipewire 0.3.79
Two same Amazon Echo Pop connected at the same time to the PC via Bluetooth.
Surprisingly, one uses SBC and the other one uses SBC-XQ.
I can't switch to SBC or SBC-XQ according to get the same codec for the twos.
I don't know if it is a pipewire or a Bluetooth problem. So I also sent a bug report to Bluez.
https://github.com/bluez/bluez/issues/597https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3491HDMI sinks not detected, but aplay lists them2023-11-10T16:18:47ZBogomil VasilevHDMI sinks not detected, but aplay lists themI usually use my AUX analog audio, which works just fine, but when I want to switch to the HDMI sound, it appears the sink is missing.
```
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC...I usually use my AUX analog audio, which works just fine, but when I want to switch to the HDMI sound, it appears the sink is missing.
```
$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [Acer B277K]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2]
Subdevices: 1/1
Subdevice #0: subdevice #0
```
```
$ wpctl status
PipeWire 'pipewire-0' [0.3.79, smirky@archy, cookie:3879994869]
└─ Clients:
31. xdg-desktop-portal [0.3.79, smirky@archy, pid:3311]
32. pipewire [0.3.79, smirky@archy, pid:92136]
33. libcanberra [0.3.79, smirky@archy, pid:3637]
34. Firefox [0.3.79, smirky@archy, pid:56719]
35. QPulse [0.3.79, smirky@archy, pid:4176]
36. Plasma PA [0.3.79, smirky@archy, pid:3637]
38. WirePlumber [0.3.79, smirky@archy, pid:92135]
39. WirePlumber [export] [0.3.79, smirky@archy, pid:92135]
53. Music Player Daemon [0.3.79, smirky@archy, pid:9812]
59. wpctl [0.3.79, smirky@archy, pid:92716]
Audio
├─ Devices:
│ 45. Built-in Audio [alsa]
│
├─ Sinks:
│ * 50. Built-in Audio Analog Stereo [vol: 1.00]
│
├─ Sink endpoints:
│
├─ Sources:
│ * 51. Built-in Audio Analog Stereo [vol: 1.00]
│
├─ Source endpoints:
│
└─ Streams:
54. Music Player Daemon
55. output_FL > ALC892 Analog:playback_FL [active]
56. output_FR > ALC892 Analog:playback_FR [active]
Video
├─ Devices:
│
├─ Sinks:
│
├─ Sink endpoints:
│
├─ Sources:
│
├─ Source endpoints:
│
└─ Streams:
Settings
└─ Default Configured Node Names:
0. Audio/Sink alsa_output.pci-0000_03_00.1.5.hdmi-stereo-extra3
1. Audio/Source alsa_input.pci-0000_00_1f.3.3.analog-stereo
```
I'm using a stock setup with 0 custom settings.
```
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
Active: active (running) since Wed 2023-09-06 01:05:38 EEST; 6min ago
TriggeredBy: ● pipewire.socket
Main PID: 92132 (pipewire)
Tasks: 3 (limit: 18783)
Memory: 6.0M
CPU: 2.317s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─92132 /usr/bin/pipewire
Sep 06 01:05:38 archy systemd[634]: Started PipeWire Multimedia Service.
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-06 01:05:38 EEST; 6min ago
TriggeredBy: ● pipewire-pulse.socket
Main PID: 92136 (pipewire-pulse)
Tasks: 3 (limit: 18783)
Memory: 3.0M
CPU: 35ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
└─92136 /usr/bin/pipewire-pulse
Sep 06 01:05:38 archy systemd[634]: Started PipeWire PulseAudio.
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Wed 2023-09-06 01:05:38 EEST; 6min ago
Main PID: 92135 (wireplumber)
Tasks: 7 (limit: 18783)
Memory: 9.4M
CPU: 272ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─92135 /usr/bin/wireplumber
Sep 06 01:05:38 archy systemd[634]: Started Multimedia Service Session Manager.
Sep 06 01:05:38 archy wireplumber[92135]: [16:03:09.246689203] [92135] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Sep 06 01:05:38 archy wireplumber[92135]: [16:03:09.246700633] [92135] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Sep 06 01:05:38 archy wireplumber[92135]: [16:03:09.246726659] [92135] INFO Camera camera_manager.cpp:284 libcamera v0.1.0
Sep 06 01:05:38 archy wireplumber[92135]: <WpPortalPermissionStorePlugin:0x562e1f978fc0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Sep 06 01:05:39 archy wireplumber[92135]: <WpSiAudioAdapter:0x562e1fb638d0> Object activation aborted: proxy destroyed
Sep 06 01:05:39 archy wireplumber[92135]: <WpSiAudioAdapter:0x562e1fb638d0> failed to activate item: Object activation aborted: proxy destroyed
```
I'm pretty sure this was working at some point, but I recently noticed that it doesn't work, so I can't exactly narrow it down in which version it got broken.
```
$ pacman -Q pipewire wireplumber
pipewire 1:0.3.79-1
wireplumber 0.4.14-1
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3489pipewire fails to build on alpha architecture; failure in test suite due to s...2023-09-24T13:49:30ZDylan Aïssipipewire fails to build on alpha architecture; failure in test suite due to sigfpeCopy-pasted from [a Debian bug report](https://bugs.debian.org/1051128).
pipewire fails to build on [Alpha architecture](https://www.debian.org/ports/alpha/) due to test suite failure. [From the build
log](https://buildd.debian.org/stat...Copy-pasted from [a Debian bug report](https://bugs.debian.org/1051128).
pipewire fails to build on [Alpha architecture](https://www.debian.org/ports/alpha/) due to test suite failure. [From the build
log](https://buildd.debian.org/status/fetch.php?pkg=pipewire&arch=alpha&ver=0.3.79-1&stamp=1693346040&raw=0):
```
8/22 test-resample FAIL 0.19s killed by signal 8 SIGFPE
```
Re-running the test under gdb reveals the failure is in:
```
(gdb) bt
#0 0x0000020001002b14 in inner_product_c (n_taps=<optimized out>, taps=0x2000102e300, s=0x11fcfbb54, d=0x11fcf9cf0)
at ../spa/plugins/audioconvert/resample-native-c.c:13
#1 do_resample_full_c (r=0x11fcfd000, src=<optimized out>, ioffs=0, in_len=0x11fcf8eb4, dst=<optimized out>, ooffs=34,
out_len=0x11fcfcf80) at ../spa/plugins/audioconvert/resample-native-c.c:44
#2 0x0000020001001cb4 in impl_native_process (r=0x11fcfd000, src=0x11fcfcf78, in_len=0x11fcfcf84, dst=0x11fcfcf70,
out_len=0x11fcfcf80) at ../spa/plugins/audioconvert/resample-native.c:238
#3 0x000002000100157c in pull_blocks (r=0x11fcfd000, first=<optimized out>, size=1024)
at ../spa/plugins/audioconvert/test-resample.c:89
#4 0x0000020001000ec8 in test_in_len () at ../spa/plugins/audioconvert/test-resample.c:123
#5 main (argc=<optimized out>, argv=<optimized out>) at ../spa/plugins/audioconvert/test-resample.c:154
```
And disassembling at the failure point reveals:
```
0x0000020001002b10 <+336>: muls $f14,$f11,$f13
=> 0x0000020001002b14 <+340>: sextl t0,t0
```
i.e. it is multiplying two single precision floating-point values
together (the location of the failure can be an instruction or
two out due to superscalar execution in the pipeline; it will be
the muls instruction that caused the fault):
```
f11 5.2433191122247536e-09 (raw 0x3e36851720000000)
f14 1.6132473000813483e-310 (raw 0x00001db280000000)
```
and we see that f14 is a denormalised floating point number. (The
interpretation by gdb that it is 1.613...e-310 is wrong in that gdb
has assumed incorrectly that it is a double precision number for
printing the value.)
The relevant module was compiled with -ffast-math. The relevant line
in the [build
log](https://buildd.debian.org/status/fetch.php?pkg=pipewire&arch=alpha&ver=0.3.79-1&stamp=1693346040&raw=0) is:
```
[89/965] cc -Ispa/plugins/audioconvert/libaudioconvert_c.a.p -Ispa/plugins/audioconvert -I../spa/plugins/audioconvert -Ispa/include -I../spa/include -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=gnu11 -fvisibility=hidden -fno-strict-aliasing -Werror=suggest-attribute=format -Wsign-compare -Wpointer-arith -Wpointer-sign -Wformat -Wformat-security -Wimplicit-fallthrough -Wmissing-braces -Wtype-limits -Wvariadic-macros -Wmaybe-uninitialized -Wno-missing-field-initializers -Wno-unused-parameter -Wno-pedantic -Wdeprecated-declarations -Wunused-result -Werror=return-type -D_GNU_SOURCE -DFASTPATH -Werror=implicit-function-declaration -Werror=int-conversion -Werror=old-style-declaration -Werror=old-style-definition -Werror=missing-parameter-type -Werror=strict-prototypes -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=. -specs=/usr/share/dpkg/pie-compile.specs -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Ofast -ffast-math -MD -MQ spa/plugins/audioconvert/libaudioconvert_c.a.p/resample-native-c.c.o -MF spa/plugins/audioconvert/libaudioconvert_c.a.p/resample-native-c.c.o.d -o spa/plugins/audioconvert/libaudioconvert_c.a.p/resample-native-c.c.o -c ../spa/plugins/audioconvert/resample-native-c.c
```
But according to the gcc manual:
This option is not turned on by any -O option besides
-Ofast since it can result in incorrect output for programs
that depend on an exact implementation of IEEE or ISO
rules/specifications for math functions. It may, however,
yield faster code for programs that do not require the
guarantees of these specifications.
That's the problem. The use of -ffast-math "can result in incorrect
output" if "depend on an exact implementation of IEEE" and on Alpha
-ffast-math turns off IEEE support for infinities, NaNs and
denormalised numbers, and the use of any of these results in a
SIGFPE signal being raised.
One wonders why pipewire would even need support for denormalised
numbers given that audio has a much more limited range of values!
Maybe the test suite is testing something that will never occur
in practice, in which case this test should be modified not to
include denormalised numbers. Or, if there is a good reason to
expect denormalised numbers to be possible then this module should
not be compiled with -ffast-math on Alpha. (Or the input should be
tested and any denormalised numbers set to zero before any further
processing occurs.)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3487Occasional segfault when switching outputs2023-12-11T15:46:58ZDavid EmettOccasional segfault when switching outputsSince updating to 0.3.79, I've been seeing occasional segfaults in the `pipewire` daemon when switching outputs using commands like the following:
pactl set-card-profile alsa_card.pci-0000_0c_00.4 output:analog-surround-51
pactl...Since updating to 0.3.79, I've been seeing occasional segfaults in the `pipewire` daemon when switching outputs using commands like the following:
pactl set-card-profile alsa_card.pci-0000_0c_00.4 output:analog-surround-51
pactl set-sink-port alsa_output.pci-0000_0c_00.4.analog-surround-51 analog-output-speaker
The segfaults aren't always in the same place, however two coredumps show a crash in `spa_node_call_ready` in `audioadapter.c`'s `follower_ready`; GDB says `this->callbacks` is `{funcs = 0x0, data = 0x0}` which is presumably the issue?https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3485Sample rate discrepancy?2023-09-06T13:42:12ZJean-Michaël CelerierSample rate discrepancy?Hello,
I have a node created with pw_filter_new_simple and the following properties:
```
PW_KEY_MEDIA_TYPE, "Audio",
PW_KEY_MEDIA_CATEGORY, "Duplex",
PW_KEY_MEDIA_ROLE, "DSP",
PW_KEY_MEDIA_NAME, "ossia",
PW_KEY_NODE_LATENCY, "256/44100"...Hello,
I have a node created with pw_filter_new_simple and the following properties:
```
PW_KEY_MEDIA_TYPE, "Audio",
PW_KEY_MEDIA_CATEGORY, "Duplex",
PW_KEY_MEDIA_ROLE, "DSP",
PW_KEY_MEDIA_NAME, "ossia",
PW_KEY_NODE_LATENCY, "256/44100",
PW_KEY_NODE_RATE, "1/44100",
PW_KEY_NODE_FORCE_QUANTUM, "true",
PW_KEY_NODE_LOCK_QUANTUM, "true",
PW_KEY_NODE_ALWAYS_PROCESS, "true",
PW_KEY_NODE_LOCK_RATE, "true",
PW_KEY_NODE_FORCE_RATE, "true",
PW_KEY_NODE_PAUSE_ON_IDLE, "false",
PW_KEY_NODE_SUSPEND_ON_IDLE, "false",
```
It shows up in pw-top as this:
R 64 256 44100 47.6us 39.1us 0.01 0.01 0 + ossia score
but from within my process function, given `struct spa_io_position* position`, I see `position->clock.rate == 1/48000` and the function is indeed called at a 256/48000 rate (I observe 5.33 milliseconds between calls). Where does this mismatch happen, what can I do?
Setting
PIPEWIRE_LATENCY=256/44100
PIPEWIRE_QUANTUM=256/44100
seems to have no effect with pipewire directly.
Going through the JACK API works.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3481pipe wire configuration question2023-11-30T14:44:37Zthrow awaypipe wire configuration questionIs there an equivalent of doing
pactl load-module module-null-sink sink_name=VirtualSpeaker sink_properties=device.description=VirtualSpeaker
pactl load-module module-null-sink media.class=Audio/Source/Virtual sink_name=VirtualMic cha...Is there an equivalent of doing
pactl load-module module-null-sink sink_name=VirtualSpeaker sink_properties=device.description=VirtualSpeaker
pactl load-module module-null-sink media.class=Audio/Source/Virtual sink_name=VirtualMic channel_map=front-left,front-right
pw-link VirtualSpeaker:monitor_FL VirtualMic:input_FL
pw-link VirtualSpeaker:monitor_FR VirtualMic:input_FR
inside of pipewires config files? More so the idea of linking deviceshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3480wishlist: add a mode in pw_stream to do pre-filling of future buffers as earl...2023-09-25T08:39:06ZGeorge Kiagiadakiswishlist: add a mode in pw_stream to do pre-filling of future buffers as early as possibleCurrently, in async (non-RT) playback mode, pw_stream calls the `process` callback about 1 driver period before the stream underruns, no matter how big is the stream's `node.latency` and the buffers it provides. So, for example, if the d...Currently, in async (non-RT) playback mode, pw_stream calls the `process` callback about 1 driver period before the stream underruns, no matter how big is the stream's `node.latency` and the buffers it provides. So, for example, if the driver's period is 1024 samples and the application fills 4096 samples on each buffer every time the `process` callback is called, then the stream will allow 3072 samples to be consumed before it calls the `process` callback again. In some cases, this is a bit tight, especially if the application needs to perform large amounts of processing or I/O in order to fill the next buffer.
This can be solved currently by having the application run a separate thread where it "pushes" into pw_stream, ignoring the `process` callback completely. It would be nice, though, if there was a mode that calls the `process` callback as soon as there is an available buffer to be dequeued for filling. This would allow the application to maintain a large queue fill level without having to run its own "push" thread.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3479LE audio issue on sink node2023-09-14T06:08:35ZsilviubarbulescuLE audio issue on sink nodeHello all,
I have an issue testing the LE audio support in Pipewire. I have a setup with 2 Ubuntu, BlueZ, enabled BlueZ Experimental ISO socket, and PipeWire (commit: 41dcac0ecdc3e03ada8787a9dad4b0421c618687) with LC3 support enabled.
...Hello all,
I have an issue testing the LE audio support in Pipewire. I have a setup with 2 Ubuntu, BlueZ, enabled BlueZ Experimental ISO socket, and PipeWire (commit: 41dcac0ecdc3e03ada8787a9dad4b0421c618687) with LC3 support enabled.
I'm trying to test the Bluetooth LE Audio setup connected or broadcast between these 2 Ubuntu PCs. My problem is that on the sink device, the PipeWire node is not created.
Investigating I found that the problem is commit cd24fe2f (bluez5: A2DP and BAP profiles to enumerate only codec profiles) because no codecless profiles are enumerated on the sink node and on the BAP sink we use codecless profiles.
@pvir I understand you test the comit with BAP connected. Am I missing something?
Attached PipeWire log from the LE audio connected sink node [log_pipewire.txt](/uploads/9c7a369c6954d2fc8583b6c645094ca9/log_pipewire.txt)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3478regression: distored audio2023-09-06T13:42:12ZRay Cregression: distored audio<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.65-3
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-releas...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.65-3
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Ubuntu 23.04
- Desktop Environment: XFCE
- Kernel version (`uname -r`): 6.2.0-27-generic
## Description of Problem:
I originally opened this as a bug against nDAX: https://github.com/kc2g-flex-tools/nDAX/issues/13
nDAX is an application that streams audio to and from a FlexRadio ham radio.
But it turns out to be an issue with pipewire. Uninstalling pipewire and going back to pulseaudio solves this issue for me. This is a regression from pulseaudio.
What I'm seeing: Frequently after TX (to a the ndax sink), the RX audio (ndax source) will be distorted, as shown in the attached screenshot. The top is audio provided by nDAX on a host running Ubuntu 23.04. The bottom is WSJT-X running on windows, attached to the same slice receiving the distorted audio in Linux, but the windows DAX audio, where I don't see the issue. Changing bands and immediately changing back will sometimes correct the audio until I transmit a couple of times again... I changed bands/changed back in the 17:38:15 time slot, which is why the top of the waterfall looks normal.
## How Reproducible:
It seems random, tuned with a realtime profile seemed to help a bit, but really the key was uninstalling this and just going back to pulseaudio.
### Steps to Reproduce:
1. run nDAX with a connection to a flex radio (you get a source and a sink)
2. wait, it's sometimes goes bad soon after transmitting (ie sending audio out a sink)
### Actual Results:
Source audio is distorted.
### Expected Results:
Fidelity.
# Additional Info (as attachments):
![256897687-670db741-43b0-492c-bf6b-b9bf812e707d](/uploads/75550efbedc0bad939850f1ff9cce0e7/256897687-670db741-43b0-492c-bf6b-b9bf812e707d.png)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3477regression (pipewire-jack): Tracktion Waveform12 fails to read JACK connections2023-09-15T14:16:41ZSkyggeregression (pipewire-jack): Tracktion Waveform12 fails to read JACK connectionsWith the new (0.3.78) version Ardour can't read inputs and outputs as mentioned in #3475.
**But also Tracktion Waveform 12 Free/Pro can't use JACK backend anymore with these errors on the console:**
```
Cannot connect input port 0 (AIR ...With the new (0.3.78) version Ardour can't read inputs and outputs as mentioned in #3475.
**But also Tracktion Waveform 12 Free/Pro can't use JACK backend anymore with these errors on the console:**
```
Cannot connect input port 0 (AIR 192 14 Analog Spatial 7.1:capture_1_mic), error 22
Cannot connect input port 1 (AIR 192 14 Analog Spatial 7.1:capture_2_mic), error 22
Cannot connect input port 2 (AIR 192 14 Analog Spatial 7.1:capture_5_gtr), error 22
Cannot connect input port 3 (AIR 192 14 Analog Spatial 7.1:capture_6_gtr), error 22
Cannot connect input port 4 (AIR 192 14 Analog Spatial 7.1:capture_3_mic), error 22
Cannot connect input port 5 (AIR 192 14 Analog Spatial 7.1:capture_4_mic), error 22
Cannot connect input port 6 (AIR 192 14 Analog Spatial 7.1:capture_7_line), error 22
Cannot connect input port 7 (AIR 192 14 Analog Spatial 7.1:capture_8_line), error 22
Cannot connect output port 0 (AIR 192 14 Analog Spatial 4.0:playback_output1), error 22
Cannot connect output port 1 (AIR 192 14 Analog Spatial 4.0:playback_output2), error 22
Cannot connect output port 2 (AIR 192 14 Analog Spatial 4.0:playback_output3), error 22
Cannot connect output port 3 (AIR 192 14 Analog Spatial 4.0:playback_output4), error 22
```
Downgrading pipewire to 0.3.76 (or switching to ALSA backend) makes it work again.
Is pipewire-jack tested before release?
But, to be not only so sarcastic, I want to thank you for resolving audio popping/crackling in 0.3.78 when adjusting system volume (in KDE Plasma) :D Great job, thanks!https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3476regression(pipewire-pulse): unable to open monitor source devices as of 0.3.772023-09-06T13:42:12ZNick Parkerregression(pipewire-pulse): unable to open monitor source devices as of 0.3.77I'm seeing errors attempting to open monitor devices via SDL2 on pipewire-pulse-0.3.77 and newer. The the monitor devices appear in the list of sources, but when trying to open them by name, sdl2 fails with "Requested PulseAudio sink/sou...I'm seeing errors attempting to open monitor devices via SDL2 on pipewire-pulse-0.3.77 and newer. The the monitor devices appear in the list of sources, but when trying to open them by name, sdl2 fails with "Requested PulseAudio sink/source missing?"
The failure first appears on pipewire-pulse-0.3.77. Downgrading to pipewire-pulse-0.3.76 allowed monitor devices to be opened again. Given this, I assume the regression is via [this commit](https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/3a8894d2a4f72879cea146ae270b6b50ac7b6576), looks related going by how it mentions naming of monitor devices?
For example, sdl2 could return a list of devices like this:
- "Monitor of Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + Headphones"
- "Tiger Lake-LP Smart Sound Technology Audio Controller Headset Mono Microphone + Headphones Stereo Microphone"
- "Tiger Lake-LP Smart Sound Technology Audio Controller Digital Microphone"
Trying to then open the source device named "Monitor of Tiger Lake-LP Smart Sound Technology Audio Controller Speaker + Headphones" fails on 0.3.77 (and newer), succeeds on 0.3.76 (and older).
I've been able to repro this across two machines, so it doesn't seem to be specific to the hardware. On one of them, I switched back to stock pulseaudio which also allowed Monitor devices to be opened again.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3475regression(pipewire-jack): Ardour fails to read JACK connections2023-09-15T14:16:40ZMichele Sorcinelliregression(pipewire-jack): Ardour fails to read JACK connectionsWhen making a JACK port connection through Ardour interface, Ardour is now unaware of the actual connection being made, even if it appears in qpwgraph.
From bisect I got 31f91ce9f4302cea55244ab741022e40bbd4e716, and reverting that and ...When making a JACK port connection through Ardour interface, Ardour is now unaware of the actual connection being made, even if it appears in qpwgraph.
From bisect I got 31f91ce9f4302cea55244ab741022e40bbd4e716, and reverting that and c41c812325ca1b0db1efc2fc06a3c90355be59d9 fixes the problem.
Steps to reproduce:
- open a new ardour session
- see how there's no output connected to the master track
- try to connect master track to an output
What should happen:
- the master track should show the connected outputs
What happens instead:
- the master track doesn't show any connected output
- pwgraph shows the connection as being made
The same can be reproduced with input ports, both MIDI and Audio.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3474After idle, the sound controls and devices are broken.2023-08-29T14:20:47ZЄгор ГеращенкоAfter idle, the sound controls and devices are broken.<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.77
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.77
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Void Linux
- Desktop Environment: KDE Plasma (Wayland)
- Kernel version (`uname -r`): 6.3.13_1
## Description of Problem:
The device sound output list is broken, you can't adjust the sound less than or above 45-55%.
## How Reproducible:
???
### Steps to Reproduce:
1. Log in to a KDE session.
2. Do nothing, wait until KDE locks the screen and the screen goes out.
3. Wake up the system
### Actual Results:
[2023-08-29_11-29-13.mkv](/uploads/de38225732b2def103e923b08fab29c3/2023-08-29_11-29-13.mkv)
After the above steps (Steps to Reproduce), it is not possible to adjust the sound above or below 45-55%.
### Expected Results:
[2023-08-29_10-41-46.mkv](/uploads/0751c213495f1f3f2eca528cf674e9bd/2023-08-29_10-41-46.mkv)
The sound works and adjusts as before.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/15906abbdc814d146dd3846fdba1c733/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3473Can't connect ports in Ardour 7.5 using PW 0.3.782023-08-29T08:09:00ZBruno UnnaCan't connect ports in Ardour 7.5 using PW 0.3.78<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: cinnamon 5.8.4
- Kernel version (`uname -r`): 6.4.12-zen1-1-zen
## Description of Problem:
After updating to pipewire 0.3.78, from 0.3.77, I lost the ability to connect hardware ports in Ardour. Normally, I would either right-click at the top of the mixer strip, or open the audio-connections window, and I would be able to check the connections I wanted. For example, I could connect channels left and right from my digital interface to channels left and right of my guitar track.
Downgrading pipewire to 0.3.77 removes the problem.
## How Reproducible:
After the update it was happening all the time with new projects.
### Steps to Reproduce:
1. Update pipewire to 0.3.78 (called 1:0.3.78-1 in Arch Linux).
2. Open Ardour.
3. Create an audio track.
4. Try to connect the track to an external hardware source using Ardour's audio connections window.
### Actual Results:
The dots that indicate the connection in the connection matrix don't stick. The connection appears to be made anyway, because I can see the corresponding lines in qpwgraph and helvum, and because when arming the track for recording the signal can be monitored. But Ardour won't record it (or won't display the recording).
### Expected Results:
Clicking on the connection matrix should enable/disable the connections, recording should produce regions unequivocally, the state of the connection of ports should be consistent between Ardour and qpwgraph.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3472Since PW 0.3.78 Guitarix is silent2023-08-31T18:17:21ZYann ColletteSince PW 0.3.78 Guitarix is silent<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version Fedora 37
- Desktop Environment: KDE
...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version Fedora 37
- Desktop Environment: KDE
- Kernel version (`uname -r`): 6.4.12-100.fc37.x86_64
## Description of Problem:
Since 0.3.78, Guitarix audio processor is silent. It looks like no audio input comes in Guitarix.
Was working with the previous version of PW: 0.3.77
## How Reproducible:
Each time I use Gutarix (0.44.1).
I also use rakarrack-plus, but with this one, everything is OK (1.2.3).
### Steps to Reproduce:
1. Start Guitarix
2. Connect one input into gx_head_amp
3. Connect the output of gx_head_amp to gx_head_fx
4. Connect the outputs of gx_head_fx to audio out
### Actual Results:
No sound
### Expected Results:
Normally, you should hear the input processed by guitarixhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3471Inconsistent ALSA sink names2023-08-29T14:14:50ZgudvinrInconsistent ALSA sink names<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: KDE Plasma 5.27.7
- Kernel version (`uname -r`): 6.1.47-1-lts
## Description of Problem:
I have analog stereo ALSA sink which might have one of 2 different names in pipewire:
* alsa_output.pci-0000_00_1f.3.3.analog-stereo
* alsa_output.pci-0000_00_1f.3.analog-stereo
I don't know why it has one name over another and it makes automated control though scripts very annoying and unreliable.
Before I switched to PW, PA didn't have this issue (although it had completely different name from either of this).
This audio controller has different sinks:
* Line Out
* Headphones (combined with mic)
* SPDIF output
I use headphones output exclusively and those are always connected.
## How Reproducible:
It is basically random in a sense that I cannot predict what the name will be on the next system startup.
So far I think that it's about 50/50 chance.
### Steps to Reproduce:
1. Start the system
### Actual Results:
Sink name might be either 1 or 2.
### Expected Results:
Having consistent sink name.
# Additional Info (as attachments):
- Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
- `pw-dump > pw-dump.log` (for alsa_output.pci-0000_00_1f.**3.3**.analog-stereo): [pw-dump.3.3.log](/uploads/f92b439da5a684f796eb8dffa6732b54/pw-dump.3.3.log)
- `pw-dump > pw-dump.log` (for alsa_output.pci-0000_00_1f.**3**.analog-stereo): [pw-dump.3.log](/uploads/18d7582252df497d2396deb33f405b12/pw-dump.3.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3468Pipewire crashing when creating certain connections in pw-jack2023-09-24T18:43:19ZUltraBlackPipewire crashing when creating certain connections in pw-jack<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Garuda Linux
- Desktop Environment: Hyprland
- Kernel version (`uname -r`): 6.4.12-zen1-1-zen
## Description of Problem:
For quite a while now, pipewire has been sometimes randomly crashing when I make certain connections in pw-jack (with carla, if that's relevant)
## How Reproducible:
I haven't found a reliable setup, it crashes pretty regularly just by creating connections around zrythm
### Steps to Reproduce:
Download Zrythm, and connect some in- and outputs. Sometimes pipewire just crashes from that.
It seems to occur more often when there is a "connection loop", as follows (for my setup):
Midi interface in -> Midi interface out
Midi interface in -> Zrythm input -> zrythm output -> midi interface out
# Additional Info (as attachments):
- [coredump](https://chonkyrabbit.eu/lettermbox/8xpng1/)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3467Locking Screen Breaks Sound2023-08-29T08:33:35Zjasker5183Locking Screen Breaks Sound<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`): 0.3.78
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Fedora Linux 38 (Workstation Edition)
- Desktop Environment: Gnome 44.4
- Kernel version (`uname -r`): 6.4.11-200.fc38.x86_64
## Description of Problem:
When I lock my screen and unlock it again Pipewire produces no sound, I then have to restart Pipewire to get sound working again.
I notice that `systemctl status pipewire` shows:
````
Aug 25 20:12:47 host pipewire[53146]: spa.audioadapter: was started
Aug 25 20:12:47 host pipewire[53146]: mod.client-node: node 0x55642d09b6f0: set_param Spa:Enum:ParamId:PortConfig (11) 0x55642d0652f8: Input/output error
Aug 25 20:12:47 host pipewire[53146]: pw.core: 0x55642d023b70: error -5 for resource 2: node_set_param(Spa:Enum:ParamId:PortConfig) failed: Input/output error
Aug 25 20:12:47 host pipewire[53146]: mod.client-node: 0x55642d0f3230: error seq:879 -5 (node_set_param(Spa:Enum:ParamId:PortConfig) failed: Input/output error)
````
## How Reproducible:
Every time I lock my screen with 0.3.78 this happens.
### Steps to Reproduce:
1. Lock screen.
2. Unlock screen.
3. No sound.
### Actual Results:
No sound after screen unlock.
### Expected Results:
Sound after screen unlock.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
* [pw-dump-working.log](/uploads/a72e26f2d32806e820b9f11a41d6d4e0/pw-dump-working.log)
* [pw-dump-broken.log](/uploads/78787fb136ba27fa3c85daa290520aeb/pw-dump-broken.log)