* [ISSUE] pipewire: can't load api.bluez5.enum.dbus: No such file or directory @ 2021-03-21 12:16 st3r4g 2021-04-09 10:32 ` st3r4g 2021-04-09 15:04 ` [ISSUE] [CLOSED] " ericonr 0 siblings, 2 replies; 3+ messages in thread From: st3r4g @ 2021-03-21 12:16 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1253 bytes --] New issue by st3r4g on void-packages repository https://github.com/void-linux/void-packages/issues/29655 Description: I'm opening this one because I realized our packaging is wrong wrt pipewire and bluetooth. This error should not be there. This is upstream default policy: ``` with-pulseaudio = [ with-audio bluez5 restore-stream streams-follow-default ] ``` which means: load the bluetooth plugin when pulseaudio functionality is installed, and we install pulseaudio functionality by default. Two possibilities: 1) Stay with upstream policy and add `libspa-bluetooth` to `depends`. This however adds unwanted dependencies for users not using bluetooth. 2) Change the policy (it should be fine as a distro) into: ``` with-bluetooth = [ bluez5 ] with-pulseaudio = [ with-audio restore-stream streams-follow-default ] ``` And provide an additional package `pipewire-bluetooth` that install the bluetooth plugin and the `with-bluetooth` file. I could try to propose this policy to upstream, if it's a good idea. [3) For now, simply wait for configuration to stabilize, since things could change?] Related: #29570 cc @ericonr ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: pipewire: can't load api.bluez5.enum.dbus: No such file or directory 2021-03-21 12:16 [ISSUE] pipewire: can't load api.bluez5.enum.dbus: No such file or directory st3r4g @ 2021-04-09 10:32 ` st3r4g 2021-04-09 15:04 ` [ISSUE] [CLOSED] " ericonr 1 sibling, 0 replies; 3+ messages in thread From: st3r4g @ 2021-04-09 10:32 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 240 bytes --] New comment by st3r4g on void-packages repository https://github.com/void-linux/void-packages/issues/29655#issuecomment-816589097 Comment: upstream decreased the log priority of the message, so it's not to be considered an error anymore. ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ISSUE] [CLOSED] pipewire: can't load api.bluez5.enum.dbus: No such file or directory 2021-03-21 12:16 [ISSUE] pipewire: can't load api.bluez5.enum.dbus: No such file or directory st3r4g 2021-04-09 10:32 ` st3r4g @ 2021-04-09 15:04 ` ericonr 1 sibling, 0 replies; 3+ messages in thread From: ericonr @ 2021-04-09 15:04 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1216 bytes --] Closed issue by st3r4g on void-packages repository https://github.com/void-linux/void-packages/issues/29655 Description: I'm opening this one because I realized our packaging is wrong wrt pipewire and bluetooth. This error should not be there. This is upstream default policy: ``` with-pulseaudio = [ with-audio bluez5 restore-stream streams-follow-default ] ``` which means: load the bluetooth plugin when pulseaudio functionality is installed, and we install pulseaudio functionality by default. Two possibilities: 1) Stay with upstream policy and add `libspa-bluetooth` to `depends`. This however adds unwanted dependencies for users not using bluetooth. And there is no going back once you do this. 2) Change the policy (it should be fine as a distro) into: ``` with-bluetooth = [ bluez5 ] with-pulseaudio = [ with-audio restore-stream streams-follow-default ] ``` And ship the `with-bluetooth` file in `libspa-bluetooth`. This looks nicer to me, in theory. [Third option: For now, simply wait for configuration to stabilize, since things could change?] Related: #29570 cc @ericonr ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2021-04-09 15:05 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-03-21 12:16 [ISSUE] pipewire: can't load api.bluez5.enum.dbus: No such file or directory st3r4g 2021-04-09 10:32 ` st3r4g 2021-04-09 15:04 ` [ISSUE] [CLOSED] " ericonr
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).