Ah, people don't have that? I have systemd units and udev rules that let you run espeakup system-wide at boot, including logging in as root in a TTY and with GUI support. On Sat, Aug 17, 2024 at 05:18:53PM -0400, Kirk Reiser wrote: > That is probably a good idea if you are lucky enough to be on a system > which actually starts speakup on boot up with the systemd service > files. On one of my systems that actually works but on my other > systems they don't come up talking. I have a speakup-start script > which sets all the appropriate files to userland permissions and runs > espeakup in userspace. > > I've noticed there have been a number of folks that have also > complained of espeakup not starting correctly on boot. > > I will also post that script if anyone wishes but if you have a system > which does work as planned then definitely do it as jookia suggests. > > Kirk > > On Sun, 18 Aug 2024, Jookia wrote: > > > On systemd system you should use > > > > systemctl restart espeakup > > > > or > > > > systemctl kill --signal=9 espeakup > > systemctl restart espeakup > > > > This will ensure the service manager knows what's happening. > > > > On Sat, Aug 17, 2024 at 04:46:34PM -0400, Kirk Reiser wrote: > > > Okay, try this it's basically a one liner. The reason you can't > > > restart espeakup is because it doesn't actually die, so it has to be > > > killed off before restarting it. > > > > > > ``` > > > #!/bin/bash > > > > > > killall -9 espeakup; espeakup > > > > > > ``` > > > > > > My bash script is named respeakup but you can name it anything you like, of course. > > > > > > Kirk > > > > > > On Sat, 17 Aug 2024, Jude DaShiell wrote: > > > > > > > It's entirely possible espeakup is crashing. When this happens, I can't > > > > restart espeakup either so end up having to reboot to regain control of > > > > the system. > > > > > > > > > > > > -- > > > > Jude <jdashiel at panix dot com> > > > > "There are four boxes to be used in defense of liberty: > > > > soap, ballot, jury, and ammo. > > > > Please use in that order." > > > > Ed Howdershelt 1940. > > > > > > > > On Sat, 17 Aug 2024, Kirk Reiser wrote: > > > > > > > > > Hi Jude: This may be a silly question, but are you sure it's speakup > > > > > crashing? Often, espeakup dies here and so I have a simple script to > > > > > kill it off and restart espeakup. I haven''t had speakup itself hang > > > > > the system for quite a while. > > > > > > > > > > Kirk > > > > > > > > > > On Sat, 17 Aug 2024, Jude DaShiell wrote: > > > > > > > > > > > Every so often speakup crashes on my computer. > > > > > > I am running a recent version of Jenux so systemd is in use here. > > > > > > What I would like to know is a procedure once the system has been rebooted > > > > > > to locate any crash messages speakup may have left in logs. pipewire is > > > > > > running the sound system along with alsa here and there's necessary > > > > > > pulseaudio artifacts pipewire uses on the system. > > > > > > > > > > > > > > > > > > -- > > > > > > Jude <jdashiel at panix dot com> > > > > > > "There are four boxes to be used in defense of liberty: > > > > > > soap, ballot, jury, and ammo. > > > > > > Please use in that order." > > > > > > Ed Howdershelt 1940. > > > > > > > > > > > > > > > > > > > > > > > > >