public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Steve Holmes <steve@holmesgrown.com>
To: speakup@linux-speakup.org
Subject: Re: how to make settings 'stick'
Date: Fri, 26 Dec 2014 12:06:07 -0800	[thread overview]
Message-ID: <20141226200607.GA573@linlap> (raw)
In-Reply-To: <alpine.LNX.2.03.1412250314540.2173@ftml.net>

Hum, I wonder what the issue could be then. I'm also using a fully
updated arch box right now. What happens when I first boot the system
and login to a normal user account, I run speakupconf and no speakup
parameters change. When I login as root, speakupconf works fine. When
I try and update any speakup parms manually from normal user, that's
when I get a "permission denied" error. I don't need to change any
options on speakupconf, do I?

Oh, and when I mean update speakup parms, I mean echoing an
appropriate value into the /sys/accessibility/speakup/* logical files.

On Thu, Dec 25, 2014 at 03:17:23AM -0500, Chuck Hallenbeck wrote:
> Steve,
> 
> I am using kernel 3.17.6-1-arch, and do not have that difficulty. Normal
> users can use speakupconf without difficulty on this system.
> 
> HTH, and Merry Christmas,
> 
> Chuck
> 
> On Wed, 24 Dec 2014, Steve Holmes wrote:
> 
> >
> > Anyone else experiencing a problem where you can't use speakupconf as a
> > normal user? After a recent kernel update, I find that I keep getting
> > permission errors when I use a normal user to set speakup settings from
> > speakupconf. If I do it from root, the script works fine. I used to be
> > able to do this from regular users but now now.
> >
> > Any ideas?
> >
> > On 12/21/14 02:06, Rob Hudson wrote:
> > > Use the speakupconf script.
> > > It comes as part of the speakup sources, under the tools directory. Copy
> > > it to a location in your path, then set up speakup the way you like it.
> > > When you run speakupconf save as root, a directory called /etc/speakup
> > > is created. When you run it as a regular user, you get a directory
> > > called .speakup under your home directory.
> > > Once you have the settings saved, you can then load them again with
> > > speakupconf load. You can put that command in your .bashrc file so you
> > > get all your settings back upon login.
> > > ----- Original Message ----- From: "David" <BearSFO@PacBell.NET>
> > > To: <speakup@linux-speakup.org>
> > > Sent: Sunday, December 21, 2014 12:31 AM
> > > Subject: how to make settings 'stick'
> > >
> > >
> > >>
> > >> Hi there -
> > >>
> > >> Every time when I reboot my system I have to go and adjust the Speakup
> > >> settings like speech speed and volume and things like that, is there a
> > >> way to make these settings 'stick' so it will not be resetted at reboot?
> > >>
> > >> thanks.
> > >>
> > >> --David
> > >>
> > >> _______________________________________________
> > >> Speakup mailing list
> > >> Speakup@linux-speakup.org
> > >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > >>
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@linux-speakup.org
> > > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> >
> 
> -- 
> 
> Scent from my ShoePhone
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 David
 ` Rob Hudson
   ` David
   ` Steve Holmes
     ` Chuck Hallenbeck
       ` Steve Holmes [this message]
         ` Chuck Hallenbeck
         ` Doug Smith
           ` Steve Holmes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141226200607.GA573@linlap \
    --to=steve@holmesgrown.com \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).