Its not just the packages, although that is part of it. The main reason
Ubuntu is still favored over Debian by many end-users is ease of installation
and upkeep. I support Linux users in STEM fields. As you probably know, Linux is
huge with researchers in STEM fields. But they don't want to figure out how to
install Debian and update it. They just want their computer to work.
Personally, I run Debian. That Ubuntu automatic update system gives me the
willies. I don't want to click a button that says "Update now". But I'm not a
researcher, I'm the support staff.
aI
have been using Speakup and ORCA at the same time for about a year on
Bookworm. I have Bookworm backports active. I agree with Jason, use
Pipewire. I'm not sure why folks want to use Ubuntu any more unless they
have some very specific package that isn't on Debian you may be asking for
more trouble than it is worth.
I
know I read the Debian accessibility FAQ, but I'm not sure exactly what I did
off the top of my head.
Make
sure that pipewire-pulse is running on your system by doing "ps -ef|grep
pipewire" or something similar.
Subject: Re:
SPFUNSUPPORTED MAY BE MALICIOUS CLI Terminals with Speakup (Was howto run
speakup/orca concurrently in ubuntu)
Thanks for the clarification
about pipewire and why it is
here.
I didn't realize that
pulseaudio is fading into the
sunset as it has been around and served well
for quite a few
years.
To
remind those who have followed this thread today, the
only real problem I
am talking about is minor compared with stuff
that is supposed to work but
doesn't.
It looks like one
should be able to get speakup to work
older world of pure text-based
command-line consoles since there
are things that runa little more smoothly
there than when GUI
tools are
needed.
By the same token,
the present implimentation of speakup
with gnome also does well and all I
was hoping to do was have
both functionalities on the same
system.
Thanks for the
information that has been provided as it
is useful and I am still
interested if there is a way to do this
but at least things are about 95%
working.
Martin
"Jason
J.G. White"
<jason@xxxxxxxxxxxx>
writes:
> While we're discussing clarifications, note that Pulseaudio is
effectively
> deprecated now. Pipewire has superseded it. Also, Pipewire
includes an
> implementation of the Pulseaudio client API, so that
client applications
> designed for Pulseaudio still work normally under
Pipewire.
Thanks for the clarification about pipewire and
why it is here.
I didn't
realize that pulseaudio is fading into the
sunset as it has been around and
served well for quite a
few
years.
To remind
those who have followed this thread today, the
only real problem I am
talking about is minor compared with stuff
that is supposed to work but
doesn't.
It looks like one
should be able to get speakup to work
older world of pure text-based
command-line consoles since there
are things that runa little more smoothly
there than when GUI
tools are
needed.
By the same token,
the present implimentation of speakup
with gnome also does well and all I
was hoping to do was have
both functionalities on the same
system.
Thanks for the
information that has been provided as it
is useful and I am still
interested if there is a way to do this
but at least things are about 95%
working.
Martin
"Jason
J.G. White"
<jason@xxxxxxxxxxxx>
writes:
> While we're discussing clarifications, note that Pulseaudio is
effectively
> deprecated now. Pipewire has superseded it. Also, Pipewire
includes an
> implementation of the Pulseaudio client API, so that
client applications
> designed for Pulseaudio still work normally under
Pipewire.