Re: [orca-list] Accessibility broken under Wayland Fedora 31

[Didier Spaier <didier slint fr>]

Hi,

as I answered to Halim, this issue can be resolved with proper settings,
so I disagree with this sentence:
> This is not a new issue but unresolved since pulseaudio exists.
Or if you mean that it's not unresolved with Debian default settings,
then as I wrote in my previous answer this issue should be raised with
its audio team (which Samuel already pointed out months ago).


About PulseAudio going away, don't hold your breath: it won't ever
replace Jack, but is good enough for its target use cases.

I never heard about Pirewire and an internet search came empty. Could
you please provide so pointers?

Best,

Didier

Le 10/11/2019 à 19:35, Jason White via orca-list a écrit :
> Halim Sahin <halim sahin t-online de> wrote:
>   
> > May be he means that a running orca which would use pulseaudio by
> > default blocks the audio device.
> > Then you can't play sound using your console screenreader which runs
> > with a dierent useraccount.
>
> That is indeed one of the problems. A second problem (probably a manifestation
> of the same issue) is that if you connect a USB audio device (e.g.,
> headphones), audio from the console screen reader won't be redirected to it.
>
> > This is not a new issue but unresolved since pulseaudio exists.
>
> And it all works fine in every other non-Linux operating system that I've
> tested.
>
> The question is whether Pipewire offers a good opportunity to address these
> long-standing issues. PulseAudio is going away, and Pipewire appears to have
> substantially more features.