* Espeakup, arch and systemd
@ Adrian Orjales
` Alexander Epaneshnikov
0 siblings, 1 reply; 6+ messages in thread
From: Adrian Orjales @ UTC (permalink / raw)
To: speakup
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
Hello all
I am trying to build my own OS based on Arch Linux, but I am having some
problems with the screen reader.
I have an arch linux fresh installation, with systemd, espeakup and
espeak-ng installed with pacman.
After installing the espeakup package, I noticed that the system was very
slow on boot, and some times espeakup did not wake up after boot.
After some research, I've discovered that the cause of the slow boot was
that the systemd espeakup service unit uses systemd-udev-settle.service and
waits for it to end to start, to ensure all hardware is discovered.
But as I've read, this operation is very discouraged because the
udev-settle discover process is asynchronous and it slows down the boot
process.
Furthermore, when this service ends, espeakup has the same problem,
sometimes it talks, sometimes it is not able to talk.
The problem of no speech is solved if I run systemctl reload espeakup &&
systemctl start espeakup manually from command line.
Now, I have tried removing the wants and requires of
systemd-udev-settle.service and left only the sound.target. The slow boot
is solved, but espeakup does not start properly, and I don't know how can I
solve this.
One of the info that I've found says that sometimes, systemd sound.target
unlocks the awaiting services when the first sound card is detected, but I
have a Nvidia gpu that is detected as a soundcard, but alsa's default card
is my onboard intel hda.
I know that this list is about speakup, not espeakup, but I'm sure that you
like me know that we are not much people talking about these topics and is
difficult to find help.
Thanks in advance
[-- Attachment #2: Type: text/html, Size: 1721 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Espeakup, arch and systemd
Espeakup, arch and systemd Adrian Orjales
@ ` Alexander Epaneshnikov
` Adrian Orjales
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Epaneshnikov @ UTC (permalink / raw)
To: Adrian Orjales; +Cc: speakup
On Sat, Apr 23, 2022 at 04:15:38PM +0200, Adrian Orjales wrote:
> Hello all
hello.
> I am trying to build my own OS based on Arch Linux, but I am having some
> problems with the screen reader.
> I have an arch linux fresh installation, with systemd, espeakup and
> espeak-ng installed with pacman.
> After installing the espeakup package, I noticed that the system was very
> slow on boot, and some times espeakup did not wake up after boot.
> After some research, I've discovered that the cause of the slow boot was
> that the systemd espeakup service unit uses systemd-udev-settle.service and
> waits for it to end to start, to ensure all hardware is discovered.
> But as I've read, this operation is very discouraged because the
> udev-settle discover process is asynchronous and it slows down the boot
> process.
to be honest, I'm not sure that the slowdown in booting is due to this.
> Furthermore, when this service ends, espeakup has the same problem,
> sometimes it talks, sometimes it is not able to talk.
> The problem of no speech is solved if I run systemctl reload espeakup &&
> systemctl start espeakup manually from command line.
did you set the default sound card?
> Now, I have tried removing the wants and requires of
> systemd-udev-settle.service and left only the sound.target. The slow boot
> is solved, but espeakup does not start properly, and I don't know how can I
> solve this.
I'm afraid it's not possible to get rid of udev-setle.target without changes in espeakup.
> One of the info that I've found says that sometimes, systemd sound.target
> unlocks the awaiting services when the first sound card is detected, but I
> have a Nvidia gpu that is detected as a soundcard, but alsa's default card
> is my onboard intel hda.
> I know that this list is about speakup, not espeakup, but I'm sure that you
> like me know that we are not much people talking about these topics and is
> difficult to find help.
> Thanks in advance
--
Sincerely, Alexander
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Espeakup, arch and systemd
` Alexander Epaneshnikov
@ ` Adrian Orjales
` Adri Orjales
0 siblings, 1 reply; 6+ messages in thread
From: Adrian Orjales @ UTC (permalink / raw)
To: Alexander Epaneshnikov; +Cc: speakup
[-- Attachment #1: Type: text/plain, Size: 528 bytes --]
Thanks for your reply, Alexander
> >to be honest, I'm not sure that the slowdown in booting is due to this.
>
After I've removed the systemd-udev-settle.service mentions on the
espeakup.service file, the slowdown was removed, I don't know why.
> > did you set the default sound card?
>
I have no idea about alsa settings, but if I run aplay -L, it shows that
the intel card is set as default. If it was not running with this card,
when I run systemctl reloadand start, espeakup must not talk, but it does.
Thanks again.
>
[-- Attachment #2: Type: text/html, Size: 1081 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Espeakup, arch and systemd
` Adrian Orjales
@ ` Adri Orjales
` Alexander Epaneshnikov
0 siblings, 1 reply; 6+ messages in thread
From: Adri Orjales @ UTC (permalink / raw)
To: Alexander Epaneshnikov; +Cc: speakup
[-- Attachment #1: Type: text/plain, Size: 884 bytes --]
Hello again
I reset the udev-settle service, i've found the problem with the slowdown on boot, was caused by a wireless mouse receiber
Now the espeakup problem persists
Only talks if i stop it and start it again
> El 23 abr 2022, a las 16:55, Adrian Orjales <adriorjalesvidal31@gmail.com> escribió:
>
>
> Thanks for your reply, Alexander
>
>
>>
>> >to be honest, I'm not sure that the slowdown in booting is due to this.
> After I've removed the systemd-udev-settle.service mentions on the espeakup.service file, the slowdown was removed, I don't know why.
>
>>
>> > did you set the default sound card?
> I have no idea about alsa settings, but if I run aplay -L, it shows that the intel card is set as default. If it was not running with this card, when I run systemctl reloadand start, espeakup must not talk, but it does.
>
>> Thanks again.
[-- Attachment #2: Type: text/html, Size: 1693 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Espeakup, arch and systemd
` Adri Orjales
@ ` Alexander Epaneshnikov
` Adrian Orjales
0 siblings, 1 reply; 6+ messages in thread
From: Alexander Epaneshnikov @ UTC (permalink / raw)
To: Adri Orjales; +Cc: speakup
On Sat, Apr 23, 2022 at 05:18:56PM +0200, Adri Orjales wrote:
> Hello again
> I reset the udev-settle service, i've found the problem with the slowdown on boot, was caused by a wireless mouse receiber
nice.
> Now the espeakup problem persists
> Only talks if i stop it and start it again
ok. let's tri to set default sound card with arch wiki's instructions [1]
[1] https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture#Set_the_default_sound_card
--
Sincerely, Alexander
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Espeakup, arch and systemd
` Alexander Epaneshnikov
@ ` Adrian Orjales
0 siblings, 0 replies; 6+ messages in thread
From: Adrian Orjales @ UTC (permalink / raw)
To: Alexander Epaneshnikov; +Cc: speakup
[-- Attachment #1: Type: text/plain, Size: 1524 bytes --]
I have set the default sound card, and still facing same issue.
At boot, espeakup is not able to speak. Only when I stop it's service and
start again it works.
Here is my espeakup.service file
[Unit]
Description=Software speech output for Speakup
Documentation=man:espeakup(8)
Wants=systemd-udev-settle.service
After=systemd-udev-settle.service sound.target
[Service]
Type=forking
PIDFile=/run/espeakup.pid
Environment="default_voice="
ExecStartPre=+modprobe speakup_soft
ExecStart=/usr/bin/espeakup --default-voice=${default_voice}
ExecReload=kill -HUP $MAINPID
Restart=always
[Install]
WantedBy=sound.target
I noticed that when I boot the machine and login into a shell, there is no
sound. If I run a speaker-test it doesn't work, because of espeakup. When I
kill espeakup service, it works again, and if I run a speaker-test, it
works perfectly fine.
El sáb, 23 abr 2022 a las 17:26, Alexander Epaneshnikov (<
aarnaarn2@gmail.com>) escribió:
> On Sat, Apr 23, 2022 at 05:18:56PM +0200, Adri Orjales wrote:
> > Hello again
> > I reset the udev-settle service, i've found the problem with the
> slowdown on boot, was caused by a wireless mouse receiber
>
> nice.
>
> > Now the espeakup problem persists
> > Only talks if i stop it and start it again
>
> ok. let's tri to set default sound card with arch wiki's instructions [1]
>
> [1]
> https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture#Set_the_default_sound_card
>
> --
> Sincerely, Alexander
>
[-- Attachment #2: Type: text/html, Size: 2125 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Espeakup, arch and systemd Adrian Orjales
` Alexander Epaneshnikov
` Adrian Orjales
` Adri Orjales
` Alexander Epaneshnikov
` Adrian Orjales
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).