* Too much of a Good Thing is Solved.
@ martin McCormick
` Rob
` Janina Sajka
0 siblings, 2 replies; 3+ messages in thread
From: martin McCormick @ UTC (permalink / raw)
To: Speakup is a screen review system for Linux.
I thought I knew too much. The proper systemd way to make
speakup stop is
sudo systemctl stop espeakup
and it stops. Starting it is the same command except one uses
start and it restarts as if nothing ever happened. I was trying
an older command that may have worked back in the day but isn't
necessary now.
Martin
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Too much of a Good Thing is Solved.
Too much of a Good Thing is Solved martin McCormick
@ ` Rob
` Janina Sajka
1 sibling, 0 replies; 3+ messages in thread
From: Rob @ UTC (permalink / raw)
To: Martin McCormick, Speakup is a screen review system for Linux.
martin McCormick <martin.m@suddenlink.net> wrote:
> I thought I knew too much. The proper systemd way to make
> speakup stop is
> sudo systemctl stop espeakup
> and it stops. Starting it is the same command except one uses
> start and it restarts as if nothing ever happened. I was trying
> an older command that may have worked back in the day but isn't
> necessary now.
>
> Martin
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
Or you could have just hit speakup+numpad enter, or the print screen key.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Too much of a Good Thing is Solved.
Too much of a Good Thing is Solved martin McCormick
` Rob
@ ` Janina Sajka
1 sibling, 0 replies; 3+ messages in thread
From: Janina Sajka @ UTC (permalink / raw)
To: speakup
Hi, Martin:
What you describe below is today's way, afaik. There's just one thing to
add, imo ...
Should you ever find yourself needing to give root password for system
maintanance, you can still do:
mod probe speakup_soft
espeakup
Sooner or later, one is likely to need that level of access! <grin> When
this happens, I have found it best to reboot after performing system
maintanance, rather than proceed booting via Ctrl-D, as the audio
environment isn't necessarily properly configured. Just my experience.
I would also add that I'm still solidly an alsa user for my machine with
multiple sound cards. I'm perfectly happy to have pa anywhere, as long
as I can control the situation with alsa. My fundamental problem with pa
seems to be it's lack of any concept of managing at the sound card
level. I'm very much about routing various specific audio outputs to
specific cards, so that's a deal breaker for me.
Janina
martin McCormick writes:
> I thought I knew too much. The proper systemd way to make
> speakup stop is
> sudo systemctl stop espeakup
> and it stops. Starting it is the same command except one uses
> start and it restarts as if nothing ever happened. I was trying
> an older command that may have worked back in the day but isn't
> necessary now.
>
> Martin
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
--
Janina Sajka
Linux Foundation Fellow
Executive Chair, Accessibility Workgroup: http://a11y.org
The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair, Accessible Platform Architectures http://www.w3.org/wai/apa
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Too much of a Good Thing is Solved martin McCormick
` Rob
` Janina Sajka
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).