pipewire issues
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues
2021-12-30T16:38:12Z
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/263
c173b23 adds a regression on the PinePhone
2021-12-30T16:38:12Z
Philip Müller
c173b23 adds a regression on the PinePhone
With the commit c173b23ac422bd3e745407bd8c543920f150e4aa `gst: use object_path to hide providers` the camera of the PinePhone fails to register and times out. Reverting that commit on **0.3.9** makes the camera work again.
Git-Bisect wa...
With the commit c173b23ac422bd3e745407bd8c543920f150e4aa `gst: use object_path to hide providers` the camera of the PinePhone fails to register and times out. Reverting that commit on **0.3.9** makes the camera work again.
Git-Bisect was done:
- [Bisect](https://gitlab.manjaro.org/manjaro-arm/issues/pinephone/phosh/-/issues/3#note_17031)
- [History](https://gitlab.manjaro.org/manjaro-arm/packages/temp/pipewire/-/commits/master/)
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/264
Inline functions can't be called with FFI
2021-12-30T16:38:12Z
Tom Wagner
Inline functions can't be called with FFI
Hello, \
I am trying to use Pipewire from Rust via its Foreign Function Interface. \
Unfortunately, there are some functions like [`pw_core_get_registry`](https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/pipewire/core.h...
Hello, \
I am trying to use Pipewire from Rust via its Foreign Function Interface. \
Unfortunately, there are some functions like [`pw_core_get_registry`](https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/src/pipewire/core.h#L348) that I can not call because they are in the header and therefore not in the .so to link to. \
As they also use a lot of deeply nested macros, they seem pretty annoying to reimplement in another language. \
Is there a reason these functions are marked `inline` and in the header, or would you consider moving them into a source file?
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/265
Target nodes change priority
2021-12-30T16:38:12Z
Alexander Miroshnichenko
Target nodes change priority
Is it possible to persistent/dynamic change `prio` attribute for every target?
```
$ pw-record --list-targets
Available targets ("*" denotes default):
38: name="alsa_card.usb-Generic_AVerMedia_PW310_Webcam_200901010001-02.capture.0.0" ...
Is it possible to persistent/dynamic change `prio` attribute for every target?
```
$ pw-record --list-targets
Available targets ("*" denotes default):
38: name="alsa_card.usb-Generic_AVerMedia_PW310_Webcam_200901010001-02.capture.0.0" description="AVerMedia PW310 Webcam Analog Stereo" prio=1945
* 40: name="alsa_card.pci-0000:00:1b.0.capture.0.0" description="7 Series/C216 Chipset Family High Definition Audio Controller (Z77 Extreme4 motherboard) Analog Stereo" prio=2009
53: name="alsa_card.usb-C-Media_Electronics_Inc._Microsoft_LifeChat_LX-3000-00.capture.0.0" description="LifeChat LX-3000 Headset Mono" prio=1872
```
```
$ pw-play --list-targets
Available targets ("*" denotes default):
* 39: name="alsa_card.pci-0000:00:1b.0.playback.0.0" description="7 Series/C216 Chipset Family High Definition Audio Controller (Z77 Extreme4 motherboard) Analog Stereo" prio=1009
78: name="alsa_card.usb-C-Media_Electronics_Inc._Microsoft_LifeChat_LX-3000-00.playback.0.0" description="LifeChat LX-3000 Headset Analog Stereo" prio=881
```
For this example I want to use sinks in order of priority: 78, 39. For sources: 53, 38, 40.
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/266
PulseAudio support is not yet fully implemented
2021-12-30T16:38:12Z
Sergey Kondakov
PulseAudio support is not yet fully implemented
I tried using PW as sole sound management system with replacement of PA and JACK. Haven't tested JACK compliance yet but immediately noticed that there are quite a few missing functions (can't list them now because of tests on a differen...
I tried using PW as sole sound management system with replacement of PA and JACK. Haven't tested JACK compliance yet but immediately noticed that there are quite a few missing functions (can't list them now because of tests on a different system) in PA support, so `paman` dies and `pavucontrol` complains. Meaning that, depending on what applications expect, they may be partially or fully inoperable yet.
#249 may be considered a subset of this issue.
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/267
Crash in `impl_add_listener` coming from `pw_core_spa_device_export`
2021-12-30T16:38:12Z
Björn Daase
bjoern.daase@gmail.com
Crash in `impl_add_listener` coming from `pw_core_spa_device_export`
* Fedora 32
* pipewire 0.3.9
Pipewire regularly crashes for me on Fedora 32 (~once per day). It is yet still unclear what exactly are the steps that reproduce that crash.
Here is the trace:
```rust
PID: 9639 (pipewire-media...
* Fedora 32
* pipewire 0.3.9
Pipewire regularly crashes for me on Fedora 32 (~once per day). It is yet still unclear what exactly are the steps that reproduce that crash.
Here is the trace:
```rust
PID: 9639 (pipewire-media-)
UID: 1000 (bjoern)
GID: 1000 (bjoern)
Signal: 11 (SEGV)
Timestamp: Tue 2020-08-18 09:37:05 CEST (2h 58min ago)
Command Line: /usr/bin/pipewire-media-session -d bluez5
Executable: /usr/bin/pipewire-media-session
Control Group: /user.slice/user-1000.slice/user@1000.service/pipewire.service
Unit: user@1000.service
User Unit: pipewire.service
Slice: user-1000.slice
Owner UID: 1000 (bjoern)
Boot ID: c7e0ecb8393b4338889f55f703914f1e
Machine ID: 995443f1f6d243e787e3f4243cd8d44b
Hostname: xps-9370
Storage: /var/lib/systemd/coredump/core.pipewire-media-.1000.c7e0ecb8393b4338889f55f703914f1e.9639.1597736225000000000000.lz4
Message: Process 9639 (pipewire-media-) of user 1000 dumped core.
Stack trace of thread 9639:
#0 0x00007fd9a59b141d impl_add_listener (libspa-alsa.so + 0x1441d)
#1 0x00007fd9a5aa1165 pw_core_spa_device_export (libpipewire-module-client-device.so + 0x3165)
#2 0x00007fd9a734496c pw_core_export (libpipewire-0.3.so.0 + 0x2f96c)
#3 0x0000561783cec3e7 sm_media_session_export_device (pipewire-media-session + 0x2f3e7)
#4 0x0000561783cd6cbf alsa_udev_object_info (pipewire-media-session + 0x19cbf)
#5 0x00007fd9a59afd71 emit_object_info.isra.0 (libspa-alsa.so + 0x12d71)
#6 0x00007fd9a59b0547 impl_device_add_listener (libspa-alsa.so + 0x13547)
#7 0x0000561783cd80fd sm_alsa_monitor_start (pipewire-media-session + 0x1b0fd)
#8 0x0000561783ccf6ae main (pipewire-media-session + 0x126ae)
#9 0x00007fd9a6ff6042 __libc_start_main (libc.so.6 + 0x27042)
#10 0x0000561783ccfa7e _start (pipewire-media-session + 0x12a7e)
Stack trace of thread 9641:
#0 0x00007fd9a70d0c5e epoll_wait (libc.so.6 + 0x101c5e)
#1 0x00007fd9a73d9518 impl_pollfd_wait (libspa-support.so + 0x7518)
#2 0x00007fd9a73d6f20 loop_iterate (libspa-support.so + 0x4f20)
#3 0x00007fd9a7344f07 do_loop (libpipewire-0.3.so.0 + 0x2ff07)
#4 0x00007fd9a71a2432 start_thread (libpthread.so.0 + 0x9432)
#5 0x00007fd9a70d0913 __clone (libc.so.6 + 0x101913)
GNU gdb (GDB) Fedora 9.1-5.fc32
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/pipewire-media-session...
Reading symbols from /usr/lib/debug/usr/bin/pipewire-media-session-0.3.9-1.fc32.x86_64.debug...
warning: core file may not match specified executable file.
[New LWP 9639]
[New LWP 9641]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/pipewire-media-session -d bluez5'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fd9a59b141d in impl_add_listener (object=0x561784f773a8, listener=0x561784f7cc70, events=0x7fd9a5aaab40 <pw_protocol_native_device_event_marshal>, data=0x561784f7caa0)
at ../spa/plugins/alsa/alsa-acp-device.c:234
234 profile = card->profiles[card->active_profile_index];
[Current thread is 1 (Thread 0x7fd9a6c0c7c0 (LWP 9639))]
Missing separate debuginfos, use: dnf debuginfo-install alsa-lib-1.2.3.2-1.fc32.x86_64 dbus-libs-1.12.20-1.fc32.x86_64 glibc-2.31-4.fc32.x86_64 libgcc-10.2.1-1.fc32.x86_64 libgcrypt-1.8.5-3.fc32.x86_64 libgpg-error-1.36-3.fc32.x86_64 lz4-libs-1.9.1-2.fc32.x86_64 sssd-client-2.3.1-2.fc32.x86_64 systemd-libs-245.7-1.fc32.x86_64 xz-libs-5.2.5-1.fc32.x86_64
(gdb) thread apply all bt full
Thread 2 (Thread 0x7fd9a6337700 (LWP 9641)):
#0 0x00007fd9a70d0c5e in epoll_wait () from /lib64/libc.so.6
No symbol table info available.
#1 0x00007fd9a73d9518 in impl_pollfd_wait (object=<optimized out>, pfd=<optimized out>, ev=0x7fd9a6336c10, n_ev=<optimized out>, timeout=<optimized out>) at ../spa/plugins/support/system.c:154
ep = 0x7fd9a6336a60
i = <optimized out>
nfds = <optimized out>
#2 0x00007fd9a73d6f20 in loop_iterate (object=0x561784f0eec8, timeout=-1) at ../spa/plugins/support/loop.c:285
_f = <optimized out>
_res = -95
_o = <optimized out>
impl = 0x561784f0eec8
loop = 0x561784f0eee0
ep = {{events = 0, data = 0x0} <repeats 32 times>}
i = <optimized out>
nfds = <optimized out>
#3 0x00007fd9a7344f07 in do_loop (user_data=0x561784f0ed70) at ../src/pipewire/data-loop.c:77
_f = <optimized out>
_res = -95
_o = <optimized out>
__clframe = <optimized out>
this = 0x561784f0ed70
res = <optimized out>
__func__ = "do_loop"
#4 0x00007fd9a71a2432 in start_thread () from /lib64/libpthread.so.0
No symbol table info available.
#5 0x00007fd9a70d0913 in clone () from /lib64/libc.so.6
No symbol table info available.
Thread 1 (Thread 0x7fd9a6c0c7c0 (LWP 9639)):
#0 0x00007fd9a59b141d in impl_add_listener (object=0x561784f773a8, listener=0x561784f7cc70, events=0x7fd9a5aaab40 <pw_protocol_native_device_event_marshal>, data=0x561784f7caa0) at ../spa/plugins/alsa/alsa-acp-device.c:234
this = 0x561784f773a8
save = {list = {next = 0x0, prev = 0x2ab34ee598a6d000}}
card = 0x561784f5be30
profile = <optimized out>
i = <optimized out>
__func__ = "impl_add_listener"
#1 0x00007fd9a5aa1165 in pw_core_spa_device_export (core=<optimized out>, type=<optimized out>, props=<optimized out>, object=0x561784f773c0, user_data_size=<optimized out>) at ../src/modules/module-client-device/proxy-device.c:84
_f = <optimized out>
_res = -95
_o = 0x561784f773c0
device = 0x561784f773c0
iface = 0x561784f7caa0
diface = 0x561784f773c0
proxy = 0x561784f7caa0
data = 0x561784f7cc68
#2 0x00007fd9a734496c in pw_core_export (core=0x561784f28d00, type=0x561783d08cea "Spa:Pointer:Interface:Device", props=0x561784f7c780, object=0x561784f773c0, user_data_size=336) at ../src/pipewire/core.c:287
proxy = <optimized out>
t = <optimized out>
res = <optimized out>
__func__ = "pw_core_export"
#3 0x0000561783cec3e7 in sm_media_session_export_device (sess=0x7fff5e45aed0, props=0x561784f7c780, object=0x561784f773c0) at ../src/examples/media-session/media-session.c:1415
impl = 0x7fff5e45aed0
device = <optimized out>
handle = <optimized out>
__func__ = "sm_media_session_export_device"
#4 0x0000561783cd6cbf in alsa_create_device (info=0x7fff5e45ab90, id=<optimized out>, impl=0x561784f4f960) at ../src/examples/media-session/alsa-monitor.c:771
res = <optimized out>
iface = 0x561784f773c0
card = <optimized out>
context = <optimized out>
device = 0x561784f7c670
handle = 0x561784f773a8
factory_name = <optimized out>
context = <optimized out>
device = <optimized out>
handle = <optimized out>
res = <optimized out>
iface = <optimized out>
card = <optimized out>
factory_name = <optimized out>
__func__ = "alsa_create_device"
_err = <optimized out>
reserve = <optimized out>
#5 alsa_udev_object_info (data=0x561784f4f960, id=<optimized out>, info=0x7fff5e45ab90) at ../src/examples/media-session/alsa-monitor.c:839
impl = <optimized out>
device = 0x0
#6 0x00007fd9a59afd71 in emit_object_info (this=this@entry=0x561784f57b58, id=1, dev=dev@entry=0x561784f58a50) at ../spa/plugins/alsa/alsa-udev.c:311
_f = <optimized out>
_l = 0x561784f57ba0
_h = <optimized out>
_t = 0x561784f57ba0
info = {version = 0, type = 0x7fd9a5a1a109 "Spa:Pointer:Interface:Device", factory_name = 0x7fd9a5a1a203 "api.alsa.pcm.device", change_mask = 3, flags = 0, props = 0x7fff5e45ab80}
ctl_hndl = 0x561784f5b900
str = <optimized out>
path = "hw:1\000V\000\000\000\000\000\000\000\000\000\000\300\255E^\377\177\000\000\001\000\000\000\000\000\000"
items = {{key = 0x7fd9a5a1a217 "device.enum.api", value = 0x7fd9a5a1a4a4 "udev"}, {key = 0x7fd9a5a1a227 "device.api", value = 0x7fd9a5a1a232 "alsa"}, {key = 0x7fd9a5a1a237 "media.class", value = 0x7fd9a5a1a243 "Audio/Device"}, {key = 0x7fd9a5a1a250 "api.alsa.path", value = 0x7fff5e45ad30 "hw:1"}, {key = 0x7fd9a5a1a25e "api.alsa.card", value = 0x561784f588cb "1"}, {key = 0x7fd9a5a1a295 "device.profile-set", value = 0x561784f5a4f0 "dell-dock-tb16-usb-audio.conf"}, {key = 0x7fd9a5a1a2c6 "device.plugged.usec", value = 0x561784f58be0 "2420721248"}, {key = 0x7fd9a5a1a2e2 "device.bus-path", value = 0x561784f58c50 "pci-0000:39:00.0-usb-0:2.5:1.0"}, {key = 0x7fd9a5a1a2f2 "device.sysfs.path", value = 0x561784f58920 "/sys/devices/pci0000:00/0000:00:1c.4/0000:03:00.0/0000:04:02.0/0000:39:00.0/usb3/3-2/3-2.5/3-2.5:1.0/sound/card1"}, {key = 0x7fd9a5a1a30a "device.bus-id", value = 0x561784f598e0 "usb-Generic_USB_Audio_200901010001-00"}, {key = 0x7fd9a5a1a31f "device.bus", value = 0x561784f59a50 "usb"}, {key = 0x7fd9a5a1a334 "device.subsystem", value = 0x561784f58b10 "sound"}, {key = 0x7fd9a5a1a352 "device.vendor.id", value = 0x561784f59500 "0bda"}, {key = 0x7fd9a5a1a393 "device.vendor.name", value = 0x561784f59020 "Realtek Semiconductor Corp."}, {key = 0x7fd9a5a1a3b2 "device.product.id", value = 0x561784f59170 "4014"}, {key = 0x7fd9a5a1a3f1 "device.product.name", value = 0x7fff5e45ab40 "USB Audio"}, {key = 0x7fd9a5a1a40f "device.serial", value = 0x561784f590a0 "Generic_USB_Audio_200901010001"}, {key = 0x561784f589a8 "", value = 0x5b703d2a970cd7bb <error: Cannot access memory at address 0x5b703d2a970cd7bb>}, {key = 0x0, value = 0x561784f589a0 "\200Y\227\245\331\177"}, {key = 0x7fd9a5a1a14b "DEVPATH", value = 0x7fd9a5a1a14b "DEVPATH"}, {key = 0x7fff5e45adc0 "\001", value = 0x0}, {key = 0x5e05adc0 <error: Cannot access memory at address 0x5e05adc0>, value = 0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff>}, {key = 0x0, value = 0x561784f57b58 ""}}
n_items = <optimized out>
res = <optimized out>
pcm = 0
__func__ = "emit_object_info"
#7 0x00007fd9a59b0547 in emit_device (dev=0x561784f58a50, enumerated=true, action=0, this=0x561784f57b58) at ../spa/plugins/alsa/alsa-udev.c:381
id = 1
id = <optimized out>
_l = <optimized out>
_h = <optimized out>
_t = <optimized out>
_f = <optimized out>
#8 enum_devices (this=0x561784f57b58) at ../spa/plugins/alsa/alsa-udev.c:474
dev = 0x561784f58a50
enumerate = 0x7fff5e45adc0
devices = 0x561784f729e0
#9 impl_device_add_listener (object=0x561784f57b58, listener=0x561784f4f9b0, events=<optimized out>, data=<optimized out>) at ../spa/plugins/alsa/alsa-udev.c:527
res = <optimized out>
this = 0x561784f57b58
save = {list = {next = 0x7fff5e45adb0, prev = 0x7fff5e45adb0}}
__func__ = "impl_device_add_listener"
#10 0x0000561783cd80fd in sm_alsa_monitor_start (session=0x7fff5e45aed0) at ../src/examples/media-session/alsa-monitor.c:930
_f = <optimized out>
_res = -95
_o = <optimized out>
context = <optimized out>
impl = 0x561784f4f960
iface = 0x561784f57b70
str = <optimized out>
res = 0
__func__ = "sm_alsa_monitor_start"
#11 0x0000561783ccf6ae in main (argc=<optimized out>, argv=<optimized out>) at ../src/examples/media-session/media-session.c:2045
name = 0x561783d0f897 "alsa-acp"
impl = {this = {session = 0x0, props = 0x561784f05ce0, session_id = 0, client_session = 0x0, loop = 0x561784f05e60, context = 0x561784f0e260, dbus_connection = 0x561784f25f90, metadata = 0x561784f4f370, info = 0x0}, loop = 0x561784f05e30, dbus = 0x561784f179a0, monitor_core = 0x561784f28d00, monitor_listener = {link = {next = 0x561784f28d58, prev = 0x561784f28da8}, cb = {funcs = 0x561783d1fc60 <monitor_core_events>, data = 0x7fff5e45aed0}, removed = 0x0, priv = 0x0}, monitor_seq = 1073741827, policy_core = 0x561784f3bdb0, policy_listener = {link = {next = 0x561784f3be08, prev = 0x561784f3be58}, cb = {funcs = 0x561783d1fc00 <policy_core_events>, data = 0x7fff5e45aed0}, removed = 0x0, priv = 0x0}, proxy_policy_listener = {link = {next = 0x561784f3bdf8, prev = 0x561784f3be88}, cb = {funcs = 0x561783d1fbc0 <proxy_core_events>, data = 0x7fff5e45aed0}, removed = 0x0, priv = 0x0}, registry = 0x561784f4ee50, registry_listener = {link = {next = 0x561784f4eea8, prev = 0x561784f4eea8}, cb = {funcs = 0x561783d1fcf0 <registry_events>, data = 0x7fff5e45aed0}, removed = 0x0, priv = 0x0}, globals = {items = {data = 0x561784f25b60, size = 0, alloc = 512, extend = 64}, free_list = 4294967295}, global_list = {next = 0x7fff5e45b030, prev = 0x7fff5e45b030}, hooks = {list = {next = 0x561784f4eed8, prev = 0x561784f4f578}}, endpoint_link_list = {next = 0x7fff5e45b050, prev = 0x7fff5e45b050}, endpoint_links = {items = {data = 0x561784f25d70, size = 0, alloc = 512, extend = 64}, free_list = 4294967295}, link_list = {next = 0x7fff5e45b088, prev = 0x7fff5e45b088}, sync_list = {next = 0x7fff5e45b098, prev = 0x7fff5e45b098}, rescan_seq = 0, last_seq = 0}
support = <optimized out>
n_support = 8
res = <optimized out>
c = <optimized out>
opt_enabled = <optimized out>
opt_disabled = 0x7fff5e45c84a "bluez5"
opt_properties = <optimized out>
long_options = {{name = 0x561783d0f7e1 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x561783d0f7e6 "version", has_arg = 0, flag = 0x0, val = 86}, {name = 0x561783d0f7ee "enabled", has_arg = 1, flag = 0x0, val = 101}, {name = 0x561783d0f7f6 "disabled", has_arg = 1, flag = 0x0, val = 100}, {name = 0x561783d0f7ff "properties", has_arg = 1, flag = 0x0, val = 112}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
i = <optimized out>
item = <optimized out>
__func__ = "main"
```
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/268
Screen share image is distorted
2021-12-30T16:38:12Z
Tyler Jones
Screen share image is distorted
Hello, first issue here, so feel free to point me in the right direction to debug, or if this isn't the right place for this:
Whenever I screen share over pipewire, I get a distorted image on the screen:
![image](/uploads/ff17b6f3b75ce...
Hello, first issue here, so feel free to point me in the right direction to debug, or if this isn't the right place for this:
Whenever I screen share over pipewire, I get a distorted image on the screen:
![image](/uploads/ff17b6f3b75ceb797e6e851a29ed7f93/image.png)
The distorted image does, in a way, resemble the screen capture area. It's not completely random, but resembles the colors and such. It's just very strangely distorted to be unusable.
This image is from OBS Studio, but I get similar in Firefox when sharing my screen over WebRTC. It behaves the same whether I share a specific window or the entire screen. All of the controls to select a window or screen work properly, just the output image is distorted. If I share via X11/not pipewire, everything works okay, except I cannot share Wayland windows.
Here are details about my system:
- Manjaro Linux
- pipewire 0.3.7 (although I've tried 0.3.8-2 from the arch repo, and I've tried the pipewire-git from AUR that appears to give me a black screen)
- xdg-desktop-portal 1.7.2
- obs-studio 25.0.8-2 (with obs-xdg-portal-git)
- fedora-firefox-wayland-bin (Firefox compiled with pipewire) 79.0-5
- Video - AMD via Mesa
Thank you in advance for any help!
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/269
bluetooth a2dp sink does not work with pulseaudio clients
2021-12-30T16:38:12Z
George Kiagiadakis
bluetooth a2dp sink does not work with pulseaudio clients
I have a bluetooth headset connected to PipeWire with the A2DP profile enabled.
While I can play audio just fine on this headset with `pw-play`, `pipewiresink`, `aplay -Dpipewire`, jack clients, etc... it doesn't work with PulseAudio cl...
I have a bluetooth headset connected to PipeWire with the A2DP profile enabled.
While I can play audio just fine on this headset with `pw-play`, `pipewiresink`, `aplay -Dpipewire`, jack clients, etc... it doesn't work with PulseAudio clients (`paplay`, `pulsesink`, etc). The client connects and links to the a2dp sink node, but it looks as if the clock is not running.
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/270
Can not share screen since pipewire > 0.3.6-1
2022-07-15T07:18:21Z
willist
Can not share screen since pipewire > 0.3.6-1
I have an Arch-Linux Gnome setup and use Google Chrome (AUR: https://aur.archlinux.org/packages/google-chrome/) to run the MS Teams web client. Since Gnome uses Wayland, I installed pipewire as described in the official wiki (https://wik...
I have an Arch-Linux Gnome setup and use Google Chrome (AUR: https://aur.archlinux.org/packages/google-chrome/) to run the MS Teams web client. Since Gnome uses Wayland, I installed pipewire as described in the official wiki (https://wiki.archlinux.org/index.php/PipeWire), including the libpipewire02 bit. This worked with pipewire 0.3.6-1.
However, when I upgraded to newer versions 3.7 and now 0.3.10-1, the screen sharing stopped working. I can select the screen and the popup at the bottom saying "You're sharing your screen" appears, but the other call participant only sees my MS profile circle in the middle (i.e., screen is not shared).
How to reproduce:
- Upgrade from pipewire 0.3.6-1 to a higher version
- systemctl --user restart pipewire
- Start MS teams conversation, try to share screen
Current fix:
- Downgrade to pipewire 0.3.6-1
- systemctl --user restart pipewire (This causes the gnome-shell to crash and I end up at the gdm login screen again)
Output of `journalctl --user -u pipewire with 0.3.10-1` when starting a (MS teams) screen share in Google Chrome:
```
Aug 25 13:22:32 THINKPAD systemd[1714]: Started Multimedia Service.
Aug 25 13:22:32 THINKPAD pipewire[11160]: [E][000000463.980481][backend-ofono.c:447 ofono_register_reply()] Register() failed: org.freedesktop.DBus.Error.ServiceUnknown
Aug 25 13:22:32 THINKPAD pipewire[11160]: [E][000000463.982435][core.c:71 core_event_error()] core 0x5603e45332f0: proxy 0x5603e4550cb0 id:4: seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory"
Aug 25 13:22:32 THINKPAD pipewire[11160]: [E][000000463.982443][media-session.c:1935 core_error()] error id:4 seq:4 res:-2 (No such file or directory): can't create device: No such file or directory
Aug 25 13:22:48 THINKPAD pipewire[11157]: [W][000000479.980488][module-protocol-native.c:378 client_new()] server 0x560579d32a90: no peersec: Protocol not available
Aug 25 13:22:52 THINKPAD pipewire[11157]: [W][000000483.837801][module-protocol-native.c:378 client_new()] server 0x560579d32a90: no peersec: Protocol not available
Aug 25 13:22:52 THINKPAD pipewire[11157]: [E][000000483.837886][module-access.c:101 check_flatpak()] failed to open "/proc/1794/root": Permission denied
Aug 25 13:22:52 THINKPAD pipewire[11157]: [W][000000483.837899][module-access.c:194 context_check_access()] access 0x560579d3e600: client 0x560579e1fb10 sandbox check failed: Permission denied
Aug 25 13:22:52 THINKPAD pipewire[11157]: [W][000000483.881834][module-protocol-native.c:378 client_new()] server 0x560579d32a90: no peersec: Protocol not available
Aug 25 13:22:52 THINKPAD pipewire[11157]: [W][000000483.882156][impl-client.c:634 pw_impl_client_update_permissions()] client 0x560579e36850: invalid global 0
```
Output of `journalctl --user -u pipewire with 0.3.6-1` when starting a (MS teams) screen share in Google Chrome:
```
Aug 25 13:26:06 THINKPAD systemd[1714]: Started Multimedia Service.
Aug 25 13:26:06 THINKPAD pipewire[14651]: [W][000000677.711188][module-protocol-native.c:376 client_new()] server 0x55720f978a80: no peersec: Protocol not available
Aug 25 13:26:06 THINKPAD pipewire[14651]: [W][000000677.711319][module-protocol-native.c:376 client_new()] server 0x55720f978a80: no peersec: Protocol not available
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.721253][pipewire.c:118 open_plugin()] can't load /usr/lib/spa-0.2/jack/libspa-jack.so: /usr/lib/spa-0.2/jack/libspa-jack.so: cannot open shared object file: No such file or directory
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.721269][pipewire.c:254 pw_load_spa_handle()] can't load 'jack/libspa-jack': No such file or directory
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.721273][spa-device.c:144 pw_spa_device_load()] can't load device handle: No such file or directory
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.721275][module-device-factory.c:167 create_object()] can't create device: No such file or directory
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.721278][private.h:241 pw_core_resource_errorv()] resource 0x55720f9ba840: id:4 seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory"
Aug 25 13:26:06 THINKPAD pipewire[14654]: [E][000000677.721511][core.c:71 core_event_error()] core 0x564080632ae0: proxy 0x56408064f030 id:4: seq:4 res:-2 (No such file or directory) msg:"can't create device: No such file or directory"
Aug 25 13:26:06 THINKPAD pipewire[14654]: [E][000000677.721530][media-session.c:1647 core_error()] error id:4 seq:4 res:-2 (No such file or directory): can't create device: No such file or directory
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.722916][alsa-pcm.c:33 spa_alsa_open()] hw:1,0: open failed: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14651]: [W][000000677.722926][adapter.c:175 find_format()] adapter 0x55720fa01700: can't get format: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.722931][module-adapter.c:231 create_object()] can't create node: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.722935][private.h:241 pw_core_resource_errorv()] resource 0x55720f9ba840: id:16 seq:65 res:-16 (Device or resource busy) msg:"can't create node: Device or resource busy"
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.723055][alsa-pcm.c:33 spa_alsa_open()] hw:1,0: open failed: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14651]: [W][000000677.723060][adapter.c:175 find_format()] adapter 0x55720fa04b60: can't get format: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.723064][module-adapter.c:231 create_object()] can't create node: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14651]: [E][000000677.723067][private.h:241 pw_core_resource_errorv()] resource 0x55720f9ba840: id:17 seq:66 res:-16 (Device or resource busy) msg:"can't create node: Device or resource busy"
Aug 25 13:26:06 THINKPAD pipewire[14654]: [E][000000677.723484][core.c:71 core_event_error()] core 0x564080632ae0: proxy 0x56408068b9f0 id:16: seq:65 res:-16 (Device or resource busy) msg:"can't create node: Device or resource busy"
Aug 25 13:26:06 THINKPAD pipewire[14654]: [E][000000677.723496][media-session.c:1647 core_error()] error id:16 seq:65 res:-16 (Device or resource busy): can't create node: Device or resource busy
Aug 25 13:26:06 THINKPAD pipewire[14654]: [E][000000677.723504][core.c:71 core_event_error()] core 0x564080632ae0: proxy 0x56408068c850 id:17: seq:66 res:-16 (Device or resource busy) msg:"can't create node: Device or resource busy"
Aug 25 13:26:06 THINKPAD pipewire[14654]: [E][000000677.723509][media-session.c:1647 core_error()] error id:17 seq:66 res:-16 (Device or resource busy): can't create node: Device or resource busy
Aug 25 13:26:12 THINKPAD pipewire[14651]: [W][000000684.152920][module-protocol-native.c:376 client_new()] server 0x55720f978a80: no peersec: Protocol not available
Aug 25 13:26:16 THINKPAD pipewire[14651]: [W][000000687.871440][module-protocol-native.c:376 client_new()] server 0x55720f978a80: no peersec: Protocol not available
Aug 25 13:26:16 THINKPAD pipewire[14651]: [E][000000687.871483][module-access.c:93 check_flatpak()] failed to open "/proc/11851/root": Permission denied
Aug 25 13:26:16 THINKPAD pipewire[14651]: [W][000000687.871489][module-access.c:167 context_check_access()] module 0x55720f980710: client 0x55720fa24b90 sandbox check failed: Permission denied
Aug 25 13:26:16 THINKPAD pipewire[14651]: [W][000000687.905384][module-protocol-native.c:376 client_new()] server 0x55720f978a80: no peersec: Protocol not available
Aug 25 13:26:16 THINKPAD pipewire[14651]: [W][000000687.905667][impl-client.c:608 pw_impl_client_update_permissions()] client 0x55720fa3aa80: invalid global 738252800
Aug 25 13:26:16 THINKPAD pipewire[14651]: [W][000000687.909492][connection.c:322 prepare_packet()] old version detected
Aug 25 13:26:16 THINKPAD pipewire[14651]: [W][000000687.910068][connection.c:322 prepare_packet()] old version detected
Aug 25 13:26:45 THINKPAD pipewire[14651]: [W][000000717.339289][impl-node.c:338 suspend_node()] node 0x55720fa4ffc0: error unset format input: Input/output error
```
Output of `yay -Qs pipewire`:
```
local/libpipewire02 0.2.7-1
User space API to deal with multimedia pipelines (0.2)
local/pipewire 0.3.10-1
Server and user space API to deal with multimedia pipelines
local/pipewire-pulse 0.3.10-1
Server and user space API to deal with multimedia pipelines (PulseAudio support)
```
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/271
Conform to the XDG base directory spec in pipewire-media-session
2021-12-30T16:38:12Z
Aman
Conform to the XDG base directory spec in pipewire-media-session
Currently pipewire-media-session uses ~/.pipewire-media-session for storing
configuration. It should use the XDG base directories instead.
Currently pipewire-media-session uses ~/.pipewire-media-session for storing
configuration. It should use the XDG base directories instead.
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/272
pw-pulse mpv 5.1 audio output differs from plain mpv
2021-12-30T16:38:12Z
Ilya Trukhanov
pw-pulse mpv 5.1 audio output differs from plain mpv
The output device is stereo, so I think it's a downmixing issue.
[out.dts](/uploads/bca3d4a7e73815f72bae06d4db3f81e6/out.dts) here's a 5 second-long sample that I can replicate this with.
I'm running Gentoo Linux.
`pulseaudio --versio...
The output device is stereo, so I think it's a downmixing issue.
[out.dts](/uploads/bca3d4a7e73815f72bae06d4db3f81e6/out.dts) here's a 5 second-long sample that I can replicate this with.
I'm running Gentoo Linux.
`pulseaudio --version` returns:
```
pulseaudio --version
pulseaudio 13.0
```
`pipewire --version` returns:
```
pipewire
Compiled with libpipewire 0.3.10
Linked with libpipewire 0.3.10
```
`mpv --version` returns:
```
mpv 0.32.0 Copyright © 2000-2020 mpv/MPlayer/mplayer2 projects
built on UNKNOWN
ffmpeg library versions:
libavutil 56.51.100
libavcodec 58.91.100
libavformat 58.45.100
libswscale 5.7.100
libavfilter 7.85.100
libswresample 3.7.100
ffmpeg version: 4.3.1
```
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/273
pw-jack buffer size
2021-12-30T16:38:13Z
TatriX Imba
pw-jack buffer size
I'm trying to run Ardour 6 with pipewire(-git) via `pw-jack ardour6` and it works!
Though I can't figure out how can I change buffer size. After Ardour connects to jack it shows buffer size of 1024 which results in a noticeable delay whe...
I'm trying to run Ardour 6 with pipewire(-git) via `pw-jack ardour6` and it works!
Though I can't figure out how can I change buffer size. After Ardour connects to jack it shows buffer size of 1024 which results in a noticeable delay when using audio input. Am I missing something? Thanks!
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/274
After switching to pipewire, pulseaudio crashes and leaves system with no sound
2021-12-30T16:38:13Z
Mateus Rodrigues Costa
mateusrodcosta@gmail.com
After switching to pipewire, pulseaudio crashes and leaves system with no sound
## System Info
OS: Fedora 32 64-bits, fully updated as of 2020-09-04
Version of packages:
* **pulseaudio.x86_64** 13.99.1-4.fc32
* **pipewire.x86_64** 0.3.10-1.fc32
* **pipewire-alsa.x86_64** 0.3.10-1.fc32
* **pipewire-libjack.x86_64*...
## System Info
OS: Fedora 32 64-bits, fully updated as of 2020-09-04
Version of packages:
* **pulseaudio.x86_64** 13.99.1-4.fc32
* **pipewire.x86_64** 0.3.10-1.fc32
* **pipewire-alsa.x86_64** 0.3.10-1.fc32
* **pipewire-libjack.x86_64** 0.3.10-1.fc32
* **pipewire-libpulse.x86_64** 0.3.10-1.fc32
* **pipewire-libs.x86_64** 0.3.10-1.fc32
## Steps to reproduce
Follow the steps outlined to test pipewire in https://blogs.gnome.org/uraeus/2020/09/04/pipewire-late-summer-update-2020/ , including a full reboot.
## Expected result
Actually having audio after reboot.
## Actual result
No audio except on the test of audio output on Gnome Settings.
Apparently caused by pulseaudio crashing.
## Backtrace
Backtrace from pulseaudio coredump
```
Reading symbols from /usr/bin/pulseaudio...
Reading symbols from /usr/lib/debug/usr/bin/pulseaudio-13.99.1-4.fc32.x86_64.debug...
[New LWP 22413]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/usr/bin/pulseaudio --daemonize=no'.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 return ret;
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1 0x00007fb989f86895 in __GI_abort () at abort.c:79
#2 0x00007fb98a32aa52 in pa_signal_done () at ../pipewire-pulseaudio/src/mainloop-signal.c:63
#3 0x0000559faabfebd6 in main (argc=<optimized out>, argv=<optimized out>) at daemon/main.c:1206
```
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/275
Video playback in Chromium broken after switching to pipewire
2021-12-30T16:38:13Z
tom-seewald
Video playback in Chromium broken after switching to pipewire
# Problem:
Video playback on Chromium does not work after switching to pipewire. The video does not play (no video or audio) and it will sometimes display an error message. I should also note that I have *not* encountered similar problem...
# Problem:
Video playback on Chromium does not work after switching to pipewire. The video does not play (no video or audio) and it will sometimes display an error message. I should also note that I have *not* encountered similar problems with Firefox so far.
I believe this is related to pipewire for the following reasons:
1. Switching back to pulse audio and restarting Chromium fixes the issue, video playback works as expected.
2. Youtube specifically reports that it is an audio renderer error.
Sites I have tested:
youtube.com, twitch.tv, and vimeo.com.
# Misc
I am switching to pipewire by running the commands listed [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/snippets/1165), and switching back to pulse audio by running the commands listed [here](https://gitlab.freedesktop.org/pipewire/pipewire/-/snippets/1164).
# Operating System:
Fedora Rawhide (Workstation)
# Installed software:
```
chromium-85.0.4183.83-1.fc34.x86_64
chromium-common-85.0.4183.83-1.fc34.x86_64
pipewire-libs-0.3.10-1.fc34.x86_64
pipewire-0.3.10-1.fc34.x86_64
pipewire0.2-libs-0.2.7-4.fc33.x86_64
pipewire-libpulse-0.3.10-1.fc34.x86_64
pipewire-alsa-0.3.10-1.fc34.x86_64
pipewire-libjack-0.3.10-1.fc34.x86_64
```
# pactl info
```
Server String: pipewire-0
Library Protocol Version: 33
Server Protocol Version: 33
Is Local: yes
Client Index: 54
Tile Size: 4096
User Name: tom
Host Name: rawhide-test
Server Name: pipewire-0
Server Version: 0.3.10
Default Sample Specification: float32le 2ch 48000Hz
Default Channel Map: front-left,front-right
Default Sink: alsa_card.pci-0000:00:1b.0.playback.0.0
Default Source: alsa_card.pci-0000:00:1b.0.capture.0.0
Cookie: 0aa0:a8de
```
# Youtube debug output
[chrome-youtube-debug-output.txt](/uploads/8f4d84c5548adb484bbfadd6538249c6/chrome-youtube-debug-output.txt)
# Screenshots
![chromium-youtube-error](/uploads/84c5f11331a28cd6ec7e09c19446efa7/chromium-youtube-error.png)
![chromium-twitch-error](/uploads/44e25a7cec99c7a4c16ab4ce709f5fff/chromium-twitch-error.png)
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/276
OpenAL does not work
2021-12-30T16:38:13Z
hexchain
OpenAL does not work
Arch Linux, PipeWire 030bef8d, OpenAL 1.20.1.
Applications that use OpenAL, such as Telegram, seem to hang on start.
`openal-info` hangs with the following output:
```
% openal-info
Available playback devices:
[W][000482543.164622][mai...
Arch Linux, PipeWire 030bef8d, OpenAL 1.20.1.
Applications that use OpenAL, such as Telegram, seem to hang on start.
`openal-info` hangs with the following output:
```
% openal-info
Available playback devices:
[W][000482543.164622][mainloop.c:397 pa_mainloop_set_poll_func()] Not Implemented
```
gdb:
```
(gdb) thr apply all bt
Thread 4 (Thread 0x7ffff7486640 (LWP 2432659)):
#0 0x00007ffff7d745de in epoll_wait () from /usr/lib/libc.so.6
#1 0x00007ffff7837ff1 in impl_pollfd_wait (object=<optimized out>, pfd=<optimized out>, ev=0x7ffff7485b50, n_ev=<optimized out>, timeout=<optimized out>) at ../pipewire/spa/plugins/support/system.c:154
#2 0x00007ffff782f300 in loop_iterate (object=0x7ffff0003d78, timeout=-1) at ../pipewire/spa/plugins/support/loop.c:285
#3 0x00007ffff77b2d82 in pa_mainloop_poll (m=m@entry=0x7ffff0001f30) at ../pipewire/pipewire-pulseaudio/src/mainloop.c:305
#4 0x00007ffff77b2e11 in pa_mainloop_iterate (m=m@entry=0x7ffff0001f30, block=block@entry=1, retval=retval@entry=0x7ffff7485dfc) at ../pipewire/pipewire-pulseaudio/src/mainloop.c:344
#5 0x00007ffff77b2ec1 in pa_mainloop_run (m=0x7ffff0001f30, retval=0x7ffff7485dfc) at ../pipewire/pipewire-pulseaudio/src/mainloop.c:364
#6 0x00007ffff7eb749e in ?? () from /usr/lib/libopenal.so.1
#7 0x00007ffff7b3ec24 in std::execute_native_thread_routine (__p=0x55555558a770) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/thread.cc:80
#8 0x00007ffff7c5b3e9 in start_thread () from /usr/lib/libpthread.so.0
#9 0x00007ffff7d74293 in clone () from /usr/lib/libc.so.6
Thread 1 (Thread 0x7ffff790a740 (LWP 2432653)):
#0 0x00007ffff7c64db0 in __lll_lock_wait () from /usr/lib/libpthread.so.0
#1 0x00007ffff7c5f6f3 in __pthread_mutex_cond_lock () from /usr/lib/libpthread.so.0
#2 0x00007ffff7b38c11 in __gthread_cond_wait (__mutex=<optimized out>, __cond=<optimized out>) at /build/gcc/src/gcc-build/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu/bits/gthr-default.h:865
#3 std::condition_variable::wait (this=<optimized out>, __lock=...) at /build/gcc/src/gcc/libstdc++-v3/src/c++11/condition_variable.cc:53
#4 0x00007ffff7eb629c in ?? () from /usr/lib/libopenal.so.1
#5 0x00007ffff7eb91af in ?? () from /usr/lib/libopenal.so.1
#6 0x00007ffff7e78c9e in ?? () from /usr/lib/libopenal.so.1
#7 0x00007ffff7c6318f in __pthread_once_slow () from /usr/lib/libpthread.so.0
#8 0x00007ffff7e6ff2f in ?? () from /usr/lib/libopenal.so.1
#9 0x00007ffff7e78025 in alcGetString () from /usr/lib/libopenal.so.1
#10 0x0000555555555227 in ?? ()
#11 0x00007ffff7c9c152 in __libc_start_main () from /usr/lib/libc.so.6
#12 0x000055555555578e in _start ()
```
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/277
No sound from Flatpak applications
2021-12-30T16:38:13Z
aoeudhtns
No sound from Flatpak applications
Using the setup procedures given [in the blog post](https://blogs.gnome.org/uraeus/2020/09/04/pipewire-late-summer-update-2020/) to do a full F32 Workstation conversion, and rebooted. `pactl info` shows the right pipewire string. Firefox...
Using the setup procedures given [in the blog post](https://blogs.gnome.org/uraeus/2020/09/04/pipewire-late-summer-update-2020/) to do a full F32 Workstation conversion, and rebooted. `pactl info` shows the right pipewire string. Firefox plays audio successfully. I tried a few Flatpak applications and none of them reproduce sound.
Wim Taymans
Wim Taymans
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/278
Audacious: ALSA to PipeWire works, PulseAudio to PipeWire has playback issues
2022-07-15T07:18:21Z
aoeudhtns
Audacious: ALSA to PipeWire works, PulseAudio to PipeWire has playback issues
I used the setup described [in the recent blog](https://blogs.gnome.org/uraeus/2020/09/04/pipewire-late-summer-update-2020/) on my Fedora 32 workstation. Performed reboot, and verified with `pactl info` that PipeWire is configured as exp...
I used the setup described [in the recent blog](https://blogs.gnome.org/uraeus/2020/09/04/pipewire-late-summer-update-2020/) on my Fedora 32 workstation. Performed reboot, and verified with `pactl info` that PipeWire is configured as expected. Software listed as tested in the blog post (such as Firefox) works for me.
I opened Audacious 3.10.1 to play back some audio files. I used a 16 bit uncompressed WAV file for this test.
When playing back through PulseAudio, the audio has frequent dropouts and does not play back smoothly. I went into settings, changed the output driver from PulseAudio to ALSA, set the HW device to the PipeWire server, and tried both the Default mixer and directly setting my USB device as the HW mixer. In all ALSA tests the audio playback was smooth without noticeable dropouts.
Related to this issue, if `pavucontrol` is open when I stop playing or switch from ALSA to PulseAudio in Audacious, it pops up a modal error dialog that says "Source output callback failure: Invalid argument."
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/279
Switching to pipewire from pulseaudio causes hitch pitch echos/feedback
2021-12-30T16:38:13Z
Shaleen jain
Switching to pipewire from pulseaudio causes hitch pitch echos/feedback
Hi,
When switching to pipewire from pulseaudio by symlinking the required shared libraries, the output/input devices in gnome-control-center are reset.
On selecting a device the gnome-control-center crashes. This happens even after rest...
Hi,
When switching to pipewire from pulseaudio by symlinking the required shared libraries, the output/input devices in gnome-control-center are reset.
On selecting a device the gnome-control-center crashes. This happens even after restarting the system after the switch.
As well as normal systems sounds like charger plugged in and laptop lid being closes caused a long high pitched sound with pipewire.
System logs attached.[pipewire.log](/uploads/21ea5cbbc76c312fe10bddaa281e641c/pipewire.log)
Logs after high pitch sound [pipewire2.log](/uploads/48787bec2457427780fd519483618aa8/pipewire2.log)
OS: Arch Linux
pipewire: 0.3.10
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/280
SDL1 DOSBox crash with PipeWire
2021-12-30T16:38:13Z
Robert de Rooy
SDL1 DOSBox crash with PipeWire
Trying to start dosbox (from Fedora 32 repo) results in a crash.
```
$ dosbox
DOSBox version 0.74-3
Copyright 2002-2019 DOSBox Team, published under GNU GPL.
---
dosbox: ../src/pipewire/proxy.c:237: pw_proxy_destroy: Assertion `!proxy->d...
Trying to start dosbox (from Fedora 32 repo) results in a crash.
```
$ dosbox
DOSBox version 0.74-3
Copyright 2002-2019 DOSBox Team, published under GNU GPL.
---
dosbox: ../src/pipewire/proxy.c:237: pw_proxy_destroy: Assertion `!proxy->destroyed' failed.
```
Likewise, a build of dosbox-x that I did myself before, also crashes in a similar fashion.
```
$ dosbox-x
LOG: Early LOG Init complete
LOG: Logging init: beginning logging proper. This is the end of the early init logging
LOG: Logging: No logfile was given. All further logging will be discarded.
LOG: DOSBox-X version 0.83.5
dosbox-x: ../src/pipewire/proxy.c:237: pw_proxy_destroy: Assertion `!proxy->destroyed' failed.
Aborted
```
A SDL2 compiled build of dosbox-x fairs a bit better, but on shutdown I still get the same error.
```
dosbox-x-sdl2: ../src/pipewire/proxy.c:237: pw_proxy_destroy: Assertion `!proxy->destroyed' failed.
Aborted
```
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/281
Pulseaudio volume change not synchronized with pavucontrol and vice-versa
2021-12-30T16:38:13Z
Xakep_SDK
Pulseaudio volume change not synchronized with pavucontrol and vice-versa
1. Open pavucontrol-qt
2. Change volume using media keys or system widget
3. No volume changed in pavucontrol-qt
Same when you change in pavucontrol, widget is not updated.
pipewire 0.3.10-1
pipewire-pulse 0.3.10-1
pavucontrol-qt...
1. Open pavucontrol-qt
2. Change volume using media keys or system widget
3. No volume changed in pavucontrol-qt
Same when you change in pavucontrol, widget is not updated.
pipewire 0.3.10-1
pipewire-pulse 0.3.10-1
pavucontrol-qt 0.15.0
plasma 5.19.5
kde frameworks 5.73.0
qt 5.15.0
kde applications 20.08.1
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/282
Switching back from pipewire to pulseaudio breaks PA
2021-12-30T16:38:13Z
Mie Louk
Switching back from pipewire to pulseaudio breaks PA
I [tested](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/278#note_617718) pipewire for a bit and found it to be too unstable for my daily usage. (Though I want to test it further in the future)
When switching back via [these...
I [tested](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/278#note_617718) pipewire for a bit and found it to be too unstable for my daily usage. (Though I want to test it further in the future)
When switching back via [these lines](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/278#note_617718) PA was broken after a reboot, with the error message that the just deleted file was missing. Reinstallation of PA fixed the issue but the commands should be adjusted.