From: Storm Dragon <stormdragon2976@gmail.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: speakupconf load and save not working
Date: Fri, 23 Jan 2015 13:26:37 -0500 [thread overview]
Message-ID: <20150123182637.GD5024@asgard> (raw)
Hi,
I think maybe permissions got changed in one of the later kernels or something. Speakupconf load and save no longer work as expected. when doing speakup conf load, lines 79 and 93 (I think) say too man arguments. In the .speakup directory there are no files like there used to be.
I tried a chmod -R 666 /sys/accessibility/speakup
but that didn't help. Is there an easy fix for this?
thanks
Storm
--
Powered by Arch Linux! I am registered Linux user number 508465: https://linuxcounter.net/user/508465.html
My blog, Thoughts of a Dragon: http://www.stormdragon.tk/
get my public PGP key: gpg --keyserver wwwkeys.pgp.net --recv-key 43DDC193
My Blackberry is Broken: http://is.gd/my_blackberry_is_broken
"Brains for dinner, brains for lunch, brains for breakfast, brains for brunch. Brains at every single meal, why can't we have some guts?"
The Misfits - Braineaters
next reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Storm Dragon [this message]
` Chris Brannon
` Storm Dragon
` Storm Dragon
` Chris Brannon
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=20150123182637.GD5024@asgard \
--to=stormdragon2976@gmail.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).