alsa pcm plugin connects twice, causing harmless, but annoying, error messages
The alsa pcm plugin seems to connect twice to pipewire. Initially in the open
function, and later again in the prepare
, destroying the old connection before re-connecting.
Sometimes, this causes annoying warnings in WirePlumber, who tries to bind to all pw_client proxies by default. When dealing with alsa clients, the pw_client is often destroyed after we have called pw_registry_bind()
and before this call finishes, causing these warnings in the log:
10:55:37.142690 DEBUG wp-registry ../lib/wp/object-manager.c:971:registry_global: <WpCore:0x558f4347d080> global:177 perm:0x1c0 type:PipeWire:Interface:Client/3 -> WpClient
10:55:37.142703 DEBUG wp-registry ../lib/wp/object-manager.c:1195:wp_registry_prepare_new_global: <WpCore:0x558f4347d080> new WpGlobal:177 type:WpClient proxy:(nil)
10:55:37.142721 DEBUG wp-core ../lib/wp/core.c:645:wp_core_sync: <WpCore:0x558f4347d080> sync, seq 0x4000016c, task <GTask:0x558f43547000>
10:55:37.142767 DEBUG wp-core ../lib/wp/core.c:154:core_done: <WpCore:0x558f4347d080> done, seq 0x4000016c, task <GTask:0x558f43547000>
10:55:37.142776 DEBUG wp-registry ../lib/wp/object-manager.c:1128:expose_tmp_globals: <WpCore:0x558f4347d080> exposing 1 new globals
10:55:37.142795 DEBUG pw ../src/pipewire/proxy.c:112:pw_proxy_new: proxy 0x558f43613640: new 156 type PipeWire:Interface:Client/3 core-proxy:0x558f43502b90, marshal:0x7ff865dc4760
10:55:37.142806 DEBUG wp-proxy ../lib/wp/proxy.c:545:wp_proxy_set_feature_ready: <WpClient:0x558f4359a960> features changed: WP_PROXY_FEATURE_PW_PROXY
10:55:37.142828 DEBUG wp-registry ../lib/wp/object-manager.c:1003:registry_global_remove: <WpCore:0x558f4347d080> global removed:177 type:WpClient
10:55:37.142839 DEBUG pw ../src/pipewire/proxy.c:233:pw_proxy_destroy: proxy 0x558f43613640: destroy id:156 removed:0 zombie:0 ref:1
10:55:37.142868 MSG wp-object-manager ../lib/wp/object-manager.c:798:on_proxy_ready: <WpObjectManager:0x558f434bf630> proxy augment failed: pipewire proxy destroyed before finishing
10:55:37.142917 WARN pw ../src/pipewire/core.c:71:core_event_error: core 0x558f43502b90: proxy 0x558f43613640 id:156: seq:365 res:-2 (No such file or directory) msg:"no global 177"
10:55:37.142924 DEBUG pw ../src/pipewire/core.c:82:core_event_remove_id: core 0x558f43502b90: object remove 156
10:55:37.142928 DEBUG pw ../src/pipewire/proxy.c:267:pw_proxy_remove: proxy 0x558f43613640: remove id:156 removed:0 destroyed:1 zombie:1 ref:1
10:55:37.142931 DEBUG pw ../src/pipewire/proxy.c:294:pw_proxy_unref: proxy 0x558f43613640: free 156
10:55:37.142935 WARN pw ../src/pipewire/core.c:71:core_event_error: core 0x558f43502b90: proxy 0x558f43502b90 id:0: seq:366 res:-22 (Invalid argument) msg:"unknown resource 156 op:7"
10:55:37.143307 DEBUG wp-registry ../lib/wp/object-manager.c:971:registry_global: <WpCore:0x558f4347d080> global:177 perm:0x1c0 type:PipeWire:Interface:Client/3 -> WpClient
and on the server side:
[E][000736009.791595][private.h:241 pw_core_resource_errorv()] resource 0x56515a5b99d0: id:156 seq:365 res:-2 (No such file or directory) msg:"no global 177"
[E][000736009.791607][private.h:241 pw_core_resource_errorv()] resource 0x56515a5b99d0: id:0 seq:366 res:-22 (Invalid argument) msg:"unknown resource 156 op:7"
This doesn't cause any issues, it's just annoying and confusing to see the warnings.