Re: [orca-list] A question about pipewire that has already been asked




On 2/3/21 4:49 pm, Michał Zegan via orca-list wrote:
Restart pipewire by doing:
systemctl --user restart pipewire pipewire-pulse
Interestingly systemctl --user restart pipewire

is enough to solve it for me.

I'm wondering whether we might need to configure a Wireplumber policy for Orca and console-based screen readers to make everything work as desired. One of the advantages of Pipewire is that the policies (including control of the node graph) are separated from the main demon.

Also, Wireplumber is work in progress but could be interesting for Orca-related use cases.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]