pipewire issueshttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues2023-05-01T20:36:37Zhttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2753module-rtp-recv errors when trying to load from pipewire-pulse.conf2023-05-01T20:36:37ZScott Moreaumodule-rtp-recv errors when trying to load from pipewire-pulse.confWith pipewire 9dd1c78f50aa, RTP works great with module-null-sink+module-rtp-send on the server and module-rtp-recv on the client. The server loads the modules without problem from pipewire-pulse.conf but on the client, attempting to loa...With pipewire 9dd1c78f50aa, RTP works great with module-null-sink+module-rtp-send on the server and module-rtp-recv on the client. The server loads the modules without problem from pipewire-pulse.conf but on the client, attempting to load module-rtp-recv in context.exec section, I get the following errors:
Oct 08 04:53:45 desktop pipewire-pulse[1449]: mod.rtp-source: join mcast failed: No such device
Oct 08 04:53:45 desktop pipewire-pulse[1449]: mod.protocol-pulse: 0x55a41cfb45c0: [pactl] failed to load module index:536870912 name:module-rtp-recv tag:2 result:-19 (No such device)
If I load the module manually, it works fine.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2752QUESTION -- does the video sharing portion of PipeWire do anything else?2022-10-10T03:23:19ZDallas StrouseQUESTION -- does the video sharing portion of PipeWire do anything else?I made an issue on the Wayland protocols tracker to allow the mouse location to be obtained by an app or service: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/110
My question is, would PipeWire, should it be used fo...I made an issue on the Wayland protocols tracker to allow the mouse location to be obtained by an app or service: https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/110
My question is, would PipeWire, should it be used for video, also report the x and y values of the location of the mouse cursor relative to the screen resolution? I don't have much experience in handling bare PipeWire, so I thought it wise to make an issue asking about it.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2751pipewire doesn't let devices sleep when audio isn't in use causing issues wit...2023-09-22T11:21:42ZPeter Robinsonpipewire doesn't let devices sleep when audio isn't in use causing issues with battery powered devicesPipewire doesn't let devices go to sleep causing power management issues and stopping devices from going to sleep. This in turn stops entire subsystems from going to sleep.
On my Lenovo Thinkpad X1 gen9 the realtek codec runs at 100% ac...Pipewire doesn't let devices go to sleep causing power management issues and stopping devices from going to sleep. This in turn stops entire subsystems from going to sleep.
On my Lenovo Thinkpad X1 gen9 the realtek codec runs at 100% according to powertop which in turn stops i2c buses going to sleep. If I add in USB audio interfaces the USB bus connected also can't sleep.
On battery powered devices this causes quite a large reduction in possible runtime.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2750Behringer umc404hd like interface setup2023-06-07T15:05:35ZxxxcrowBehringer umc404hd like interface setup- PipeWire version (`pipewire --version`): Compiled with libpipewire 0.3.59
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Garuda Linux
- Desktop Environment: KDE
- Kernel version (`uname -r`): 5.19.13-ze...- PipeWire version (`pipewire --version`): Compiled with libpipewire 0.3.59
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Garuda Linux
- Desktop Environment: KDE
- Kernel version (`uname -r`): 5.19.13-zen1-1-zen
## Description of Problem:
I have a generic Chinese interface, it shows that it's using the same chip as Behringer umc404hd (mine is "icon upod-pro")
It has 2 inputs and 2 outputs, and some buttons and knobs
With windows and asio4all everything works great and as intended
But when i plug it into any linux i see next differences(assuming i set the sound to play wherever):
1. The sound just plays, when instead originally i needed to press the button "Input to PC -> Mixing"
2. If i press the button, it looks like it adds a little bit more sound. Or if i do press "Mic with DSP" it adds mic sound with effects on top of already playing sound.
3. The most annoying problem. The channels are both playing the guitar AND the mic.
So. I tried the approach from https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#behringer-umc404hd-microphoneguitar-virtual-sources
I edited the config:
```conf
context.modules = [
{ name = libpipewire-module-loopback
args = {
node.description = "CODEC Microphone"
capture.props = {
node.name = "capture.CODEC_Mic"
audio.position = [ AUX0 ]
stream.dont-remix = true
target.object = "alsa_input.usb-BurrBrown_from_Texas_Instruments_USB_AUDIO_CODEC-00.pro-input-0"
node.dont-reconnect = true
node.passive = true
}
playback.props = {
node.name = "CODEC_Mic"
media.class = "Audio/Source"
audio.position = [ MONO ]
}
}
}
{ name = libpipewire-module-loopback
args = {
node.description = "CODEC Guitar"
capture.props = {
node.name = "capture.CODEC_Guitar"
audio.position = [ AUX1 ]
stream.dont-remix = true
target.object = "alsa_input.usb-BurrBrown_from_Texas_Instruments_USB_AUDIO_CODEC-00.pro-input-0"
node.dont-reconnect = true
node.passive = true
}
playback.props = {
node.name = "CODEC_Guitar"
media.class = "Audio/Source"
audio.position = [ MONO ]
}
}
}
]
```
Now my `pw-cli ls Node` looks like that:
```
id 40, type PipeWire:Interface:Node/3
object.serial = "122"
object.path = "alsa:pcm:2:hw:2,0:playback"
factory.id = "18"
client.id = "36"
device.id = "39"
priority.session = "872"
priority.driver = "872"
node.description = "PCM2900C Audio CODEC Pro"
node.name = "alsa_output.usb-BurrBrown_from_Texas_Instruments_USB_AUDIO_CODEC-00.pro-output-0"
node.nick = "USB AUDIO CODEC"
media.class = "Audio/Sink"
id 44, type PipeWire:Interface:Node/3
object.serial = "44"
factory.id = "18"
client.id = "41"
node.description = "CODEC Microphone"
node.name = "capture.CODEC_Mic"
media.class = "Stream/Input/Audio"
id 45, type PipeWire:Interface:Node/3
object.serial = "45"
factory.id = "18"
client.id = "41"
node.description = "CODEC Microphone"
node.name = "CODEC_Mic"
media.class = "Audio/Source"
id 46, type PipeWire:Interface:Node/3
object.serial = "46"
factory.id = "18"
client.id = "42"
node.description = "CODEC Guitar"
node.name = "capture.CODEC_Guitar"
media.class = "Stream/Input/Audio"
id 47, type PipeWire:Interface:Node/3
object.serial = "47"
factory.id = "18"
client.id = "42"
node.description = "CODEC Guitar"
node.name = "CODEC_Guitar"
media.class = "Audio/Source"
id 53, type PipeWire:Interface:Node/3
object.serial = "54"
factory.id = "10"
client.id = "36"
node.name = "Midi-Bridge"
media.class = "Midi/Bridge"
id 59, type PipeWire:Interface:Node/3
object.serial = "123"
object.path = "alsa:pcm:2:hw:2,0:capture"
factory.id = "18"
client.id = "36"
device.id = "39"
priority.session = "1872"
priority.driver = "1872"
node.description = "PCM2900C Audio CODEC Pro"
node.name = "alsa_input.usb-BurrBrown_from_Texas_Instruments_USB_AUDIO_CODEC-00.pro-input-0"
node.nick = "USB AUDIO CODEC"
media.class = "Audio/Source"
```
And.. the sound is still stereo. I don't even want to say about the buttons..
## How Reproducible:
You need icon upod-pro
The issue persist before and after trying the config from the docs
### Steps to Reproduce:
1. Plug-in the device
2. Go to JACK graph
3. Connect the nodes
4. Capture 0 to sink input 0, sink capture 0 to output 0 (?)
### Actual Results:
Listen to the guitar playing and the same time with the mic
### Expected Results:
The sound from channel 0 is the guitar, and from the channel 1 is the mic
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/7c8094f3177686301c7e3e37a4ffbe05/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2749Filter chain segfault in 0.3.592022-10-09T08:35:02ZRomain D.Filter chain segfault in 0.3.59I am hitting a segmentation fault with pipewire 0.3.59 with the following config (which I have reduced to a minimal working example; the issue disappers when not piping into the convolvers or when removing the lv2 plugin):
~~~
context.p...I am hitting a segmentation fault with pipewire 0.3.59 with the following config (which I have reduced to a minimal working example; the issue disappers when not piping into the convolvers or when removing the lv2 plugin):
~~~
context.properties = {
core.daemon = true
core.name = pipewire-0
default.clock.rate = 44100
default.clock.allowed-rates = [ 44100 ]
}
context.spa-libs = {
audio.convert.* = audioconvert/libspa-audioconvert
api.alsa.* = alsa/libspa-alsa
api.v4l2.* = v4l2/libspa-v4l2
api.libcamera.* = libcamera/libspa-libcamera
api.bluez5.* = bluez5/libspa-bluez5
api.vulkan.* = vulkan/libspa-vulkan
api.jack.* = jack/libspa-jack
support.* = support/libspa-support
}
context.modules = [
{ name = libpipewire-module-rt }
{ name = libpipewire-module-protocol-native }
{ name = libpipewire-module-profiler }
{ name = libpipewire-module-metadata }
{ name = libpipewire-module-spa-device-factory }
{ name = libpipewire-module-spa-node-factory }
{ name = libpipewire-module-client-node }
{ name = libpipewire-module-client-device }
{ name = libpipewire-module-portal }
{ name = libpipewire-module-access }
{ name = libpipewire-module-adapter }
{ name = libpipewire-module-link-factory }
{ name = libpipewire-module-session-manager }
{ name = libpipewire-module-filter-chain
args = { node.name = "main" node.description = "Speakers DSP Sink" media.name = "Speakers DSP Sink"
filter.graph = {
nodes = [
{ type = lv2 plugin = "http://lsp-plug.in/plugins/lv2/loud_comp_stereo" name = loudComp control = { "volume" = -30.0 } }
{ type = builtin label = convolver name = convL config = { filename = "/home/romain/.config/alsa/drc/filter-L.wav" channel = 0 } }
{ type = builtin label = convolver name = convR config = { filename = "/home/romain/.config/alsa/drc/filter-R.wav" channel = 1 } }
]
inputs = [ "loudComp:in_l" "loudComp:in_r" ]
links = [ { output = "loudComp:out_l" input = "convL:In" }
{ output = "loudComp:out_r" input = "convR:In" } ]
outputs = [ "convL:Out" "convR:Out" ]
}
# see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2299#note_1342506
capture.props { node.name = "dsp.capture" media.class = Audio/Sink audio.channels = 2 audio.position = [ FL FR ] }
playback.props { node.name = "dsp.playback" node.passive = true node.target = "alsa_output.usb-Yamaha_Corporation_Steinberg_UR22-00.pro-output-0" }
}
}
]
context.objects = [
{ factory = spa-node-factory
args = { factory.name = support.node.driver node.name = Dummy-Driver node.group = pipewire.dummy
priority.driver = 20000 } }
{ factory = spa-node-factory
args = { factory.name = support.node.driver node.name = Freewheel-Driver
priority.driver = 19000 node.group = pipewire.freewheel node.freewheel = true } }
]
~~~
This works as expected with 0.3.58, but with 0.3.59 I see this in my journal whenever some application tries to play audio:
~~~
Oct 08 15:51:02 Silmeria kernel: pipewire[50287]: segfault at 0 ip 00007fc97d8665e5 sp 00007fc981075858 error 6 in lsp-plugins-lv2-1.2.3.so[7fc97d833000+135000]
Oct 08 15:51:02 Silmeria kernel: Code: f2 0f f0 4c 06 10 f2 0f f0 54 06 20 f2 0f f0 5c 06 30 f2 0f f0 64 06 40 f2 0f f0 6c 06 50 f2 0f f0 74 06 60 f2 0f f0 7c 06 70 <0f> 11 04 07 0f 11 4c 07 10 0f 11 54 07 20 0f 11 5c 07 30 0f 11 64
~~~
And here is a gdb backtrace:
~~~
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fc97d8665e5 in lsp::sse3::copy (dst=0x0, src=0x561cd1aa9110, count=992) at /usr/src/debug/lsp-plugins/modules/lsp-dsp-lib/include/private/dsp/arch/x86/sse3/copy.h:37
37 /usr/src/debug/lsp-plugins/modules/lsp-dsp-lib/include/private/dsp/arch/x86/sse3/copy.h: Directory not empty.
[Current thread is 1 (Thread 0x7fc9810766c0 (LWP 50287))]
(gdb) bt
#0 0x00007fc97d8665e5 in lsp::sse3::copy (dst=0x0, src=0x561cd1aa9110, count=992) at /usr/src/debug/lsp-plugins/modules/lsp-dsp-lib/include/private/dsp/arch/x86/sse3/copy.h:37
#1 0x00007fc97d8fcefd in lsp::dspu::Bypass::process (count=1024, wet=<optimized out>, dry=<optimized out>, dst=<optimized out>, this=0x561cd1a9d02c)
at ../../lsp-dsp-units/src/main/ctl/Bypass.cpp:109
#2 lsp::plugins::loud_comp::process (this=0x561cd1729010, samples=1024) at ../../lsp-plugins-loud-comp/src/main/plug/loud_comp.cpp:550
#3 0x00007fc97d95e59d in lsp::lv2::Wrapper::run (samples=1024, this=0x561cd1715ca0)
at /usr/src/debug/lsp-plugins/modules/lsp-plugin-fw/include/lsp-plug.in/plug-fw/wrap/lv2/impl/wrapper.h:559
#4 lsp::lv2::run (instance=0x561cd1715ca0, sample_count=1024) at wrap/lv2.cpp:178
#5 0x00007fc9815eaed6 in lilv_instance_run (sample_count=<optimized out>, instance=<optimized out>) at /usr/include/lilv-0/lilv/lilv.h:1935
#6 lv2_run (instance=0x561cd19b2680, SampleCount=<optimized out>) at ../pipewire/src/modules/module-filter-chain/lv2_plugin.c:394
#7 0x00007fc9815db5f2 in playback_process (d=0x561cd167a1f0) at ../pipewire/src/modules/module-filter-chain.c:657
#8 0x00007fc98332f6b2 in call_process (impl=0x561cd17f8ac0) at ../pipewire/src/pipewire/stream.c:442
#9 impl_node_process_output (object=0x561cd17f8ac0) at ../pipewire/src/pipewire/stream.c:1084
#10 0x00007fc98108374a in follower_ready (data=0x561cd182ae48, status=<optimized out>) at ../pipewire/spa/plugins/audioconvert/audioadapter.c:1169
#11 0x00007fc983334dd2 in pw_stream_trigger_process (stream=0x561cd17f8ac0) at ../pipewire/src/pipewire/stream.c:2391
#12 pw_stream_trigger_process (stream=0x561cd17f8ac0) at ../pipewire/src/pipewire/stream.c:2375
#13 0x00007fc98332f353 in call_process (impl=0x561cd17f77b0) at ../pipewire/src/pipewire/stream.c:442
#14 impl_node_process_input (object=0x561cd17f77b0) at ../pipewire/src/pipewire/stream.c:1005
#15 0x00007fc981083999 in impl_node_process (object=0x561cd180a338) at ../pipewire/spa/plugins/audioconvert/audioadapter.c:1434
#16 0x00007fc98330fa79 in process_node (data=0x561cd1827e00) at ../pipewire/src/pipewire/impl-node.c:1120
#17 0x00007fc98330ff57 in node_on_fd_events (source=<optimized out>) at ../pipewire/src/pipewire/impl-node.c:1178
#18 0x00007fc9833aa337 in loop_iterate (object=<optimized out>, timeout=<optimized out>) at ../pipewire/spa/plugins/support/loop.c:431
#19 0x00007fc9832e8e87 in do_loop (user_data=0x561cd1624a80) at ../pipewire/src/pipewire/data-loop.c:81
#20 0x00007fc98313c8fd in start_thread (arg=<optimized out>) at pthread_create.c:442
#21 0x00007fc9831bdc74 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:100
~~~https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2748Audio freezes and requires restart2022-10-07T18:43:30ZJohn TooheyAudio freezes and requires restart<!-- 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.58
- 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.58
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: None/dwm
- Kernel version (`uname -r`): 5.19.12-arch1-1
## Description of Problem:
Sometimes when using pipewire to watch to videos, play music or engage on signal calls my audio will just cut out randomly - and until I run a `systemctl --user restart pipewire.service pipewire-pulse.service` it remains as such.
A `systemctl --user status pipewire.service` provides no meaningful information (in the sense that all the logs are from before the
## How Reproducible:
Unfortunately I doubt it has high reproducability. If it helps I have an Intel sound card and also had this issue with pulse-audio.
### Steps to Reproduce:
1. Use audio
2. Have it randomly stop
3. Restart it
### Actual Results:
Audio dies
### Expected Results:
To continue having audio
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:[pw-dump.log](/uploads/b1ad5806077f996e5fab591d0b982b59/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2747pipewire-pulse intermittently fails to reconnect to remote output after switc...2022-10-07T18:44:19ZStrangiatopipewire-pulse intermittently fails to reconnect to remote output after switching to ethernet from wi-fiHi
I use pipewrire-pulse to stream audio from my laptop to the speakers connected to my deskop over network.
My laptop runs Arch Linux with Gnome and pipewire 1:0.3.58-1, my desktop also runs Arch Linux and pipewire 1:0.3.58-1 but with ...Hi
I use pipewrire-pulse to stream audio from my laptop to the speakers connected to my deskop over network.
My laptop runs Arch Linux with Gnome and pipewire 1:0.3.58-1, my desktop also runs Arch Linux and pipewire 1:0.3.58-1 but with KDE Plasma.
I have configured my systems occording the instructions available in the following article from Arch wiki:
https://wiki.archlinux.org/title/PipeWire#Sharing_audio_devices_with_computers_on_the_network
Steps to reproduce:
1. connect to wi-fi network
2. stream audio over network - I stream with Strawberry music player or Opera
browser playing a video in youtube
3. during the streaming, connect a network cable to the ethernet adapter
After the last step, my laptop disconnects from wi-fi, then the wired connection is stabilished thanks to [this dispatcher](https://wiki.archlinux.org/title/NetworkManager#Use_dispatcher_to_automatically_toggle_wireless_depending_on_LAN_cable_being_plugged_in) and one of the following results occurs inconsistently:
1. Sometimes the streaming continues as expected
2. Sometimes the streaming hangs permanently until suspend/resume cycle
3. Sometimes the streaming hangs for a few seconds, then the laptop disconnects from the desktop computer, the remote audio output disappears from sound menu of Gnome and the sound is output from the laptop speakers.
When the result 3 occurs, journal log prints these messages:
```
out 07 10:52:37 arch-laptop NetworkManager[426]: <info> [1665150757.4535] policy: set 'Conexão cabeada 1' (enp1s0) as default for IPv4 routing and DNS
out 07 10:52:37 arch-laptop audit[426]: USYS_CONFIG pid=426 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wireless-enabled:off" pid=30414 uid=0 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
out 07 10:52:37 arch-laptop NetworkManager[426]: <info> [1665150757.4544] audit: op="radio-control" arg="wireless-enabled:off" pid=30414 uid=0 result="success"
out 07 10:52:37 arch-laptop NetworkManager[426]: <info> [1665150757.4551] manager: rfkill: Wi-Fi now disabled by radio killswitch
out 07 10:52:37 arch-laptop kernel: audit: type=1111 audit(1665150757.451:262): pid=426 uid=0 auid=4294967295 ses=4294967295 msg='op=radio-control arg="wireless-enabled:off" pid=30414 uid=0 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
out 07 10:52:37 arch-laptop NetworkManager[426]: <info> [1665150757.4560] device (wlan0): new IWD device state is disconnected
out 07 10:52:37 arch-laptop gnome-shell[1222]: DWifi Debug: Device Current State: 20
out 07 10:52:37 arch-laptop NetworkManager[426]: <info> [1665150757.4624] manager: NetworkManager state is now CONNECTED_SITE
out 07 10:52:37 arch-laptop systemd[1093]: Starting Rygel DLNA/UPnP server...
out 07 10:52:37 arch-laptop ntpd[30325]: ntpd exiting on signal 15 (Terminated)
out 07 10:52:37 arch-laptop ntpd[30325]: 72.30.35.89 local addr 192.168.0.18 -> <null>
out 07 10:52:37 arch-laptop ntpd[30325]: 189.91.231.12 local addr 192.168.0.18 -> <null>
out 07 10:52:37 arch-laptop ntpd[30325]: 212.18.3.18 local addr 192.168.0.18 -> <null>
out 07 10:52:37 arch-laptop ntpd[30325]: 143.107.229.210 local addr 192.168.0.18 -> <null>
out 07 10:52:37 arch-laptop systemd[1]: Stopping Network Time Service...
out 07 10:52:37 arch-laptop systemd[1]: ntpd.service: Deactivated successfully.
out 07 10:52:37 arch-laptop systemd[1]: Stopped Network Time Service.
out 07 10:52:37 arch-laptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ntpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
out 07 10:52:37 arch-laptop kernel: audit: type=1131 audit(1665150757.477:263): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ntpd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
out 07 10:52:37 arch-laptop rygel[30494]: Rygel v0.40.4 inciando…
out 07 10:52:37 arch-laptop systemd[1093]: Started Rygel DLNA/UPnP server.
out 07 10:52:37 arch-laptop rygel[30494]: Novo plug-in “Playbin” disponível
out 07 10:52:37 arch-laptop NetworkManager[426]: <info> [1665150757.7248] manager: NetworkManager state is now CONNECTED_GLOBAL
out 07 10:52:37 arch-laptop rygel[30494]: Novo plug-in “MediaExport” disponível
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop mx-extract[30525]: rygel-media-export-extract.vala:180: Started with descriptors 3 (in) 4 (out), extracting meta-data: true
out 07 10:52:38 arch-laptop rygel[30494]: “file:///home/stalker/M%C3%BAsica” colhido
out 07 10:52:38 arch-laptop rygel[30494]: rygel-media-export-harvesting-task.vala:309: Harvesting of file:///home/stalker/M%C3%BAsica done in 0,116045
out 07 10:52:38 arch-laptop rygel[30494]: “file:///home/stalker/V%C3%ADdeos” colhido
out 07 10:52:38 arch-laptop rygel[30494]: rygel-media-export-harvesting-task.vala:309: Harvesting of file:///home/stalker/V%C3%ADdeos done in 0,134623
out 07 10:52:38 arch-laptop mx-extract[30524]: rygel-media-export-extract.vala:180: Started with descriptors 3 (in) 4 (out), extracting meta-data: true
out 07 10:52:38 arch-laptop rygel[30494]: “file:///home/stalker/Imagens” colhido
out 07 10:52:38 arch-laptop rygel[30494]: rygel-media-export-harvesting-task.vala:309: Harvesting of file:///home/stalker/Imagens done in 0,169907
out 07 10:52:38 arch-laptop mx-extract[30526]: rygel-media-export-extract.vala:180: Started with descriptors 3 (in) 4 (out), extracting meta-data: true
out 07 10:52:38 arch-laptop mx-extract[30527]: rygel-media-export-extract.vala:180: Started with descriptors 3 (in) 4 (out), extracting meta-data: true
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: “file:///home/stalker/Downloads” colhido
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: rygel-media-export-harvesting-task.vala:309: Harvesting of file:///home/stalker/Downloads done in 0,226372
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop PackageKit[813]: get-updates transaction /389_cdecbded from uid 1000 finished with success after 4ms
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:38 arch-laptop PackageKit[813]: get-updates transaction /390_eabecdae from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /391_cdacdcbe from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /392_aabddbeb from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /393_cbbceaaa from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /395_ceaeeacd from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /394_dcbadcec from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /396_dedcdcac from uid 1000 finished with success after 3ms
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /397_bdaeadad from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /398_eabbbaba from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /399_dbbccdcd from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /400_bbdbeada from uid 1000 finished with success after 3ms
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /401_badeecda from uid 1000 finished with success after 3ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /402_bcdacbee from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /403_caecdbae from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop PackageKit[813]: get-updates transaction /404_ccababbe from uid 1000 finished with success after 2ms
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:39 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:40 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:40 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop rygel[30494]: Error sending SSDP packet to FF05::C: Erro ao enviar mensagem: A rede está fora de alcance
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: mod.pulse-tunnel: failed to connect: Connection refused
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: mod.zeroconf-discover: Can't load module: Endereço ou dispositivo inexistente
out 07 10:52:41 arch-laptop pipewire-pulse[1106]: spa.loop: 0x56090c668df8: queue full 64, need 152
out 07 10:52:41 arch-laptop gsd-media-keys[1444]: Unable to get default sink
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2746bluetooth,Connecting a smartphone (bt 4.2) and a PC (bt 5.3) => only HSP, no ...2022-10-05T18:06:11Zpromeneurbluetooth,Connecting a smartphone (bt 4.2) and a PC (bt 5.3) => only HSP, no A2DPBluetooth 5.2 pci card EDUP LOVE EP-9651GS (chipset Intel AX210)
Samsung S7, Bluetooth 4.2
KDE Gears 22.08.1
Operating System: openSUSE Tumbleweed 20221003
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Ker...Bluetooth 5.2 pci card EDUP LOVE EP-9651GS (chipset Intel AX210)
Samsung S7, Bluetooth 4.2
KDE Gears 22.08.1
Operating System: openSUSE Tumbleweed 20221003
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 5.19.13-1-default (64-bit)
Graphics Platform: X11
bluez 5.65
pipewire 3.58
At the PC I connect the smartphone, then I get only HSP, no A2DP.
At the smartphone I connect the PC, then I get only HSP, no A2DP.https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2745Freeze in Firefox/Thunderbird related to pipewire-pulse + libcanberra-pulse2022-10-07T16:39:06ZGabriel CoronaFreeze in Firefox/Thunderbird related to pipewire-pulse + libcanberra-pulseFor some time, I have random freezes when trying to opening menus in Firefox or Thunderbird. The application unfreezes after some long timeout. It apparently started to happening after I replaces PulseAudio with Pipewire.
The freeze hap...For some time, I have random freezes when trying to opening menus in Firefox or Thunderbird. The application unfreezes after some long timeout. It apparently started to happening after I replaces PulseAudio with Pipewire.
The freeze happen because Firefox appanretly triggers a libcanberra notifification when opening a menu. This calls libcanberra-pulse (when this plugin is installed) which tries to initialize a pulseaudio main loop: this moon loop apparently never initialized correctly for some reason. It seems be be related to some state in pipewire-pulse because killing this process unfreezes the application.
All versions of Thunderbird/Firefox seems to be affected.
This is not reliably reproducible, it only happens from time to time.
once it starts happening, restarting the application does not fix the problem
and all the affected applications are affected at the same time.
What does not fix the issue:
* restarting the application.
What fixes the issue:
* restarting the system;
* killing wireplumber;
* killing and restarting wireplumber;
* killing pipewire-pulse;
* killing pipewire-pulse and restarting pipewire-pulse.
Killing wireplumber does not appear to unfreeze the frozen application but killing pipewire-pulse seems to unfreeze the frozen application.
I collected some stack traces and apparently the problem happens in
libcanberra-pulse :
<pre>
Thread 1 (Thread 0x7f5fdf4bb780 (LWP 2004) "firefox-bin"):
#0 __futex_abstimed_wait_common64 (private=0, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0x7f5f992d5f3c) at ./nptl/futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x7f5f992d5f3c, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0, cancel=cancel@entry=true) at ./nptl/futex-internal.c:87
#2 0x00007f5fdee844bb in __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0x7f5f992d5f3c, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at ./nptl/futex-internal.c:139
#3 0x00007f5fdee86c00 in __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f5f97b907c0, cond=0x7f5f992d5f10) at ./nptl/pthread_cond_wait.c:503
#4 ___pthread_cond_wait (cond=0x7f5f992d5f10, mutex=0x7f5f97b907c0) at ./nptl/pthread_cond_wait.c:618
#5 0x00007f5facf68577 in pa_cond_wait (c=<optimized out>, m=<optimized out>) at ../src/pulsecore/mutex-posix.c:146
#6 0x00007f5fad53da48 in pa_threaded_mainloop_wait (m=0x7f5f98c52f40) at ../src/pulse/thread-mainloop.c:216
#7 0x00007f5fae589d90 in pulse_driver_open (c=0x7f5fa5487440) at ./src/pulse.c:436
#8 0x00007f5f94f4e379 in driver_open (c=c@entry=0x7f5fa5487440) at ./src/dso.c:273
#9 0x00007f5f94f45868 in context_open_unlocked (c=c@entry=0x7f5fa5487440) at ./src/common.c:293
#10 0x00007f5f94f4650e in ca_context_play_full (c=c@entry=0x7f5fa5487440, id=id@entry=0, p=0x7f5f991c7de0, cb=cb@entry=0x0, userdata=userdata@entry=0x0) at ./src/common.c:517
#11 0x00007f5f94f46915 in ca_context_play (c=0x7f5fa5487440, id=0) at ./src/common.c:462
#12 0x00007f5fd520603c in nsSound::PlayEventSound(unsigned int) () from /home/gabriel/software/firefox/libxul.so
#13 0x00007f5fd53f19cc in nsMenuPopupFrame::ShowPopup(bool) () from /home/gabriel/software/firefox/libxul.so
#14 0x00007f5fd53fd8fb in nsXULPopupManager::ShowPopupCallback(nsIContent*, nsMenuPopupFrame*, bool, bool) () from /home/gabriel/software/firefox/libxul.so
#15 0x00007f5fd53fc7a1 in nsXULPopupManager::BeginShowingPopup(PendingPopup const&, bool, bool) () from /home/gabriel/software/firefox/libxul.so
#16 0x00007f5fd53fc485 in nsXULPopupManager::ShowMenu(nsIContent*, bool) () from /home/gabriel/software/firefox/libxul.so
#17 0x00007f5fd53f9d60 in mozilla::detail::RunnableFunction<nsMenuFrame::OpenMenu(bool)::$_0>::Run() () from /home/gabriel/software/firefox/libxul.so
#18 0x00007f5fd7243f80 in mozilla::TaskController::DoExecuteNextTaskOnlyMainThreadInternal(mozilla::detail::BaseAutoLock<mozilla::Mutex&> const&) () from /home/gabriel/software/firefox/libxul.so
#19 0x00007f5fd724b2ea in nsThread::ProcessNextEvent(bool, bool*) () from /home/gabriel/software/firefox/libxul.so
#20 0x00007f5fd72928f5 in mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) () from /home/gabriel/software/firefox/libxul.so
#21 0x00007f5fd7dd032f in MessageLoop::Run() () from /home/gabriel/software/firefox/libxul.so
#22 0x00007f5fd84f4249 in nsBaseAppShell::Run() () from /home/gabriel/software/firefox/libxul.so
#23 0x00007f5fd5fc75c5 in nsAppStartup::Run() () from /home/gabriel/software/firefox/libxul.so
#24 0x00007f5fd603cf60 in XREMain::XRE_mainRun() () from /home/gabriel/software/firefox/libxul.so
#25 0x00007f5fd603d893 in XREMain::XRE_main(int, char**, mozilla::BootstrapConfig const&) () from /home/gabriel/software/firefox/libxul.so
#26 0x00007f5fd603dc76 in XRE_main(int, char**, mozilla::BootstrapConfig const&) () from /home/gabriel/software/firefox/libxul.so
#27 0x000055b10856e652 in main ()
[Inferior 1 (process 2004) detached]
</pre>
Apparently clicking on a menu triggers a libcanberra notification which
goes trough pulseaudio (through libcanberra-pulse). Looking at canberra source code, it creates a
pulse audio threaded mainloop which appears to never reach the
PA_CONTEXT_READY state.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012563https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2744Realtek ALC4080 (UCM): working profile not available2023-03-02T14:11:51ZMaurizio AvogadroRealtek ALC4080 (UCM): working profile not available<!-- 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.59
- 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.59
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Debian GNU/Linux bookworm/sid (up-to-date testing)
- Desktop Environment: KDE Plasma v5.25.5
- Kernel version (`uname -r`): 6.0.0-x64v2+amdnative-xanmod1
## Description of Problem:
While within Gnome I can make the audio subsystem work by manually selecting the "Play HiFi quality Music" profile (defined since ALSA UCM2 v1.2.7 for my mainboard) of my onboard Realtek ALC4080 USB audio card, in KDE Plasma its only available profile is "off", which means no sound output is possible.
For the HDMI audio device, which I don't use and I keep on its default "off" profile, a working profile can instead be selected in both Gnome and KDE Plasma: this makes me suspect I'm facing an issue that is specific to my sound card, possibly having something to do with its UCM configuration.
Disabling and masking the pipewire user units and enabling back pulseaudio solves the issue; the pipewire-pulse daemon aims to be a drop-in replacement for pulseaudio.
Interesting enough, there is a difference between Pulseaudio and Pipewire in the output of
`pactl list cards | grep -E '(Profile|available:)'`
With Pulseaudio:
```
Profiles:
HiFi: Play HiFi quality Music (sinks: 3, sources: 2, priority: 8000, available: yes)
off: Spento (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: HiFi
```
With Pipewire:
```
Profiles:
off: Spento (sinks: 0, sources: 0, priority: 0, available: yes)
HiFi: Play HiFi quality Music (sinks: 3, sources: 2, priority: 8000, available: no)
Active Profile: off
```
The "HiFi" profile is not available with Pipewire; the profile can still be selected manually with the command
`pacmd set-card-profile alsa_card.usb-Generic_USB_Audio-00 HiFi`
which makes sound output through the the card work perfectly.
As I described above, in Gnome the working profile is _not_ automatically selected (but can be selected manually), while in KDE Plasma it appears only available profiles can be selected.
The involved hardware is a MSI MAG X570S TORPEDO MAX mainboard with a Realtek ALC4080 USB audio card onboard.
## How Reproducible:
Always reproducible with such hardware and KDE Plasma.
### Steps to Reproduce:
1. install the package pipewire-pulse
2. disable and mask pulseaudio user sockets and services
3. enable and start pipewire/wireplumber/pipewire-pulse sockets and services
### Actual Results:
No sound from the onboard ALC4080 card and the "Play HiFi quality Music" can't be selected (KDE Plasma) or must be enabled manually (Gnome)
### Expected Results:
Sound can be played through the onboard card and the "Play HiFi quality Music" profile is automatically selected.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`: [pw-dump.log](/uploads/965b629c469cda7eee13ce3572d3c013/pw-dump.log)
- ~/.config/pipewire/pipewire-pulse.conf (to enable network transparency): [pipewire-pulse.conf](/uploads/2000c87985e8582210711a5a3e677601/pipewire-pulse.conf)
- KDE Plasma audio management panel screenshot: ![Screenshot_20221005_110628](/uploads/bcf117263020a72a81da3d9824f8ab74/Screenshot_20221005_110628.png)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2743Click, crack, like a tape meow with Roland Rubix 44 (0.3.59, AMD Ryzen)2022-10-09T12:45:01ZDavid HorvathClick, crack, like a tape meow with Roland Rubix 44 (0.3.59, AMD Ryzen)<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
- Distrib...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
Fedora Linux 36 (Workstation Edition)
- Desktop Environment:
Gnome 3 with Wayland
- Kernel version (`uname -r`):
5.19.12-200.fc36.x86_64
## Description of Problem:
I bought a new notebook with Ryzen 7 6000 series. My old notebook is an Intel i7 (6-8 years old). The old notebook worked fine with Fedora 35 with my Roland Rubix 44 interface (Waveform Pro DAW, ALSA mode, buffer 128). The new notebook is faster, but with Fedora 36 the sound is clicked, crackled, and like a tape meow. With buffer 256 and Jack mode. If I run DAW with ALSA mode, the MIDI is a chaos, the DAW crash always.
I tried dnf downgrade, the result is noticeably better, but not the best.
In pw-top I see many of ERROR if I start DAW. I'm not playing a sound yet, but it's already counting errors.
Could it be that it doesn't work properly with the new processor? I doubt that.
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
[pw-dump.log](/uploads/51a876c174b7bcfa925858f971ad11bf/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2742Kodi "loses" AV-Preceiver as an audio output device2022-10-05T18:43:45ZGrandma-BettyKodi "loses" AV-Preceiver as an audio output device<!-- 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.55
- 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.55
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Buildroot 2022.08-git
- Desktop Environment: x11
- Kernel version (`uname -r`): 5.18.19
- Kodi version: 19.4 Matrix
- Batocera version: V35 stable release
## Description of Problem:
I'm using the retro gaming system [Batocera.linux](https://github.com/batocera-linux/batocera.linux) (which is based on [Buildroot](https://buildroot.org/)) which on top of the Linux system it mainly has two systems implemented: [Emulation Station](https://www.emulationstation.org/) (also called "ES") and Kodi, both natively implemented. The user can switch between Emulation Station and Kodi on the fly while the underlying Linux system is running. However, according to Kodi, I have an audio issue I was not able to resolve with the Batocera.linux dev team since months now.
My media center hardware chain setup is the following, all devices connected via HDMI:
HTPC (with Batocera.linux installed) --> NAD T187 AV-Preceiver --> LG OLED55GX6 4K TV
Where the HTPC HDMI output is a physical AMD Radeon 6800XT graphics card.
When starting the OS and booting directly into Kodi (Batocera.linux has an option to enable booting into Kodi directly), Kodi recognizes the AV-Preceiver for Audio output device (HDMI#3 in my case, as seen on the following screenshot), so everything is as intended:
![1](/uploads/9d24cf1e1ef2d8b7a676e2fd76288dcd/1.jpg)
Therefore I am able to passthrough any audio formats (True-HD, DTS, etc.) to the AV-Preceiver, also as intended:
![2](/uploads/e9f5510ac159f1fa133a27e55478dc16/2.jpg)
So far, so good.
Now comes the problem:
When exiting from Kodi to Emulation Station and then going back to Kodi, the AV-Preceiver (HDMI#3) disappears completely, it's not even selectable anymore from the list of audio devices:
![3](/uploads/52f3f58eea531ca9773d2a1edf5a330a/3.jpg)
Instead "ALSA" is being chosen by default and therefore it is not possible to passthrough the according audio formats True-HD / DTS anymore:
![4](/uploads/779bf628a2c96d30eedddf56fb07943d/4.jpg)
I'm not sure about the issue but it seems somehow Emulation Station does not release the sound driver accordingly but maybe I'm completely wrong and the problem is another one.
Only a system reboot makes the AV-Preceiver (HDMI#3) appear again.
Let me know if I can provide anyhing else. Any help and/or hints to solve this issue would be very appreciated, thanks!
### Actual Results:
Kodi "loses" the AV-Preceiver (HDMI#3) as an audio output device somehow when exiting Kodi and loading it again.
### Expected Results:
Exiting Kodi and going back to Kodi should preserve the AV-Preceiver (HDMI#3) as audio output device.
# Additional Info (as attachments):
Not sure if it really matters but I created two Pipewire logfiles and two Kodi logfiles:
Two logfiles after the first boot without exiting Kodi where the AV-Preceiver (HDMI#3) is still available as audio output device:
[Before.zip](/uploads/ecee55260b39bfd0694a27aa65d9ffba/Before.zip)
Two logfiles after exiting Kodi and starting it again where the AV-Preceiver (HDMI#3) is not available anymore:
[After.zip](/uploads/c291046d0f20c95874f064a3b2868f42/After.zip)
I already troubleshooted the issue a lot with Batocera devs without success. In addition I posted this issue a while ago on Kodi's Github repository without any answer yet but I got the feeling, that you as a Pipewire dev can help more with this. Maybe I'm wrong but still worth a try, I hope you can find time to take a look into it.
Thanks a bunch in advance!https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2741Pipewire service is always masked after upgrade of packages2023-05-15T12:51:49ZChad SmykayPipewire service is always masked after upgrade of packages<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
- Distri...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`):
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy
- Desktop Environment:
Gnome
- Kernel version (`uname -r`):
5.19.0-76051900-generic
## Description of Problem:
Everytime the pipewire packages are upgrades the service becomes masked by systemctl
## How Reproducible:
Not sure how to reproduce as I followed these instructions to install originally
https://askubuntu.com/questions/1339765/replacing-pulseaudio-with-pipewire-in-ubuntu-20-04
### Steps to Reproduce:
1. Use snap or apt to upgrade to latest Pipewire
2. systemctl --user status pipe-media-session.service
3. Once I reenable it and unmask it my bluetooth services start to work again.
### Actual Results:
After an upgrade pipewire services in systemctl are masked.
### Expected Results:
They should not be masked after an upgrade.
# Additional Info (as attachments):
- `[pw-dump.log](/uploads/10f9f7ed595a266ff89d06a461e1d9c2/pw-dump.log)`:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2740Seek bar of a lot of music player mute the sound2022-10-16T17:47:04ZichthyxSeek bar of a lot of music player mute the sound- PipeWire version (`pipewire --version`):
tried :
* 0.3.56
* 0.3.57
* 0.3.58
* 0.3.59 (arch testing)
- Distribution and distribution version : archlinux
- Desktop Environment: sway
- Kernel version (`uname -r`): 5.19.12-zen1-1-zen
## ...- PipeWire version (`pipewire --version`):
tried :
* 0.3.56
* 0.3.57
* 0.3.58
* 0.3.59 (arch testing)
- Distribution and distribution version : archlinux
- Desktop Environment: sway
- Kernel version (`uname -r`): 5.19.12-zen1-1-zen
## Description of Problem:
Using archlinux since some updates I have a weird bug.
I can't use the seek bar of many player, when clicking sound goes off for like 10 to 50 sec like it's buffering or don't know what pipewire is doing.
Player experience issue :
* Quodlibet
* Strawberry
* Lollypop
Player without the bug :
* Audacious
* Mpv
Not sure if it's related to gstreamer ?
## How Reproducible:
1. Listen music with quodlibet for e.g
2. click on the seek bar to move trough the music.
### Actual Results:
Sound goes off...
### Expected Results:
Should instant move in the position of the time bar.
# Attachment
[pw-dump.log](/uploads/f4f20ee2d77733cc58b0f9308a18d449/pw-dump.log)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2739Pipewire - Broken pipe2023-07-31T18:25:52ZNamBarnPipewire - Broken pipe```
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/pipewire.service.d
└─00-uresourced.conf
Act...```
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/pipewire.service.d
└─00-uresourced.conf
Active: active (running) since Tue 2022-10-04 12:24:54 +07; 15min ago
TriggeredBy: ● pipewire.socket
Main PID: 1836 (pipewire)
Tasks: 2 (limit: 18948)
Memory: 52.0M
CPU: 19.850s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─1836 /usr/bin/pipewire
Oct 04 12:24:57 fedora pipewire[1836]: mod.filter-chain: error id:3 seq:33 res:-2 (No such file or directory): no node available
Oct 04 12:24:57 fedora pipewire[1836]: mod.filter-chain: error id:3 seq:33 res:-2 (No such file or directory): no node available
Oct 04 12:24:57 fedora pipewire[1836]: mod.filter-chain: error id:3 seq:33 res:-2 (No such file or directory): no node available
Oct 04 12:24:57 fedora pipewire[1836]: mod.filter-chain: error id:3 seq:33 res:-2 (No such file or directory): no node available
Oct 04 12:24:57 fedora pipewire[1836]: mod.filter-chain: error id:3 seq:33 res:-2 (No such file or directory): no node available
Oct 04 12:40:06 fedora pipewire[1836]: spa.alsa: front:0: (0 missed) snd_pcm_avail after recover: Broken pipe
Oct 04 12:40:08 fedora pipewire[1836]: spa.alsa: front:0: (12 missed) snd_pcm_avail after recover: Broken pipe
Oct 04 12:40:10 fedora pipewire[1836]: spa.alsa: front:0: (12 missed) snd_pcm_avail after recover: Broken pipe
Oct 04 12:40:12 fedora pipewire[1836]: spa.alsa: front:0: (12 missed) snd_pcm_avail after recover: Broken pipe
Oct 04 12:40:14 fedora pipewire[1836]: spa.alsa: front:0: (12 missed) snd_pcm_avail after recover: Broken pipe
```
when i play game from steam it's happended everytime need helphttps://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2738[bluetooth] No sound with Marshall STANMORE II2022-10-04T19:15:15ZJean-Michaël Celerier[bluetooth] No sound with Marshall STANMORE IIAttached [pw.dump](/uploads/ff7f5543f1eeca5360aed5bcc0bab0e7/pw.dump), what other information can I give?
It's connected, and seems to show three codecs in pavucontrol: aptx, sbc, and sbc-xq.
My headphones work (but they have codecs mS...Attached [pw.dump](/uploads/ff7f5543f1eeca5360aed5bcc0bab0e7/pw.dump), what other information can I give?
It's connected, and seems to show three codecs in pavucontrol: aptx, sbc, and sbc-xq.
My headphones work (but they have codecs mSBC and CVSD).https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2737filter-chain convolver segfault at start2022-10-08T20:42:03ZDuncan Overbruckfilter-chain convolver segfault at start<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
```
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
```
- Distribu...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
```
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
```
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Void Linux
- Desktop Environment: none
- Kernel version (`uname -r`): 5.18.19_1
## Description of Problem:
Segfault in filter-chain with convolver node.
## How Reproducible:
Using the attached configuration file.
### Steps to Reproduce:
1.Start the pipewire daemon with the attached config file.
# Additional Info (as attachments):
- [filter-chain-segfault.log](/uploads/3efcad30ec1ec54a4525519bc81136a6/filter-chain-segfault.log)
- [convolver.conf](/uploads/cffc99b343ae116e6450c2fef0cd8dee/convolver.conf)https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2736Pipewire doesn't start after upgrade2022-10-02T22:14:24ZSFGrenadePipewire doesn't start after upgrade<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
```
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
```
- D...<!-- If you are filing this issue with a regular release please try master as it might already be fixed. -->
- PipeWire version (`pipewire --version`):
```
pipewire
Compiled with libpipewire 0.3.59
Linked with libpipewire 0.3.59
```
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Zorin OS 16.1
- Desktop Environment: Gnome
- Kernel version (`uname -r`): 5.15.0-48-generic
## Description of Problem:
After upgrading packages with apt (pipewire upgraded from `0.3.58-1~ubuntu20.04` to `0.3.59.r3.gd22feab-1~ubuntu20.04`) it didn't want to start anymore.
Checking `journalctl --boot 0 --user-unit pipewire.service` resulted:
```
Okt 02 13:52:17 sfg-Zorin-PC systemd[1517]: Started PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Main process exited, code=killed, status=11/SEGV
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Failed with result 'signal'.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Scheduled restart job, restart counter is at 1.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: Stopped PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: Started PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC pipewire[1602]: mod.rt: Can't find xdg-portal: (null)
Okt 02 13:52:18 sfg-Zorin-PC pipewire[1602]: mod.rt: found session bus but no portal
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Main process exited, code=killed, status=11/SEGV
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Failed with result 'signal'.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Scheduled restart job, restart counter is at 2.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: Stopped PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: Started PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC pipewire[1616]: mod.rt: Can't find xdg-portal: (null)
Okt 02 13:52:18 sfg-Zorin-PC pipewire[1616]: mod.rt: found session bus but no portal
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Main process exited, code=killed, status=11/SEGV
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Failed with result 'signal'.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Scheduled restart job, restart counter is at 3.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: Stopped PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: Started PipeWire Multimedia Service.
Okt 02 13:52:18 sfg-Zorin-PC pipewire[1619]: mod.rt: Can't find xdg-portal: (null)
Okt 02 13:52:18 sfg-Zorin-PC pipewire[1619]: mod.rt: found session bus but no portal
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Main process exited, code=killed, status=11/SEGV
Okt 02 13:52:18 sfg-Zorin-PC systemd[1517]: pipewire.service: Failed with result 'signal'.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: pipewire.service: Scheduled restart job, restart counter is at 4.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: Stopped PipeWire Multimedia Service.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: Started PipeWire Multimedia Service.
Okt 02 13:52:19 sfg-Zorin-PC pipewire[1623]: mod.rt: Can't find xdg-portal: (null)
Okt 02 13:52:19 sfg-Zorin-PC pipewire[1623]: mod.rt: found session bus but no portal
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: pipewire.service: Main process exited, code=killed, status=11/SEGV
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: pipewire.service: Failed with result 'signal'.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: pipewire.service: Scheduled restart job, restart counter is at 5.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: Stopped PipeWire Multimedia Service.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: pipewire.service: Start request repeated too quickly.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: pipewire.service: Failed with result 'signal'.
Okt 02 13:52:19 sfg-Zorin-PC systemd[1517]: Failed to start PipeWire Multimedia Service.
```
## How Reproducible:
### Steps to Reproduce:
1.
2.
3.
### Actual Results:
### Expected Results:
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:
```
sfg@sfg-Zorin-PC:~$ pw-dump
can't connect: Host is down
```https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2735pipewire-jack: audio input no longer working with Scarlett 18i20 3rd gen audi...2023-06-07T21:34:27ZIain Mottpipewire-jack: audio input no longer working with Scarlett 18i20 3rd gen audio interface, even with kernel 5.19.8-arch1-1<!-- 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.58
- 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.58
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: xfce4
- Kernel version (`uname -r`): 5.19.8-arch1-1
## Description of Problem:
I posted this issue earlier (https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2734), having tested with kernels 5.15.69-1-lts and 5.19.9-ach1-1. I was advised to downgrade to 5.19.8. Unfortunately the problem persists with the earlier kernel. I will continue trying with earlier kernels (5.19.*) and report back if I succeed, since it's possible that kernel 5.15.69-1-lts was equally problematic.
Here is the text from my earlier post:
___________________
After recent system updates audio input on Scarlett 18i20 sound card no longer works with pipewire-jack 1:0.3.58-1. All the hardware inputs appear correctly in the PipeWire graph, however when an input is connected to the input of a DAW (eg. Ardour) or other audio app (eg. Puredata) the input signal is not received. When testing with Puredata and when the Scarlett's "AUX0" and "AUX1" inputs are connected to Puredata's stereo inputs, it seems that the incoming signal is the same as that sent from Puredata's stereo outs.
I did not attempt to downgrade the package, however, replacing pipewire-jack with jack2 and making the correct connection with qjackctl solves the immediate problem.
I was initially testing with Arch Linux's current kernel (which i believe is 5.19.9-ach1-1, will have to check) but also tried the 5.15.69-1-lts kernel. The problem is the same.
__________________
## How Reproducible:
### Steps to Reproduce:
1.Occurs on both my laptop and desktop, both running Arch Linux.
### Actual Results:
see above
# Additional Info (as attachments):
- `pw-dump > pw-dump.log`:https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2734pipewire-jack: audio input no longer working with Scarlett 18i20 3rd gen audi...2022-09-30T21:33:27ZIain Mottpipewire-jack: audio input no longer working with Scarlett 18i20 3rd gen audio interface<!-- 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.58
- 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.58
- Distribution and distribution version (`PRETTY_NAME` from `/etc/os-release`): Arch Linux
- Desktop Environment: xfce
- Kernel version (`uname -r`): 5.15.69-1-lts as well as 5.19.9-ach1-1
## Description of Problem:
After recent system updates audio input on Scarlett 18i20 sound card no longer works with pipewire-jack 1:0.3.58-1. All the hardware inputs appear correctly in the PipeWire graph, however when an input is connected to the input of a DAW (eg. Ardour) or other audio app (eg. Puredata) the input signal is not received. When testing with Puredata and when the Scarlett's "AUX0" and "AUX1" inputs are connected to Puredata's stereo inputs, it seems that the incoming signal is the same as that sent from Puredata's stereo outs.
I did not attempt to downgrade the package, however, replacing pipewire-jack with jack2 and making the correct connection with qjackctl solves the immediate problem.
I was initially testing with Arch Linux's current kernel (which i believe is 5.19.9-ach1-1, will have to check) but also tried the 5.15.69-1-lts kernel. The problem is the same.
## How Reproducible:
Occurs on both my laptop and desktop, both running Arch Linux.
### Steps to Reproduce:
1. sudo pacman -Syu
2.
3.
### Actual Results:
see above
### Expected Results:
# Additional Info (as attachments):
[pw-dump.log](/uploads/b727fe6e8c7dae1ca8d1e96c85eea998/pw-dump.log)