changing voices fails for wakeup-settings 1.2-0ubuntu1

[ssducf]

I installed more festival voices with apt-get install and they showed up in the preferences pane for wakeup-settings,
but when I select a voice, it does not change what is played.

To repeat:

1) Install a number of voices, for example
  apt-get install festvox-en1 festvox-us1 festvox-us2 festvox-us3
2) run wakeup settings, choose a good test string, select preferences, select a voice
3) click play
4) choose a different voice, and click play

Results:
The same default voice is played no matter what voice is selected.

Expected:
When the voice is changed, a different voice should be played, or at least one similar to what festival itself plays when the voice is selected in festival.

Version: Ubuntu 12.04, wakeup 1.2-0ubuntu1

[newbuntu (dsglass)]

I could only confirm this for voices that provide the same description, e.g., those provided by festvox-us1 and festvox-us2. Let me know if the attached patch fixes the issue (apply by running `sudo patch /usr/bin/wakeup-settings wakeup-settings031914.patch`).

[ssducf (ssd-ubu)]

Tried the patch. It let me change the voice once.
After that, any attempts to change the voice had no effect.
I tried purging ~/.wakeup/ and killing the festival server it left
running, but no effect.

[newbuntu (dsglass)]

Can you give the output when running wakeup-settings at command line and following the steps you outlined in the bug description?

[ssducf (ssd-ubu)]

Ok, I've played with this and tried every voice on my system.
I think some of the voices are buggy in that either they either don't play as intended, or the description is wrong, which confused me into thinking the voice wasn't changing at all the first time I tested.

I think what is really happening is that wakeup-settings tries to kill festival after playing a test, but fails.
So if I change the voice preference and then click play again, it is still using the old voice with the old festival process.
But if I run "pkill fest" between changing the voice and clicking play, it does change the voice.

Attached is output.

[newbuntu (dsglass)]

Interesting, could you find out which festival component does not get killed when the alarm is stopped? (I do not see this problem on my end) Try running `pgrep -a fest` before and after clicking play and after stopping the alarm.

[ssducf (ssd-ubu)]

Intersting...my pgrep doesn't have a -a option, where'd that come from?

$ pkill fest
$ wakeup ssd 0
[...]
/usr/bin/wakeup: line 43: kill: (17365) - No such process
/usr/bin/wakeup: line 43: kill: (17381) - No such process
$ ps -ef|grep fest
ssd 17314 9273 0 07:34 pts/9 00:00:00 festival --server (voice_us1_mbrola)
ssd 17359 17314 0 07:34 pts/9 00:00:00 [festival] <defunct>

I find the gap in pid's interesting. Like, maybe festival is daemonizing and preventing wakeup from tracking its pid.

[newbuntu (dsglass)]

Ah, this looks familiar; I just realized (despite the fact that it's so bluntly put in the bug description) that you are running version 1.2. Can you try installing version 1.4? I think this might have been fixed since then. Also, just to be on the same page, what version of festival do you have? (`festival --version`)?