[aur-general] PKGBUILD regression for espeakup
Hi, Lol well, this worked for a few days, then when I started my computer today, I'm stucking using the default voice. Nothing has changed, I have just installed updates, and nothing was mensioned on archlinux.org. Here's the output from systemctl status epseakup@en-us.service espeakup@en-us.service - Software speech output for Speakup (default voice: en-us) Loaded: loaded (/usr/lib/systemd/system/espeakup@.service; enabled) Active: failed (Result: start-limit) since Fri 2013-11-01 23:18:44 EDT; 28s ago Process: 689 ExecStart=/usr/bin/espeakup --default-voice=%i (code=exited, status=0/SUCCESS) Main PID: 690 (code=exited, status=2) Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service: main process exited, code=exited, status=2/INVALIDARGUMENT Nov 01 23:18:44 dungeon-master systemd[1]: Unit espeakup@en-us.service entered failed state. Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service holdoff time over, scheduling restart. Nov 01 23:18:44 dungeon-master systemd[1]: Stopping Software speech output for Speakup (default voice: en-us)... Nov 01 23:18:44 dungeon-master systemd[1]: Starting Software speech output for Speakup (default voice: en-us)... Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service start request repeated too quickly, refusing to start. Nov 01 23:18:44 dungeon-master systemd[1]: Failed to start Software speech output for Speakup (default voice: en-us). Nov 01 23:18:44 dungeon-master systemd[1]: Unit espeakup@en-us.service entered failed state. Of course it is wrong about speech not starting, or I wouldn't be able to write this. But, does anyone have any idea what has gone wrong? Thanks Storm -- -- Registered Linux user number 508465: https://linuxcounter.net/user/508465.html My blog, Thoughts of a Dragon: http://www.stormdragon.us/ My last.fm profile: http://www.last.fm/user/stormdragon2976 "No life anymore only darkness and pain, shape of shadow no flesh nor blood. All passions now gone no reason to be, cursed by the Lord of the Rings." Battlelore - The Curse of the Kings
Storm Dragon wrote:
Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service: main process exited, code=exited, status=2/INVALIDARGUMENT Nov 01 23:18:44 dungeon-master systemd[1]: Unit espeakup@en-us.service entered failed state. Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service holdoff time over, scheduling restart. Nov 01 23:18:44 dungeon-master systemd[1]: Stopping Software speech output for Speakup (default voice: en-us)... Nov 01 23:18:44 dungeon-master systemd[1]: Starting Software speech output for Speakup (default voice: en-us)... Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service start request repeated too quickly, refusing to start. Nov 01 23:18:44 dungeon-master systemd[1]: Failed to start Software speech output for Speakup (default voice: en-us). Nov 01 23:18:44 dungeon-master systemd[1]: Unit espeakup@en-us.service entered failed state.
You can include "RestartSec=15" in the "[Service]" section of the service file to work around the "request repeated too quickly" error. To correctly resolve this you will need to determine why it is exiting and adjust accordingly, e.g. by adding dependency and ordering entries to the service file (e.g. "After=..." in the "[Unit]" section). Regards, Xyne
Hi, I tried SetSec and was still getting problems. So, it got me wondering how it could still be starting with the British English voice... After a lot of searching, changing settings, and more than a little cussing (lol), I figured out there was 2 symlinks to espeakup@.service. One was the correct en-us call, but apparently the other was from when I was using uppercase %I. The link file was something like espeakup@en\x... So, I removed that, had to do it manually cause systemctl wouldn't touch it, and now everything is great again. Thanks for the help Storm On Sat, Nov 02, 2013 at 07:09:24PM +0000, Xyne wrote:
Storm Dragon wrote:
Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service: main process exited, code=exited, status=2/INVALIDARGUMENT Nov 01 23:18:44 dungeon-master systemd[1]: Unit espeakup@en-us.service entered failed state. Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service holdoff time over, scheduling restart. Nov 01 23:18:44 dungeon-master systemd[1]: Stopping Software speech output for Speakup (default voice: en-us)... Nov 01 23:18:44 dungeon-master systemd[1]: Starting Software speech output for Speakup (default voice: en-us)... Nov 01 23:18:44 dungeon-master systemd[1]: espeakup@en-us.service start request repeated too quickly, refusing to start. Nov 01 23:18:44 dungeon-master systemd[1]: Failed to start Software speech output for Speakup (default voice: en-us). Nov 01 23:18:44 dungeon-master systemd[1]: Unit espeakup@en-us.service entered failed state.
You can include "RestartSec=15" in the "[Service]" section of the service file to work around the "request repeated too quickly" error.
To correctly resolve this you will need to determine why it is exiting and adjust accordingly, e.g. by adding dependency and ordering entries to the service file (e.g. "After=..." in the "[Unit]" section).
Regards, Xyne
-- -- Registered Linux user number 508465: https://linuxcounter.net/user/508465.html My blog, Thoughts of a Dragon: http://www.stormdragon.us/ Get paid to read email: http://is.gd/feRiB "I dole out justice with the tip of my boot. It's got a logic that you just can't refute." Moxy Fruvous - Kick in the Ass
Storm Dragon wrote:
Hi, I tried SetSec and was still getting problems. So, it got me wondering how it could still be starting with the British English voice... After a lot of searching, changing settings, and more than a little cussing (lol), I figured out there was 2 symlinks to espeakup@.service. One was the correct en-us call, but apparently the other was from when I was using uppercase %I. The link file was something like espeakup@en\x... So, I removed that, had to do it manually cause systemctl wouldn't touch it, and now everything is great again. Thanks for the help Storm
I'm glad that you've got it working now. Your next challenge is to stop top-posting on this list before you get pulled into a back alley and beaten with broken broom handles. ;)
Hi, Top posting is the wave of the future. It's best to have the important stuff right at the top. :) Storm On Sun, Nov 03, 2013 at 11:48:15PM +0000, Xyne wrote:
Storm Dragon wrote:
Hi, I tried SetSec and was still getting problems. So, it got me wondering how it could still be starting with the British English voice... After a lot of searching, changing settings, and more than a little cussing (lol), I figured out there was 2 symlinks to espeakup@.service. One was the correct en-us call, but apparently the other was from when I was using uppercase %I. The link file was something like espeakup@en\x... So, I removed that, had to do it manually cause systemctl wouldn't touch it, and now everything is great again. Thanks for the help Storm
I'm glad that you've got it working now. Your next challenge is to stop top-posting on this list before you get pulled into a back alley and beaten with broken broom handles. ;)
-- -- Registered Linux user number 508465: https://linuxcounter.net/user/508465.html My blog, Thoughts of a Dragon: http://www.stormdragon.us/ Need a safe and easy way to backup and share files? Try Dropbox: http://db.tt/jeY50HR "Mighty Elric, Mightier Sword. Sorcerer and Swordsman, slayer of kin, Lord of a dying race. King of ruin, dragon master, Champion of Doom." Domine - Chronicles of the Black Sword
Because it messes up the natural reading order and prevents you from following the context.
Why is top posting bad?
cheers! mar77i
participants (3)
-
Martti Kühne
-
Storm Dragon
-
Xyne