Bug 398355

Summary:	qt.speech.tts.flite: "Failed to start audio output (error 1)"
Product:	[Applications] okular	Reporter:	Pedro <monteirotorres>
Component:	general	Assignee:	Okular developers <okular-devel>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	luigi.toscano, nate
Priority:	NOR
Version First Reported In:	1.4.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Pedro 2018-09-07 12:52:03 UTC

Trying to use the text to speech feature, Jovi installed properly the option to read is there, but it fails with this message. Can only detect it when I run from terminal to be able to see error messages.

flite: udb failed to find entry for: hh-w
flite: udb failed to find entry for: y-s
flite: udb failed to find entry for: hh-l
flite: udb failed to find entry for: w-s
flite: udb failed to find entry for: hh-l
flite: udb failed to find entry for: hh-w
using null output device, none available
qt.speech.tts.flite: "Failed to start audio output (error 1)"

Comment 1 Luigi Toscano 2018-09-07 12:54:22 UTC

For the record, Jovie is unused. Qt 5 provides a module called QtSpeech and Qt 5 applications use it. I did not configure it yet but I suspect you lack some settings for the backend used (flite).
I'm pretty sure this is not an Okular issue.

Comment 2 Nate Graham 2018-09-13 17:32:52 UTC

What version of Ubuntu are you using?

Comment 3 Andrew Crouthamel 2018-09-30 02:44:39 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-11-01 18:47:55 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!