pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2021-02-06T18:12:04Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/682Metadata events for default devices on client connection2021-02-06T18:12:04ZWellington Wallace Miguel MeloMetadata events for default devices on client connectionWhen a client adds a listener to metadata events `pw_metadata_add_listener` is it supposed to always receive at least one event delivering the default input and output device? On my computer when PulseEffects initializes and adds a metad...When a client adds a listener to metadata events `pw_metadata_add_listener` is it supposed to always receive at least one event delivering the default input and output device? On my computer when PulseEffects initializes and adds a metadata listener I always receive an event with the default devices right after the connection is made. As well as the others that come when I change the default in Pavucontrol manually. So I assumed that this would always be the case and used that connection as a way to get the default devices in the initialization. But based on an issue opened by a user today this may not be the case in all configurations https://github.com/wwmm/pulseeffects/issues/896#issuecomment-774094920
Somehow after the user set the default device once things were fixed. And now when PulseEffects initializes it always receives one metadata event with the default devices. According to the user he changed motherboard recently. Maybe this triggered some king of bug in PipeWire and this signal stopped being emitted?https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/689PIPEWIRE_DEBUG and PIPEWIRE_LOG doesnt work2021-02-07T15:23:59ZPLYSHKAPIPEWIRE_DEBUG and PIPEWIRE_LOG doesnt workWhile i was trying to get more info about #680 issue, i noticed that i can't get anything from game using PIPEWIRE_LOG and PIPEWIRE_DEBUG env var
I tried setting it on various sound emitters (like `aplay`), or just game (in steam with a...While i was trying to get more info about #680 issue, i noticed that i can't get anything from game using PIPEWIRE_LOG and PIPEWIRE_DEBUG env var
I tried setting it on various sound emitters (like `aplay`), or just game (in steam with added `%command%` at end of env vars) with something like this:
`PIPEWIRE_DEBUG=5 PIPEWIRE_LOG=/home/user/pipewire.log program`, which means i would have plenty of output even without any warnings/errors with trace.
But there's no output in terminal and no output to file, i mean - no file at all.
I tried creating such file, but it would be empty whole time.
Tried setting log to just file to potentially output to the same directory, but still nothing.
My hardware/software info could be found in #680 issue, if that's important.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/691Automatic quantum adjustment does not work properly with bluetooth2021-02-08T10:56:04ZPLYSHKAAutomatic quantum adjustment does not work properly with bluetoothContinuing from #680
We figured out that problem was with quantum levels. This happened for me only when i played wine games and with any bluetooth headset/radio.
Pipewire does not correctly adjust quantum amount and this results in cr...Continuing from #680
We figured out that problem was with quantum levels. This happened for me only when i played wine games and with any bluetooth headset/radio.
Pipewire does not correctly adjust quantum amount and this results in crackling, low quality audio.
If i would set minimum quantum amount in `/etc/pipewire/pipewire.conf` to 256, it would work fine and without crackling.
I noticed in logs one time that it lowers it from default amount to lower and lower, and eventually it stops at 128, which is lower than needed for proper audio.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/692RLIMIT_MEMLOCK warning since ~0.3.202021-02-08T18:26:02ZSebastian GothRLIMIT_MEMLOCK warning since ~0.3.20As of at least f03deb53 i do get
```
Feb 07 21:10:24 db systemd[900]: Started PipeWire PulseAudio.
Feb 07 21:11:15 db pipewire-pulse[203851]: Failed to mlock memory 0x7fa8c3730000 32832: This is not a problem but for best performance, c...As of at least f03deb53 i do get
```
Feb 07 21:10:24 db systemd[900]: Started PipeWire PulseAudio.
Feb 07 21:11:15 db pipewire-pulse[203851]: Failed to mlock memory 0x7fa8c3730000 32832: This is not a problem but for best performance, consider increasing RLIMIT_MEMLOCK
```
Also i notice rare but occasional crackling. That i also had when started using pipewire but vanished when i set up memlock limits. So i figure that might correlate.
```
$ cat /etc/security/limits.d/99-realtime-privileges.conf
@realtime - rtprio 98
@realtime - memlock unlimited
```
```
$ id | grep -c \(realtime\)
1
```
```
$ ulimit -a
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 128010
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 98
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 128010
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
```
The pipewire* processes run under the correct user.
A trivial example program with mlock(..., 32832) works fine.
Tested also with 0.3.21-1 from Arch as well as 37d8cbd5.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/700AptX and other codecs not available despite building with libopenaptx2021-02-09T09:01:12Zunderscore_jAptX and other codecs not available despite building with libopenaptxOS: NixOS (unstable channel)
Linux: 5.10.13
Bluez: 5.55
PipeWire: 0.3.18
Headphones: Sennheiser HD4.50BTNC
I might be missing something simple, but despite building with libopenaptx, sbc and ldacbt, I cannot choose any of those codecs ...OS: NixOS (unstable channel)
Linux: 5.10.13
Bluez: 5.55
PipeWire: 0.3.18
Headphones: Sennheiser HD4.50BTNC
I might be missing something simple, but despite building with libopenaptx, sbc and ldacbt, I cannot choose any of those codecs for my headphones (although I could when using pulseaudio with pulseaudio-modules-bt).
Note that since I am using NixOS, the bluez config might have changed when switching from pulseaudio - if there is anything I need to configure, that could be the cause.
Let me know what additional information I should provide.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/696qjackctl does not start2021-02-09T09:15:54ZWiedzmin89qjackctl does not startqjackctl 0.9.1-1
console out: `qjackctl: symbol lookup error: qjackctl: undefined symbol: jack_session_commands_free`qjackctl 0.9.1-1
console out: `qjackctl: symbol lookup error: qjackctl: undefined symbol: jack_session_commands_free`https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/695Headphone as default port2021-02-09T15:16:53ZLeiser Fernández GalloHeadphone as default portPCs tend to have 2 ports for the same audio card, one at the back (speaker) and one in the front (headphone). In the past the headphones one used to be the default but currently (0.3.21) the speaker one is. It will be nice to have the ol...PCs tend to have 2 ports for the same audio card, one at the back (speaker) and one in the front (headphone). In the past the headphones one used to be the default but currently (0.3.21) the speaker one is. It will be nice to have the old behavior back or at least a way for setting it up by hand.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/690pipewire-media-session crashed2021-02-09T17:50:36ZCsaba R.pipewire-media-session crashedI built and running febe8054. Crashed pipewire-media-session. [pw-bug.txt](/uploads/a7c1dd174f053b4640499b77cc08e0ba/pw-bug.txt)I built and running febe8054. Crashed pipewire-media-session. [pw-bug.txt](/uploads/a7c1dd174f053b4640499b77cc08e0ba/pw-bug.txt)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/694pipewire-pulse: Sink input volume update feedback loop (should ignore identic...2021-02-10T18:32:53Zsaivertpipewire-pulse: Sink input volume update feedback loop (should ignore identical volume updates)Has anyone noticed issues with volume control in applications that use pulseaudio volume control?
Because pipewire-pulse seems to cause a feedback loop in how it handles the volume updates. I had to fix my code to avoid it:
https://git...Has anyone noticed issues with volume control in applications that use pulseaudio volume control?
Because pipewire-pulse seems to cause a feedback loop in how it handles the volume updates. I had to fix my code to avoid it:
https://github.com/saivert/ddb_output_pulse2/commit/f2556506b6cba0f98f63666612c7a465a1a154ef
```diff
diff --git a/pulse.c b/pulse.c
index 4a3c933..73582f2 100644
--- a/pulse.c
+++ b/pulse.c
@@ -282,6 +282,7 @@ static void _pa_sink_input_info_cb(pa_context *c,
void *data)
{
if (i && plugin.has_volume) {
+ if (pa_cvolume_equal(&pa_vol, &i->volume)) return;
memcpy(&pa_vol, &i->volume, sizeof(pa_vol));
pa_volume_t v = pa_cvolume_avg(&pa_vol);
if (v <= PA_VOLUME_NORM) {
```
I guess that is good practice regardless but this code never caused issues with actual pulseaudio.
Please check the `do_set_stream_volume` function in `pulse-server.c`. It doesn't check if the volume actually changed.
It does look like Pulseaudio does: https://github.com/pulseaudio/pulseaudio/blob/c05c6f9eeecb507542be2f0399c73ec2572601e1/src/pulsecore/sink-input.c#L1288https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/693HFP capture doesn't work properly on pulseaudio apps2021-02-10T21:29:59ZP VHFP capture doesn't work properly on pulseaudio appsOn current master, capture from Bluetooth HFP mode in pulseaudio apps doesn't work properly.
In parec and gnome-sound-recorder, parts of input is missing (i.e. every n-th ~50ms segment of input deleted) resulting to a too short recordi...On current master, capture from Bluetooth HFP mode in pulseaudio apps doesn't work properly.
In parec and gnome-sound-recorder, parts of input is missing (i.e. every n-th ~50ms segment of input deleted) resulting to a too short recording. Recording clock also runs slower in gnome-sound-recorder.
Seems to have been introduced in 4f28edd4f76083904e593a91, the previous commit still works.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/720pw-uninstalled.sh must be run from PipeWire source tree2021-02-13T06:15:07ZBepw-uninstalled.sh must be run from PipeWire source treeIt would be nice to be able to run this script from any directory. I typically want to run it from the source tree of another application I am developing, but I first have to switch to the PipeWire source tree.It would be nice to be able to run this script from any directory. I typically want to run it from the source tree of another application I am developing, but I first have to switch to the PipeWire source tree.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/723Ambiguity regarding which codec is actually being used via Bluetooth; Trying ...2021-02-13T11:21:14ZFurvyAmbiguity regarding which codec is actually being used via Bluetooth; Trying to default aptx on startupKind of both a question and an issue. I just switched over to pipewire and am using a startup script where I use bluetoothctl to autoconnect to my device, but its ambiguous of what codec that pipewire is actually using. Pulseaudio previo...Kind of both a question and an issue. I just switched over to pipewire and am using a startup script where I use bluetoothctl to autoconnect to my device, but its ambiguous of what codec that pipewire is actually using. Pulseaudio previously would seem to "save" the previously-used codec, for instance if aptx were selected, it would stay that way on reconnect after reboot and indicate it directly.
Using `blueman-applet` and `pavucontrol`, the Bluetooth device I am connecting is registered as a "Headphone" device (Not actually a Headphone, it is an amplifier, but not an issue here). Under "Configuration" in pavucontrol, it lists the Profile as `High Fidelity Playback (A2DP Sink)` without any information of what codec is actually being used. An example of direct information of what codec is actually being used would be `High Fidelity Playback (A2DP Sink, codec aptX)`
I understand that the actual codecs available can be manually configured by editing `/etc/pipewire/media-session.d/bluez-monitor.conf` under the following default options:
```
# Enabled A2DP codecs (default: all)
#bluez5.codecs = [ sbc aac ldac aptx aptx_hd ]
```
My current configuration is:
```
bluez5.codecs = [ aptx ]
```
I am trying to force pipewire to have no choice but to use the aptx codec instead of sbc or something else due to the ambiguity. I have also tried changing `Enabled A2DP codecs (default: all)` to `Enabled A2DP codecs (default: aptx)` However, under the aforementioned Profile listing, regardless of setting, the profile still remains with no direct indication of what codec is being used.
I assume based on my current configuration, the aptx codec is being used even though pavucontrol does not directly indicate it, right? Is there any sort of command-line options to verify this? I cannot run `bluez-hcidump` even though I have `bluez-utils` installed either to find anything out. Must be some overlooked bug I guess, or I did not install something.
Thanks for any help or guidancehttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/727headset wont hold sound2021-02-13T20:12:10ZLewis Andersonheadset wont hold soundIn lutris world of warcraft the sound wont stay thru headset it keeps jumping back to speakers.In lutris world of warcraft the sound wont stay thru headset it keeps jumping back to speakers.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/735Anker SoundCore Liberty Air 2 Pro not selectable as an output device2021-02-14T22:23:50ZBjörn Daasebjoern.daase@gmail.comAnker SoundCore Liberty Air 2 Pro not selectable as an output deviceBluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
* Fedora 33
* pipewire 0.3.21-2.fc33
* GNOME
* Kernel 5.10.15-200.fc33
* Anker SoundCore Liberty Air 2 Pro
Description of Pro...Bluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
* Fedora 33
* pipewire 0.3.21-2.fc33
* GNOME
* Kernel 5.10.15-200.fc33
* Anker SoundCore Liberty Air 2 Pro
Description of Problem:
Pipewire does not allow me to select to my Anker SoundCore Liberty Air 2 Pro as an output device. They simply don't appear e.g. as an output device in g-c-c.
They however work fine with pulseaudio.
How Reproducible:
Always.
Additional Info Eg. Additional Kernel Patches, pw-dump > file (As Attachment Please):
[pw-dump.txt](/uploads/7281c6b758695a9b7439d15132b8191b/pw-dump.txt)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/742[not-an-issue] File bluez-monitor.conf has duplicate comment2021-02-15T18:43:57ZUnicodeMan[not-an-issue] File bluez-monitor.conf has duplicate commentI suspect a very minor issue where the code was commented:
in pipewire/src/daemon/media-session.d/bluez-monitor.conf,
```conf
...
13 # Supported headset roles: hsp_hs (HSP Headset),
14 # hsp_ag (HSP Audio G...I suspect a very minor issue where the code was commented:
in pipewire/src/daemon/media-session.d/bluez-monitor.conf,
```conf
...
13 # Supported headset roles: hsp_hs (HSP Headset),
14 # hsp_ag (HSP Audio Gateway),
15 # hfp_hf (HFP Hands-Free),
16 # hfp_ag (HFP Audio Gateway)
17 #bluez5.headset-roles = [ hsp_hs hsp_ag hfp_hf hfp_ag ]
...
```
Lines 14 and 16 are the same (except 14th has a comma at the end of the line).
bluez5.headset-roles seems to have same duplication (hsp_ag mentioned twice).
I propose removing 14th line in file pipewire/src/daemon/media-session.d/bluez-monitor.conf.
Sorry for not bringing pull request, I am complete noob with gitlab at the moment.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/745Tests 1-2 fail2021-02-16T14:00:36ZGerman PacenzaTests 1-2 fail```
1/21 test-audioadapter FAIL 0.08s (killed by signal 6 SIGABRT)
--- command ---
13:37:50 SPA_PLUGIN_DIR='/home/german/.cache/paru/clone/pipewire-git/src/build/spa/plugins/' /home/german/.cache/paru/clone/pipewire-git/...```
1/21 test-audioadapter FAIL 0.08s (killed by signal 6 SIGABRT)
--- command ---
13:37:50 SPA_PLUGIN_DIR='/home/german/.cache/paru/clone/pipewire-git/src/build/spa/plugins/' /home/german/.cache/paru/clone/pipewire-git/src/build/spa/plugins/audioconvert/test-audioadapter
--- stderr ---
[D][test-source.c:842 impl_init()] test-source 0x5556152aa2a0: init
[D][resample.c:986 impl_init()] mode:0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f1b0eb90368: mode 2
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f1b0eb90368: 0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f1b0eb90368: mode 2
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f1b0eb90368: 0
[T][test-source.c:154 impl_node_add_listener()] test-source 0x5556152aa2a0: add listener 0x7f1b0eb90070
[D][audioadapter.c:640 follower_info()] audioadapter 0x7f1b0eb90010: follower info Output
[T][audioconvert.c:868 impl_node_add_listener()] 0x7f1b0eb90368: add listener 0x7f1b0eb901d0
[T][audioadapter.c:605 convert_port_info()] audioadapter 0x7f1b0eb90010: port info 1:0
[D][audioadapter.c:1086 configure_adapt()] 0x7f1b0eb90010: configure convert 0x7f1b0eb90380
[D][audioconvert.c:774 impl_node_set_param()] mode:3 direction:1 0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f1b0eb90368: mode 3
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f1b0eb90368: 0
[T][audioadapter.c:605 convert_port_info()] audioadapter 0x7f1b0eb90010: port info 1:0
[D][audioadapter.c:155 link_io()] audioadapter 0x7f1b0eb90010: controls
[D][audioadapter.c:164 link_io()] audioadapter 0x7f1b0eb90010: set RateMatch on follower disabled -2 No such file or directory
[D][audioconvert.c:1064 impl_node_port_set_io()] set io 1 0 0
[D][fmtconvert.c:766 impl_node_port_set_io()] fmtconvert 0x7f1b0edd24b8: port 0:0 update io 1 0x7f1b0eb90210
[T][audioadapter.c:757 impl_node_add_listener()] audioadapter 0x7f1b0eb90010: add listener 0x7ffec4e2ae10
[T][test-source.c:154 impl_node_add_listener()] test-source 0x5556152aa2a0: add listener 0x7ffec4e2ad50
[D][audioadapter.c:640 follower_info()] audioadapter 0x7f1b0eb90010: follower info Output
input 0, output 64
[T][audioconvert.c:868 impl_node_add_listener()] 0x7f1b0eb90368: add listener 0x7ffec4e2ad50
input 0, output 64
[D][test-audioadapter.c:201 test_split_setup()] set profile 6@48000
[D][audioadapter.c:389 impl_node_set_param()] audioadapter 0x7f1b0eb90010: set param 11
[D][audioconvert.c:774 impl_node_set_param()] mode:3 direction:1 0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f1b0eb90368: mode 3
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f1b0eb90368: 0
[D][audioconvert.c:692 reconfigure_mode()] audioconvert 0x7f1b0eb90368: port config 6
[D][splitter.c:314 impl_node_set_param()] splitter 0x7f1b0edfb788: port config 48000/6
*** buffer overflow detected ***: terminated
-------
2/21 test-audioconvert FAIL 0.13s (killed by signal 6 SIGABRT)
--- command ---
13:37:50 SPA_PLUGIN_DIR='/home/german/.cache/paru/clone/pipewire-git/src/build/spa/plugins/' /home/german/.cache/paru/clone/pipewire-git/src/build/spa/plugins/audioconvert/test-audioconvert
--- stderr ---
[D][resample.c:986 impl_init()] mode:0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f6b11b3a010: mode 2
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f6b11b3a010: 0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f6b11b3a010: mode 2
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f6b11b3a010: 0
[T][audioconvert.c:868 impl_node_add_listener()] 0x7f6b11b3a010: add listener 0x7ffeae51b870
port 0 0 0x7f6b11d7c318
port 1 0 0x7f6b11da0980
input 64, output 64
[D][audioconvert.c:1011 impl_node_port_set_param()] audioconvert 0x7f6b11b3a010: set param 4 on port 0:0 0x7ffeae51ba50
[D][fmtconvert.c:664 impl_node_port_set_param()] fmtconvert 0x7f6b11d7c160: set param 4 on port 0:0 0x7ffeae51ba50
[D][fmtconvert.c:640 port_set_format()] fmtconvert 0x7f6b11d7c160: set format on port 0:0 res:2 stride:4
[T][audioconvert.c:868 impl_node_add_listener()] 0x7f6b11b3a010: add listener 0x7ffeae51b870
port 0 0 0x7f6b11d7c318
port 1 0 0x7f6b11da0980
[D][audioconvert.c:774 impl_node_set_param()] mode:3 direction:1 0
[D][audioconvert.c:641 reconfigure_mode()] audioconvert 0x7f6b11b3a010: mode 3
[D][audioconvert.c:405 clean_convert()] audioconvert 0x7f6b11b3a010: 0
port 1 0 (nil)
[D][audioconvert.c:692 reconfigure_mode()] audioconvert 0x7f6b11b3a010: port config 6
[D][splitter.c:314 impl_node_set_param()] splitter 0x7f6b11da5430: port config 48000/6
*** buffer overflow detected ***: terminated
-------
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/743Galaxy Buds+ won't pair/connect2021-02-16T16:01:23ZMatyas BGalaxy Buds+ won't pair/connectPipewire 0.3.21 installed using the 'manjaro-pipewire' package, kernel 5.10.15, bluez 5.55
```
# bluetoothctl pair d8:XX:XX:XX:XX:c7
Attempting to pair with D8:XX:XX:XX:XX:C7
Failed to pair: org.bluez.Error.AuthenticationCanceled
# sys...Pipewire 0.3.21 installed using the 'manjaro-pipewire' package, kernel 5.10.15, bluez 5.55
```
# bluetoothctl pair d8:XX:XX:XX:XX:c7
Attempting to pair with D8:XX:XX:XX:XX:C7
Failed to pair: org.bluez.Error.AuthenticationCanceled
# systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
Active: active (running) since Mon 2021-02-15 22:08:54 CET; 40min ago
Docs: man:bluetoothd(8)
Main PID: 3715 (bluetoothd)
Status: "Running"
Tasks: 1 (limit: 76496)
Memory: 2.3M
CGroup: /system.slice/bluetooth.service
└─3715 /usr/lib/bluetooth/bluetoothd
feb 15 22:34:21 laptop-manjaro bluetoothd[3715]: Endpoint unregistered: sender=:1.202 path=/MediaEndpoint/A2DPSource/sbc
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSource/ldac
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSink/aptx_hd
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSource/aptx_hd
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSink/aptx
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSource/aptx
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSink/sbc
feb 15 22:34:22 laptop-manjaro bluetoothd[3715]: Endpoint registered: sender=:1.205 path=/MediaEndpoint/A2DPSource/sbc
feb 15 22:36:34 laptop-manjaro bluetoothd[3715]: Pair device timed out for hci0
feb 15 22:40:23 laptop-manjaro bluetoothd[3715]: Pair device timed out for hci0
```
furthermore in debug mode i can see the following about this device:
```
[D][000001124.407847][bluez5-dbus.c:2433 interface_added()] Found object /org/bluez/hci0/dev_D8_XX_XX_XX_XX_C7, interface org.freedesktop.DBus.Introspectable
[D][000001124.407882][bluez5-dbus.c:2433 interface_added()] Found object /org/bluez/hci0/dev_D8_XX_XX_XX_XX_C7, interface org.bluez.Device1
[D][000001124.407916][bluez5-dbus.c:661 device_update_props()] device 0x558932209e40: Address=D8:XX:XX:XX:XX:C7
[D][000001124.407950][bluez5-dbus.c:661 device_update_props()] device 0x558932209e40: AddressType=random
[D][000001124.407986][bluez5-dbus.c:661 device_update_props()] device 0x558932209e40: Name=Buds+
[D][000001124.408020][bluez5-dbus.c:661 device_update_props()] device 0x558932209e40: Alias=Buds+
[D][000001124.408053][bluez5-dbus.c:724 device_update_props()] device 0x558932209e40: Paired=0
[D][000001124.408086][bluez5-dbus.c:724 device_update_props()] device 0x558932209e40: Trusted=0
[D][000001124.408118][bluez5-dbus.c:724 device_update_props()] device 0x558932209e40: Blocked=0
[D][000001124.408150][bluez5-dbus.c:724 device_update_props()] device 0x558932209e40: LegacyPairing=0
[D][000001124.408184][bluez5-dbus.c:714 device_update_props()] device 0x558932209e40: RSSI=-82
[D][000001124.408220][bluez5-dbus.c:724 device_update_props()] device 0x558932209e40: Connected=0
[D][000001124.408261][bluez5-dbus.c:661 device_update_props()] device 0x558932209e40: Adapter=/org/bluez/hci0
[D][000001124.408297][bluez5-dbus.c:771 device_update_props()] device 0x558932209e40: unhandled key ManufacturerData type 97
[D][000001124.408332][bluez5-dbus.c:724 device_update_props()] device 0x558932209e40: ServicesResolved=0
[D][000001124.408368][bluez5-dbus.c:2433 interface_added()] Found object /org/bluez/hci0/dev_D8_XX_XX_XX_XX_C7, interface org.freedesktop.DBus.Properties
...
[D][000001129.128846][bluez5-dbus.c:2718 filter_cb()] Properties changed in device /org/bluez/hci0/dev_D8_XX_XX_XX_XX_C7
[D][000001129.128922][bluez5-dbus.c:714 device_update_props()] device 0x558932209e40: RSSI=-81
[D][000001129.128941][bluez5-dbus.c:771 device_update_props()] device 0x558932209e40: unhandled key ManufacturerData type 97
```
Kindly asking for advice how to proceed? How to either track down the issue, or allow pairing/connecting.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/739SIGSEV in remove_sources2021-02-17T07:07:05ZBjörn Daasebjoern.daase@gmail.comSIGSEV in remove_sourcesBluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
* Fedora 33
* pipewire 0.3.21+nightly-210214.fc33
* GNOME
* Kernel 5.10.15-200.fc33
Description of Problem:
I get frequent c...Bluetooth Radio, Bluetooth Headset, Desktop Environment, Distribution, Version (Bluez, Kernel, and PipeWire):
* Fedora 33
* pipewire 0.3.21+nightly-210214.fc33
* GNOME
* Kernel 5.10.15-200.fc33
Description of Problem:
I get frequent crashes in `remove_sources`, however it is still unclear to me how to reproduce the crash reliably. This is the full backtrace
```
Core was generated by `/usr/bin/pipewire-media-session'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fe46297c21e in remove_sources (this=this@entry=0x556b8605fcc8) at ../spa/plugins/alsa/alsa-acp-device.c:118
118 spa_loop_remove_source(this->loop, &this->sources[i]);
(gdb) bt full
#0 0x00007fe46297c21e in remove_sources (this=this@entry=0x556b8605fcc8) at ../spa/plugins/alsa/alsa-acp-device.c:118
_f = 0x7fe46422a4a0
_res = -95
_o = 0x556b85fcf390
i = 0
#1 0x00007fe46297c27f in impl_clear (handle=0x556b8605fcc8) at ../spa/plugins/alsa/alsa-acp-device.c:875
this = 0x556b8605fcc8
#2 0x00007fe4641af5c5 in unref_handle (handle=0x556b8605fca0) at ../src/pipewire/pipewire.c:196
__func__ = {<optimized out> <repeats 13 times>}
#3 0x00007fe4641b4a5b in unref_handle (handle=<optimized out>) at ../src/pipewire/pipewire.c:193
__func__ = {<optimized out> <repeats 13 times>}
#4 pw_deinit () at ../src/pipewire/pipewire.c:473
h = <optimized out>
support = 0x7fe46420f0a0 <global_support.lto_priv>
registry = 0x7fe4642104e0 <global_registry>
p = 0x556b86028f70
#5 0x0000556b84825b4a in main (argc=<optimized out>, argv=<optimized out>) at ../src/examples/media-session/media-session.c:2304
impl = {this = {session = 0x0, props = 0x556b85fcdb00, session_id = 0, client_session = 0x0, loop = 0x556b85fcf280, context = 0x556b85fd7840, dbus_connection = 0x556b85ff4d50, metadata = 0x0,
info = 0x556b8618b4a0}, conf = 0x556b85fcdcd0, modules = 0x556b85fce160, loop = 0x556b85fce6b0, dbus = 0x556b85fe1cc0, monitor_core = 0x556b85ff7580, monitor_listener = {link = {
next = 0x556b85ff75d8, prev = 0x556b85ff7628}, cb = {funcs = 0x556b84865b40 <monitor_core_events>, data = 0x7ffc1c4637d0}, removed = 0x0, priv = 0x0}, monitor_seq = 1073747272,
policy_core = 0x556b8600a710, policy_listener = {link = {next = 0x556b8600a768, prev = 0x556b8600a7b8}, cb = {funcs = 0x556b84865c00 <policy_core_events>, data = 0x7ffc1c4637d0}, removed = 0x0,
priv = 0x0}, proxy_policy_listener = {link = {next = 0x556b8600a758, prev = 0x556b8600a7e8}, cb = {funcs = 0x556b84865bc0 <proxy_core_events>, data = 0x7ffc1c4637d0}, removed = 0x0, priv = 0x0},
registry = 0x556b8601d8d0, registry_listener = {link = {next = 0x556b8601d928, prev = 0x556b8601d928}, cb = {funcs = 0x556b84865b90 <registry_events>, data = 0x7ffc1c4637d0}, removed = 0x0,
priv = 0x0}, globals = {items = {data = 0x556b861c2530, size = 856, alloc = 1024, extend = 64}, free_list = 4294967295}, global_list = {next = 0x7ffc1c463940, prev = 0x7ffc1c463940}, hooks = {list = {
next = 0x7ffc1c463950, prev = 0x7ffc1c463950}}, endpoint_link_list = {next = 0x7ffc1c463960, prev = 0x7ffc1c463960}, endpoint_links = {items = {data = 0x556b85ff4b30, size = 0, alloc = 512,
extend = 64}, free_list = 4294967295}, link_list = {next = 0x7ffc1c463998, prev = 0x7ffc1c463998}, sync_list = {next = 0x7ffc1c4639a8, prev = 0x7ffc1c4639a8}, rescan_seq = 1073748618,
last_seq = 1073748415, scanning = 0, rescan_pending = 0}
support = <optimized out>
str = <optimized out>
n_support = 8
res = <optimized out>
c = <optimized out>
i = <optimized out>
item = 0x7ffc1c463950
long_options = {{name = 0x556b84855700 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x556b84855705 "version", has_arg = 0, flag = 0x0, val = 86}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
__func__ = "main"
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/721Volume from one Firefox tab immediately applies to all the rest2021-02-17T10:50:03ZSergey KondakovVolume from one Firefox tab immediately applies to all the restIn addition to even worse issue of https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/698#note_799428 that leads to permanent hanging of video on Youtube and whole pipeline, I've noticed that, if that is worked around by explicit ...In addition to even worse issue of https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/698#note_799428 that leads to permanent hanging of video on Youtube and whole pipeline, I've noticed that, if that is worked around by explicit definition of rate and everything works generally smoothly, sometimes videos are being muted or have volume that's not what's rendered in player's slider.
It seems like it caused by automatic application of 0% volume on all tabs/streams if one was silenced. I use Youtube addon to force autoplay off and mute by default as fallback for the damn Youtube trash player not stopping anyway. So on every reload of page or player it gets to 0% due to it trying to autoplay again, and it mutes all the rest with it. But sometimes all streams are silenced on seek or closing a tab which is likely have the same cause: application of 0% state to everything. 0% volume is also getting written into ~/.config/pipewire/media-session.d/restore-stream sometimes.
So there is probably some kind of problem with differentiating different streams having the same name and parent app.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/736make `monitor` loopback inputs opt-in2021-02-17T14:56:22ZBemake `monitor` loopback inputs opt-inPipeWire creates a loopback `monitor` JACK port for every hardware output channel. This is unexpected and confusing. It is also unnecessary as far as I can tell. IIUC loopbacks are just a hack around the lack of ability to arbitrarily ro...PipeWire creates a loopback `monitor` JACK port for every hardware output channel. This is unexpected and confusing. It is also unnecessary as far as I can tell. IIUC loopbacks are just a hack around the lack of ability to arbitrarily route audio between applications, which PipeWire provides.