[pulseaudio-discuss] [Support] TJ's console speech question (fwd)

Jude DaShiell jdashiel at panix.com
Mon Sep 5 03:21:40 UTC 2016


---------- Forwarded message ----------
Date: Sun, 4 Sep 2016 20:43:41
From: kendell clark via Support <support at sonargnulinux.com>
Reply-To: kendell clark <coffeekingms at gmail.com>
To: support at sonargnulinux.com
Subject: Re: [Support] TJ's console speech question

It will if you copy it into the skeleton folder. I have no idea why it's
called that but if you copy that pulse file into /etc/skel, any new user
that gets created gets those files copied to their home folder. You'll
probably want to create the folder hierarchy, so you'd want to create
/etc/skel/.config/pulse, then put the file in there. To do that, in a
terminal execute sudo mkdir -p /etc/skel/.config/pulse. The "-p" option
creates multiple levels of folders at a time. Then in that same terminal
type sudo cp ~/.config/pulse/default.pa /etc/skel/.config/pulse. You can
do this via the graphical file manager but this is a little faster,
since the file manager is just going to say "oops, you don't have
permission to copy to this folder". The sudo command runs one command as
root. So when you typed sudo cp, you're copying that file as root which
can do anything so isn't denied access. The reason you're denied access
is because that's a system wide folder, so will affect everyone on the
system so security permissions are very tight. There's no "user account
control" prompt in linux, at least not exactly. There are password
prompts when you run a program that needs root privilages on your
desktop though.
Kendell Clark

Tj via Support wrote:
> Hi there,
> First of all, thanks so much.  I never would have, in a million years,
> figured that out on my own!
> Anyhow, that leads me to having one more question.
> Let's say I create another user -- for the fiance, for example, and
> she logs in.  Since I have removed the pulse configuration and
> replaced it with my own configuration, will pulse work for her, or,
> will I have to place this new configuration in her account as well?
> If I have to manually do this, is there some way to include it in all
> future accounts I make on the system?
> Speaking of sonar versions, I believe I have fixed my "can't update,"
> issue.  I downloaded 2016.03 from the blog.  When looking at the sonar
> site, I realised it's up to .07.  Oops.  ANyhow, I've installed that,
> and have, thus far, gotten farther in my update process.  IT's
> downloading extremely slowly, but, it's downloading, so that's farther
> than I've gotten before!
> Thanks so much for your help.  I'll get the hang of this sooner or
> later, and be educated on where to go to find answers.  For
> accessibility stuff, it's a difficult journey to find what I need.
> Google doesn't help there too incredibly much, but, that's all right.
> I will prevale!  :).
> A final time, thanks!
> Tj
> On 09/04/2016 06:00 PM, kendell clark via Support wrote:
>> hi all
>> TJ, I'm sorry to read about your frustrations with console speech. I've
>> been trying to solve it for months and kept running up against one
>> constant issue. We use a sound server called pulse audio. In plain
>> english, this means that applications connect to pulse audio to get
>> sound when they need it instead of talking to your hardware. This makes
>> coding them a lot easier apparently since pulse audio takes care of the
>> hardware bits. But there is one very serious problem, that was
>> apparently designed into pulse audio. It runs as the user you're logged
>> in as, so probably tj for you. Speakup, being built into the linux
>> kernel, runs as root. That's the master user who has permissions over
>> every single file on the system and can do anything. It has to or it
>> couldn't get access to the screen to read it. Pulse audio denies it
>> access so it can't speak. I don't know how it does this, but it does. A
>> few weeks ago a friend of mine developed an option you can put into
>> pulse audio's config file to make it listen on a socket. this means that
>> apps running as other users can connect and pulse audio won't block
>> them. I'll attach the file instead of having you write the option out as
>> it's a bit geekish. Put this file in /home/tj/.config/pulse. You can
>> shorten this to ~/ if you want, but make sure it goes there. Before you
>> restart pulse audio, delete the system wide config file. To do this,
>> enter a terminal and type sudo rm -rf /etc/pulse.  If you forget to do
>> this you're likely to lose all sound when you restart pulse audio. I
>> customized the pulse configuration file to make it switch over to new
>> sound devices when you plug them in, like versions of windows do. This
>> option is now in the user specific config file I'm attaching and if
>> they're in both places pulse audio will fail hard. Then reinstall pulse
>> audio with sudo pacman -S pulseaudio. You will only have to do this
>> once, and this stuff won't be needed in the next version of sonar. Then
>> restart pulse audio. To do that, in a terminal, which you can get to by
>> pressing alt+control+t, type killall pulseaudio. It will start itself on
>> it's own, and speech should work. I'm putting this in the next version
>> of sonar, which is due out next month. I'm sorry there's been no alpha
>> release, I'm still working on it. The distro we're a part of, manjaro,
>> took about 90 percent of the software I put into sonar out of it until
>> they could make sure  that the desktop sonar uses was 100 percent
>> accessible (I already do that) and make sure all the keyboard shortcuts
>> and such work and don't break (that's over my head and I can't do that).
>> They will put the software back when they're done and as soon as they do
>> I'll release the alpha. I've held off because I don't want to give you
>> guys a version of sonar that's nothing more than a talking desktop with
>> no software at all not even a browser.
>> Thanks
>> Kendell Clark
>> Mark Peveto via Support wrote:
>>> Hi all,
>>> I read TJ's question about console speech earlier, and i'll do my best to get him going.
>>> TJ, this may be an involved process, but it does work, so lemme know if you haven't had any luck as of yet.
>>> Everything happens after coffee!
>>> Mark Peveto
>>> Registered Linux user number 600552
>>> Sent from talking arch using alpine 2.20.15
>>> Talking arch homepage: https://talkingarch.tk
>>> Latest version of alpine: git clone http://repo.or.cz/alpine.git
>>> _______________________________________________
>>> Support mailing list
>>> Support at sonargnulinux.com
>>> http://sonargnulinux.com/mailman/listinfo/support_sonargnulinux.com
>> _______________________________________________
>> Support mailing list
>> Support at sonargnulinux.com
>> http://sonargnulinux.com/mailman/listinfo/support_sonargnulinux.com
> _______________________________________________
> Support mailing list
> Support at sonargnulinux.com
> http://sonargnulinux.com/mailman/listinfo/support_sonargnulinux.com

Support mailing list
Support at sonargnulinux.com

More information about the pulseaudio-discuss mailing list