Re: Speech-dispatcher problem

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

 



[Didier]

Thank you.

You wrote:

> let's find under which user orca was started, maybe not you.
> 
> This command should tell you that:
> id -nu 500
That's me. My system is installed many, many years ago and just upgraded.

> I assume that you own numeric is at least 1000, check with:
> id -u

It's me.

My problem may have to do with PipWire/Wireplumber. But I'm not able to debug the issue and find why the audio device cannot be opened.

Lars

> Le 05/01/2023 à 22:34, Linux for blind general discussion a écrit :
> > Lars here.
> > 
> > After upgrading from Fedora 35 to 36, I have no speech in X. Nor does
> > spd-say hello says nothing. Pulseaudio is running as system daemon.
> > When redirecting logs to stdout, I get Error: Can't connect to unix
> > socket /run/user/500/speech-dispatcher/speechd.sock, connection refused.
> > 
> > Starting the speech-dispathcer server manually gives:
> > 
> > Error: Module reported error in request from speechd (code 3xx):
> > 300-Opening sound device failed. Reason: Cannot open plugin server.
> > error: file not found.
> > 
> > What does that mean, and how do I fix it?
> > 
> > Thanks in advance
> > Lars
> 
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@xxxxxxxxxx
> https://listman.redhat.com/mailman/listinfo/blinux-list

_______________________________________________
Blinux-list mailing list
Blinux-list@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/blinux-list




[Index of Archives]     [Linux Speakup]     [Fedora]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]