--
---------- Forwarded message ----------
Date: Tue, 28 Jun 2016 23:00:55
From: Mark Peveto via Support <[email protected]>
Reply-To: Mark Peveto <[email protected]>
To: Mark Peveto <[email protected]>
Cc: Sonar support <[email protected]>
Subject: Re: [Support] epic fail on espeak research
I got espeak back in as it should be, using downgrade.
sudo downgrade espeak, and again, choosing option 3. I also went back to
/etc/pulse/default.pa, and removed the tale end of the line where it said
tsched=0
Since it didn't help, figured it didn't need to be there.
So, all's back as it was, with the exception of running espeakup-git instead of
plain espeakup.
Well, that broke my brain for sure, so I'm done for tonight. See yall in the
mornin.
Mark Peveto
Registered Linux user number 600552
Sent from sonar using alpine 2.20.13
On Tue, 28 Jun 2016, Mark Peveto wrote:
Well, i had to try it.
I went ahead and installed espeakup-git, and espeak-ng-git, hoping to perhaps
solve our problem for us, but instead I ran into these.
[southernprince@purrwurr1 ~]$ sudo espeakup
[southernprince@purrwurr1 ~]$ Assertion 'p' failed at pulse/simple.c:273,
function pa_simple_write(). Aborting.
As you can see from above, I executed sudo espeakup, and got no errors. But
when I switched over to a console and logged in, when espeakup should've
spoken, O got those errors. Next, I went back
to my terminal, and tried to at least get espeak-ng-git itself to talk to me.
It did, and witn no errors.
sudo espeak
hi
hi
hi
Again, it echoed back hi, and returned no errors, or they'd have been printed
out. Next, I switched over to my etc/pulse directory, and edited default.pa,
which my output shows. What you don't
get to see is my change to default.pa. I went down the file, until I found
load-module load-module-udev-detect, and added tshed=0 to the end of the line.
load-module load-module-udev-detect tsched=0
Then saved the file.
[southernprince@purrwurr1 ~]$ cd /etc/pulse
[southernprince@purrwurr1 pulse]$ sudo nano default.pa
[southernprince@purrwurr1 pulse]$ cd
[southernprince@purrwurr1 ~]$ sudo pkill pulseaudio
[southernprince@purrwurr1 ~]$
[southernprince@purrwurr1 ~]$ sudo espeakup
I killed pulseaudio so it'd restart with my new settings, then executed
espeakup again. Switching to a console again, I got errors, but after changing
the line in default.pa, the errirs changed
slightly.
[southernprince@purrwurr1 ~]$ ALSA lib pcm_dmix.c:1029:(snd_pcm_dmix_open)
unable to open slave
error: Device or resource busy
espeakup: pcm.c:1122: snd_pcm_drain: Assertion `pcm' failed.
[southernprince@purrwurr1 ~]$
--
I'll get up in the mornin, and remove these, putting back regular espeak. I'll
leave espeakup-git, since it was working fine. Espeakup-ng-git breaks things,
too. But hey, figured I'd try.
Mark Peveto
Registered linux user number 600552
Sent from Sonar!
_______________________________________________
Support mailing list
[email protected]
http://sonargnulinux.com/mailman/listinfo/support_sonargnulinux.com
_______________________________________________
pulseaudio-discuss mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
